Reach everyone,
without the copy-paste.

Through Slack OAuth v2 — the standard "Add to Slack" flow. BulkReach requests four bot scopes: team:read, users:read, users:read.email and chat:write. The bot token is encrypted with AES-256-GCM before it is stored, and the column holding it is revoked from client roles at the database level, so it is only ever readable by the server.

You pair a WhatsApp number by scanning a QR code, exactly as you would to link WhatsApp Web. The session runs on a dedicated always-on service, and the session credentials are encrypted before being stored so the connection survives restarts without a re-scan. WhatsApp automation is unofficial and against WhatsApp's terms of service, so BulkReach requires per-recipient opt-in and paces sends deliberately.

Any unofficial WhatsApp automation carries ban risk, and a banned number cannot be recovered. BulkReach reduces that risk rather than eliminating it: imported contacts start opted-out until you confirm consent, the sender re-checks consent at delivery time, and messages are spaced three to eight seconds apart at random on top of a hard floor in the sending service. Messaging people who never asked to hear from you is what gets numbers banned, and BulkReach is built to make that inconvenient.

Slack allows roughly one chat.postMessage per second per workspace, so BulkReach paces Slack sends at that rate — about 1,000 messages in 17 minutes. WhatsApp sends are spaced three to eight seconds apart at random to reduce ban risk, so they are intentionally slower. Sends run through a queue, so closing the browser does not interrupt them.

Yes. Every table is scoped by tenant and protected by Postgres Row Level Security, so one workspace's queries cannot return another workspace's rows even if the application had a bug. The three server-side paths that bypass RLS — the send dispatcher, the Slack OAuth callback and the WhatsApp service — scope every query by tenant explicitly, and the repository ships an audit script that fails if any table is left unprotected.

Yes. Pick a date and time when composing, and the send is queued but held until it is due. A scheduler checks every minute and dispatches anything that has come due. Scheduled sends can be edited or cancelled up until they start, and times are shown in your workspace timezone.

Nothing is lost. Each recipient is a separate queued row, so a send that is interrupted resumes from where it stopped rather than restarting and double-messaging people. Failures are recorded per recipient with the provider error, visible in the delivery log for that send.

Yes. Templates support {{name}}, {{first_name}}, {{email}} and {{phone}}, resolved per recipient at send time. The compose screen previews the message as a selected recipient would receive it, and warns about placeholders that do not match a known variable rather than silently sending a blank.

Yes. CSV import accepts a phone column and an optional name column, and recognises common header variations. Numbers are normalised to international format and duplicates are merged. Imported numbers arrive opted-out unless you explicitly confirm that the people on the list agreed to be contacted.