Last verified: October 9, 2026
What You Can Now Do
Context Memo now gives you a screen callers switch in call-flow settings, so you can control whether inbound calls are screened or ring straight through unscreened. The switch ships off, which means your current routing behavior is unchanged until you deliberately turn screening on. Once it's on, screening applies to the next inbound call and every one after it, with no waiting period and no request to us. The decision this hands back to you is a simple one you previously couldn't make on your own: does an unknown inbound caller get filtered first, or does the phone ring immediately?
Where It Is in Context Memo
The control lives in call-flow settings, alongside the rest of your inbound routing configuration. The screen callers switch is labeled on that screen and displays its current state, so you can confirm at a glance whether screening is active before you make a change. This is the only place the setting is exposed today.
How to Use It
- Open call-flow settings in Context Memo. The screen callers switch reads off unless someone on your team has already changed it.
- Turn the switch on. Inbound calls are screened from that point forward.
- Confirm the state reads on before you navigate away. The displayed state is the live state, so what you see is what callers will experience.
- Place a test inbound call from a number outside your team. You should hit the screening step before the call connects, which verifies the setting end to end rather than trusting the toggle alone.
- Switch it back off whenever you want direct routing. Unscreened calls resume on the next inbound call.
- Record the change wherever your team tracks call-handling configuration, if you audit routing behavior. The switch has two states and no version history, so your own log is the trail.
Why We Built It
Customers told us they wanted to choose whether incoming calls should be screened or routed immediately. Before this switch, that choice wasn't theirs to make in the product, so the call-handling workflow had to bend to the default rather than the other way around. Teams that needed speed got a screening step they didn't want, and teams that needed a filter got raw inbound calls they had to triage by hand.
Defaulting the switch to off was deliberate. Shipping a behavior change that silently alters how every customer's phone rings isn't a change we'd make for you. You opt in, you verify it with a test call, and you reverse it in one click if it doesn't fit.
What It Does Not Do Yet
This is one switch with one state, and it governs the call flow it sits in. There's no scheduling layer, no per-number exception, and no caller allow list in this release. If you want screening active during business hours and off overnight, that's a manual toggle today, not a rule you can configure. Teams that need time-based or caller-specific behavior should keep that logic wherever it currently lives and treat this switch as the global on/off for screening.
The switch also doesn't log state changes. If multiple people on your team have access to call-flow settings and you need to know who turned screening on or off and when, capture that in your own change management process until we expose it.