What the receptionist needs to do
- Check real availability for a service and person
- Hold a slot while the caller decides
- Send a deposit link and confirm when it is paid
- Find, move or cancel the caller’s own booking
- Hand the conversation to a person with the context
Use MCP or the REST API
MCP (Model Context Protocol) is an open standard that lets AI agents call tools. TSF Booking runs an MCP server at book.scalingfirm.com/mcp on every plan, with tools such as search_availability, create_booking_hold, create_deposit_request and request_human_handover. Platforms without MCP can use the REST API, documented in OpenAPI.
Keep it safe
The agent uses the same availability, deposit rules and cancellation policy as your booking page, and every action it takes appears in your audit trail.
Give the receptionist its own key with only the scopes it needs. Before it moves or cancels a booking, it must match the caller’s phone number and first name. Refunds and bulk changes can wait for a person to approve.
Set it up in TSF Booking
- Open Developers and create a key with the Receptionist agent preset.
- Add the MCP server URL and the key to your voice or chat platform.
- Make a test call and book a test appointment.
- Check the audit trail to see each action the agent took.
Questions
Which AI platforms work with it?
Any voice or chat platform that supports MCP or can call a REST API, including assistants such as Claude.
Can the AI take deposits?
It sends a deposit link. The booking confirms when Stripe reports the payment.
What if a caller asks something the AI cannot answer?
It hands over to a person, and the conversation lands in your inbox with the context.