A useful chatbot booking flow helps a visitor choose a time, provide the necessary details, and understand what happens next. In Chatbot Leads, the widget submits a booking request for review. An appointment request is not a confirmed meeting until the approval process is completed.
Make that distinction visible in your labels and confirmation copy. “Request a consultation” is more accurate than promising an instantly confirmed appointment when a team member still needs to approve it.
Define the meeting before configuring the calendar
Choose the purpose of the meeting: an introductory call, a project discussion, or another service your team actually offers. Decide which meeting types are available and who is responsible for reviewing requests.
Set a realistic duration and availability through the existing availability controls. Do not promise every calendar hour is available, and do not imply an external calendar integration is connected unless you have configured and tested it.
Configure Availability in Edit Bot
- Open the bot’s Availability section. Check that booking is enabled and review the existing calendar rules and notification recipients.
- Set the visitor-facing options. Configure meeting-type choices, timezone display, headings, labels, and the topic field’s visibility or requirement.
- Review the contact requirements. The booking form requires email for confirmation. Phone calls require a phone number; virtual calls can leave it optional.
- Match the form to the site. Adjust booking colors, spacing, padding, and corners while maintaining readable contrast.
- Save both kinds of settings. Use Save Changes for the bot configuration and Save Rules for availability rules. These are separate saves.
Understand the visitor’s steps
The booking form uses a compact calendar, a time-slot selection step, and a review summary. Visitors should be able to check their information before submitting the request. Keep the displayed timezone understandable, particularly when the business and visitor are in different locations.
“We received your consultation request. Our team will review the selected time and send an update. Please wait for confirmation before treating the appointment as booked.”
Adjust this wording to your actual approval and notification process. Do not promise a reply time your team cannot support.
Preview appearance, then test the live workflow
Use Show Preview → Booking to inspect the booking form with sample availability. The preview is designed for appearance testing; it does not create a real booking request.
Next, use the live widget with your own test contact details. Confirm that the requested date, time, timezone, meeting type, and topic arrive correctly. Verify that the configured recipient receives the expected notification and that the approval process produces the intended outcome. Label test records clearly so the team does not mistake them for customer requests.
Test the situations that create confusion
- No availability: confirm the visitor receives a useful message and another way to contact the business.
- A changed selection: go back a step and confirm the review summary reflects the new choice.
- Missing contact details: ensure errors explain what needs correcting.
- Mobile screens: check the calendar, time options, review controls, and submit button without horizontal scrolling.
- Uncertain submission: check for an existing request before retrying if the connection fails after clicking submit.
The widget rechecks the selected slot before sending. That check is useful, but it should not be described as a guarantee that all scheduling conflicts are impossible.
Common questions
Does the preview book a real appointment?
No. It uses sample availability. Test the live widget separately when you are ready to verify delivery and approval.
Where should I explain the approval requirement?
Make it clear in the booking introduction and the submission confirmation. Use consistent wording in any follow-up message.
What if a visitor needs help before choosing a time?
Keep a short inquiry form available. Ask what they need and let the team recommend the next step. See which qualification questions are useful.
Make requesting a call straightforward
Build a clear path from a visitor’s question to a booking request your team can review.
Get started with Chatbot LeadsBy Chatbot Leads Team · October 30, 2026. Product instructions reflect the current configuration. Examples are illustrative; the featured image is an AI-generated conceptual illustration, not a product screenshot.
