Adding a channel to support AI: config change or new work?
A new channel like LINE is a config change only if it identifies the customer and the AI's actions stay the same.
Key points
- First: can you identify the customer?
- Second: do the AI's actions change?
- Both same: config change; else new work
- New work: set sign-off bar and checker
Contents
First, check the new channel can identify the customer
A&A perspective
A request to add a channel first splits on one question: on the new channel, can your current setup confirm which of your customers is writing? Adding a channel here means running the support AI your vendor built for you through an entry point other than today's web chat. As a guide, look at companies that already let AI take actions as far as refunds.
From the sources
Anthropic's customer stories include Decagon, which provides AI customer support for businesses. According to the page, Decagon connects to existing ticketing systems and customer databases so that enterprises can offer white-glove support at scale.
From the sources
Its co-founder uses refunds as the example. Rather than giving instructions for a refund, the AI agent checks the customer's eligibility and processes the refund through the payment system.
A&A perspective
The page does not mention identity checks. Still, the order it describes, connecting to the customer record and then checking eligibility, only works if you already know which customer you are dealing with. That is the reading of Automate & Augment (A&A), which writes this article.
A&A perspective
Put as a question for the buyer, it becomes this: can the new channel tell which person in your customer records is writing, without a member of staff stepping in?
A&A perspective
The channel's name does not settle it. A chat placed on the screen members see after they log in can confirm who they are. A chat on the same company's public site, before login, cannot.
A&A perspective
A LINE Official Account, the account a business uses to talk with customers on the LINE messaging app, works the same way. If someone has only added you as a friend, you do not know who they are. If your vendor has already built account linking, where a friend logs in once on your site so their LINE account is tied to their membership, you can.
A&A perspective
So a request that only says "support LINE too" leaves the substance open. Write in the request whether you mean "on LINE, only for customers linked to a membership" or "on LINE, without knowing who the customer is".
List the actions and check whether the AI's actions change
A&A perspective
The second check comes from listing the actions today's AI can take and seeing whether the new channel would open a different set.
From the sources
Anthropic's customer stories also include Chatbase, which provides a platform for businesses to automate customer support with AI. According to the page, Chatbase connects to the business systems a company uses, so AI agents can take actions from checking order status to processing refunds with human oversight.
From the sources
The page says sensitive operations, such as checking invoices and processing refunds, can carry optional human oversight.
A&A perspective
In A&A's view, when answering and acting run on the same platform, adding a channel also adds one more entry point from which the AI can act.
Hypothetical example
Say that on today's web chat the AI can do three things: look up order status, change a delivery date and accept a refund request. For the new channel, you choose which of the three to open, one by one.
A&A perspective
If you only ask for "the same thing", the refund request opens even on a channel where you cannot confirm who is writing. Not choosing one by one has the same result as opening everything.
A&A perspective
The other way is to have the new channel give guidance only and pass anything that needs an action to today's web chat. No actions are added, so the work stays light. Even then, write in the request which requests get passed to the web chat.
A&A perspective
But if the answer to the first check differs from today, guidance only still does not make it a config change, because the sign-off bar for accepting the delivery changes.
Both same: config change; else new work
A&A perspective
If both answers match today's channel, you can ask for it as a config change under your current contract. If either differs, ask for a quote as new work, even if not a single word of the replies changes.
From the sources
The Chatbase page writes about channels by type of customer. For consumers it names messaging channels such as Instagram, and for business customers it separately names an integration with a workplace chat tool. At the top, the same page also lists four channels, including web chat, without that split.
A&A perspective
A&A reads this split as a hint that what separates channels is who is on the other end, not the channel's name. The Chatbase and Decagon pages are both company profiles, and neither says that adding a channel should be ordered as new work. Splitting the request by the two checks is A&A's reading.
Hypothetical example
Here is a hypothetical example. You have the support AI on a web chat for logged-in members and want to add five channels. It is not a real company.
Hypothetical example
Two of them can go as a config change. A chat inside your member app, which needs a login, uses the same login and reaches the same customer record, so you can confirm who is writing. The actions stay as they are; the replies only get shorter to fit the app screen.
Hypothetical example
A LINE Official Account can also confirm the customer if it answers only customers linked to a membership and the linking is already built. Even then, it is a config change only if it opens the same actions as today.
Hypothetical example
The other three are new work. A LINE Official Account where people have only added you as a friend gives you nothing but a display name. On Instagram direct messages (DMs), the account name does not tie to a customer record.
Hypothetical example
A chat on your public site, before login, cannot confirm the customer either. The screen is the same as today, but it sits outside the login.
A&A perspective
The last one, the public-site chat, is the easy one to miss. The screen and the replies are the same as today, so it looks as if settings alone will do. It is still new work, because someone has to split which actions open before and after login.
For new work, write the sign-off bar and checker first
A&A perspective
For a channel you order as new work, write two things before you ask: the sign-off bar, and the person at your company who checks the AI's actions. The sign-off bar means the conditions you check before you accept the delivery (your acceptance criteria).
Hypothetical example
A hypothetical case: your web chat's sign-off bar says "80% of inquiries are closed without a person", and you extend the web chat to Instagram DMs with the same bar.
Hypothetical example
In a DM you do not know the customer's order number, so the AI starts by asking for it. Some customers stop replying at that point, so the share closed automatically drops, whether or not the build is good.
A&A perspective
What you rewrite here, before the 80% figure, is what that figure assumes. Decide whether you measure only requests that include an order number, or whether the bar for DMs is the time to the first reply.
From the sources
The Chatbase page says the company is streamlining its human review into simple one-click confirmations. It also quotes the founder: "Customers want to know there is a human on the other side they can reach if they need to."
A&A perspective
If you open actions to people you cannot confirm, a human check has to come in somewhere. The time it uses is your own staff's, not your vendor's.
A&A perspective
So the request should say who checks, roughly how many items arrive a day, and on which screen. A&A thinks checks are more likely to actually happen when alerts arrive in a tool people already look at every day.
A&A perspective
Who checks and how to undo when AI is allowed to write data or issue refunds is also covered in "How far to let AI write: the checker and undo plan for a first delivery".
Summary
A&A perspective
On the new channel, check whether your current setup can confirm which customer is writing.
A&A perspective
List the actions the AI can take and check whether the new channel opens a different set.
A&A perspective
If both are the same, ask for a config change; if either differs, ask for it as new work.
A&A perspective
For new work, write the sign-off bar and the person who checks the AI's actions before you ask.
A&A perspective
Adding a channel means redrawing, channel by channel, the line between what people handle and what AI does.
Whether a new channel can go as a config change depends on two checks, not on the channel's name. If the new channel can confirm which customer is writing with your current setup and the AI's actions stay the same, ask for a config change under your current contract. If either differs, treat it as new work even when the replies are identical, and write the sign-off bar and the person who checks the AI's actions before you ask.
FAQ
My vendor says it is "just a settings change." Can I go ahead?
Check the two points first. If your current setup can confirm which customer is writing on the new channel and it opens the same actions as today, you can ask for a config change. If either differs, ask for a quote as new work even if the job is light, and write in the request the sign-off bar and the person at your company who checks the AI's actions.
If the new channel only gives guidance, is that a config change?
Not on a channel where you cannot confirm the customer. No actions are added, but sign-off conditions such as the share of inquiries closed automatically no longer hold as they are, so rebuilding them makes it new work.
What if today's web chat does not confirm who the customer is either?
Then the first check is the same as today, so the second check decides. If the new channel opens the same actions, you can ask for a config change. If you want to open a new action that is risky without confirming the customer, such as refunds, the second check changes, so it becomes new work. Include building a way to confirm the customer in that work.
Sources & editorial note
Primary pages read for this article. Publication dates below belong to the sources; access dates record our research.
- Chatbase helps companies deliver instant, personalized customer support with Claude
Anthropic · undated customer-story page; no publication or update date shown
Accessed 2026-10-23 - Decagon delivers white-glove customer service at scale with Claude
Anthropic · undated customer-story page; no publication or update date shown
Accessed 2026-10-23