Last verified: October 5, 2026
What You Can Now Do
Context Memo customers can now receive a Slack notification when an incoming call arrives, with the caller's source whispered in the notification. The alert lands in your Slack workspace in real time and tells you where the call came from, so the person who picks up already knows the context before they say hello. The task this changes is triage. You stop watching a separate call console to see whether anything is coming in, and you stop treating every inbound call as an unknown. The source identification means a call tied to a memo, a campaign, or a specific entry point is recognizable at the moment it rings, not after someone pulls the record.
Where It Is in Context Memo
This runs through the Twilio webhook integration and delivers into the Slack workspace you already have connected under Integrations. If you have Slack alerts configured for citation and crawl notifications, incoming call alerts use the same connection and the same channel selection. Nothing new appears as a separate page; the behavior is part of the alerting layer, and the notification itself is the interface.
How to Use It
- Open Integrations and confirm your Slack workspace is connected. If the connection is active, you'll see the workspace name and the channel Context Memo is authorized to post in.
- Choose the channel that should receive call alerts. Pick a channel that the people who actually answer calls are in, not a general marketing channel. The alert is only useful to whoever can act on it in the next thirty seconds.
- Connect the Twilio webhook so Context Memo receives the incoming call event. Once it is live, call events begin flowing to the alerting layer without further configuration.
- Place a test call to the number routed through Twilio. A notification should appear in your selected channel with the call source identified. If the notification arrives without a source, the webhook is connected but the source data is not being passed, which is the first thing to check.
- Assign ownership in the channel. Decide who responds when the alert fires, and whether a thread reply is the expected acknowledgment. The integration delivers the signal; your team decides what counts as handled.
Why We Built It
Customers told us they were monitoring call systems separately from everything else, and that calls were getting missed because nobody was looking at the right screen at the right time. The cost was straightforward: inbound calls are among the highest-intent signals a B2B brand gets, and an unanswered one is a buyer who has already done the research and reached out. When a call did get answered, the person picking up had no context on where the caller came from, so the first two minutes went to questions the system could have answered. Slack is where the team already is. The alert belongs there.
What It Does Not Do Yet
The integration delivers notifications. It does not route calls, record them, or log them against a contact record inside Context Memo. If you need the call written back to your CRM, that remains a manual step or a job for your CRM's own telephony integration; we are not replacing HubSpot or a dialer here, and those tools have more functionality for call lifecycle management than we do.
Source identification depends on what Twilio passes through the webhook. If your call routing does not distinguish entry points, the notification will arrive with the call but without a meaningful source label. Set up distinct numbers or routing rules on the Twilio side first if source attribution matters to you.
There is also no in-app history view for call alerts yet. Slack is the record. If you need a durable log of inbound call volume over time, export from Twilio rather than relying on channel scrollback.
Alerts fire per call with no batching or quiet hours. In a high-volume channel that is noise, so give call alerts their own channel rather than mixing them with citation and crawl notifications.