A paid deposit is not a confirmed appointment

A med spa in Fort Lauderdale runs an Instagram promo for lip filler on a Tuesday. A new client messages at 8:40 pm: she wants Saturday at 11:00, before a wedding. The chatbot checks the calendar, sees 11:00 open, and sends her a deposit link. She pays $100. The payment processor emails her a receipt that says "Thank you for your booking." The chatbot replies "You're all set for Saturday!"

Nothing ever wrote that appointment to the booking system. The deposit sat in the payment account with a name and an amount, not an appointment. Wednesday morning, the front desk booked a returning client into Saturday at 11:00 by phone. Saturday at 10:50, both women are in the lobby. One of them leaves with a refund and a story she tells her friends.

The deposit was real. The appointment was never confirmed.

Hive AI builds AI chatbots, voice agents, and integrations for med spas, dental offices, and home service companies that take deposits and want "paid" and "booked" to mean the same thing everywhere.

Why "paid" and "booked" drift apart

Most practices run payments and scheduling in two different tools. A deposit link from a chatbot, a text, or an Instagram DM usually lives in the payment tool. The appointment lives in the booking system. Something has to connect them: a webhook, a zap, a staff member copying details over in the morning.

When that connection is missing, slow, or fails silently, you get the gap:

• the client has a receipt and believes she's booked
• the calendar still shows the slot as open
• the chatbot, the front desk, and the phone line all keep offering that slot
• the deposit can't be matched to a visit when it's time to apply it, refund it, or keep it under your no-show policy

A faster chatbot makes this worse. It collects more deposits, at more hours, for slots nobody actually held.

What "confirmed" should mean

When Hive AI connects your chat, phones, payments, and booking system, a deposit moves through steps your practice decides once:

• the agent places a short hold on the exact slot in the booking system before it sends the deposit link, so nobody else can take it
• the deposit link carries the hold, so a successful payment turns that hold into a booked appointment in the same step
• the client gets "confirmed" only after the booking system shows the appointment, not when the payment goes through
• if the hold expires, the payment fails, or the write to the calendar doesn't come back, the slot is released and the case goes to a named person at the front desk with the client's message, the payment status, and the time she asked for
• deposit, cancellation, and no-show terms come from your approved policy, word for word, and the agent never promises a refund or an exception

The agent never invents an opening, and it never tells a client she's booked because a payment cleared somewhere else.

The same Tuesday night, done right

Here's that chat with the steps connected. At 8:41 pm the agent places a 15-minute hold on Saturday 11:00 with the injector she asked for, and sends a deposit link with your policy in two lines. She pays at 8:46. The booking system writes the appointment, the hold becomes a booking, and only then does the agent reply: "You're confirmed for Saturday at 11:00. Here's what to expect before filler." Wednesday morning, the front desk sees 11:00 taken and books the returning client at 1:00.

If she had paid at 9:05, after the hold expired and someone else took the slot, the agent wouldn't have said "you're all set." It would have told her the time was no longer available, offered the next two openings, and opened a task for the front desk to move or refund the deposit the next morning.

Keep the receipt

Every deposit should leave a record your team can read in one place:

• which slot was held, for whom, and when the hold started and ended
• when the deposit was paid, how much, and which appointment it's attached to
• what the client was told, word for word, and when
• who handled anything that didn't match, and what they decided

When a client says "I paid and you gave my spot away," you can see exactly what happened. When an integration misses a write, it shows up as an open task the same night, not as two people in your lobby on Saturday.

Why this matters before you buy

Practices often judge an AI chatbot by how many deposits it collects after hours. That number matters. But a deposit attached to nothing is a refund, a double booking, or a no-show fee you can't enforce because you can't prove which appointment it was for.

The fix isn't another payment tool. It's getting the payment tool and the calendar you already pay for to agree before anyone tells a client she's booked.

Start with one workflow

Work with Hive AI starts with a five-day Bootcamp: one workflow, your real tools, and a Friday recommendation with an evidence path. For many med spas, "deposit to confirmed appointment" is the first workflow worth fixing.

Start a HIVE Bootcamp or talk to Hive AI about connecting your deposits to your schedule