Why Regulated Conversations Are Different
July 26, 2026
Every regulated business handles important customer conversations. Most handle them the same way an unregulated business would: with general-purpose communication tools, partial visibility, and the assumption that compliance is a layer you add on top.
Of conversations are missed with manual call review
More coverage across risk, coaching, and revenue opportunities when using Spoke
Every regulated business handles customer conversations. Most handle them the same way an unregulated business would: with general-purpose communication tools, partial visibility, and the assumption that compliance is a layer you add on top. This assumption is why regulated businesses keep having the same compliance failures, the same performance gaps, and the same management blind spots. It is also why fixing them is harder than it looks.
The moment usually arrives unexpectedly. A regulator asks a question, or a customer complaint surfaces, or a manager reviews a call they were not supposed to need to review, when someone in the room realizes that the conversation that matters most is one the organization cannot fully account for.
Sometimes it is a broker's mobile call that was never captured. Sometimes it is a claims adjuster's text message that sets an expectation the firm cannot now document. Sometimes it is a patient conversation that should have followed a specific protocol and did not, and nobody knew until it became a complaint. Sometimes it is just the quiet recognition that a significant proportion of the organization's most consequential conversations are happening somewhere the management team cannot see.
The reaction is usually to treat it as a specific problem with a specific fix. Tighten the mobile communication policy. Improve the QA sampling rate. Run another training program. These are not wrong responses. They are just insufficient ones, because they treat symptoms rather than the condition underneath.
The condition is this: most regulated businesses are using communication infrastructure designed for a different problem. Their phone systems were built for connectivity. Their compliance programs were built for documentation. Their coaching programs were built for the conversations their managers have time to review. None of these systems were built for the actual challenge of regulated communication. Which is not connecting people, or documenting conversations after they happen, or reviewing a sample of what was said. It is managing conversations as they happen, across every channel, at full volume, in a way that is simultaneously compliant, visible, and continuously improving.
That is a harder problem. And it is the problem that distinguishes the regulated businesses ahead of the curve from the ones reacting to it.
What makes a regulated conversation different from any other business conversation?
The difference is not the subject matter, the channel, or the people involved. It is the weight the conversation carries after it ends.
In most business contexts, a conversation is ephemeral. It is a means of exchanging information, reaching agreement, or moving something forward. Once it has served that purpose, it recedes. The outcome matters. The conversation itself, as an artifact, largely does not.
In a regulated environment, the conversation does not recede. It becomes evidence of what was represented, what was disclosed, what was agreed, and what obligations were created. It may be reviewed months or years later: in a regulatory examination, a customer dispute, or a legal proceeding, by people whose interest is in what was said rather than what was decided.
A financial advisor speaking with a client about a product recommendation is creating evidence of whether suitability was properly assessed and appropriate risk disclosures were made. An insurance adjuster explaining coverage to a claimant is creating evidence of what the firm committed to and under what terms. A care coordinator following up with a patient about a treatment plan is creating evidence of what instructions were given and whether they met the required standard. In each case, the conversation is simultaneously serving an immediate purpose and creating a permanent record that may define the organization's legal and regulatory position long after the customer has forgotten what was said.
A financial advisor speaking with a client about a product recommendation is creating evidence of whether suitability was properly assessed and appropriate risk disclosures were made. An insurance adjuster explaining coverage to a claimant is creating evidence of what the firm committed to and under what terms. A care coordinator following up with a patient about a treatment plan is creating evidence of what instructions were given and whether they met the required standard. In each case, the conversation is simultaneously serving an immediate purpose and creating a permanent record that may define the organisation's legal and regulatory position long after the customer has forgotten what was said.
When conversations carry this weight, three things follow:
- They must be captured: not selectively, not by sample, but completely, across every channel the conversation might use.
- They must be supervised: reviewed against the standards the regulatory framework sets, in a timeframe that makes supervision meaningful rather than historical.
- They must be improvable: the conversation record should not just be evidence and compliance, it should be the basis for making future conversations better.
Most regulated businesses do the first thing partially and inconsistently. Most do the second thing inadequately. Almost none do the third thing systematically.
Why do general-purpose communication tools fail in regulated environments?
General-purpose communication tools — the phone systems, messaging platforms, and collaboration tools most businesses use — were designed to solve a connectivity problem. They are very good at it. The problem is that connectivity is not the constraint in a regulated environment. Compliance is the constraint. Visibility is the constraint. The ability to learn systematically from conversations is the constraint. General-purpose tools were not built around any of these because the market they were built for did not have them.
The consequences are structural and predictable.
The capture failure
General-purpose phone systems capture what happens on the system. They do not capture what happens when a staff member picks up their personal mobile instead. General-purpose messaging platforms capture conversations within their ecosystem. They do not capture the WhatsApp thread running alongside them. The coverage gap that general-purpose tools produce in regulated environments is not a configuration problem, it is an architecture problem. The tools were built to capture conversations in their system, not all conversations regardless of system.
The supervision failure
General-purpose call recording gives you a recording. It does not give you a compliance review, a coaching output, or a risk flag. Taking a recording and turning it into supervisory intelligence requires a separate process, usually a manual QA team reviewing a sample of recordings and producing a report. This process is slow, inconsistent, and covers a fraction of the conversation volume. The regulatory obligation is supervision. General-purpose tools provide raw material for supervision. They do not provide the supervision.
The improvement failure
The conversations a regulated business has with its customers are, in aggregate, the most detailed operational record the business has. They contain every compliance gap, every coaching opportunity, every sales technique that works and every one that does not, every customer signal that predicts a complaint or a cancellation or a referral. Almost none of this intelligence is extracted and used by organizations relying on general-purpose tools and manual review.
12x — The ratio of customer conversations that happen in a typical regulated business to the conversations reviewed in any meaningful way by management. For a contact center handling 50,000 calls a month with a 3% manual QA rate, 48,500 conversations generate no supervisory intelligence whatsoever. (Source: Spoke analysis of customer operational data, 2024–2025)
What does the status quo actually cost?
The cost of inadequate conversation management in regulated organizations is distributed across three areas. Most organizations see the costs in isolation without connecting them to the common root cause.
Regulatory and legal cost
The most visible cost is direct enforcement. Fines for communication record failures in US regulated industries have exceeded $2 billion since 2020, primarily involving conversations that happened on channels firms were not monitoring. These are not fines for bad conversations. They are fines for conversations that could not be produced. Below the fine level, there is a larger and less visible cost: the settlement premium firms pay in customer disputes because they cannot produce the communication records that would establish what was actually said. A firm that cannot produce the record of an advisor's conversation with a client cannot establish whether the advice was suitable. The settlement value of that dispute reflects the inability.
Performance cost
In regulated sales environments, the performance gap between top performers and average performers persists at levels that training and conventional coaching have not closed. The coaching is based on a sample too small to identify what top performers actually do differently at the level of specific conversation moments. The performance gap is a visibility gap wearing the clothes of a talent gap. In regulated contact centers, the same dynamic appears in quality scores, complaint rates, and customer satisfaction metrics. The coaching program produces improvement in the conversations it reviews. The improvement does not generalize to the conversations it does not review.
Management cost
The management time consumed by inadequate communication infrastructure is significant and consistently underestimated. A team leader in a regulated contact center spending six hours a week reviewing calls manually is spending six hours not developing their team. A compliance officer spending three days responding to a records request that should have required three hours is spending three days not managing compliance risk. The bandwidth that inadequate infrastructure consumes does not appear on a P&L. It is real and it is large, and it is the most recoverable of the three costs once the infrastructure problem is addressed.
What does it look like to manage regulated conversations properly?
Regulated businesses that manage customer conversations effectively share a set of characteristics worth describing, not as best practices, but as a coherent operating model.
Conversations are infrastructure, not events
The first shift is treating the conversation as the entity the organization is responsible for managing, not just the outcome or the record. In practice, this means including every channel a customer might communicate over as managed infrastructure that works as the conversation happens, not retrofitted into it afterwards. For example, the mobile phone a field advisor uses is inside the compliance perimeter. The WhatsApp message a care coordinator sends is captured. The call a broker makes from home is recorded and supervised. Not because a policy says it should be, but because the infrastructure makes it the default.
Supervision is automated, not sampled
The second shift is from supervision as a manual sampling process, to supervision as an automated and comprehensive one. Automated review of every conversation against defined compliance and quality standards within seconds of the conversation ending, is not an incremental improvement on today's manual call review / call QA process, it is a magnitude shift in positive outcomes. Today's compliance exposure that lives in the 97% of conversations that a manual QA process cannot review, is not a program shortcoming, it is a structural consequence of trying to do a volume job with a manual process limited by headcount and cost.
Improvement is continuous, not periodic
The third shift is from improvement as a periodic intervention; the training day, the coaching program, the performance review; to improvement as a continuous output of the conversation infrastructure. Every conversation reviewed automatically generates coaching intelligence. Every pattern identified across the full conversation population (every call) becomes available for targeted coaching. The top performer's approach, captured across hundreds of conversations, becomes teachable. The organization is not just managing conversations to avoid problems. It is using them to get better: continuously, measurably, at a rate that compounds call after call, day after day.
Where does the technology help and where does it fall short?
The technology that makes comprehensive conversation management possible in regulated environments is real and has matured significantly. It is also frequently oversold, and the overselling creates implementation failures that damage trust in the category. A clear-eyed view of what works and what does not is more useful than an optimistic one, especially in regulated environments where the stakes of an implementation failure are not just operational, but potentially regulatory and punitive.
What works reliably
Automated call capture and retention at scale works. The infrastructure for routing business calls and messages through compliant, recorded channels, regardless of device or location, is mature and deployable. The coverage gap is a solvable problem with current technology.
Automated scoring of conversations against defined, rule-based criteria works. Whether a required disclosure was made, whether prohibited language was used, whether a specific workflow step was completed. These are questions automated review answers accurately at scale. The rubric needs to be translated from human judgment into observable criteria, which requires care, but once done, the scoring is consistent in ways that human call reviews and QA can never be.
Pattern identification across a large conversation population works. Identifying a specific objection that is handled differently by top and average performers, or that disclosure omissions are concentrated in a specific time window or product category, is something automated analysis does well at sufficient volume.
Personalized coachng that drives measurable performance improvement works well. Today's technologies are able to identify patterns based on best performers, and elimanate 100% of manager workload (call reviews and creation of coaching plans), making automated, personalized, and regular coaching a reality. Approaches using regular micro-coaching and peer-led examples works extreamly well, offeirng people concrete examples while the target conversation is fresh in their mind – not two months after the fact.
What does not work as advertised
Automated nuanced judgment does not work reliably. A system that accurately scores whether a disclosure was made cannot accurately score whether it was made in a way a reasonable customer would have understood. A system that identifies risk language patterns cannot accurately assess whether the risk language was appropriate given the conversation's context. These judgments require human review, and the AI systems that claim to replace human judgment in these areas are overclaiming. Good platforms will flag probable risks for human review.
Full replacement of human call QA does not work reliably. The right model is automation handling volume and humans handling complexity. A QA team reviewing the 5–15% of conversations that automated systems flag for attention, rather than sampling 3% at random, is doing higher-value work, not redundant work.
The regulated businesses that have implemented conversation management technology most effectively are the ones that calibrated their expectations against what it actually does. The coverage problem is solved. The supervision problem is substantially improved. The manager time problem, eliminated. The nuanced judgment problems are not automated away, they are made more manageable by concentrating human attention where it is genuinely needed.
Questions we get asked
We have a compliance program already. Why is this not enough?
Most compliance programs address the obligation as it was written: they document what was required, retain what was required, and review what they have capacity to review. The gap is between what the program was designed for and where conversations are actually happening. If the program was designed for desk phone calls and a significant proportion of your team's customer conversations happen on personal mobile devices, the program is compliant within its own scope, and non-compliant with the actual communication environment. However, the main gap is the missed opportunities that come with seeing and understanding everything inside your business. Missed revenue, new risks, improved people and process. The question is not whether you have a program. It is whether the program reaches all the conversations it is supposed to reach (especially on mobile phones), and what you learn and improve.
Is this a problem that clearer regulation will eventually solve?
Regulatory clarity helps but does not solve the infrastructure problem. The SEC's off-channel enforcement actions did not happen because firms were unclear about whether personal mobile communications needed to be captured. They happened because firms knew the obligation existed but lacked the infrastructure to meet it. Clearer regulation with the same infrastructure produces the same gap. You need to close that gap.
Where do you start if the gap is large and appetite for a large program is limited?
Start with coverage. The coverage gap, conversations happening on channels the organization does not monitor, is both the most serious exposure and often the most straightforward to close. Extending compliant communication infrastructure to mobile and field-based staff does not require replacing the existing call review and QA program, coaching framework, or compliance team. It often does not require you changing phone systems. There are simple solutions to close the gap between where conversations are happening and where the compliance program can reach. Everything else can follow.
How do you make the internal business case for this investment?
The case has three components that work differently at different levels of the organization. For compliance and legal teams: the cost of adequate communication infrastructure compared to the cost of a single significant enforcement action or litigation settlement is favorable in almost every regulated sector. For the operations team: the management time recovered from manual call reviews / call QA and the performance improvement from better coaching. For the commercial team: the value of closing the performance gap between top performers and average performers in regulated sales environments. The full benefit does not rest on any single one of these. In most regulated businesses, at least two of the three are compelling on their own.
What new compliance trends should you be concerned about as a regulated business?
We are seeing an increasing rise in litigation and successful class-action lawsuits. What is worrying is that these actions often fall outside what a regulated business might consider to be 'regulated'. There has been a serious rise in TCPA (Telephone Consumer Protection Act and the Telemarketing Sales Rule (TSR) fines recently. And it's not the banking watchdogs or the healthcare regulators who are bringing action or handing down fines, it's private law firms with deep pockets. In a lot of these cases, the volume may be small, a few thousands people sent an SMS message without opting in. Companies need to be thinking about compliance and regulation as a holistic program, an opportunity to improve revenue, people, and process, not as a mandate that has to be met to a minimum standard.
"The rich data we get from Spoke now allows us to make pretty exceptional decisions."
See how Spoke closes your compliance gap on mobile phones
Book time with our sales and solutions engineers to see how Spoke can turn your compliance gap into a revenue generating continuous business improvement engine.
