Answers from approved information
The agent answers routine questions using the business knowledge base. When the information is not available, it does not invent an answer.
AI Booking Agent
A clearer way to handle enquiries and booking requests.
The Hengivo booking agent handles a website conversation, answers from the business knowledge base and collects the details needed to record a booking request or lead.
Current product
What the booking agent does today
The current workflow supports website chat and two structured actions: saving a lead and saving a booking request.
Collects booking-request details
It asks for the customer’s full name, contact details, service, preferred date and preferred time.
Saves before confirming
Once all five fields are collected, the agent saves the booking request and confirms that the request was recorded.
Captures unsupported enquiries
If a question is outside the knowledge base, the agent collects the customer’s details and saves a lead for the team to follow up.
Keeps the conversation in context
Short-term conversation memory allows the customer to continue without repeating the same information at every step.
Works through website chat
The current workflow supports a hosted chat experience and an embeddable website chat widget.
From conversation to structured record
Visitor message
Assistant decides: answer, lead or booking
Details collected
Structured record saved
Team reviews and confirms
Example interaction
See how a booking request is collected
The visual below is an illustrative scenario using synthetic business data. It is not a screenshot of a live client system.
Booking requestBooking request received
- Name
- Alex Morgan
- Contact
- [email protected]
- Service
- Deep cleaning
- Preferred date
- Friday, 21 August
- Preferred time
- 2:00 PM
System design
What happens behind the conversation
The system combines website chat, approved business information, short-term conversation memory and separate actions for lead capture and booking requests. Each action creates a structured record that staff can review.
- Website chat
- Booking and support assistant
- Approved business information
- Conversation memory
- Lead record
- Booking-request record
Process
From the first message to staff follow-up
- 01
A customer starts a website chat
The customer asks a question or describes the booking they want to request.
- 02
The assistant responds
It answers from approved business information or begins collecting the required details.
- 03
The request is recorded
A complete booking request or unsupported enquiry is saved as a structured record.
- 04
Staff review the record
The business checks availability, follows up with the customer and confirms the next step.
The request is recorded; availability remains with the business.
The agent records the customer’s preferred date and time. It does not check a live calendar or create a confirmed appointment in the current workflow. The business reviews the request and confirms availability with the customer.
Additional integrations
Additional integrations can be scoped separately.
Calendar availability, WhatsApp, CRM connections, multilingual support and reporting are not included by default. They can be considered during technical scoping when the required systems and integration access are known.
- Calendar availability
- WhatsApp and messaging channels
- CRM and business tools
- Multilingual support
- Reporting and analytics
Pilot project
Pilot the booking agent with one business process.
The pilot defines the services, customer questions, booking information, knowledge base, test scenarios and delivery requirements before implementation begins.
Frequently asked questions
Does the booking agent confirm an appointment?
No. It records a booking request with the customer’s preferred date and time. The business remains responsible for checking availability and confirming the appointment.
Can it answer questions about prices and services?
Yes, when that information is included in the approved business knowledge base. If the answer is not available, the agent captures the enquiry instead of inventing one.
Can it work through WhatsApp or check a calendar?
Those capabilities are not included in the current default workflow. They can be assessed as additional integrations during technical scoping.
Where are leads and booking requests stored?
The current workflow saves them as structured records in configured n8n data tables. A different approved destination can be considered as part of an integration project.
Can we see the system before starting a project?
Yes. Request a private demonstration using synthetic business data.
See how the booking agent handles a real conversation.
Request a demonstration using synthetic business information, or discuss a focused pilot based on your enquiry and booking process.