The question hides a second one: is money really moving through a messaging app? It is not, and that is exactly why this works. Inside WhatsApp you get the conversation and the link. The charge happens outside, on infrastructure built for charges. That distinction is the difference between an agent that books appointments and one that closes sales. An appointment is a promise. A confirmed payment is a decision.
How does it actually work?
Six things happen in order, and the order is not decorative.
First, the agent books the appointment inside the chat, against the real availability of your calendar. Second, if payment collection is enabled, it requests a payment link from the connected provider for the amount you configured, the full price or a deposit. Third, the link arrives in the conversation as a payment card with the amount visible.
Fourth, the customer taps and pays on the provider's hosted checkout. Card data is typed on the provider's page, under the provider's own security, never in the chat and never on our servers. Fifth, the provider notifies the platform through a webhook, server to server. Sixth, and only then, the system marks the payment as received, confirms the appointment, notifies the business owner by WhatsApp and email, moves the deal to Won, and fires a Purchase event to Meta through the Conversions API.
The money path, plainly: it goes from the customer's card to the business's own payment account. It does not pass through WhatsApp and it does not pass through HeySetter. Payouts land in the provider's dashboard on its usual schedule, exactly as if the customer had paid on your website. The agent's job is to put the right link in front of the right person at the right moment, and the whole sequence fits inside one conversation that started with a reply in under 30 seconds.
Charging while the intent is still warm
Most businesses collect on arrival. It feels safer and it is the habit inherited from the front desk. It is also the most expensive moment to ask, because by then the desire that produced the message has cooled for hours or days.
The speed research says the same thing about attention. The Lead Response Management Study led by Dr. James Oldroyd at MIT in 2007 found that answering within 5 minutes makes a lead 21 times more likely to qualify than answering at 30 minutes. Harvard Business Review, in its 2011 piece "The Short Life of Online Sales Leads", found that responding within the first hour makes qualification 7 times more likely than responding at 2 hours, and 60 times more likely than responding at 24 hours. Intent has a half-life, and the payment request inherits it.
This is also the honest answer to no-shows. Someone who paid a deposit has made a commitment that costs something to break. And because the appointment is only confirmed when the payment is confirmed, an unpaid slot is never quietly counted as a sale.
What happens if the customer does not pay?
Nothing gets guessed. Every payment carries a status: pending, paid or expired. The deadline is yours to configure, so a $40 consultation can carry a deadline of a few hours and a larger service a few days.
While the status is pending, the automatic follow-up sequence does its work: a message at 2 hours, a firmer one at 8 hours, and a re-engagement message at 48 hours. That last one goes out as an approved template, because it falls outside WhatsApp's 24-hour customer service window. Since July 1, 2025, Meta charges per delivered template message and does not charge for replies inside an open service window, so that third touch is the only one carrying a per-message cost.
The appointment stays pending through all of this. It never counts as won, it never fires a Purchase event, and it shows in your pipeline as pending, so you decide whether to hold the slot or offer it to somebody else. When the deadline passes, the payment moves to expired and the reason is logged. Nothing disappears silently.
Turn WhatsApp chats into paid bookings, automatically.
Start freeWhy is the provider's confirmation the source of truth?
Because "I already paid" is a claim, not a fact. Screenshots can be old, transfers bounce, and a customer can be honest and still be wrong about whether the charge went through.
HeySetter does accept manual confirmation from the chat, useful for businesses that also take transfers or cash. That is a human decision and it is recorded as one. But the automatic path only marks a payment as received when the provider's webhook says so, and a deal only moves to Won on that same signal. A pipeline built on the customer's word is a forecast. A pipeline built on webhooks is revenue.
What an AI agent cannot do inside WhatsApp
Honesty belongs here. WhatsApp is not a payment processor in most markets. Native in-chat payment features do exist in some countries and not in others, and what is available depends on your market, your type of business, and Meta's rules at the time you are reading this. Anyone who tells you there is a single universal in-chat checkout is selling you a simplification.
Meta's commerce policies also apply regardless of who writes the messages: there are categories that cannot be sold through the channel, and an AI agent is not an exception to that. Beyond policy, the hard limits. An agent cannot make a bank approve a declined card, cannot see full card data, and cannot confirm a payment that no provider confirmed.
What it can do is the part that gets skipped in practice: ask for the money at the exact moment the person is ready to give it.
Simulated example
Simulated example. Not a recording of a customer account.
Customer: Do you have anything tomorrow afternoon? Agent: Yes. Tomorrow I have 1:30 PM and 4:00 PM open. Which one works for you? Customer: 1:30. Agent: Perfect. To lock in 1:30 PM I need the $40 deposit. Here is your secure link. Payment card in the chat: Pay deposit · $40.00 · Secure checkout Customer pays on the provider's checkout page. Agent: Payment confirmed. You are booked for tomorrow at 1:30 PM, and I will remind you 24 hours before.
Behind those seven lines: a calendar write, a payment link created, a webhook received, a booking confirmed, an owner notified and a deal moved to Won.
Frequently asked questions
No. Funds move from your customer to your own Stripe or Bold account, on that provider's payout schedule. HeySetter creates the link, delivers it in the chat and listens for the confirmation. We are never in the middle of the transaction and we never hold your customers' funds.
Yes. You set the amount when you enable payment collection, so you can ask for a deposit that covers your cost of an empty slot rather than the full service price. Many businesses find a small deposit does most of the work of preventing no-shows.
Then you leave payment collection off and the agent simply books, confirms and reminds. Payments are a capability you switch on for the services that need it, not a requirement, and the rest of the flow works exactly the same.
Every payment has a status of pending, paid or expired, and each change is logged with its reason. Your pipeline moves a deal to Won only on the provider's confirmation, so what you see in the dashboard matches what you see in your Stripe or Bold account. Ready to see it charge for you? Start the 7-day free trial, no card, and send your first payment link from your own WhatsApp number.
