Last verified: October 8, 2026
What You Can Now Do
Context Memo now lets you preview how your Twilio call widget will appear on your website before publishing it live, using the Preview button on the Twilio card in settings. The widget renders on a dedicated preview page, so you see the actual control your visitors will see rather than a static description of it. That changes one task: verifying the widget is no longer a post-deployment step. You check it, then you publish, instead of publishing to the live site and correcting from there.
Where It Is in Context Memo
Open Settings, then find the Twilio integration card. The card now carries a Preview button alongside your existing call-hours configuration. Clicking it opens a new preview page that renders the widget using your current Twilio settings. Everything you were already managing on that card (call hours and the rest of your Twilio configuration) stays where it was. The Preview control is the only addition to the card itself.
How to Use It
- Go to Settings and locate the Twilio card. Your existing call-hours configuration appears as before, with a Preview button now on the card.
- Confirm your call hours are set the way you want them. The preview renders against your current configuration, so the state of these fields is what you will see.
- Click Preview. The preview page opens and renders a live version of your call widget.
- Inspect the widget on that page: placement, labels, and behavior when you interact with it. This is the rendering your site visitors get.
- Return to the Twilio card if something is wrong, adjust the configuration, and click Preview again to re-check. Repeat until the widget matches what you want on the site.
- Publish the widget to your site once the preview is correct. Your deployment path does not change.
Why We Built It
Customers told us they had no way to see the Twilio widget without shipping it. To find out how it looked and behaved, they had to publish to the live site, load their own page, and judge it in front of real visitors. Every correction meant another publish cycle. That is an expensive way to answer a question as small as "is this in the right place and does it say the right thing," and it put configuration mistakes in front of buyers before anyone internal had looked at them.
For teams with a change-control process, the cost was higher. A visible widget on a production page is a change someone has to approve, log, or roll back. Checking appearance in a preview route keeps that loop internal.
What It Does Not Do Yet
The preview page renders the widget itself. It does not render your website around it, so the widget is shown outside your own page layout, CSS, and surrounding elements. Use it to verify the widget's own appearance and behavior, then do a quick visual pass on the live page after publishing to confirm it sits correctly within your design. If you need to see the widget in situ before going live, stage it on a non-indexed page of your own site.
Publishing remains a separate action. The Preview button validates; it does not deploy. Nothing you do on the preview page changes what is live until you publish.
The preview reflects the Twilio configuration in Context Memo at the time you open it. If a teammate is editing the same settings, re-open the preview after their changes land rather than assuming the page you have open is current.