There is a sentence being said in Australian contact centres right now, thousands of times an hour. It is polite. It is well meant. It costs more than any piece of software you will buy this year.
"Sorry, can you repeat that?"
Nobody puts it on a dashboard. There is no report that adds it up. But every single time it gets said, a customer learns something unflattering about your business: that everything they just told you has been thrown away.
Forty seconds that never show up in the numbers
Picture a customer. She gets a text about an overdue payment. She taps the link, keys in her account number, her date of birth and the last four digits of her card. The page hangs. She gives up and rings the number in the message.
The IVR asks for her account number. She keys it in again. Ninety seconds of hold music. Then a human comes on the line, and he is lovely, and he asks for her account number.
She has now identified herself three times, to one company, about one problem. She has not yet been allowed to say what the problem is.
Here is the uncomfortable part. Nothing in that journey registers as a failure. The message was delivered. The IVR did its job. The call was answered inside SLA. Average handle time looks respectable. Every system reports success, and the customer hangs up thinking you are a shambles.
Repeating yourself is a tax on bad architecture
This is not a soft problem, and it is not a training problem. It is a measurable operational cost.
Gartner research found that 62% of customer service channel transitions are "high effort", and that easy transitions save around four minutes of agent time per journey, largely because agents stop having to re-collect information the customer has already handed over. Four minutes. Multiply that by your monthly contact volume and you have the budget for a fairly serious platform.
The same research turned up something more interesting. Of the customers who got an easy transition into an assisted channel, 74% said they would go back to self-service next time. Read that twice, because it inverts the usual assumption. Continuity is not just a nicety you extend to the customer. It is the thing that makes your cheaper channels work.
Gartner has also been blunt about the flip side: customers do not actually mind switching channels, so long as the issue gets resolved in one continuous interaction and their context travels with them. The channel switch was never the villain. The amnesia was.
The channel switch was never the villain. The amnesia was.
Why nobody has fixed it
Because it does not appear anywhere.
Contact centre reporting is built to measure what happens inside a channel. Calls answered. Messages delivered. Chats resolved. First contact resolution, which sounds like it should catch this and does not, because it counts contacts within a channel rather than a customer trying three of them.
The repetition happens in the gaps between the systems, and the gaps do not have owners. Marketing owns the SMS platform. IT owns identity. Operations owns voice. Each of them is hitting their numbers. The customer is having a terrible time, and there is no single dashboard on which that terrible time is visible.
So when the annual planning cycle comes around, the money goes into the channels, because the channels have metrics and metrics attract budget. And the gaps stay exactly as they are for another year.
Why the memory keeps getting dropped
Walk into most mid-market contact centres and you will find four systems, usually from four different vendors and bought in four different years, doing four jobs very competently and in total isolation.
- Messaging lives in a bulk SMS tool that marketing bought.
- Voice lives in the contact centre platform.
- Email lives with whoever owns the marketing automation stack.
- Identity checks live in something bolted onto the login page by IT in 2019.
Each one is fine. None of them tells the others what just happened. So the memory of the conversation gets split into four pieces and then quietly deleted, over and over, every time the customer moves.
Your customer does not experience four channels. She experiences one company, doing a poor impression of an organisation that knows who she is.
Memory is a decision, not a feature request
You do not buy memory. You decide to have it, and then you build for it. That means being honest about the four things a conversation has to hold on to.
Who it is. Identity is the foundation, because memory you cannot trust is worse than no memory at all. Verified identity, handled properly at the front door, is what makes it safe to carry context forward at all. Twilio Verify does this work quietly, across SMS, voice, email and silent network signals, so the customer proves who she is once and is trusted afterwards.
What was said. The words themselves, wherever they were said. Messaging, voice and email are not three conversations, they are three transcripts of one. On Twilio's platform they are treated that way: Twilio Messaging, Twilio Voice and Twilio SendGrid feed one identity-resolved record in Twilio Conversation Memory, whichever channel the words arrived on.
Where it happened. Channel is context. A customer who has already tried self-service twice is telling you something before she says a word.
What it means. This is where the memory meets the person answering the call. Inside the contact centre, NeonNow IQ takes the context Twilio holds and turns it into intent, sentiment, resolution state and a summary the agent can use in three seconds. That is the difference between an agent who has a wall of text in front of him and an agent who already knows why she is calling.
What it looks like when the memory holds
Run the same story again, with the memory intact.
She gets the text. It carries a registered, branded sender ID, so she can see at a glance that it is really you. She taps the link and verifies herself once. The page hangs, because pages sometimes hang. She rings the number.
This time, the call opens with her already identified, because the verification she completed ninety seconds ago is still valid. The agent sees the payment she was trying to make, the two fields she managed to complete, and a one-line summary of the intent. He says: "Hi Sarah, I can see you were partway through sorting the July payment. Shall we finish it off?"
Same customer. Same four minutes, except now they belong to her instead of to the process. That is the idea behind NeonNow Outreach: messaging, voice, email and identity from Twilio's customer engagement platform, delivered as one product for Australian contact centres, with NeonNow IQ putting the context in front of your agents and our team looking after the set-up. Twilio brings the platform and the memory. We bring the contact centre know-how and the local delivery. And your compliance team gets names it already knows.
None of this is exotic. It is not an AI moonshot. It is the deeply unglamorous work of making sure that what a customer tells you at 9.02am is still known to you at 9.04am.
In Australia, the stakes have already gone up
Since 1 July 2026, text messages sent with an unregistered brand name at the top have arrived on Australian phones labelled "Unverified", grouped in the same thread as the scams. The SMS Sender ID Register was a good thing and it was overdue. It has also quietly raised the stakes on everything above.
Because the message is now carrying an identity claim. It says, at the carrier level, this is really us. And if the customer taps through on that message and lands in a system that immediately asks who she is, you have made a promise in the first three seconds and broken it in the fourth.
Identity and memory are the same problem wearing different hats. You cannot carry context forward safely unless you know who you are carrying it for. And once you do know, there is no excuse for asking again.
The sentence you want to hear instead
Here is the test I would apply to any customer engagement stack, and it takes about ten seconds.
Follow one customer through one problem across two channels. Count how many times she has to say something she has already said. If the answer is more than zero, you do not have a channel problem, a staffing problem or an AI problem. You have a memory problem, and it is costing you money in a place your reporting cannot see.
The goal is not to eliminate the phone call. The goal is to eliminate the apology at the start of it.
Find out what your conversations are forgetting
We built a short scorecard that walks through exactly this: where your conversations lose their memory, what it is costing you, and which fixes are worth doing first. It takes about five minutes and you get your results immediately. [SCORECARD LINK]
If you would rather just see it working, book a demo and we will run one customer journey end to end, across messaging, voice and email, without asking her to repeat herself once. Or talk to our team if you want to start with a conversation rather than a screen share.
.svg)
