Skip to content
Voxa Docs

Introduction

Voxa is a conversation orchestration platform for WhatsApp campaigns, competitions, and customer engagement — built for teams that need clean data, reliable flows, and one workspace their operations team can trust.

What Voxa does in one paragraph

Section titled “What Voxa does in one paragraph”

You paste your Meta WhatsApp Business credentials into Voxa. You build a flow in the visual builder — a sequence of prompts, validations, and branches. You wrap that flow in a campaign with entry rules, a scheduled window, and a wa.me link or QR code. Contacts enter via the link, keyword, or QR scan. Voxa orchestrates the conversation, validates each answer, handles retries, and writes a structured entry per contact. You export the entries as XLSX or CSV from the dashboard. Every message, every state transition, every credential change is audit-logged.

Who it’s for

Section titled “Who it’s for”
  • Marketing and competition teams running WhatsApp-led campaigns that need clean, structured entry data.
  • Agencies running multi-tenant campaigns for multiple brands out of one operator workspace.
  • Product teams building conversational front-ends that sit in front of existing back-office systems.
  • Compliance-aware organisations — Voxa is built POPIA-first from the ground up (Information Officer, Responsible Party / Operator terminology, encryption at rest, retention tables, signed-URL media delivery).

Problems it solves

Section titled “Problems it solves”
  • Fragmented tooling. Replaces the Meta Business Manager + Google Sheet + ad-hoc Zapier workflow that most teams cobble together for WhatsApp campaigns.
  • Opaque delivery. Per-tenant and per-campaign analytics, audit logs, and delivery receipts so marketing knows exactly what shipped to whom.
  • Risky hand-rolled integrations. The Meta webhook, signature verification, signed-URL media, rate limiting, encryption at rest, and graceful shutdown are all handled for you.
  • Unclean data at collection time. Validation nodes (regex, SA ID checksum, custom operators) reject bad input before it becomes a downstream cleanup cost.

What Voxa is not

Section titled “What Voxa is not”
  • Not a chatbot authoring tool with a drag-and-drop “AI” persona builder. Voxa is flow-driven orchestration — deterministic node graphs with optional LLM calls on the roadmap.
  • Not a CRM. Voxa stores the contact data a campaign needs and exports structured entries; it is not a replacement for HubSpot, Salesforce, or Zoho.
  • Not a multi-agent live-chat inbox. The conversations view is operator oversight, not a shared-inbox product. Agent collaboration is on the roadmap if customer demand pushes it.
  • Not a template-editor for WhatsApp. Voxa stores templates Meta has already approved; you create and approve templates through Meta Business Manager for now.

What ships today (honest scope)

Section titled “What ships today (honest scope)”

Fully functional, production-ready:

  • Self-serve signup with 14-day trial.
  • Five-role tenancy model (super_admin / admin / owner / editor / viewer).
  • Meta WhatsApp Business Cloud API connection — encrypted credential storage, HMAC webhook verification, inbound and outbound routing.
  • Visual flow builder with 9 node types — message, question, media_capture, validation, condition, delay, submission, end, start.
  • Flow versioning with draft / published semantics.
  • Campaigns with link / QR / keyword entry modes and scheduling metadata.
  • Contacts, tags, custom fields, opt-in / opt-out tracking.
  • Entries with duplicate detection, media references, and async XLSX / CSV export.
  • Audit log on every mutation.
  • Paystack billing with 14-day trial, plan caps, self-serve checkout, webhook sync.
  • POPIA-compliant privacy posture — Information Officer, retention table, no model-training on customer data.

What’s not shipped (so you don’t build against it):

  • Broadcast-mode campaigns (queue exists, worker does not).
  • WhatsApp template sending from flow nodes (templates store only).
  • 2FA (TOTP column exists, enforcement does not).
  • CSV contact import, saved segments, automatic STOP keyword handler.
  • Campaign auto-transition on starts_at / ends_at.
  • Built-in LLM connectors, telephony, public REST API, SDKs.

See Integrations overview and each guide for the current-state details.

Where to go next

Section titled “Where to go next”