AI Chat Support on Website and Mobile App: Real Split
A brand with a website and a mobile app has at least three chat entry points: the web page, the iOS app and the Android app. Customers use them for different things, and one AI agent has to serve all three with the same knowledge. These are the numbers from a deployment for an e-bike brand, counted on 19 November 2026 for the previous 30 days, and the rules the chat runs on.
Where 15,725 conversations came from
- Website: 11,010 conversations.
- Android app: 2,865.
- iOS app: 1,850.
Three in ten conversations started inside the app. People in the app already own the product and ask how to use it. Website visitors include people who have not bought yet. One agent covers both, and it knows which entry point a conversation came from.
Nine storefronts, one agent
The same 15,725 conversations by storefront: United Kingdom 2,684, France 2,601, Italy 2,573, Germany 2,390, Spain 1,705, the EU store 1,695, the Netherlands 1,171, Poland 696, United States 202. The agent answers in the customer's language and applies the prices, shipping options and policies of the store the customer is on. A question about delivery time from the Polish store and from the UK store gets two different answers, both correct.
What the chat answers
A chat reply goes out the moment it is written and cannot be taken back. So the chat answers facts and published policy:
- product questions, specifications and compatibility,
- stock,
- order and shipping status, after confirming the order belongs to the person asking,
- how to use the product and how to troubleshoot it, with the steps and the video guide for that model,
- policy text: warranty terms, return conditions, delivery times.
What the chat turns into a ticket
Anything that needs a person to act: an invoice, a refund, compensation, a reshipment, an exchange, a cancellation, an order change, an address change. The chat AI does not agree to it, does not suggest a remedy and does not quote an amount. It creates a ticket with the facts it has gathered, tells the customer the ticket number and the email address where the team will follow up, and continues with factual questions.
In the 30 days counted, the chat AI created 1,694 tickets this way. Agents did not step into the chat window. The requests that needed people reached them as tickets with the facts attached.
Do not make the customer choose a department first
Our chat opens with two buttons, pre-sales and after-sales. In one week, 1,300 conversations began with a tap on one of them, and the reply to that tap was a question back to the customer. A button that produces a question is a wasted turn. The first reply to a tap should already help: for after-sales, ask for the order number and say what the agent can check with it.
Keep a standard answer whole
When the knowledge base holds a standard answer to a question, the chat gives all of it. A support lead asked the chat a question that has a standard answer in the knowledge base and received only part of it. Chat answers should be short, and the place to save words is the wrapping around the answer. The facts stay complete.
Send the right video
Video guides are matched to the product model by the video's own title, not by the name of the page it was listed on. A page shared by several models once supplied a tail-light video for the wrong one. When a customer says the video does not match their product, the agent must not send the same link again.
Chat does not sleep
Of the 15,725 conversations, 6,902 started outside 09:00 to 18:00 Central European Time, 3,537 on a Saturday or Sunday, and 2,079 between 22:00 and 06:00. A staffed live chat covers a fraction of those hours. The pattern is in after-hours customer service with AI.
What to connect
- The chat window on the website, and the chat screen in the app through the same service, with the storefront and the entry point passed along.
- Read-only order lookup. See AI chatbot order tracking.
- The knowledge base. See what goes into it.
- The ticket system that receives the handoff. See when AI hands over.
Who this fits
Brands that sell in several countries, have an app or plan one, and receive the same product and order questions in every language. The free plan maps your chat entry points and what each should answer within two working days.