Capture with a reason
Back-in-stock and price-drop alerts, saved searches, newsletter sign-up and team follow-ups all collect contact details in context.
Use case · Lead capture
Capture leads in the conversation.
Zubby asks for contact details when they help the shopper, for an alert, saved search or follow-up, and records consent for supported segments and connected email tools. Journeys need their own supported source trigger; lead.created is not a journey trigger.
Plans from $49/month. Try Growth for 14 days.
Platform actions require the applicable plan, connected adapter and permissions. Order writes also require supported identity verification and confirmation. New Shopify connections are coming soon; custom stores do not inherit native cart actions from API ingestion. Check platform action limits.
Included in every plan; Klaviyo and Mailchimp sync need your own accounts.
What it does
Conversational lead capture asks for an email at a relevant moment, explains why, and records the answer. Because the request is tied to what the shopper wants, such as an alert when their size is back, it feels like service rather than an interruption.
Keep fields to a minimum, never pre-tick consent, and separate service messages from marketing.
Capabilities
What you get
Consent recorded
Each lead keeps the shopper’s choice, and unsubscribes and suppression lists are honored in every send.
Segments and journeys
Leads join your shopper list with their interests, ready for supported segments. Growth journeys require their own supported trigger and eligibility; capture alone does not enroll them.
Sync to your email tools
Send leads to Klaviyo, including a newsletter list, or Mailchimp audiences and tags.
How to get started
Choose the reasons
Decide which alerts or follow-ups the agent may offer and write your consent wording.
Connect your destination
Connect Klaviyo or Mailchimp if you use them, and check that leads arrive with the right fields.
Follow up
Choose a supported source trigger, such as a confirmed back-in-stock event, for an eligible Growth journey. Review drafts before separate activation; do not assume lead capture is an enrollment event.
Good to know
- Lead capture is off by default; you choose when the agent may ask.
- Consent rules differ by country and channel, and you set the wording.
- Klaviyo and Mailchimp sync use your own accounts with those providers.
Frequently asked questions
When does the agent ask for an email?
When there is a reason the shopper will value: a back-in-stock alert, a price-drop alert, a saved search, a follow-up from your team, or a newsletter you offer. Lead capture is off until you turn it on.
How is consent handled?
The shopper's choice is recorded with the lead, unsubscribes and suppression lists are respected, and every marketing email includes an unsubscribe link. You set the consent wording for your markets.
Where do the leads go?
Into your Zubby shoppers and segments, where a journey can follow up only when a separately supported trigger and eligibility apply. Capturing a lead does not itself enroll a journey. You can also sync them to Klaviyo (including a newsletter list) or Mailchimp, and on Pro read them through the API.
Does it replace my popup?
It can sit alongside it. Chat capture works best when the request is tied to what the shopper is doing, so compare both on your own store.
Keep exploring
Try it on your store
See Zubby answer from your own catalog.
Start the 14-day Growth trial, connect your WooCommerce store, and read real shopper conversations before you open the assistant to all traffic.