What should the salon booking agent do?

The agent has one job: move a booking request from natural language to a confirmed appointment without guessing business facts. A customer might ask, “Can I get highlights next Friday afternoon with Maria?” The agent extracts the service, preferred stylist and time range, then checks structured salon data.

The workflow should support a small, explicit action set: answer booking-policy questions, find services, find eligible staff, search real availability, propose slots, create a confirmed booking and request staff help. Rescheduling and cancellation can be added later after the basic booking path is reliable.

What data must exist before you build the agent?

A booking agent cannot repair missing business rules with better prompting. Create a structured service catalogue first. Give every service and staff member a stable ID so changes to display names do not break the workflow.

What architecture prevents invented slots and double bookings?

The text equivalent of the diagram is: interpret the request; validate the service; retrieve eligible staff and live busy intervals; calculate candidate slots; obtain customer confirmation; recheck the selected slot; create one booking; record the result. Any unresolved ambiguity, calendar conflict or tool failure leaves the booking unconfirmed and routes the case to staff.

How do you build the salon booking agent step by step?

1. Define the booking boundary. Write the actions the agent may perform and the actions it must refuse or escalate. Begin with new bookings only. Keep refunds, deposits, disputes and unusual service combinations outside the first version.
2. Create the service catalogue. Store official service IDs, names, aliases, durations, buffers, prices, consultation flags and eligible staff. Do not put these changing facts only inside the prompt.
3. Define booking states. Use explicit statuses such as collecting_details, searching, awaiting_confirmation, committing, confirmed, conflict and human_help. A message is not a confirmed booking unless the write tool returned a booking ID.
4. Connect read-only tools first. Give the agent tools such as get_services, get_eligible_staff and check_availability. Keep create_booking unavailable until validation and confirmation pass.
5. Write narrow agent instructions. Tell the model to use catalogue data for facts, ask when the service is ambiguous, show no more than three suitable slots and never describe a booking as confirmed before receiving a booking ID.
6. Calculate candidate slots deterministically. Query busy ranges for eligible staff, subtract them from working hours, then apply service duration, buffer, holidays and lead-time rules. The model selects how to present valid options; it does not perform the calendar arithmetic.
7. Require explicit customer confirmation. Show service, stylist or “any available stylist,” local date, local time, duration and current catalogue price. Store the customer's affirmative response with the chosen slot.
8. Recheck and create atomically. Query availability again immediately before the write. Create the event only if the slot is still free. Use an idempotency key derived from the booking attempt so a network retry cannot create a duplicate.
9. Log, notify and test. Store the request, selected catalogue IDs, tool results, confirmation, booking ID and final status. Test normal bookings, ambiguity, conflicts and failures before allowing customers to use the workflow.

What should the agent instructions contain?

The following is a design example, not a complete production prompt. Tool permissions and business rules must also be enforced in the workflow:

ROLE
You help customers find and request hair salon appointments.
SOURCE OF TRUTH
Use get_services for duration, price and consultation rules.
Use check_availability for slots. Never invent either.
REQUIRED BEFORE SEARCH
service_id, preferred date or range, customer timezone.
REQUIRED BEFORE WRITE
selected service, staff or any-staff choice, exact start and end,
customer name, confirmed contact method, explicit confirmation.
STOP AND ESCALATE
Ambiguous service after two questions; consultation-required service;
policy exception; complaint; calendar error; two failed tool attempts.
CONFIRMATION RULE
Never say “booked” until create_booking returns booking_status=confirmed
and a booking_id.

How should the n8n workflow be divided?

n8n can coordinate the conversation trigger, structured data, AI Agent node, calendar operations, validation branches, notifications and logs. Keep the model-facing tools small and precisely named. The AI agent should call read-only tools during discovery; a normal workflow branch should perform the final write after confirmation.

How do you prevent double-booking?

Checking availability once is not enough. Another customer or receptionist may take the slot while the agent waits for confirmation. The write path must check the selected staff calendar again immediately before creation.

Google Calendar's Freebusy endpoint returns busy periods for specified calendars and time ranges. Event creation uses an event with start and end values. Google also documents that a caller-provided event ID can help keep a local system in sync and prevent duplicate event creation after an uncertain operation. If the salon uses a dedicated booking platform, apply the equivalent availability and idempotency controls supported by that platform.

Which actions need human help?

• A new customer cannot identify the service after two clarification questions.
• Colour correction, extensions or another service requires consultation.
• The customer requests an exception to price, timing, deposit or cancellation policy.
• The calendar or booking tool returns an error twice.
• The requested stylist is unavailable and the customer rejects alternatives.
• The customer makes a complaint or asks for compensation.
• The workflow detects conflicting customer or booking records.

Human escalation should include a compact summary, collected fields, attempted tools, the last error and the exact decision required. Staff should not have to restart the conversation.

How do you test the agent before launch?

Criteria for success

• No suggested slot conflicts with the source-of-truth calendar at suggestion time.
• No booking is created without explicit confirmation and a second availability check.
• Repeated delivery of the same confirmed request creates no duplicate booking.
• Every confirmed message maps to a stored booking ID and audit event.
• Unsupported services and tool failures reach staff with useful context.
• Test results are recorded before the workflow is opened to real customers.