Book appointments and trigger actions
Move a conversation beyond an answer: collect the details that matter, use the right connected source, and create a booking, lead or support follow-up with human control intact.
Choose the right flow
- Google Calendar for availability-aware scheduling and calendar events.
- Calendly to share the appropriate booking link and event type.
- DMtoLead's internal scheduler for a lightweight appointment table inside your workspace.
- HubSpot, Pipedrive or Zendesk to keep the follow-up in your existing sales or support system.
Set up an appointment assistant
- 1
Connect the calendar or booking source
Open Training → Knowledge and connect Google Calendar, Calendly, or create a built-in appointment source. Confirm the account, event type or service the assistant should use.
- 2
Create an appointment-focused AI Assistant job
Give it the business rules: services, duration, timezone, opening hours, cancellation policy and the cases a teammate must approve.
- 3
Collect only missing details
A useful booking conversation usually needs the service, preferred day or time, and contact details. Do not repeat information the customer has already given.
- 4
Test an available and unavailable request
Check that the assistant confirms only a verified slot. For unavailable times, it should offer alternatives, share the booking link, or ask a person to take over.
Send qualified follow-up
The same pattern applies to leads and support. Connect HubSpot or Pipedrive when a qualified conversation should enter your sales pipeline, and Zendesk when a support issue needs a ticket. You can also send the event to an internal system through an outbound webhook.
Tell the assistant which fields are required before it creates an action. That keeps your CRM clean and gives the receiving teammate a useful summary instead of a context-free notification.
Keep humans in control
Escalate exceptions, sensitive changes, unapproved discounts and ambiguous requests. A teammate can take over in the inbox with the full conversation context preserved; manual replies do not use credits.