Last verified: October 7, 2026
What You Can Now Do
Context Memo now prevents callback slots from being offered during times when you're marked as busy in Google Calendar. Your calendar is read as a constraint on slot generation, so the availability a prospect sees already excludes anything you're booked into. The practical change: you stop maintaining callback availability as a second, hand-updated copy of your calendar. Set the outer window once, and the busy filter handles the rest as meetings get added and moved.
Where It Is in Context Memo
This lives in the callback scheduling area, alongside your Google Calendar connection and availability settings. It is not a new page or menu item. The change is in how available slots are generated, so the same screen you already use to configure callback availability now produces a filtered slot list rather than a raw window.
How to Use It
- Connect Google Calendar from the callback scheduling settings and grant busy/free access. Once the connection is live, slot generation starts reading availability on the connected account.
- Confirm which calendar you want treated as the source of truth. Whatever is marked busy on that calendar is what gets excluded.
- Set your callback availability window: the days and hours you're willing to take calls at all. This remains the outer bound, and calendar busy times are subtracted from it.
- Open the slot preview and compare it against your calendar for the same period. Times you're booked should not appear in the list.
- Block a test hour inside your availability window, then regenerate slots. That hour should drop out. Remove the block and it returns.
- Leave the window wider than you previously did. Because conflicts are now filtered automatically, a narrow manual window is no longer the safety mechanism it used to be.
Why We Built It
Customers were managing callback availability by hand, and the cost showed up twice. Either they kept their offered hours artificially narrow to avoid collisions, which meant fewer bookable slots and slower follow-up on live interest, or they left the window wide and absorbed the double-bookings: a callback landing on top of a customer call, then a rescheduling email, then a prospect who had already moved on. Calendar truth lived in Google Calendar; scheduling truth lived somewhere else. This removes the gap between them.
What It Does Not Do Yet
- Google Calendar only. Other calendar providers are not read. If your team's availability lives elsewhere, you'll still need to manage that window manually.
- Busy/free status, not event content. The filter reads whether you're busy, not what the event is. It can't make exceptions for a specific meeting type, nor can it treat a tentative hold differently from a confirmed meeting. If you want a block ignored, mark it free.
- Filtering happens at slot generation. Callbacks booked before a conflicting meeting appeared on your calendar stay booked. If someone drops a meeting on top of an existing callback, that collision still needs a human decision.
- One direction. Context Memo reads your calendar as a constraint. It does not write callback events back into Google Calendar, so your calendar won't show the callback as a block unless you add it.
A note on access scope, since this comes up in security review: the constraint is built on busy/free availability rather than event detail, which is the narrower read. If your team requires a documented justification for the calendar connection, that distinction is the one to put in the request.