Last verified: October 5, 2026
What You Can Now Do
Context Memo now lets you create callback offers so leads can book a scheduled call at a time of their choosing, with calendar integration and automated Twilio call routing. Until this deploy, an offer that collected a phone number meant one behavior: the call fired right away. Now the lead picks a slot, gets an ICS file for their calendar, and Twilio places the call when that slot arrives. The decision this changes is per-offer and concrete: for each offer you run, you choose whether speed-to-call or lead-chosen timing will convert better for that audience, instead of accepting immediate dial as the only option.
Where It Is in Context Memo
This lives in the Offers area, alongside your existing offer types. When you create or edit an offer, the type selector includes the scheduled callback option. Choosing it reveals the callback form fields, the time-slot configuration for that offer, and the Twilio routing destination the scheduled call will use. Existing offers are untouched; nothing changes unless you switch an offer's type or create a new one.
How to Use It
- Create a new offer in the Offers area and select the scheduled callback type. The editor swaps the immediate-call setup for the callback form and slot configuration.
- Set the time slots you want to make bookable. These become the only windows the lead sees on the public form, so the slots you publish are the slots your team has to cover.
- Confirm the Twilio routing destination for the offer. That number is what the scheduled call connects to when the slot comes due, so point it at the queue or line that will actually be staffed at those hours.
- Publish the offer and place it where your AI-sourced traffic lands, typically a memo page or landing page on your own domain. The lead now sees a form plus a time picker rather than a call-me-now prompt.
- Check the first few bookings end to end. On submission the lead receives an ICS calendar file for the slot they chose, and the call routes automatically at that time. Verifying one real booking before you scale the offer is worth the five minutes.
Why We Built It
The complaint was consistent: leads were being called the moment they filled in a form, whether or not that moment worked for them. For time-sensitive and preference-driven audiences, that friction showed up as abandoned forms, declined calls, and voicemail chains that never closed. Letting the lead choose when to receive the call removes that friction and gives your team a known, staffable slot instead of an unpredictable dial queue.
What It Does Not Do Yet
This deploy covers four things: the callback form, time-slot selection, ICS file generation, and Twilio routing at the scheduled time. Several adjacent pieces are not part of it.
- Rescheduling and cancellation are manual. The ICS file puts the slot on the lead's calendar, but changing or cancelling the booking is handled by your team outside the offer, not through a self-serve link.
- Reminders are not sent from the offer. If you want a nudge before the slot, send it from your existing sequencing or CRM workflow.
- Routing is per-offer, not per-rep. The scheduled call goes to the destination configured on that offer. If you need distribution across multiple reps, configure that on the Twilio side or create separate offers.
- Slot coverage is your responsibility. Context Memo publishes the windows you configure and places the call. It does not check whether anyone is available to answer, so align your slots with real staffing before you publish.
More broadly, this is a first-call booking mechanism attached to an offer, not a replacement for the meeting scheduler in your CRM. Those tools handle the rest of the sales cycle with far more functionality, and this feature is deliberately narrow: convert the lead who arrived from an AI answer into a call that actually happens.