HomeHow it works

How it works

Six parts,
one WhatsApp number.

What happens between connecting your line and reading the report — what the system does on your behalf, and where it deliberately stops and waits for a person.

Your number

One scan, and the line is yours

Birsend drives the WhatsApp number your customers already have saved. You add it, scan a pairing code from the phone that owns it, and the session is held on our servers rather than in your browser — so the tab can close and the sending carries on.

  • No Business API application, no template approval, no new SIM
  • Seven states are reported honestly, including “Session expired” and “Blocked by WhatsApp”
  • If the phone stays offline for days the session lapses and you scan once more

A campaign

Built as a draft, scheduled on purpose

A campaign is a message, an audience, a number and an hour. Saving it and scheduling it are separate acts, because one of them is a decision about thousands of phones. The audience is resolved when the send starts rather than when you save, so somebody who joined in between is included and somebody who opted out is not.

  • Audiences are segments, built from the tags you set when importing
  • One picture or document per campaign, from the file library
  • A campaign may tighten the workspace’s hours, cap and pace — never widen them

A campaign body is sent exactly as written. Placeholders like {first_name} fill on automatic replies, not on campaigns.

The send

A minute at a time, and stoppable

The sender wakes once a minute, takes the campaigns whose hour has come, and works through the audience at the pace you chose — six, twelve or twenty messages a minute. It gives itself forty-five seconds per pass and hands the rest to the next one, so a large audience spreads out instead of arriving in a burst that gets a number flagged.

  • A person who cannot be messaged is skipped with the reason, and the run carries on
  • A closed window, a reached cap or a disconnected number stops the run instead — nobody behind them is marked anything
  • Pause is re-read before every batch, so it lands within a minute and remembers who it had reached
  • A campaign left an hour past its moment is cancelled rather than delivered late

Sending hours are judged in UTC for now, because a workspace has no timezone of its own yet. For 09:00–20:00 in Istanbul, enter 06:00–17:00.

Virtual Phone

What your customer sees, from your side

Every reply lands in a shared inbox that reads like WhatsApp, because it is the same conversation — the campaign message and the answer to it sit in one thread. Your team answers from there, with the name of whoever wrote each message kept on it.

  • Several numbers on one screen, switched from the header, each with its own hours and conversations
  • A thread can be handed over, so four people share one line without answering twice
  • Delivery states come back from WhatsApp itself — sent, delivered, read, and the provider’s reason when one fails
The shared inbox — the campaign and the reply in one thread.

Reports

Where it fell off, not just how much went

Figures are rolled up once a day rather than counted on demand, which is what makes a year of history open as fast as a week. Every period is compared against the same number of days immediately before it, and the funnel names the step that lost the most people so the next campaign has something to act on.

  • Messages sent, delivery rate, reply rate and link clicks, over any window
  • The funnel splits the blame: refused by your own rules, or never accepted by WhatsApp
  • Days are counted in UTC so a label can never disagree with the total beside it

Two doors out

Your software, and your agent

A REST API for systems you wrote, and an MCP server for an AI agent — twenty-two endpoints and twenty-two tools, on the same number and under the same rules. They are separate key types on purpose: software does exactly what you programmed, and an agent does something reasonable you did not specify.

  • No DELETE on any endpoint, and no way to create a campaign from either door
  • A key can never exceed the person who minted it, and narrows when they are demoted
  • Every message from either door passes the same window, cap, consent check and word filter
An agent working the inbox through the MCP server.

Ready to do it rather than read about it?

The setup guide is the same ground in the order you would work through it, with the two settings that matter first and roughly how long each part takes.

Cookies

The site runs what it needs to work, including the Crisp chat bubble. Google Analytics is the one thing we will not load unless you agree to it.