Memory
It already knows who's calling.
A caller shouldn't have to say their email, their order number, and their problem a third time. Zumu recognizes a returning caller, on the phone, in the widget, or over email, and carries the verified facts forward so the agent already has them.
- Recognizes returning callers on the phone, the widget, or email
- Carries verified facts forward, not a raw transcript
- Works across calls, chat, and the website widget
- No one repeats themselves
- Phone, widget, and email. Never SMS.
- Channels
- A confirmed identity, a verified fact, an open issue
- What carries forward
- A raw transcript nobody asked it to keep
- What does not
The returning-caller ledger
The call rings. The agent already has the file.
A phone number comes in. The agent resolves it to a caller it already knows, pulls one verified fact in from each of three prior interactions, and the greeting completes with a name and the open issue attached, before the caller says a word.
Inbound call
+1 •••-•••-0148
Renata Cole, verified by phone number and email on file
Verified email on file, confirmed by the caller
Order 48213 flagged: wrong item received
Replacement confirmed shipped, tracking sent
What the agent says
Hi Renata, I can see the replacement for order 48213 shipped yesterday. Calling to check on that?
No one repeats themselves. Not their email, not their order, not the problem they already reported.
How memory is built
A fact only becomes memory once it's confirmed
Memory isn't a copy of the transcript. It's the short list of facts the agent actually checked with the caller.
- 01
A fact comes up
On a call, in the widget, or over email, the caller states something: an email, an order number, a problem they already reported.
- 02
The agent confirms it
Before anything is written down, the agent reads the fact back and the caller confirms it is right.
- 03
The confirmed fact becomes memory
Only the confirmed fact is saved, tied to that caller, ready for the next call, chat, or email.
What memory is not. A raw transcript dump nobody asked it to keep. If a fact was never confirmed, it never becomes memory. The small talk around it never does either.
Cross-channel proof
Same caller. Three doors. One memory.
A caller can start on the phone, pick it back up in the widget, and follow up by email. The agent reads and writes the same memory no matter which door they use.
Phone
A call to the main line
Widget
A chat on your website
Email
A reply to a thread
Whichever door the caller uses, the agent reads and writes the same memory. A fact confirmed on the phone is already there when the next contact comes in on the widget.
Phone, widget, and email today. Not SMS.
A short word on trust
What gets kept, and who decides
- Verified facts only
- Memory holds what a caller confirmed, not a guess the agent made or a line pulled out of context.
- You decide what counts as sensitive
- What gets remembered, and how it's handled, is a configuration conversation with your team, not a fixed setting we picked for you.
- Traceable, not hidden
- Every fact in memory traces back to the call, chat, or email it came from. Nothing shows up without a source.
Book a demo
Bring a caller who calls back.
Bring a real returning-caller scenario: a repeat order, a reopened case, a follow-up email. We will show you what the agent already knows the second time they get in touch.
- No credit card for the demo
- Your own scenario, not a canned one