Send to ten thousand people.
Account for every one.
Postady runs your WhatsApp campaigns, your shared inbox and your contact consent on Meta's official Cloud API — and keeps a record of every message that leaves, one recipient at a time.
A campaign as Postady stores it: 2,000 recipients, one row each.
- Read
- 1,204
- Delivered
- 703
- Sent
- 41
- Failed
- 34
- Skipped, opted out
- 18
Failed recipients can be retried on their own. Skipped ones are never charged against your allowance.
What happens when you press Launch
Four steps, in this order, every time.
The audience is frozen
Postady writes one row per recipient at launch. Contacts added, edited or tagged while the campaign runs don't join it and don't fall out of it.
Each message is reserved before it is sent
A recipient takes one message from your allowance first, under a key made of the campaign and the contact. A worker restart replays the same key, so nobody is messaged or billed twice.
The worker paces itself
Send rate follows your number's quality rating and messaging tier. The campaign's status is re-read between recipients, so pause and cancel land on the next one rather than at the end of the batch.
Receipts land on the same row
Delivered and read events from Meta update the recipient they belong to. A provider failure releases the reservation and the message goes back to your allowance.
What you get
Campaigns
Filter an audience by tag, attribute or name, save it as a segment, pick an approved template, fill its variables, and schedule it in your workspace's time zone.
Shared inbox
Assign conversations to a person or a team, leave internal notes, apply labels, and see typing and presence live. A reply lease stops two agents answering the same customer.
Contacts and consent
Opt-in, opt-out and blocked state sit on the contact record and are checked before the queue, not after the send.
Templates
Synced from Meta with their approval status. Text, currency and date variables are typed, and previews render in the template's own language.
Analytics
Delivery, read and failure rates per campaign, consent health across the audience, and usage against the current billing period. Every figure comes from your own data.
API and webhooks
Scoped API keys and signed webhook endpoints, against the same HTTP contracts the dashboard itself uses.
Replies come back to a team, not to one phone
Every campaign message opens a conversation. Postady puts it in front of whoever is on shift, with the whole history attached.
Meera Raghavan · +91 98765 43210
Your order #4417 has shipped. Track it any time — reply here if anything looks wrong.
Can I change the delivery address? Moved last week.
Assigned to Arun · Support
Of course. Send me the new address and I'll update it before it leaves the warehouse.
Note, team only: address change approved by ops
Safeguards
Consent is enforced before the queue
Opted-out and blocked contacts are removed from the audience at launch and counted as skipped.
Meta credentials are encrypted at rest
Access tokens and app secrets are sealed with AES-256-GCM. Plaintext never leaves the API, not even to your own dashboard.
Sessions are short and rechecked
Signed, HTTP-only cookies lasting twelve hours. Workspace membership is revalidated on every request, so removing a teammate takes effect immediately.
Roles decide what each person can do
Owner, admin, agent and analyst. Campaign launches and credential changes stay with owners and admins.
Webhooks are verified, then routed
Inbound events are checked against the signing secret of the connection they claim to come from, then matched to a workspace by business account and phone number.
Questions
Do I need my own WhatsApp Business account?
Yes. You connect it through Meta's Embedded Signup from inside Postady, which takes a few minutes. The business account and the numbers stay yours — Postady sends on their behalf and can be disconnected at any time.
Is this an unofficial WhatsApp bridge?
No. Postady talks to the WhatsApp Business Cloud API that Meta publishes. There is no phone to keep plugged in and nothing to get banned for using.
What happens if a campaign goes wrong halfway through?
Pause it. The worker finishes the recipient it is on and stops. You can resume where it left off, cancel the rest, or retry only the recipients that failed.
Can two agents reply to the same person at once?
No. Opening a conversation takes a short reply lease, and other agents see it is held. The lease expires on its own if someone walks away.
Can I drive it from my own systems?
Yes. Every screen in the dashboard is built on the public HTTP API. Issue a scoped key, and register a signed webhook endpoint to receive message and campaign events.