Last verified: October 5, 2026
What You Can Now Do
Context Memo now shows AI-generated call summaries and caller name lookups directly in your leads view, with tracking numbers displayed as caller ID in the call data. Open a lead and the inbound call is already described: what was discussed, who called, and which tracking number the call came in on. The task this changes is triage. You no longer decide which calls are worth listening to by guessing from a timestamp and a phone number. You read the summary, judge the intent, and route or follow up from the same screen.
Where It Is in Context Memo
Leads view. Select any lead with inbound call activity and the call entries now carry three new pieces of information on the record itself: the AI-generated summary of the conversation, the enriched caller name where a match is found, and the tracking number rendered as caller ID. There is no separate call log to open and no second tab to keep.
How to Use It
- Open the leads view and filter to leads with recent inbound calls. Each call entry displays the tracking number as caller ID rather than a bare destination number, so you can tell at a glance which number the buyer dialed.
- Select a call entry to read its AI-generated summary. You get the substance of the conversation in text, without playing the recording.
- Check the caller name on the record. Where enrichment returns a match, the name appears alongside the number, so the lead is identifiable before anyone picks up the phone to call back.
- Match the tracking number to the source that produced it. That tells you which published asset or campaign path the caller came through, and it closes the loop between what you published and who called.
- Act on the lead from the same view. Qualify it, assign it, or write your follow-up note with the summary in front of you instead of reconstructing the call from memory.
- Export or sync the lead to your CRM once the context is attached, so the record your sales team sees is already annotated.
Why We Built It
Customers told us the call was the least visible part of the lead. To find out what was discussed, someone had to open a recording and listen, or log into a separate system that held the call data, and then type what they heard back into a note. Caller identity was worse: a number with no name, and no quick way to know whether the person on the other end was a qualified buyer or a vendor pitch. The cost was time per lead and slower follow-up, and in practice it meant most calls were never reviewed at all, so the intent signal in them was simply lost.
What It Does Not Do Yet
Caller name lookups depend on enrichment returning a match. When no match exists, the call still shows the number and the summary, but the name field stays empty. Summaries describe the conversation; they are not a transcript, so for disputes, compliance review, or verbatim quotes you will still want the recording itself.
This also sits inside the leads view, not inside your CRM. We are not replacing your CRM record, and we are not trying to. The pattern we recommend is to use the leads view as the place where call context gets attached, then sync the enriched lead onward to the system your sales team already works in. Our HubSpot integration is the path for that today.
Call summaries are generated for inbound calls captured on tracking numbers. Activity that reaches you on untracked lines will not appear here, so if you want full coverage of phone intent, make sure the numbers you publish are the tracked ones.