In regulated industries (healthcare, financial services, insurance, telecoms), AI customer service has to do everything an unregulated deployment does plus three more things: prove who the customer is, log every decision in a way an auditor can reconstruct, and stay within rules that vary by jurisdiction and product line. The shape of the work is similar; the constraints on it are heavier.
A patient calls a hospital line about a prescription. A consumer calls a bank about a charge. A customer calls an insurer about a claim. All three want a quick answer. Each one is also a regulated interaction, where the answer the AI gives or the action it takes is subject to compliance, audit, and recourse that an e-commerce customer service team can largely ignore.
What people in the field are saying
kdschemin has written about how AI is being put to work in serious-stakes domains, including "AI is reading X-rays and saving lives". Service Matters covers the contact-centre side of regulated work, including security: "Is your contact centre a cybersecurity...".
What is different about regulated CX?
Three things mainly. Identity and verification: the AI cannot just trust a session; it has to satisfy the regulator's bar for proving the customer is who they say they are before doing anything sensitive. Audit and reconstruction: every action has to be reconstructable, with inputs, outputs, model decisions, and timestamps. Scope and disclosure: there are statements the AI is allowed to make, statements it is not, and disclosures it must make to the customer.
Why does this make deployment slower?
Each of those three adds requirements that vendor defaults often do not meet. Verification has to be plugged into the regulated identity stack. Audit logs have to be retained for the required period in the required format. Scripts and prompts have to be reviewed by compliance before launch, and re-reviewed after changes. The pace of deployment is set by the slowest of these, not the fastest.
Where do regulated industries gain?
Where the constraints already exist for humans. Banking already trains agents on what they can and cannot say; AI is another agent that has to be trained the same way. Healthcare already runs disclosure scripts; the AI says the same script. Insurance already records every claim interaction; the AI's interactions are recorded the same way. The infrastructure for regulated CX is more developed than for retail, which makes it ready to absorb an AI agent.
What is the practical pattern?
Start narrow. Pick one regulated interaction with a well-understood compliance shape (a balance inquiry in banking, an appointment booking in healthcare). Wire identity verification through the existing stack. Capture the full audit trail. Get compliance sign-off on the prompt and disclosure. Launch. Use what you learn to build the second one. The vendors with stronger regulated CX practices follow exactly this pattern, not "deploy everywhere fast."
Related: the field note on HIPAA and AI in healthcare support, contact-centre AI security, and AI guardrails in customer service.