Skip to main content
Booking during the call is the point of the whole system. A qualified lead that has to be called back converts worse than one that already has a slot.

​
Booking settings

Under Appointment settings, define the rules the agent books within:
How long each service takes. Set it per service where they differ — a diagnostic visit and a full install shouldn’t occupy the same slot. Realistic durations are what stop the day falling apart by 2pm.
Whether you book exact times or windows — 8–10, 10–12, 12–2. Windows absorb traffic and overruns; exact times raise expectations you have to meet.
The minimum notice before a bookable slot, and how far ahead you’ll take bookings. Lead time protects your dispatcher from a job appearing twenty minutes out.
Travel and turnaround time between jobs. Without buffers the agent books back-to-back across town.
How many jobs can run concurrently — typically your crew count. Prevents three bookings in one slot with one truck.

​
Where availability comes from

The agent books against real availability, not a static grid. Connect a calendar or a field-service CRM so it sees what your team actually has open. See Calendars and Field-service CRM.
Without a connected source of availability, the agent can only work from the rules above — which means it can’t see a job your dispatcher added by hand this morning. Connect something before you take real bookings.

​
Confirmations and reminders

Once a booking is made, Recepta.ai handles the lifecycle around it: Reminders go by SMS or email depending on what you’ve configured and what the customer consented to. SMS requires approved A2P registration.
A reminder the evening before plus one on the morning of the visit cuts no-shows more than any single message does. Include a way to reschedule — a moved job is worth far more than a missed one.

​
Rescheduling and cancellations

Customers can reschedule or cancel through the agent on a call or by replying to a reminder. Changes propagate to your calendar and to your connected CRM.
Only one write-capable field-service CRM can be connected at a time. This is deliberate — with two connected, a reschedule can dispatch to the wrong system and dead-end. See Field-service CRM.

​
Post-visit feedback

Enable feedback requests to capture how the job went. Beyond the review value, the outcomes tell you which services and which crews generate follow-up problems — and they feed the dormant-customer and reactivation sequences.

​
Taking payment

Deposits at booking and balances after the visit can be collected over text. See Payments.