WhatsApp Chatbot Onboarding Checklist: From Sign-Up to First Live Reply

A WhatsApp chatbot onboarding checklist is the difference between a launch that takes a weekend and one that drags for a month. The work itself is not hard — the waste comes from doing it in the wrong order: training an agent before the number exists, publishing a number before the display name is approved, announcing a launch before a single test conversation has run. Here is the sequence that avoids rework, from sign-up to first live reply.

Phase 1: Account and number

• Create the Meta Business account and the WhatsApp Business Account inside it.
• Add and verify your number by SMS or voice call — and confirm it is a dedicated business number, not a personal line.
• Submit the display name early, in parallel with verification, so its review runs while you do the rest.
• Add a payment method to Meta's Billing Hub so message delivery never pauses when a free tier runs out.
• Connect the number to your platform and confirm the connection test passes.

Phase 2: Knowledge before conversation

The agent is only as good as what it knows, and this phase is where most launches are won or lost. Upload the documents customers actually ask about: prices, hours, delivery and return policies, services, and the twenty questions your staff answer every week. Write the agent's instructions in plain language — who it is, what it may promise, and when it must hand off to a human. Leave out documents the agent should not quote (internal pricing, supplier costs, draft policies), because anything uploaded is answerable. The document-training detail is in the

training guide.

Phase 3: Test conversations

• Message the number yourself with the ten most common customer questions and read every answer.
• Test the edges: a question with no answer in the documents, a price question, an angry message, and a request for a human.
• Check the handoff: does a human actually see the conversation, and does the customer get told someone will reply?
• Test templates separately — a template that looks fine in the editor can read badly in a real thread.
• Fix the agent's instructions from what the tests reveal, then re-test the same questions.

Phase 4: Launch checks

• The display name is approved and shows correctly in a chat header.
• The profile has a photo, a description, and business hours that match your website.
• Your website, Google profile, and social bios point to the right number — the API number, not an old app number.
• Staff know the number is live, who watches the inbox, and what the handoff procedure is.
• A fallback is in place: if the agent or platform goes down, someone sees the messages and replies.

The first week after launch

Launch is not the end of onboarding; the first week is. Read every conversation for the first few days — not a sample, all of them — and log every wrong answer back into the documents or instructions. Watch for the pattern that matters most: questions the agent cannot answer because the document does not exist yet. Each one is a document to write, and after a week of that loop the agent stops surprising you. Businesses that skip this week keep answering the same failures for months; businesses that do it once launch properly.

Owner: “We launched on Friday and announced everywhere.” Nobody had tested the handoff. The first real customer asked for a human and waited two days. Test the handoff before you announce.

What onboarding does not include

Onboarding is activation, not marketing. It does not include broadcast campaigns — and a scope note matters here: Neksio is not a bulk or broadcast tool, so a launch plan built on sending lists needs a different tool. Onboarding gets you answering customers who message you, reliably, from day one. Growth comes after the first week of clean conversations, not before it.