Frequently asked questions

A panel for sending WhatsApp messages from a number you already own — campaigns to a list, a shared inbox for the replies, and rules that decide who may be messaged and when.

No, and that is the main thing to understand before signing up. Birsend drives an ordinary WhatsApp account by pairing with it, the same way WhatsApp Web does. There is no Meta business verification, no template approval queue and no per-message conversation fee. The trade is that you are working inside a consumer account rather than a commercial agreement, so the discipline about consent and pace is on you and on us rather than on a review process.

Small and mid-sized businesses that already talk to customers on WhatsApp and have outgrown doing it by hand — a few hundred to a few tens of thousands of contacts, one to ten numbers, a handful of people sharing an inbox.

Anybody who needs cold outreach to purchased lists. It is not a limitation we plan to remove: the guardrails that refuse it are the same ones that keep a number usable. If your list has no opt-in behind it, this is the wrong tool and it will fight you.

To use the panel, no — you pair a number by scanning a code, and never see a line of code. To use the REST API or the MCP server, yes, but both are optional and nothing in the panel depends on them.

You can send in any language. The interface is English, and the opt-out watcher recognises stop words in Turkish and English.

Yes, and it is the one rule with no override. A contact marked as opted out is refused at send time — every send path asks the same guard, so the panel, a campaign, the API and an agent all hit the same wall. There is deliberately no setting that re-enables it, because a switch for that would be a switch for breaking the law.

They are opted out automatically, before any auto-reply can fire, and a consent record is filed with their own words attached as evidence. It reads Turkish and English — stop, dur, iptal, çıkar, listeden çıkar, abonelikten çık, istemiyorum, rahatsız etmeyin, unsubscribe, remove me, and others.

It is built hard against that. The match is on the whole message, not a word inside it, and only on messages under thirty characters — so "stop" is an opt-out and "please don't stop sending me offers" is not. A short courtesy tail is allowed, so "iptal ediyorum" and "stop lutfen" still count.

Yes, and it is stricter than it sounds. With it on, Birsend sends only to contacts with recorded consent — a contact whose consent is simply unknown is refused too, not just one who opted out. It is the setting to turn on before your first import if you are unsure about your list.

Each contact carries a consent trail rather than a single flag: what changed, when, where it came from, and for a reply, what they actually wrote. The flag is the fast answer; the trail is what stands up if a complaint is ever disputed.

No. No tool can do that, and any that says otherwise is selling you something. Birsend gives you consent records, an opt-out that is honoured absolutely, and an audit log of who did what. The lawful basis for your messaging, your privacy notice and your relationship with your customers are yours.

Yes. Nobody can promise otherwise on a consumer WhatsApp account, and we will not. What Birsend does is remove the common causes: a modest pace, a daily ceiling, sending hours, a warm-up limit on a young line, and a refusal to message people without consent. What it cannot fix is an audience that did not ask to hear from you — enough of them reporting you will restrict a number no matter how politely it was sent.

Give the campaign a future time and it arms itself. A scheduler checks every minute, so nine o'clock means nine o'clock. A time already in the past is refused when you save.

No. Everything goes through the scheduler, so an immediate send means scheduling it a minute out. It is a small awkwardness that buys one guarantee: there is exactly one path a message can take out of the product.

Yes. It halts within a minute and remembers exactly who it had reached. Resuming continues from the next unsent person, and nobody can be messaged twice — one database row per recipient makes that a constraint rather than a promise.

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

Left more than an hour past its time with a window open, it is cancelled rather than sent late, and the reason names the hour it was promised for. Last Tuesday's promotion arriving on Friday cannot be taken back; a cancelled campaign can be given a new time.

Not yet, and this is the gap worth knowing about before you sign up. Campaign bodies are sent exactly as written — a {first_name} placeholder arrives as those literal characters. Placeholders do fill on automatic replies. The groundwork is there and the sending half is not written.

Not from the panel. Send a small campaign to a handful of numbers you own — it is the only rehearsal that also shows you how the message looks on a real phone. There is a dry mode, but it is an installation-wide switch held by whoever runs the server, and it marks every recipient as skipped, so it consumes the campaign rather than previewing it.

Because some were skipped, and every one of them carries a reason: blocked, opted out, consent required and missing. Read the reasons rather than the total — "skipped: 40" is a number, the reasons are an answer.

Yes — images, video, audio, documents and stickers, up to 10 MB each. A campaign can carry one attachment, the same file for everybody on the list.

No. A campaign holds one file, so per-person documents — an invoice each, a personalised PDF — are not something it can do today.

Shortening a URL through Birsend so clicks are counted. You see the total clicks on a link and when they happened.

No. Clicks are counted per link, not per contact — nothing tags an outgoing link with who received it, so "who clicked" is not a question the data can answer. Worth knowing if you were planning to segment on it.

Not from the panel. The link domain is set once for the whole installation by whoever runs the server, so it is not a per-workspace setting you can change.

Message bodies you save and reuse, so the same wording does not get retyped differently by four people. These are yours, not WhatsApp's — there is no approval queue.

Yes, a REST API with twenty-two endpoints, authenticated with a workspace-scoped key. It sends messages, reads conversations, and manages contacts, files and campaigns.

A Model Context Protocol endpoint that exposes twenty-two tools, so an AI agent — Claude, or anything else speaking MCP — can work your workspace directly instead of you writing an integration.

No, and that is the point of where the guard lives. A key sending at three in the morning goes through the same seven checks as a person clicking send: connected number, blocked, opted out, consent required, campaign paused, workspace paused, window, daily cap. A refusal names the setting that refused it.

No. There is no delete endpoint on the public API at all. An automated credential that can erase your contact history is a bad trade for the convenience, and if you need that, do it in the panel where somebody is accountable for it.

No. A request that passes the guardrails sends a real message, so develop against a number you own.

Not for your own integrations. Delivery receipts arrive to us over a webhook from the WhatsApp side, but Birsend does not currently call a URL of yours when something happens — you would poll.

Create an account and a workspace, then connect a number. The pricing section lists what each plan includes.

Through us rather than a self-serve checkout — there is no card form in the panel today, and a plan change is a conversation. What you can set yourself is the invoice identity: company or individual, tax number, address.

Yes, by telling us. There is no contract holding you in and no cancellation fee. Export your contacts before you go, and read the answer above about message history so nothing is a surprise.

Yes, if you are the owner and it is not your only one — you type the workspace name to confirm, and it becomes unreachable immediately. Closing an account entirely is still something you ask us to do.

No. This installation does not send email at all, so there are no usage warnings, no threshold alerts and no reports in your inbox. Everything is on the dashboard, which is why the allowance card is on it. Do not build a process that depends on a mail from us.

Not yet. It is not built, and the panel says so on the security screen rather than showing a switch that does nothing. What does exist is session management: you can see where you are signed in and sign out everywhere.