Let Shoppers Ask for a Sales Call From Your Shopify Chat
Some purchases end with "can someone call me?" Sales Callback lets your Shopify chat offer a call back and take a name and phone number, under a disclosure you write, and records the number on the lead with the disclosure you configured.
A shopper has spent ten minutes asking your chat about frame sizes, or fabric options, or what a 200-unit order would look like. Then they ask: "Can someone just call me?"
That's a good moment to be ready for. Sales Callback lets the assistant offer a call back, take a name and a phone number, and get both to your team along with the disclosure you configured. This post covers what the shopper is offered, what you write, and where the number goes. Sales Callback shipped on September 22, 2026.
Why some shoppers want a call
Most questions in a store chat are answered in the chat. Sizing, shipping, compatibility, return windows: the assistant reads your catalogue and your knowledge base and replies. A few aren't like that. They're expensive, or custom, or they involve several people on the buyer's side, and the shopper wants to talk it through with someone who can make a call on price or timing.
Email works for those, but it's slow and it loses the moment. A shopper who asked for a call and got "we'll be in touch" often isn't there by the time you are. A phone number with the conversation attached gives your team a warmer start.
What the shopper is offered
When a shopper asks to speak to someone, or asks to be contacted, the assistant can offer two options: your team calls them, or they call you. The assistant is instructed to offer the callback alongside the phone number or contact page you already publish, not in place of it, so a shopper who would rather pick up the phone themselves can.
If they choose the call back, the assistant asks for their name and phone number, and it is instructed to include your disclosure in that same message. Its instructions also cover the following:
- No email required. A name and a number are enough to create the lead. If the shopper volunteers an email it travels with the lead, and the assistant is instructed not to ask for one before passing a number on.
- Ask once. If the shopper declines or ignores the offer, the assistant is instructed to keep whatever they did give and move on.
- Only the shopper's own number. The assistant is instructed to take a number only from what the shopper typed in that conversation, not from the page or anywhere else.
The disclosure you write
The disclosure is yours, up to 400 characters. Something like "We'll only use this to have a sales rep call you about your question." It tells the shopper what the number is for, and it belongs in the message that asks for the number, before they give it.
The assistant is instructed to include it word for word, without shortening, rephrasing or translating it, even when the conversation is in another language. That's a deliberate tradeoff: a translated disclosure would read more naturally, but it would not be the text you wrote.
The pairing itself is enforced in code. With the switch on and the disclosure empty, phone capture stays off and Configure says so. The assistant's capture tool then has no phone field, so it can't pass on a number, and a number that arrives anyway is dropped rather than stored.
Where the number goes
- The Leads page. The number gets its own column with a badge that says whether your disclosure was found word for word in the chat ahead of the number: "Disclosure shown", "Disclosure shown after the number" when the assistant quoted it only once the shopper had already given the number, "Not found in chat", or "Disclosure configured" when no check was recorded. Hover it to see the disclosure that was configured and the time the number was taken. Open the lead and you get a click-to-call link, the configured disclosure in full, the AI's summary of what the shopper wanted, and a link to the whole conversation in replay.
- The CSV export. Four columns: the phone number, the configured disclosure, the time the number was taken ("Consent Captured At") and whether the disclosure was found in the chat ("Disclosure Shown (Checked In Chat)", which reads "After the number" when it was quoted only afterwards). They're at the end of the file, so a spreadsheet or import that reads columns by position keeps working.
- Your lead webhook. The default payload includes the phone number, the configured disclosure and the time the number was taken, and they're there (as nulls) even when a lead has no number, so a workflow that reads them doesn't break. Custom templates can use
{{phone}},{{consentText}}and{{consentShownAt}}(the time the number was taken). A webhook into a Slack channel is the quickest way to get a call request in front of a rep. - Klaviyo. If you send leads to Klaviyo, the number becomes the profile's phone number, converted to the international format Klaviyo expects. The disclosure isn't sent to Klaviyo, and no text-message subscription is created. If a number can't be read as a phone number and the shopper also gave an email, the profile is still created without the number, so the lead isn't lost.
The other CRM connectors don't receive the number. If your team works out of one of those, the webhook is the route for call requests.
Each lead keeps the disclosure that was configured when its number was taken. Change your wording next month and older leads keep the earlier text.
Setting it up
- In your dashboard, open Configure, then Lead Capture. Lead capture itself needs to be on; it's included from the Essentials plan up.
- In the Sales Callback section, turn on Ask for a phone number.
- Write your consent disclosure. Say what the number is for and who will call.
- Decide where call requests should go: the Leads page, plus a lead webhook (Essentials and up) or Klaviyo (Core and up).
- Save, then try it on your storefront: ask the chat to have someone call you, check that your disclosure appears in the message that asks for your number, and check the lead arrives where you expect.
Worth knowing
The assistant puts your disclosure into the conversation because it's instructed to, the same way it follows the rest of your configuration. The record on the lead is the text you configured and the time the number was taken, not a reading of the transcript. To see what the assistant wrote to a particular shopper, open the conversation from the lead; it's one click.
Phone numbers are stored as the shopper typed them, and Milly Chat doesn't check that a number is real. Treat a call request the way you'd treat any inbound lead: worth a call, and the conversation tells you what to say when they pick up.
Frequently Asked Questions
Can the chat take a phone number without a disclosure?
Not through Sales Callback. It has two parts: the switch in Lead Capture and a consent disclosure you write. Until both are set, the assistant's capture tool has no phone field, so it can't pass on a number, and a number sent without them is dropped rather than stored.
Does a shopper have to give an email to request a call?
No. A name and a phone number are enough. If the shopper offers an email as well it's included with the lead, and the assistant is instructed not to ask for one in order to pass on a number they've already given.
Where does a phone number captured in chat end up?
On the Leads page, with the disclosure that was configured and the time the number was taken, and in the CSV export. It's also sent to your lead webhook, and to Klaviyo if you use it, where it becomes the profile's phone number with no text-message subscription. Other CRM connectors don't receive the number.