Last verified: October 5, 2026
What You Can Now Do
Context Memo now tracks and displays call metrics from your Twilio integration, including recording data and call performance tied to individual leads. If you run pay-per-call offers, the call no longer disappears into your phone system. You open a lead record and see whether a call was placed, whether it connected, how it performed, and whether a recording exists. The task this changes: qualifying and disputing pay-per-call leads. Instead of exporting Twilio logs and matching numbers by hand against your lead list, you check the lead record and make the call on the lead right there.
Where It Is in Context Memo
Call data surfaces in two places: the Leads view, where each lead record now carries its associated call activity and recording, and the Offers view, where call metrics roll up against the offer that generated them. Both sit in the lead management area of the product. Twilio credentials and webhook setup live with your other integration settings.
How to Use It
- Connect Twilio in your integration settings. Enter your Twilio account credentials. Context Memo registers the webhook endpoint that receives call events from Twilio. You'll see the integration marked active once the first event arrives.
- Confirm call recording is enabled on the Twilio side. Recording is a Twilio-level setting. If it's off, call events still flow and metrics still populate, but no audio is stored. Turn it on before you rely on recordings for lead review.
- Place or receive a call through your connected Twilio number. Twilio fires the event, Context Memo handles the webhook, and the call is written against the matching lead. No manual import step.
- Open the lead record in the Leads view. The call appears with its performance data and a link to the stored recording. This is where you verify that a lead you're being billed for, or billing on, actually produced a connected call.
- Switch to the Offers view to see call activity by offer. Call metrics are grouped against the offer that drove them, so you can compare which offers are generating connected calls and which are generating noise.
- Pull the recording when a lead is contested. The stored audio is attached to the lead, so a disputed call gets resolved against evidence rather than against two different spreadsheets.
Why We Built It
The gap customers described was simple: they could see the lead in one system and the call in another, with nothing linking them. Which calls were actually made? Which ones connected? Which lead does this recording belong to? Answering those questions meant pulling Twilio logs, matching timestamps and phone numbers by hand, and accepting that some reconciliation would never get done. That manual matching cost real hours every billing cycle, and it meant pay-per-call performance was reviewed late or not at all. Call activity and lead records now live on the same screen.
What It Does Not Do Yet
This release covers Twilio specifically. If you route calls through another provider, those events are not ingested, and the workaround is to keep that traffic in your existing reporting until we add the connector.
Call data arrives by webhook, which means it appears when Twilio sends it. There is no backfill of call history from before the integration was connected. If you need historical call records tied to older leads, export them from Twilio and treat them as a separate reconciliation.
Recording storage depends on Twilio's recording setting being enabled, and the recording is surfaced as stored call data rather than transcribed or analyzed. Keyword search inside call audio is not available in this release.
One boundary worth stating plainly: this is lead and call visibility, not a replacement for your CRM. Context Memo is not a CMS or a full CRM, and we don't intend it to be. Keep the system of record where it is, use ours to see what AI search and your call-driven offers are actually producing, and sync the outcomes you care about through your existing stack.
If you run pay-per-call offers alongside AI visibility work, the practical upside is attribution continuity. A buyer asks a model about your category, lands on a memo published on your domain, and dials the number. The call now lands on the lead record with the offer attached, so the path from AI answer to connected call is visible in one place instead of inferred across three tools.