Answers first.
A human if you need one.

On the Numbers screen, add the number and scan the pairing code with the WhatsApp app on the phone that holds it. There is no business verification to apply for. The session is held by our WhatsApp service rather than by your browser, so you can close the tab afterwards.

No. Use the number your customers already have saved — that is the point of it. Replies come back to the same line, into a shared inbox.

Set your sending rules. The sending window, the daily cap, the pace and the opt-in requirement all apply to whatever you do next, and the window is the setting people most often get wrong. The setup guide does these in the right order.

About half an hour of real work, most of it deciding on your sending rules and preparing the contact file. Connecting the number itself takes under a minute.

When the send starts, not when you save the campaign. Somebody added to the segment in between is included, and somebody who opted out in between is not. The count shown while you are building it is an estimate for that moment.

Yes. It stops within a minute and remembers exactly who it had reached. Resuming picks up from the next unsent person — one row per recipient makes “nobody twice” a guarantee rather than a hope.

Because the messages already delivered need a record to belong to. A paused campaign is half sent and waiting to finish, which is exactly the case the guard exists for. Let it finish, then delete it.

A campaign left more than an hour past its hour, with a sending window open, is cancelled automatically rather than delivered late. The reason on the campaign names the hour it was promised for. Give it a new time to send it — a time already past is refused.

Campaign bodies are sent exactly as written; placeholders fill on automatic replies only. This is a known gap rather than a setting — the groundwork exists and the sending half is not written yet. Check the preview before scheduling.

Not one you can switch on from the panel. The safe rehearsal is a second campaign aimed at a handful of numbers you own — send that, read it on a real phone, then pause and resume it once so you have seen those buttons work.

CSV and plain text. Export as CSV from Excel or Sheets first — an .xlsx will not parse. The import shows you what it read before anything is written and reports every row it could not read rather than refusing the whole file.

No. A single international column is fine — the API and the importer both take the number whole. The panel’s single-contact form asks for the dial code separately because it has a country picker beside the field.

It makes Birsend refuse anybody without consent on file, everywhere: campaigns, the inbox and the API. Turn it on if your list’s consent is unclear. The flag on an import is what a send checks, so ticking it on a cold list is how a number gets reported.

They are opted out at once, before any automatic reply rule gets the chance to greet them on the way out. From then on every send to them is refused absolutely. The change is filed as evidence with its source and time.

Yes. Every consent change is stored as an event with where it came from and when, and it is on the contact next to what they were sent. “They never told us” and “they told us to stop” are kept as different facts, so ticking a box again later cannot quietly undo a request to stop.

There is no DELETE on any public endpoint. Removing a contact takes their consent record and their history out of the workspace’s sight, which is not something to hand to a script. The contacts page does it with somebody watching.

None is sent, and none exists. There is no outbound email on this platform at all. You create the account yourself with a name, an address and a password, and you pass the password on — the account works the moment you save it.

There is no reset link, for the same reason. An admin sets a new password on the team screen. That also signs out every other session on the account.

Sixteen areas, each with “see it” and “change it”. Three roles ship configured — Admin, Agent, Analyst — and you can add your own. Turning on “change” turns on “see” with it, because the other combination is a screen somebody can act on but not open.

Yes, and they are separate areas on purpose: either one shows the shape of the whole business. The activity log is narrower still — it reaches only the owner and admins by default, because it shows every colleague’s actions with times and addresses.

Their sign-in stops working and every session and API key they held is revoked. Everything they wrote — messages, notes, campaigns, log entries — keeps their name on it.

Yes. The Logs page under Workspace records every change with the old value beside the new one — “time zone was Europe/London, now Asia/Tokyo” rather than “profile updated”. It covers seventeen areas including sign-ins and refused sign-ins.

No, by anybody, including the workspace owner. There is no delete route anywhere. Entries leave on age alone — currently after 180 days, applied to everything equally.

Never their values. A password change is recorded as having happened, with the field shown as bullets so it is visible that it changed. Only a hash of an API key is ever stored, and the key itself is shown once.