Last verified: October 9, 2026
What You Can Now Do
Context Memo customers can now record and configure greeting audio and call flow settings directly in the Settings dashboard, controlling how inbound calls are handled. Before this deploy, the greeting a caller heard and the path that call took were fixed from our side. Now both are yours. You record the greeting in the browser, write the script the call follows, and set the routing behavior that decides what happens after the greeting ends. The practical change: when a prospect calls in after reading one of your memos, you decide what they hear and where they land, and you can change it the same afternoon without filing a request.
Where It Is in Context Memo
Open Settings and select the Call Flow panel. The screen holds three things: a recorder for your greeting audio, a field for the call script, and the routing controls that govern what the system does with a call once the greeting plays. Call screening logic (the real/not-real check that separates live callers from automated dialers) runs on the same panel and applies to inbound calls as they arrive. The panel reads from and writes to the existing call management system, so anything you set here applies to the calls you were already receiving.
How to Use It
- Go to Settings → Call Flow. The panel loads your current greeting state and routing configuration.
- Click record and speak your greeting. The recorder captures audio in the browser using wav-recorder, no upload or external file prep. Play it back before you save; re-record if the take is wrong.
- Save the greeting. It becomes the audio played to inbound callers on the next call, not on a delayed publish cycle.
- Enter your call script in the script field. This is the text the flow follows after the greeting, so write it the way you want a caller to hear it, not as internal notes.
- Set your routing behavior. Choose what the system does once the greeting and script complete, and confirm the real/not-real screening setting matches how aggressive you want filtering to be.
- Place a test call to your own number. You'll hear the saved greeting and move through the configured path. If any step sounds wrong, return to the panel and change that one field rather than rebuilding the flow.
Why We Built It
Customers told us plainly that they had no way to customize greeting audio or call flow behavior from within the product. That meant every greeting change was a support conversation, and every routing tweak waited on us. Teams running inbound campaigns were left with a generic opening on calls they had paid attention to earn, and the people best positioned to fix the wording were the people who couldn't touch it.
What It Does Not Do Yet
A few limits worth knowing before you build around this panel:
- One greeting per configuration. There is no conditional greeting by caller, time of day, or source. If you need different openings for different campaigns, you change the recording when the campaign changes.
- No version history on recordings. Saving a new greeting replaces the previous one. Keep a local copy of takes you may want back.
- Routing is configured, not visually mapped. You set behavior through the panel's controls. There is no branching flow diagram, so complex multi-branch trees are better documented outside the product for your team's reference.
- Screening is a filter, not a report. The real/not-real logic acts on calls as they come in. The panel is where you tune it, not where you analyze what it caught.
Everything else on this panel is self-service as of this deploy. Record, script, route, test. If a configuration behaves differently than the panel says it should, that's a bug and we want to hear about it rather than see you work around it.