Service Booking Agent

In your workspace, click Create Agent and pick the Service Booking card. This tells DomainChat the agent's one job: turning conversations into booked, paid slots.

You tell us about your business — this personalizes the agent from the first message:

• Service / business name — e.g. "Spin Sports Academy" or "Dr. Mehta Clinic".
• Service type — Sports Academy, Salon/Parlor/Spa, Clinic/Doctor/Consultant, Masterclass/Workshops, Home Services/Repairs, or Other. This tailors the agent's tone and examples — but any service with a bookable slot works: tutors, labs, photographers, car detailing, and everything else.
• Contact details — email is mandatory (shown when customers ask how to reach a human, used on confirmations); phone is optional.
• Booking policies — three editable, pre-filled answers (cancellation, refund, reschedule) that become the agent's policy answers. Customers will ask "can I cancel?" — with these, the agent answers in your words.
• CRM — every booking automatically saves the customer (name, email, phone) to your customer list. DC CRM is built in and free; HubSpot, Zoho, or Freshworks available if your team already uses them.

This is the heart of the agent — your services, prices, availability, and payments live on Cal ID or Cal.com, and the agent reads them live. Connecting a platform is required to finish the wizard: a booking agent without a booking engine can't take bookings. The step includes business examples (sports academy, clinic, masterclass, salon, home repairs — the one matching your service type is highlighted), provider cards, and an open step-by-step setup guide.

Test Connection is a live check, not a formality: it verifies your booking URL and API key actually work, requires at least one event type to exist, and reports payment readiness — "3 services (2 paid)" means payments will be collected; if all services are free you'll see a note explaining how to set prices and connect a gateway.

Feed the agent your business knowledge — scrape your website, upload documents (price lists, class schedules, facility rules), add custom Q&A, or type notes directly. Then review the AI-generated greeting and starter chips, set your brand color and logo, and deploy. The booking-platform webhook (which pushes payment confirmations back into chats) is registered automatically when you connect — no manual setup.

When a customer wants to book, the agent shows your services as tappable cards — each with the service name, duration, price badge, and a seats-left badge for group classes. Services the customer already has a confirmed booking for show a BOOKED badge — tapping those switches straight to rescheduling instead of double-booking.

Tapping a service opens an interactive month calendar inside the chat. Only genuinely available dates are pickable (availability comes live from your platform), then the open time slots for that day appear as buttons. The customer picks one and fills their name, email, and phone — this is also what saves them to your CRM automatically.

If the service is free, the booking is created on your platform immediately and the chat shows a confirmation ticket: service, date & time, and the booking reference. A calendar invite and email go out from your booking platform at the same moment.

If the service has a price, a checkout window opens on top of the chat with the customer's details pre-filled — they pay through your connected gateway (Razorpay, Stripe, or PayPal) without ever leaving the conversation. If their gateway prefers a full page, there's an "Open in new tab" button inside the window. Either way, the moment payment succeeds the window closes itself and the confirmation with the BK- reference appears in the chat automatically — no refresh, no "did it work?".

The slot is held as "awaiting payment". After about 30 minutes the agent sends a recovery nudge — an email with the checkout link, and a message in the chat channel if the conversation is still active — exactly once, never spammy. You can also resend the link any time from the dashboard (see below).

"Cancel my booking" or "move my slot to Sunday" pulls up their booking card with Cancel and Reschedule buttons. Rescheduling re-opens the same in-chat calendar to pick a new time; cancelling is one confirm-tap away. Changes apply on your booking platform instantly, and refunds for paid bookings process automatically.

On channels without an in-chat calendar, the agent explains that everything about the booking is managed directly on your booking platform and sends a 📅 Manage Booking button — tapping it opens that specific booking's page where the customer cancels or reschedules themselves, with refunds handled there automatically.

Payment won't go through? Their booking can't be found? Cancellation disabled by you? After two failed attempts at anything, the agent stops retrying and proactively shares your business contact details so a human can take over — it never leaves a customer hanging.

WhatsApp and Meta channels only allow businesses to message a user within 24 hours of that user's last message. DomainChat respects this strictly: chat reminders and payment nudges are only sent when the conversation is inside the window. Outside it, your booking platform's own email reminders cover the customer — they were already scheduled when the event was created. Confirmations for bookings the customer just made always land inside the window.

• "No bookable services found" — you haven't created an event type on the platform yet. Create one per service (guide above), then retest.
• Invalid URL — use your public booking link (https://cal.id/username or https://cal.com/username).
• Invalid API key — re-copy from Settings → Developer → API keys; keys start with calid_ (Cal ID) or cal_live_ (Cal.com).
• "All services are currently free" — not an error. It means no event has a price; if you intend to charge, set prices and connect a gateway on the platform.

The chat polls for a few minutes automatically; the customer can also tap "Check payment status" on the pending card. If it still shows pending, the webhook may have failed — open Workspace → Integrations → Calendar and use Register webhook, or check that the booking appears on your platform's dashboard (the booking itself is safe there).

The conversation was outside the 24-hour messaging window (Meta/WhatsApp rules) — the email reminder was still sent by your platform. Nothing is lost; nothing is spammed.

It matches your confirmed bookings by the current chat session and by the customer's email (recognized across visits and channels). No email verification step — the same trust model as "find my booking". Abandoned (unpaid) bookings don't badge; past bookings clear automatically.

Workspace → Integrations → Calendar shows your connection status, webhook health, and a manual webhook register button. Disconnecting is clean — the webhook is removed from your platform account automatically.