Last verified: October 8, 2026
What You Can Now Do
Context Memo now puts reschedule and cancel controls in the callback invite itself: customers can reschedule or cancel a callback directly from the invite link in their email. The invite email that goes out when a callback is booked carries two new actions alongside the confirmation details, so the person who received it can move the time or drop it without logging in. For your team, that changes one task: you stop fielding reschedule requests by reply email and manually editing the booking. The customer makes the change, and the booking record, confirmation, and connected calendar event follow.
Where It Is in Context Memo
This lives in the callback scheduling area, and most of what's new is customer-facing rather than a new screen for you. The change spans three places: callback invite generation (the email now includes reschedule and cancel links), the confirmation flow (it handles a changed or canceled callback and reissues confirmation), and the calendar integration (the event is updated or removed to match). Open any existing callback record to see its current state after a customer acts on an invite.
How to Use It
- Book a callback the way you do today. The invite email generated for that booking now includes reschedule and cancel links tied to that specific callback.
- Send yourself a test invite before you rely on it at volume. Confirm both links render and resolve correctly from your sending domain and your customers' common mail clients.
- Click the reschedule link as the recipient would. You land on the invite page with available times; selecting a new one writes the change back and triggers a fresh confirmation.
- Click the cancel link on a separate test booking. The callback is canceled, the confirmation reflects it, and the connected calendar event is removed.
- Return to the callback record in Context Memo and verify the state matches what you did from the email: new time, or canceled. This is the check to run once per environment, not per booking.
- Update the internal playbook your team uses for reschedule requests. Point customers to the links in their original invite instead of collecting a new preferred time over email.
Why We Built It
The request was consistent and specific: customers no longer want to log back into the product to change or cancel a scheduled callback, because the thing they're changing arrived in their inbox. Before this, a reschedule meant either a round trip through login or an email to your team, who then edited the booking and re-sent a confirmation by hand. That friction landed in two places you can watch in your own data: the volume of callback-related support messages, and the callbacks that quietly become no-shows because canceling was harder than not showing up.
What It Does Not Do Yet
The links act on the single callback they were issued for. There's no bulk action for a customer with several scheduled callbacks, and nothing here changes how your own team reschedules on a customer's behalf, which still happens in the product interface.
Two operational notes worth confirming on your side. First, the actions are only as reachable as the invite email, so if a customer deletes it or your invites are being filtered, they're back to the old path. Treat invite deliverability as a dependency of this feature, not a separate concern. Second, calendar updates follow your existing integration setup. If a callback was added to a calendar that isn't connected through Context Memo, that copy won't update on its own and the customer will need to clear it themselves.
For teams with compliance review on customer-facing email, the practical change to document is narrow: invite emails now contain two action links that alter a scheduled record without an authenticated session in the product UI. Run that past whoever owns your email and access review, note it, and move on. Nothing else about how invites are generated or who receives them has changed.