Dingbo AI
Dingbo AI · Field notes

Role-Based AI Agents for Customer Service: Five Roles

Updated 2026-11-19 · Shenzhen Dingbo Intelligent Technology Co., Ltd.

Dingbo AI builds and runs AI agents for customer service. You pay per completed task.

Want AI to take over a repetitive job? Get a free assessment

Email only. We reply within 24 hours, free of charge.

One AI assistant that "handles support" is hard to manage, because nobody can say what it is responsible for. The system in our case study is organised the way a support team is: by role. Each role is a job with a scope, a list of things it passes on, and a named person who answers for it. This page describes the five roles as they run today for an e-bike brand with nine storefronts.

The five roles

A role is not a separate chatbot. All five share one knowledge base, one order lookup and one set of reply principles. What differs is the scope: which requests the role takes, which solutions it may propose, and where its cases go when they leave its scope.

What a role does with one case

Inside every role the work has the same shape. The AI distils the incoming message and the earlier thread into structured facts with sources, checks the order, the shipment and the knowledge base, proposes a solution from a fixed list, and writes the reply in the customer's language. The list of solutions is short and named: answer the facts, ask for missing information, troubleshoot, reassure about delivery time, reship a part, reship a missing item, arrange a local repair, change an address, check with the carrier, return and refund, compensate. A solution that is not on the list cannot be proposed.

Each role has an owner

Every role has a named person responsible for it. Approved work then goes to an execution list split by what a person has to do, and each part of that list has its own owner:

The split follows the action a person must take, not where the request came from. A refund agreed in chat and a refund agreed by email land in the same place.

When the owner is offline

When the responsible person is offline, the AI keeps checking facts and preparing plans and drafts. It does not carry out anything that needs that person's decision. When they start work, the queue is ready to review. Simple replies that need no decision keep going out: measured on 19 November 2026 over the previous 30 days, the AI sent 3,331 email replies on its own, and half of them left within 6.3 minutes of the customer's email.

Two buttons for the agent

An agent reviewing a draft has two choices. The first sends the reply and keeps the ticket open, for cases that are still a conversation. The second sends the reply and closes the ticket, and it asks one question first: does this case need someone to do something? If yes, the agent confirms the solution record, and the task goes to the execution list and to the team's group chat at that moment. If no, the agent picks the reason, such as remote troubleshooting, and the record is filed. Every close is tied to one record either way.

A second pair of eyes on what the AI did alone

Replies the AI sends on its own fall into two kinds. A plain answer is filed and can be spot-checked. A reply that carries a solution or asks someone to act goes to an "AI review" queue first, sorted by type: pre-sales questions, partial refunds and spare parts, cancellations, order changes, invoices, and product questions after delivery. A reviewer approves each one before anything is executed, writes an improvement note when something is wrong, and can pass the case to an agent.

The AI steps back when a person steps in

Once an agent has replied on a ticket, the AI stops sending on that ticket by itself. There are two exceptions, both narrow. When the customer accepts the solution the agent proposed, the AI confirms and closes the ticket in the agent's name. When the customer writes again after the ticket was closed, it counts as a new round and is judged from the start.

Why roles beat one general assistant

Who this fits

Brands with a support team of several people, more than one sales channel or country, and cases that pass between people before they close. If one person answers everything from one inbox, start with a single role, usually orders and shipping, and add roles as volume grows.

The approval lines are in human-in-the-loop AI agents, and the handoff between roles and people in when AI hands over. The free plan maps your team's roles within two working days.

Which job eats the most hours on your team? Tell us in one line and we will sketch a plan for free

We connect to the systems and documents you already use, the AI works through your process, and your people review and approve. You see real numbers from a pilot before you pay for anything, then you pay for completed work.

Or email us directly: yzh317179958@163.com

Free assessmentReply within 24h