Support your current customers, not only new leads
Written by the Allinaa team · Updated
Most chatbot advice is about winning new customers. Yet many of the messages a small business gets come from people who already bought: "How do I reset it?", "When is my next service due?", "It's leaking again."
Sales questions vs. support questions
| Sales visitor | Existing customer | |
|---|---|---|
| Wants | To decide whether to buy | To get something working, or fixed |
| Mood | Curious | Often frustrated |
| Good outcome | A request for a quote or a visit | A solved problem, or a clear next step with a person |
| Knowledge needed | Services, area, prices | How-to steps, warranty terms, service process |
The same assistant can do both, but the support side needs its own knowledge and its own rules for when to hand over.
How-to answers from your help content
Gather what you already send customers: setup guides, care instructions, aftercare sheets, "before your first visit" emails and troubleshooting notes. Paste the useful parts into the knowledge, or let the setup wizard draft from your help pages. Keep each answer short and in steps:
Example knowledge entry: "Thermostat shows a blank screen: 1) Replace the two AA batteries. 2) Check the breaker labeled HVAC. 3) If the screen stays blank, the customer should not open the unit; offer a service visit request."
The assistant can link to your manuals or help articles, but only to links in your approved information or on the page the customer is reading. It never makes up a link.
Service problems: collect details, request a follow-up
When something has gone wrong, the assistant's job is to collect a usable report rather than solve everything. Tell it in the knowledge what your technicians need: the product or model, when it was installed or bought, what is happening, and since when. It asks only what is still missing, up to three short questions, and then offers the request form with the "I'd like someone from the team to follow up" option. On Premium, the customer can attach photos to the request.
The assistant is told not to invent policies, so it won't promise a refund, a free repair or a time it can't confirm. Write your warranty terms into the knowledge so it can quote them correctly.
Escalating to a person
- Standard: the assistant says the request will be passed to your team, and the customer sends it through the form. You get an email, and the request appears in the inquiry inbox.
- Premium: the customer can press "Talk to a person", or the assistant hands off when someone is upset or can't be helped. A team member takes over the chat live and can hand it back to the AI afterwards. See Human handoff and live takeover.
Write your escalation triggers explicitly, for example: "Anyone mentioning a safety issue, a repeat failure or a billing dispute should be offered a person straight away."
Your hours, and ours
Your customers get AI answers at any hour. Replies from your own people come during your working hours, so say what those are in the knowledge ("We answer support requests Monday to Friday, 8 AM to 5 PM Pacific") and the assistant will set expectations correctly.
Allinaa's own support for you, the business, runs Monday to Friday, 9 AM to 6 PM Eastern Time, with a first response within one business day. That covers questions about your assistant, knowledge updates and corrections, not your customers' support requests.
Writing support knowledge
- Separate "safe to do yourself" from "call us". Changing a filter is fine; opening an electrical panel is not.
- Use decision steps. "If A, try B; if that didn't help, offer the form" works better than a long paragraph.
- Include the vocabulary customers use. "The little light keeps blinking" should lead to the right article.
- Review monthly. The monthly report lists the questions the assistant couldn't answer, and support gaps show up there first.
Our guide Writing chatbot knowledge covers structure in more detail. Common pre-sale questions are covered in FAQ answers, and delivery and returns questions in Shipping, returns and order questions.
Illustrative example, not a real customer conversation. It assumes the business added the manufacturer's error codes to its knowledge.
Customer: My water softener is beeping and showing 'Err 3'. You installed it last spring.
Assistant: Error 3 on that model usually means the control valve didn't finish a cycle. Try unplugging the unit for 30 seconds and plugging it back in. Did the beeping stop?
Customer: No, still beeping.
Assistant: Thanks for trying. This needs a technician. You can send a service request with the form. Mention the error code, and the team will contact you to arrange a visit.
Questions and answers
Can the assistant log into a customer's account to check something?
No. It has no access to customer accounts or your internal systems. The widget skips pages whose address has a segment such as account or checkout; keep it off any other page that shows customer data.
Can it tell existing customers from new visitors?
Not automatically. It goes by what the person writes, so include support answers in the knowledge and let the conversation show which kind of question it is.
Will it promise a repair or a refund?
It is instructed not to invent policies or promises. It can quote your written warranty terms and collect a request, and your team decides the rest.
Does it replace our support staff?
It takes repeat how-to questions off their plate and collects better reports. People still handle diagnosis, exceptions and upset customers. See Will a chatbot replace staff?