Meeting scheduling
Julian checks availability and books while qualifying, so the meeting happens inside the conversation. He also sends reminders, reschedules, and re-books no-shows.
Julian books the meeting inside the conversation. He checks team availability and suggests times while qualifying, so booking happens as part of the natural conversation rather than becoming a follow-up task. He then handles reminders, rescheduling, and re-booking no-shows without your team getting involved.
Booking in-conversation is the whole point. Every handoff to "I'll send you a link" introduces a step where a qualified, interested prospect can go cold — and that step is entirely avoidable.
How booking works
Qualify and check availability together
Julian evaluates fit while simultaneously checking the calendar of whichever rep the routing logic selects.
Suggest times in conversation
Real availability, offered while the prospect is still engaged.
Book onto the routed rep's calendar
Respecting territory, deal size, product line, or custom routing rules — no manual calendar checking by a rep.
Attach the context
What the prospect asked about, how they qualified, and what they care about.
Context-rich bookings
Every confirmed meeting arrives with background: what the prospect asked about, how they qualified, and what they care about. The rep enters with situational awareness rather than starting discovery from scratch.
The prospect has already answered your discovery questions. A rep who re-asks them has told the prospect that nobody read the notes — which is a worse first impression than a cold call.
No-shows and rescheduling
Julian manages attendance friction directly. When prospects cancel or schedules shift, he sends reminders, offers to reschedule, and re-books without your team getting involved.
| Situation | What happens |
|---|---|
| Meeting approaching | Reminder sent |
| Prospect cancels | Reschedule offered |
| Prospect no-shows | Re-engagement and re-booking |
| Schedule shifts | Re-booked automatically |
No-show recovery is usually the largest silent leak in an inbound funnel. The lead was qualified, the meeting was booked, and the pipeline is lost to a scheduling gap nobody owns. Check what your current process does with a no-show before assuming this is marginal.
Setup requirements
Connect every receiving rep's calendar
Google Calendar or Outlook. Booking works against real availability, so an unconnected calendar means failures or double-bookings.
Confirm routing before booking
Julian books onto whichever rep routing selects, so routing errors become booking errors. See lead routing.
Set meeting duration and buffers
So back-to-back bookings don't leave reps without preparation time.
Define the handoff payload
Confirm the rep receives the transcript, qualification reasoning, and next step.
Test end to end
Run a test lead through, confirm the invite lands with context, then cancel it and confirm reschedule behaviour.
Reported outcomes
11x reports customers seeing a 1.5x increase in qualified meetings with this approach.
Published by 11x as customer-reported data, not a guarantee. See case studies.