Documentation

Add WhatsApp conversations to your Next.js app with @quami/sendo: the webhook, sending, AI agents and the team inbox operations live in the package; the webhook route, the schema and the screens are registry items you own. Your data stays in your database.

• Meta setupApp, WhatsApp product, test number, system user token and webhook.
• Meta pricingWho pays Meta for WhatsApp messages, the dimensions a price depends on, where to find Meta's official rate card, and why a payment method matters.
• Sendo ConnectThe optional paid service: Quami as your Meta Tech Provider. Configuration, the signed webhook relay, secret rotation, the test event, signup through Connect, disconnecting numbers, suspension, doctor checks and what passes through Quami.
• API referenceConfig, events, sending, templates, conversations, agents and adapters.
• Agents and modelsGive an agent any AI SDK model: OpenRouter or a gateway for exploring, a direct provider for production, and what each turn costs.
• InboxLayout, setup, languages and strings, motion tokens and server-action auth for the team inbox.
• LanguagesRender the Sendo screens in English or Spanish, format dates and numbers for a region, edit any string and add a third language.
• Team inboxRoles, step-in, notes, snippets and tags, agent pause, drafts and model cost in sendo.inbox.
• WorkflowsRules (business hours, routing, auto-assign, escalation, auto-close), the rules screen, rules sync and the every-minute tick route.
• SecuritySensitive data, private storage, signed URLs, tokens and authorization inside tools.
• AdaptersWhere Sendo stores its data: Supabase, Drizzle or Prisma over your own Postgres, and what changes for access control and media.
• RetentionPruning sendo_events with pg_cron or a Vercel Cron route, your own policy for messages and media, exporting a number's history (v1 JSON), the numbers screen's Export conversations and Delete history (allowPurge), and purging a disconnected number.
• Multi-numberSeveral numbers and tenants on one deployment: routing, accounts and access.
• ChannelsWhatsApp today; what changes for Instagram and Messenger later, and what doesn't.
• Numbers and tenantsSend as an organization with { tenant }, default numbers, and the sendo.accounts API: add, label, pause, disconnect, purge.
• Embedded SignupLet an admin connect a WhatsApp number from your app, plus the billing state: what Meta requires, completeEmbeddedSignup, errors and refreshBilling.
• CoexistenceKeep using the WhatsApp Business app on a number the inbox also works: Meta's seven limits, echoes, agent pause and history import.
• Links, QR and chat bubbleBring conversations in with wa.me links, printable QR codes and a chat bubble, and see how many came from each source.
• CLInpx @quami/sendo doctor, accounts add, list, set-default, disconnect and export, and rules sync: checks, flags and environment.
• MetricsMessages per day, first response time, work per person, AI resolution, sources, tags and cost: the sendo.metrics API, the Metrics screen and the SQL behind them.
• Voice notes and costTranscribe inbound voice notes before the agent answers, and see what every agent turn and conversation cost.
• Broadcasts and opt-inSend one approved template to many contacts: who is eligible by category, opt-in and opt-out keywords, the tick, billing pauses and the Broadcasts screen.
• Para agentesDocs for coding agents: the sendo mcp server (one-line setup for Claude Code and Cursor), llms.txt, AGENTS.md in every registry item and doctor --json.
• Migrating from Respond.io or KapsoMove a WhatsApp number, contacts and workflows from a hosted inbox into your own app with Sendo.
• RoadmapWhat already shipped, what Sendo Connect is and isn’t, when it opens, and the channels still to come.