Last verified: October 9, 2026
What You Can Now Do
Context Memo now lets you configure Twilio call routing settings and control which pages trigger calls, using per-page switches in your dashboard settings. Before this deploy, the Twilio integration was effectively a single switch: on for everything, or off. Now you see your call numbers, the memos and websites they're attached to, and a switch beside each page. The decision this changes is placement. Instead of accepting calls from any page Context Memo publishes for you, you choose the pages where a call makes sense (a pricing memo, a comparison memo, a high-intent product page) and leave the rest quiet.
Where It Is in Context Memo
Go to your dashboard settings. The Twilio integration now has its own settings widget there. On that screen you'll find the call numbers configured for your account, the memos and websites associated with each number, and the per-page toggles that govern call behavior. Call-number configuration is handled by a new API route behind the widget, so what you set in the UI is what the integration reads at runtime.
How to Use It
- Open the Twilio widget in dashboard settings. You'll see the call numbers currently provisioned for your account, with the memos and websites each one covers.
- Confirm the call number on each website. If a number is attached to the wrong property, correct it here. The widget writes through the new call-number configuration route, so the change applies to the integration rather than sitting in a local view.
- Review the page list for that website. Every page Context Memo knows about appears with its own switch, including published memos.
- Turn calls on only for the pages where you want them. Toggle each page individually. A page with its switch off will not trigger a call, even though the integration remains active on the account.
- Save and load one enabled page and one disabled page. This is the verification step. The enabled page should surface the call behavior you configured; the disabled page should do nothing.
- Re-check the list after you publish new memos. New pages arrive in the widget, and you decide whether each one joins the enabled set.
Why We Built It
Customers told us the integration was all or nothing. Once Twilio was connected, every page carried the same call behavior, which meant teams either accepted calls on pages where a call was the wrong next step, or they switched off the integration entirely and lost the channel on the pages where it converted. That cost them two things: control over which buyer moments produced a phone call, and a clean read on which pages were actually driving calls, because the signal was spread across every page at once. Granular control was the fix customers asked for, so the per-page switch is now the unit of configuration.
What It Does Not Do Yet
This deploy covers configuration, not reporting. The widget shows you call numbers, the memos and websites they serve, and the page-level switches. It does not yet show call volume, call outcomes, or attribution back to the memo that produced the call. For now, read call activity in Twilio and match it against your enabled page list; the switches give you a clean enough segmentation that the comparison is straightforward.
Three other limits worth knowing before you configure:
- Toggles are per page, not per rule. There's no scheduling, no geography condition, and no persona condition behind a switch. A page is enabled or it isn't.
- New pages are not enabled automatically. Publish a memo and it appears in the widget, but you decide its state. That's deliberate, and it means the list needs a pass whenever you ship a batch of memos.
- Routing settings live with the call number. Changes apply at the number level across the websites that number serves, so split numbers across properties if you need different routing per property.
If you manage Twilio for several brands or business units from one account, configure one website end to end first, verify it on a live page, then replicate the pattern. The widget makes the current state readable at a glance, which is the point: you should be able to answer "which of our pages can ring a phone right now" without opening a support ticket.