One integration for every business you serve.
If your product serves many businesses, such as clinics on a clinic platform, each one becomes a business tenant. Their contacts, consent, messages and senders stay apart, while you run everything through one API.
What you get
Business tenants
Create, update and disable tenants through the API with your own reference for each. Disabling a tenant stops its sends and keeps its history.
Nothing crosses between tenants
The same phone number in two tenants has separate consent and history. Fallback never uses another tenant's number or header.
Keys scoped to tenants
Limit an API key to one or more tenants. A key for several tenants must name the tenant on every send; Hopwire never guesses.
Shared senders by permission
Let chosen tenants send through your WhatsApp number or SMS header with an explicit grant per tenant. Messages name the business they are sent for.
Tenant context everywhere
Webhook events carry the tenant, and endpoints can be limited to specific tenants and event types.
Hosted onboarding and bulk setup
At launchCreate tenants by CSV, send hosted setup links, publish one template to many tenants and follow each approval separately.
Consolidated billing
At launchOne bill with a breakdown per tenant, plus quotas and spend alerts.
Tenant branding
Release 2Versioned brand profiles and layouts per tenant, inherited from your defaults.
How it works
Create a tenant
Add the business with your own reference, time zone and legal details.
Give it a sender
Connect the business's own WhatsApp number and SMS header, or grant it use of yours.
Send with its name
Pass the tenant on each send, or use a key limited to that tenant.
Watch each business
Filter the explorer, usage and webhooks by tenant.
Questions
Do my business customers need Hopwire accounts?
No. You operate their tenants through your integration. Delegated access for them is planned as an option.
Whose DLT registration is used?
By default each business registers its own Principal Entity. Where you are the legal sender and your registration allows it, businesses can send under yours.
Can a clinic's message fall back to another clinic's number?
No. Routing and fallback only use senders the tenant owns or has been explicitly granted.
Who receives a reply on a shared number?
The tenant that last messaged that person through the number, otherwise the number's owner.
Related
- SaaS platformsAvailableGive each business on your platform its own sender, contacts and history, while you run one integration and one account.
- RoutingAvailableEvery message tries WhatsApp and falls back to SMS after a confirmed failure or timeout. Override the channel per send.
- For agenciesRelease 3Separate client workspaces, delegated access, transfers and white-label for agencies. Planned for Release 3.
- HealthcareAvailableAppointment reminders and patient OTPs from each clinic's identity, with SMS fallback and clinic data kept separate.
Start with the beta.
Hopwire is free during the invite-only beta. Tell us what you send and we will reply by email.