Last verified: October 9, 2026
What You Can Now Do
Context Memo now lets you record and configure custom voicemail greetings for busy and after-hours call scenarios, and the default messaging behind them has been rewritten to be clearer. Before this deploy, every caller who hit a busy line or dialed outside your hours heard the same system message, regardless of which brand they thought they were calling. Now the recording is yours: your name, your hours, your instruction for what the caller should do next. The decision this changes is a small operational one you can finish today. Instead of accepting a generic message as a cost of doing business, you decide what a missed call sounds like, and you decide it separately for a busy line and for a closed office.
Where It Is in Context Memo
This sits in your account's call handling settings, under the configuration for busy and after-hours states. That screen now shows a greeting slot for each state, which message is currently live in it, and a record control. If you have not recorded anything, the slot shows the updated default so you can hear what callers get before you change it.
How to Use It
- Open call handling settings and select the busy state. The screen shows the greeting currently playing for that state, either your recording or the new default.
- Record your busy greeting and save it. The slot updates to show your recording as live, and you can play it back from the same screen.
- Select the after-hours state and record a separate greeting. Treat these as two different messages: a busy line means "we are here, try again," and after-hours means "we are closed, here is when we are back."
- Confirm your after-hours window is set correctly. The greeting plays on the schedule your call handling configuration already uses, so a wrong window sends the wrong message at the wrong time.
- Call your own line twice to verify, once while the line is busy and once outside your hours. You should hear your recording play and then the voicemail prompt.
- If a recording is wrong, re-record over the same slot. Clearing a slot returns that state to the updated default rather than silence.
Why We Built It
Callers were hearing generic or unclear voicemail messages when they reached a busy line or called after hours, with no indication of who they had reached or what to do about it. The cost was not a dropped feature, it was a dropped impression: the one moment where a prospect gets a recorded answer from you was the one moment you could not control. Customers told us they wanted their own greetings, in their own voice, with clear instructions for the caller. That is what this deploy gives them.
What It Does Not Do Yet
- Only two states are covered. Busy and after-hours each take a custom recording. Other routing states continue to use default messaging.
- Greetings are recorded in-product, one per state. There is no bulk import, no per-number variation, and no separate language versions in this release.
- Scheduling is inherited, not new. Your after-hours greeting follows the hours already configured for call handling, so changing when the greeting plays means changing those hours.
- Defaults are the fallback, and they are better than they were, but they are still defaults. A slot you never record will play a system message, so the clarity improvement only goes as far as the recording you make.
One practical note on scope. This is a call handling improvement, not a change to how AI models read or cite your brand. Our view of the stack has not changed: the memos you publish on your own domain are what shape the answers buyers get from ChatGPT, Claude, Gemini, and Perplexity. A voicemail greeting shapes what a human hears when the model sends them to your number and nobody picks up. Both are brand surfaces. This one was overdue, it was inconsistent with the rest of the product, and it is now yours to set.