Smart Assistant Setup: Domains, Personas, Playbooks

In this series — Part 4 of 8 (AI Assistant). · Previous: Knowledge Base Chat (L1): Grounded Answers from… · Next: FAQs, Scripts & Reply Formats: Train Your AI Li… · Series start

Before you start: If you skipped earlier steps, read Knowledge Base Chat (L1): Grounded Answers from… first so nothing here feels confusing.

Docs give the AI facts. Smart Assistant setup gives it manners, boundaries, and a job description.

Teams skip domains, pick a vague “friendly AI,” write zero playbooks, and then watch the bot “help” on refunds and legal disputes it should never touch. Tone drifts. Escalation never fires. Brand trust takes the hit.

In this guide, you'll discover domains, personas, and playbooks for L2 — without shipping a chatty personality on empty truth. As a WAPilot team that configures assistants weekly, we see thin solid setups beat ornate unfinished ones.

Soft goal: in-scope domains, explicit out-of-scope handoffs, one clear persona, three to five core playbooks, Knowledge Base linked, tested before go-live.

Operators who rush this step usually rebuild the same journey twice after customers complain.

Keep the path short enough that a new agent can explain it in one minute during standup.

Official Cloud API discipline still applies: consent first, Approved templates when required, pause when quality dips.

What does Smart Assistant setup include in Wapilot?

Sources: Meta's Cloud API get-started guide and send messages docs. L1 Knowledge Base is what is true; L2 Smart Assistant is how the AI talks and acts. Define in-scope domains and explicit out-of-scope handoffs, pick a clear persona (role + tone), add three to five core playbooks, link the Knowledge Base, and test before go-live.

Domains might include pricing, shipping, onboarding help, and appointment basics. Out of domain: legal disputes, large refunds, custom enterprise deals — human only. Persona answers who you are, how you sound, and language preferences. One persona per use case beats one vague friendly AI.

Grounded chat first: Knowledge Base Chat. Escalation design: AI escalation handoff.

How should playbooks map situation to action?

Price ask → plan summary + CTA. Angry customer → brief apology → escalate. Booking intent → collect fields, offer a WhatsApp form, or hand off. Write playbooks short enough agents would use them too. Ship thin and solid — then expand.

Attributed example, from a WAPilot clinic workspace (2026): without an anger playbook, the bot kept troubleshooting while patients asked for a human. Adding a hard escalate on “agent please” and apology script cut repeat frustration messages the same week.

1. List in-scope domains and out-of-scope handoffs.
2. Pick one clear persona per use case.
3. Write 3–5 core playbooks.
4. Link the Knowledge Base.
5. Test before go-live.

Rule sources: Meta Cloud API get-started and send messages docs. Wapilot Smart Assistant shapes behavior on Cloud API chats; Meta still enforces messaging quality.

What order should setup follow?

Truth docs ready → domains → persona → playbooks → link KB → test → limited WhatsApp release. Do not enable live tools until this layer is stable. Forms can support booking playbooks once published to Meta.

What L2 mistakes look “smart” but fail?

No out-of-scope list, slangy persona, novel-length playbooks, and L2 without L1. How we know: WAPilot L2 reviews weekly map behavior failures to missing playbooks — against Meta’s public messaging context.

Next: FAQs, scripts, and reply formats train how you say repeat answers on WhatsApp.

Keep replies short — WhatsApp hates essays even when the persona is warm.

Industry profiles help, but one clear role still beats five overlapping voices.

Review domains monthly as products and policies change.

Human escalation is a feature of Smart Assistant setup, not a failure.

Treat this guide as an operations checklist, not a one-time read. Print the ordered steps and assign an owner for each gate before you flip traffic live.

When something fails in production, capture the customer wording, the node that fired, and the Meta-facing symptom before you redesign the whole canvas.

Keep internal links few and intentional — adjacent series posts and the hub beat random keyword stuffing across twenty URLs.

Respect quiet hours and staffing plans. Automation that earns replies without inbox coverage creates the same unread spikes as careless campaigns.

Version names, changelogs, and a fifteen-minute post-publish review prevent mystery drafts from becoming the source of truth.

If quality rating slides after a launch, pause broad triggers first, fix consent and relevance, then warm traffic again on official Cloud API.

Document product paths clearly for your team: Automation → drip sequences for timed nurture, Flow Builder for interactive journeys, Forms published to Meta for structured intake, AI Knowledge Base versus Smart Assistant for open questions, CRM pipeline beside inbox, and calling under rabbit-calls / WhatsApp calling when voice is needed.

Rehearse the bot-to-agent handoff on a test number: summary present, owner assigned, customer not left in silence. Shared numbers still share one customer care window.

FAQs

Can I run L2 without a Knowledge Base?

You can, but invent risk rises — link L1 for factual topics whenever possible.

How many playbooks do I need on day one?

Three to five core situations beat a huge unfinished library.

What is out of scope?

Anything policy marks human-only: legal, large refunds, medical/financial advice beyond scripts.

Does a bot-to-agent handoff reset the window on a shared number?

No. One customer thread, one service window. Two brands on one Cloud API line share that clock — split numbers before you scale support and promos on the same line.

Recap: ship the habit, keep a human exit, and measure what customers actually do. When you are ready, start a free trial and grow on official Cloud API.