Self-service meeting booking is a settled feature: every B2B prospect expects a Pick a Time button. The question is whether your booking tool talks to CRM well enough that booked meetings auto-create the right records, in the right pipeline, with the right context.
Booking page per use case
One generic page is a mistake. Build pages by intent:
- /meet/demo (30 min, AE pod, requires qualified inbound)
- /meet/csm-checkin (30 min, CSM pod, account-only)
- /meet/exec-call (45 min, leadership, gated link)
- /meet/support (15 min, support tier 2, ticket required)
Each page has different routing, fields, and confirmation logic.
Pre-booking qualification fields
The booking form is your last chance to filter. Required fields: company name, work email (block free domains for /meet/demo), team size, current stack. If qualifications fail, route to a self-serve resource page instead of an AE calendar.
// Form validation: block personal emails on demo page
const freeEmails = ['gmail.com','yahoo.com','hotmail.com','outlook.com'];
const domain = email.value.split('@')[1];
if(freeEmails.includes(domain)){
alert('Please use your work email');
return false;
}
CRM contact resolution on book
When someone books, search CRM by email. If a Contact exists, link the booking to that Contact’s Account. If a Lead exists, link to the Lead. If neither, create a Lead with Source = Bookings.
existing = zoho.crm.searchRecords("Contacts","(Email:equals:" + booking.email + ")");
if(existing.size() > 0)
{
contactId = existing.get(0).get("id");
zoho.crm.createRecord("Events", {"What_Id":lookupOpenDeal(contactId),"Who_Id":contactId,"Subject":booking.event_type,"Start_DateTime":booking.start});
}
else
{
newLead = {"Email":booking.email,"Last_Name":booking.last_name,"Company":booking.company,"Lead_Source":"Bookings"};
zoho.crm.createRecord("Leads", newLead);
}
Round-robin rules that respect territory
Default round-robin assigns by next-up. Smarter: by territory, by language, by industry vertical. Build the routing logic in Bookings (Settings, Booking Page, Routing) or, if Bookings can not express your rule, do it in Deluge after creation.
Reschedule and cancel flow
When a customer reschedules, the CRM Event should update, not create a duplicate. When they cancel, the Event status flips to Cancelled, AE gets notified, Cliq channel pings the AM if it was a high-stakes meeting.
Buffer time and prep
Auto-add 15-min buffers between meetings so AEs are not back-to-back. Prep brief auto-fires 15 min before (we covered this in the Meeting article): account summary, last activities, deal context.
Confirmation and reminder cadence
Confirmation email immediately. Reminder 24 hours before. Reminder 1 hour before with the join link. SMS reminder for high-value or first-time meetings (configure under Bookings, Notifications). No-shows often blame the lack of reminders, fairly.
Calendar conflicts: source of truth
Bookings checks the AE’s primary calendar (synced from Google/Microsoft) for availability. If AE adds a focus block in their personal calendar that does not sync, Bookings will book over it. Train AEs to always create blocks on the synced work calendar.
Workflow: post-booking actions
For demo bookings, fire a confirmation email with relevant content (industry case study, prep doc). Booking already has industry from the form; pull the matching asset URL and embed.
Reporting: bookings to opportunity
Track bookings created → meeting held → opportunity created → won. Conversion at each step is the funnel. If meeting-held to opportunity is low, your AE qualification on the call is off; if booking-to-meeting-held is low, your no-show rate is high (improve reminders or qualification).
Partner and field events
For partner-led bookings (a partner books on behalf of a customer), use a separate page with the partner field captured. Pipeline attribution depends on this.
What to do this week: build the four use-case pages with the right qualification fields, ship the duplicate-detection Deluge, and pull a weekly bookings-to-opportunity report. Most bookings programs leak at the qualification step; data shows where.