Questions, answered.

Most teams send their first event within 5 minutes using the Web SDK. A full lifecycle migration from an existing tool typically takes 1–2 weeks.

No. Every generally-available module is included on every plan. Turn on what you need, add others later — no migrations required. We roll modules out in batches, so some show as “coming soon” until they graduate.

Yes. 25,000 monthly tracked users forever, every generally-available module included. No credit card required. The Email module + broadcasts require a verified sending domain (free to add on any tier); system messages like auth, receipts, and support auto-replies run on Sendora without DNS setup.

One MTU = one identity with at least one tracked activity in the month, counted once across every module. An anonymous visitor who later signs in is the same user, not two — the meter dedupes the conversion, so you're never double-billed for onboarding. System lifecycle events (push.delivered, email.delivered, etc.) and webhook deliveries are free and never count.

Only for users you already track. MTU counts distinct identities with activity this month — a broadcast doesn't create new tracked users, and public visitors who file a support ticket or chat with the widget are never MTUs. Support, KB, and search are bundled, not metered.

No. Team and agent seats are unlimited on every paid plan, and you're billed on monthly tracked users, not stored contacts. We think per-contact and per-seat billing punish growth.

Only real cost: Email (over a free allowance; bring your own provider = $0), SMS (carrier cost + a flat fee), and AI ($0.20 per resolution vs Intercom's $0.99). Everything else rides your plan. You can set a hard spend cap so metered usage never surprises you.

Nothing breaks. You move to the next tier (or overage at the published MTU rate) at the end of the cycle, and we notify you before it happens. Annual plans are 2 months free.

Yes. Monthly plans cancel any time. Annual plans are prepaid and convert to month-to-month at the end.

For customer-authored email (the Email module API, workflow email steps, broadcasts) you add a domain you own — one-time DNS setup, DKIM signed by your domain, your reputation stays yours. System messages (auth, billing, support auto-replies) run on Sendora's infrastructure so you can start without any DNS work.

Bring your own provider (Twilio, MessageBird, Sinch) and pay the provider directly. The SMS module abstracts the provider API so you can swap without touching application code.

Sending reputation is tied to the From domain. If every customer sent from Sendora's domain, one bad actor could get Sendora's mail marked as spam everywhere — hurting every other customer. BYOD isolates reputation per customer. It's also how Resend, Postmark, and SendGrid work.

US by default. EU region available on request. We do not move data across regions without consent.

Yes, any time. Events export as JSONL to S3/GCS, profiles as CSV. No lock-in.

Yes. Every event carries a consent allowlist. DSAR workflows are built into the platform.