Setting up customer support in your first week: a playbook
Five days is enough. Day one connect one channel, day two write down the answers you repeat, day three switch on the bot, day four set deadlines and ownership, day five measure. Doing more than this in week one is how support setups get abandoned.
- One channel, done properly, beats four half-configured ones.
- Writing down your repeated answers is the real work, not the software.
- Set deadlines you already meet, then tighten them.
- Measure from week one so you can tell whether anything improved.
Day one: one channel, properly connected
Pick the channel your customers already use, which in India is almost always WhatsApp, and connect it properly through the Cloud API rather than running the business from somebody's personal app.
Do not connect four channels on day one. Each one adds configuration, testing and a place for messages to go unanswered, and a business with one well-run channel comfortably outperforms one with four half-configured.
While you are there, set the business profile properly: name, description, hours, address and a link. It takes ten minutes and it answers a surprising number of questions before anybody asks them.
Test it yourself from a different phone. Send a message, check it arrives, reply, check that arrives too. Do this before anything else is built on top.
Use a number the business owns rather than an employee's personal one. It sounds obvious and it is regularly ignored, and the cost lands the day that employee leaves and takes the customer relationship, the history and the number with them.
Day two: write down what you repeat
This is the actual work, and the part people skip in favour of configuring software.
Go through a month of messages and list the questions you answer repeatedly. Most small businesses find eight to fifteen. Write a clear, complete answer for each, the version you would want a customer to receive on your best day.
- Opening hours and whether you are open now.
- Prices or price ranges.
- Delivery areas and timelines.
- Return, refund and exchange policy.
- Location and how to reach you.
- Payment methods.
These become your knowledge base. If you do nothing else this week, do this, because every later improvement depends on it and it is useful even without a bot.
Day three: switch on the bot
In Convo360, create an AI agent, point it at the knowledge base you wrote yesterday, and write a short system prompt: who you are, your tone, and what the bot must never answer.
That last part matters more than the rest. Be explicit: never quote a price not in the knowledge base, never decide a refund, never give medical or legal advice, always hand over if unsure.
Set the fallback message, which is what a customer hears if your AI provider has a problem. Then test with ten real questions from day two's list, and ten awkward ones you made up.
Leave it on for the rest of the day and read every conversation that evening. You are looking for one thing: did it answer anything it should have handed over.
Keep the prompt short. Three or four sentences describing the business, the tone and the boundaries will outperform a page of instructions, and a long prompt makes it much harder to work out which line caused an odd reply.
Day four: ownership and deadlines
Now decide what happens to the messages the bot hands over.
If you are one or two people, the shared inbox is enough and you should stop here. If you are three or more, or handling more than about thirty conversations a day, switch on the Support Desk so each issue becomes a ticket with an owner.
Set your working hours honestly, including Saturday if you work it. Set first-response targets you are already meeting, not the ones you aspire to. Four working hours consistently met is worth far more than one hour missed daily.
Name one person for escalations. A group alert that everyone can see is a group alert nobody acts on.
Day five: measure, then stop
Write down four numbers so you can tell in a month whether anything improved.
| Number | Why |
|---|---|
| Messages received this week | Your baseline |
| Share that reached a human | How much the bot handles |
| First response time | What customers feel |
| Anything reopened | Whether answers held |
Then stop. Do not add channels, campaigns, surveys or routing in week one. Every one of those is worth doing and none is worth doing before the basics have run for a month.
The most common way a support setup fails is not a wrong tool, it is too much configured too quickly by somebody who then has a business to run.
Tell your customers, too. A line on your website and in your WhatsApp greeting saying you reply within a stated window during stated hours converts an unknown wait into a known one, and it noticeably reduces the second and third messages from people checking whether anyone is there.
What to add in month two
Once week one has been running for a few weeks, three additions give the most value.
Proactive messages. Order confirmed, shipped, appointment reminder. These reduce inbound volume rather than answering it faster, which is always the better trade.
A second channel, usually Instagram or the website widget, now that the bot and the knowledge base are proven.
Saved replies for the answers your team still types by hand, which will be obvious by then.
Leave surveys, routing rules and reporting until month three. They are useful and they are refinements, and refining something that has not settled is how effort gets wasted.
Step by step
- Day 1: connect one channelWhatsApp through the Cloud API, with the business profile filled in. Test it yourself from another phone before building anything on it.
- Day 2: write your repeated answersEight to fifteen questions you answer constantly, each with a clear complete answer. This becomes the knowledge base.
- Day 3: switch on the AI agentPoint it at the knowledge base, write a short prompt saying what it must never answer, and read every handover that evening.
- Day 4: ownership and deadlinesShared inbox if you are one or two people, the Support Desk above that. Set honest working hours and targets you already meet.
- Day 5: write down four numbersVolume, share reaching a human, first response time and reopens. Then stop configuring for a month.
Set support up in five days
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Can a one-person business justify this?
The bot, yes, because it covers the hours you cannot. The ticketing layer, usually not until you have a second person, since a single person with a shared inbox rarely loses track of their own work.
Should I connect all my channels at once?
No. One channel done properly beats four half-configured, and each additional channel is another place for messages to go unanswered while you are still learning what the bot gets wrong.
What if I do not have policies written down?
Then writing them is day two's work and the most valuable thing in this playbook. A bot cannot explain a policy that exists only in your head, and neither can a new employee.
How long until it is worth measuring?
Take the baseline in week one and review after a month. Anything shorter is dominated by the novelty of the change, and the first week's numbers are always distorted by testing.
What is the most common mistake in week one?
Configuring too much. Routing rules, surveys and multiple channels all get set up on day one, none get used properly, and the whole thing is abandoned within a month.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.