Managed agent
Wassist runs the AI. Write a prompt, pick a model, add tools and knowledge. No server needed.Best if you want an agent live today.
Webhook routing
Your code handles every message. Wassist forwards each inbound WhatsApp message to your endpoint, and you reply through the API.Best if you already have an agent or backend.
Which one should I pick?
Want your own MCP tools to know which customer and conversation they’re serving? That’s an App (alpha): an MCP server you install on your agents. Build on Wassist compares all three options.
You can switch any time. Routing is a per-number setting (Agent, Webhook or No action), so the same number can move from a managed agent to your webhook and back without re-linking anything.
Before you begin
Both paths need:- A Wassist account. Sign up free with your phone number.
- WhatsApp on that same phone. The sandbox only routes messages that come from the number you signed in with.
How the sandbox works
The sandbox is a shared Wassist WhatsApp number. It appears under Numbers → Sandbox numbers in the dashboard, and it’s the number that sent your login code. Everyone shares it, but routing is per user. When you connect an agent or a webhook to the sandbox, only your own chat with it changes. Other people’s chats aren’t affected, and yours isn’t affected by theirs. Your sandbox chat belongs to you, not to an organization. It’s the same chat in every organization you belong to, and only you can see it. You can route it to an agent or webhook from whichever organization you’re working in, and that organization pays for any agent usage. If you leave an organization, your sandbox chat stops using its agents and webhooks.The sandbox has no business profile, templates or analytics. When you’re ready for real customers, connect your own WhatsApp number. The same routing controls apply.