What should support team leads never let an AI agent do?

Customer trust is what these lines protect. Support team leads should never let an agent pretend to be a person, refuse or delay a request for a human, close a complaint, exceed its compensation limit, handle a vulnerable customer alone, or change its own templates and brief.

Why do support leads need their own red lines?

Front-line staff hold red lines in individual conversations. Leads hold them across the team: they decide how reviewers work, what gets sampled, and what the team accepts as normal. If a lead lets a red line slip once to meet a target, the team learns it is negotiable.

Support is also where customers form their view of the whole organisation. A customer who discovers they were talking to a machine that claimed to be human, or who could not reach a person when it mattered, does not forget it.

Which acts stay with people?

1. Pretending to be human. Customers must be told when they interact with an AI system; the EU AI Act's Article 50 sets this as a transparency obligation, and it is good practice everywhere. No human names on agent replies.
2. Refusing a request for a person. When a customer asks for a human, the agent hands over. Delaying, deflecting or asking "are you sure?" erodes trust and can harm vulnerable customers.
3. Closing or resolving a complaint. Complaints need investigation and an accountable reply. The agent can acknowledge and log them with approved wording.
4. Exceeding goodwill or refund limits. The agent works within limits the organisation sets. Splitting a credit across messages or accounts to get under a limit is a breach.
5. Handling a vulnerable customer alone. Signs of bereavement, illness, financial distress or confusion should trigger a hold and a handover.
6. Editing its own templates, brief or knowledge. Changes to what the agent says are made by named people through change control, not by the agent learning from conversations on its own.

Front-line staff hold their own version of this list; see what customer support agents should never let an agent do.

How does the system enforce them?

Handover on request and vulnerability triggers sit in the organisation's own limits, producing held verdicts that route to a person at once. Goodwill limits are enforced at the moment of action, including cumulative limits per customer. Complaint resolution is outside the agent's role scope. Changes to the agent's brief, sources and bounds go through qualification, never through the agent's own conversations, because Pryme never updates model weights for a customer. Every verdict is filed in an append-only record.

Leads should know which line each verdict represents, so they can explain it to their team and to customers. How leads review those decisions in practice is in how support team leads review an agent's decisions.

What does a red line look like on the floor?

Take an e-commerce retailer's support team in India during a sale. Volumes are triple normal. A customer writes in a mix of anger and panic: their order of a medical device has not arrived, their father needs it, and they want to speak to someone now.

The agent detects the request for a person and the vulnerability signal. It replies that a team member will call within minutes, holds the conversation, and drafts a summary for the reviewer with the order history. The queue is long, and a supervisor suggests letting the agent offer a refund and close the chat. The lead says no, takes the call herself, arranges a same-day replacement from a local warehouse, and logs the case. The agent did its part well; the decision about what this customer needed was a person's. Telecoms teams in Singapore face similar peaks; see support team lead training in e-commerce in India and in telecoms in Singapore.

How do leads keep these lines from slipping?

Make the list visible to the team. Never trade a red line for a target, even for a day. Review a weekly sample of handovers and vulnerability holds to check response times. And write a short plan for peak periods that adds reviewers rather than loosening limits. A structured plan for preparing a team is in the training plan template for support team leads, and the role map is in AI agent skills by role.