Skip to main content

UK Regulators Tell Firms Launching Personal AI Agents to Come to Them First, and Say Existing Law Already Applies

The CMA, FCA, ICO and Ofcom wrote to ministers on 16 November about personal AI agents due to launch in the UK. What the letter is reported to say and a practical checklist for firms that deploy agents or receive customers' agents.

KBY News Desk7 min read
A diverse group of professionals working together in a modern conference room with laptops.

The heads of four UK regulators wrote to ministers on Monday 16 November to say that several personal AI agents are about to launch in the UK, that not every developer has talked to the regulators early or openly, and that the rules already on the books apply to these products. The letter, sent through the Digital Regulation Cooperation Forum (DRCF), came from the Competition and Markets Authority, the Financial Conduct Authority, the Information Commissioner’s Office and Ofcom. It was reported on 17 November, and it reads as a warning to two groups at once: the firms building agents that act for consumers, and the firms, banks and telecoms providers in particular, whose customers will use them.

This is a look back at a letter from five days ago, written because its practical consequences have not been spelled out for the people who will have to deal with them: IT teams that deploy AI agents, and organisations whose websites, call centres and payment systems will soon be dealing with other people’s agents.

#What the letter says, as reported

We could not read the letter on the DRCF’s own site, which refused automated access, so what follows is based on two published accounts of it: a report by the UK AI newsletter Resultsense, which quotes and summarises the letter, and a summary on LexisNexis’s legal news service. Where the two agree, we say so. Nothing here should be read as a quotation from the letter itself.

According to Resultsense, the letter went to the Chancellor, the culture and business secretaries and the Minister for AI, and it was published by the DRCF. It describes personal agents as a step change in how AI is used and says there are real questions about how well the public understands how they work. The regulators see benefits, and single out agents that help consumers save money on everyday purchases. Their worry is the run-up to launch: Resultsense reports the letter saying some firms have engaged early and constructively but that engagement has not been consistently early or open across all the relevant regulators. The regulators say they will not hesitate to use their powers.

Both accounts list the same expectations. Firms must meet their legal and regulatory obligations before launch, including checking whether their service needs authorisation or registration, and must assess the risks and put safeguards in place. The letter names three risks to address: fraud and scams, personal data being shared in ways users would not expect, and misleading recommendations, decisions or information. Agents must leave users in control, with a clear understanding of the risks specific to agents, and must not undermine the operational resilience of the systems they connect to. LexisNexis adds that changes to a product have to be assessed against the same requirements and that engagement with regulators continues after launch.

The second audience is anyone who does deals with agent providers. Resultsense says the letter addresses firms that strike commercial arrangements with agent providers and names financial services and telecoms firms. Their own obligations to customers carry on when those customers act through an AI agent. LexisNexis puts it the same way: prospective commercial partners, including financial services firms, should engage early, and their obligations apply when customers use agents.

The letter follows a joint DRCF statement in October. CIO’s report of that statement quotes it as saying that existing legal and regulatory frameworks apply to personal AI agents, including competition, consumer and data protection law, online safety, financial services, payments and cyber security requirements, and that an agent’s autonomy “does not diminish the responsibility of organisations that deploy it”. Resultsense’s reading is that writing to ministers a few weeks after that statement suggests the regulators expect launches soon. That is their interpretation, not something the letter says, and we mention it as such.

#Our view: a short letter that moves liability to the deployer

As reported, the letter announces no new rule and leans on obligations that already exist. What it does is close an excuse: on the position CIO reports from October, an agent’s autonomy does not reduce the responsibility of the organisation that deploys it, and the regulators are telling firms in advance that they will not accept “the agent did it”. That matters most for the IT teams who are, right now, switching on agents that act inside business systems: Microsoft’s agents in Copilot, Google’s in Workspace, and the agent builders that sit on top of them. We have written before about how fast those defaults are changing, for example when Claude was enabled by default in Microsoft 365 Copilot from 9 December. The letter is about consumer-facing agents, but its logic applies equally to an agent that answers customers or moves money on behalf of your staff.

There is a second reading, for organisations on the receiving end. Customers will arrive with agents in tow: an agent that books a table, asks for a refund, chases a delivery or compares your price. The regulators say your obligations to the customer do not change because an agent is in the middle. The Register, reporting on a different story on 20 November, noted how differently large retailers and airlines are already treating agent traffic: it says Amazon has blocked shopping agents from its main site, Walmart has invited third-party agents in through its own gateway, and United Airlines has banned transactions from unauthorised AI bots. We think most UK organisations will end up somewhere between those poles, and that the letter pushes them to decide on purpose and not by default.

We would expect the first real enforcement on this subject to come from the data protection side, because two of the three risks the regulators name, personal data shared unexpectedly and misleading outputs, sit most directly in that territory. That is a prediction. What would prove us wrong is a first case brought by the FCA or CMA over an agent that moved money or steered a purchase.

#What to do on Monday morning

  1. Make a list of every AI agent your organisation runs or has switched on, who approved it, what systems and data it can reach, and whether it can act (send, buy, delete, approve) or only suggest. The regulators’ language assumes you can produce it.
  2. For each agent that talks to customers or touches money, write down who is accountable for what it does, in your own organisation and in the supplier’s contract, and where the logs are that would show what it did and on whose instruction.
  3. Check what personal data each agent sends out of your tenant and where it is processed. “Shared in ways users would not expect” is the regulators’ phrase, as Resultsense reports it, and it is the one most likely to catch an agent that was enabled for convenience.
  4. If you take payments, bookings or support requests online, decide your position on customers’ own agents: allow, allow with limits, or block. Check your terms of service says the same thing, and ask your fraud team how an agent-initiated request is verified.
  5. Set rate limits and failure behaviour on any internal API that an agent can call. The letter says agents must not undermine the operational resilience of the systems they connect to, and a runaway agent hitting a booking system is the easy example.
  6. If you are a bank, building society, insurer, telecoms provider or a supplier to one, ask the regulators you deal with whether they expect you to engage ahead of an agent partnership. LexisNexis’s summary says the letter asks prospective commercial partners, including financial services firms, to engage early.

For small businesses, the useful message is simpler. If you use an AI tool that can send emails, place orders or make changes on its own, you are responsible for what it does. Check what it is allowed to do, and turn off the actions it does not need. If a supplier offers to connect an AI agent to your accounts or customer list, ask them in writing who is responsible if it makes a mistake and where the record of its actions is kept.

#What is not yet known

We do not know which products the regulators have in mind, when they launch, or whether the letter will be followed by formal guidance. We have not been able to read the letter itself, so details such as the exact wording on authorisation and registration may differ from the summaries we have cited. We will update this story if the DRCF’s own page or a regulator publishes more.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Resultsense: Regulators warn ministers on personal AI agent launches (17 November 2026)resultsense.com
  2. 02LexisNexis: DRCF regulators set out expectations for firms launching personal AI agents (17 November 2026)lexisnexis.co.uk
  3. 03CIO: Enterprises must take blame for their AI agents' mistakes, say regulatorscio.com
  4. 04The Register: Signal slams door on prying AI agents to protect privacytheregister.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on UK Regulators Tell Firms Launching Personal AI Agents to Come to Them First, and Say Existing Law Already Applies. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.