Ten Twilio Content template types, from Text and Media through List Picker, Carousel and Authentication. Placeholders are dragged from a sidebar onto droppable fields. Templates are submitted to Meta and their approval status is synced back — only approved templates can be sent.
BridgeOne
One account,every channel.
BridgeOne turns a spreadsheet or database of customers into personalised messages sent over three channels — and then tells you what happened to every one of them.
Desktop app · macOS · Windows · Linux
BridgeOne — dashboard preview
What it does
One workspace for WhatsApp, SMS and Email.
For businesses that already have a Twilio account and an SMTP sender, a list of customers living in a spreadsheet or database, and a need to reach them on more than one channel — without wiring provider APIs, template approval flows, compliance suppression and delivery reporting together themselves.
- 01
Connects your providers
Bring your own Twilio account for SMS and WhatsApp, and your own SMTP server for Email. BridgeOne never resells messaging — it orchestrates the accounts you already own, so delivery, sender identity and per-message cost stay yours.
- 02
Ingests your data
Recipients and personalisation values come from your own sources — an uploaded file, a Google Sheet, files on Drive, or a live database.
- 03
Builds and personalises
Templates are authored inside the app. Any column from your data can be dropped into the copy as a variable and is substituted per recipient at send time.
- 04
Sends and reports
Campaigns are dispatched server-side in chunks, with provider webhooks writing every delivery outcome back — a unified cross-channel view of volume, delivery rate, failures and spend.
- Not a messaging provider.
- Not a CRM.
- Does not bypass provider rules.
The workflow
Channels unlock in a chain.
- 01BridgeOneaccount + plan
- 02Twiliothe foundation
- 03SMSneeds Twilio
- 04WhatsAppneeds SMS
Email sits outside the chain entirely — it runs on SMTP, needs no Twilio, and is therefore always available to set up first.
WhatsApp requires SMS specifically because once your Twilio number is live it can receive WhatsApp's verification codes inside BridgeOne.
In the order the app enforces
- Sign-up
- Twilio
- Channels
- Data
- Template
- Campaign
- Report
Channels
Exactly three.
Twilio is the shared foundation SMS and WhatsApp both send through. It is deliberately not a channel, and is excluded from the channel count.
SMS
A builder with live character, encoding and segment analysis as you type. The phone-number column is auto-guessed from your data. One optional image or PDF attachment, up to 5 MB, automatically converts the message to MMS.
Two builders: Simple Email, a rich-text composer, and Canvas Designer, free-positioning design across one or more pages. Runs on your own SMTP, so it needs no Twilio and can be set up first.
All three hubs are organised the same way — Templates, Campaigns, Logs, Compliance and Settings — so learning one teaches you the others. Email swaps the two-way Chat tab for Sender Reputation, having no inbound conversation surface.
Your data
Every source becomes columns and rows.
A one-off file import or a saved source reused across campaigns — either way the result is normalised into one universal shape, so the validators, variable mapping, snapshots and send path never learn where the rows came from.
- CSV
- Excel
- JSON
- Google Sheets
- Google Drive
- PostgreSQL
- MySQL
- MongoDB
- Firestore
- Databases
- External databases are dialled from BridgeOne's server, so those connectors surface the outbound IP you must allow-list. Table and collection discovery is built in.
- Validation
- An import-time check and a campaign-time check both run. Both are warning-only — a data-quality warning is something you acknowledge and send anyway if you choose.
- Source status
- Not tested · Connected · Needs reconnect · Error
Personalisation
Two syntaxes, one of them invisible.
BridgeOne uses a two-syntax system, and the translation is invisible to you. A variable-mapping layer binds each placeholder to a column in the selected data source.
- What you write
- <<FirstName>>
- What Twilio receives
- {{1}}
Variable integrity is checked before every send: if a template references a column its data source no longer has, you are warned and offered a different source rather than sending broken copy.
Saved-source templates store only column names, so fresh rows are re-imported at campaign time — which is exactly when schema drift surfaces.
Campaigns
A template, a source, and who it resolves to.
A campaign binds a template to a data source. Variables are mapped to columns, recipients are resolved, suppressed and opted-out contacts are excluded, and the campaign is sent now or scheduled.
- Sending
- Entirely server-side. The client writes intent; the backend resolves recipients, renders each message from the row values and dispatches it. Closing the app does not stop a send.
- Scheduling
- Scheduled campaigns are claimed by backend schedulers that run every minute.
- Snapshots
- At send time the resolved rows are frozen into a backend-owned snapshot, so recipient data never travels inside the campaign document and a completed run stays explicable after the source has moved on.
- Pre-send guards
- Sends are blocked, in order, on a missing name or template, an import still running, no recipients, a broken attachment pair, unconfigured SMTP, and template validation.
- SMS ceilings
- Per-minute, per-hour and per-day rate limits, daily and monthly spend limits, and caps on recipients and segments per campaign — enforced before dispatch, with an audit record written when one blocks a send.
- While running
- A progress bar, queued, sent, delivered, failed and undelivered counters, delivery and success rates, the recipient-filtering breakdown, and any send errors.
Dashboard
The Control Center.
The Dashboard is BridgeOne's Control Center. It answers three questions in order: how far along is my setup and what is my one next step, how well am I actually delivering, and is each connection healthy.
The Dashboard is a consumer of state, never a producer. It reads the same services every other screen reads, and only prioritises and renders — which is why it can never contradict another screen.
- Current Plan
- The active plan and price, activation and renewal dates, and a gauge filled with the remaining fraction of the term. Hidden entirely when there is no active plan, so no empty placeholder is ever shown.
- Setup Progress
- A gauge reading connected channels over total channels, and beside it the single recommended next step. There is only ever one.
- Messaging Health
- The aggregate seven-day delivery-success rate across every channel, with a per-channel breakdown and the single channel that lost the most messages.
- Twilio Foundation
- The shared connection SMS and WhatsApp both send through, presented separately from the channel grid.
- Communication Channels
- Every channel is always shown. One whose prerequisite is unmet renders locked with the reason rather than vanishing.
The health denominator counts only terminal outcomes. If nothing has been delivered or failed yet the score is not zero — it is undefined, and the card reads “No data yet” rather than showing a 0% that would read as a total outage.
Reporting
Read what happened.
The cross-channel view: aggregate performance and cost, not per-message detail. A time range and a channel filter, and a refresh that reloads both the analytics and the Twilio balance.
- Summary
- Total Messages · Delivery Rate · Failed · Twilio Balance
- Charts
- Message Volume · Delivery Status · Cost Over Time · By Channel
- Delivery rate
- Delivered ÷ (delivered + failed). The denominator is terminal outcomes, not messages sent, so the figure never dips simply because a large send is still running.
BridgeOne — reporting preview
Reports
How is my messaging doing?
Cross-channel, aggregated, chart-driven. Filters by time range and channel. Totals, rates, trends and spend.
Logs
What happened to this one message?
Per-channel and per-message, inside each channel hub. Filters by status, operation type and date range.
AI assistance
Five operations, inside the builders.
An AI Assistant panel lives inside the two Email builders, with a smaller rewrite control in the SMS template builder. Seven tone presets, body-length presets and ten rewrite modes sit alongside them.
- Content
- Design
- Rewrite
- Personalize
- Templates
There is no AI in the inbox — no suggested replies, no auto-drafting, no summarisation. The Dashboard's recommended next step is likewise not AI; it is a deterministic priority ladder over connection statuses.
Compliance
It does not bypass provider rules.
WhatsApp templates still go to Meta for approval, US SMS still goes through carrier registration, and BridgeOne surfaces those waits rather than hiding them.
- Per channel
- Every channel has a dedicated Compliance tab. The rules differ per channel, but the shape is shared: a suppression list, usage counters, limits and an append-only audit trail.
- SMS
- Deliberately Twilio-first. Twilio's Advanced Opt-Out owns the STOP, START and HELP reply text — BridgeOne does not re-implement it. What it keeps is a mirror suppression list those replies land in, the audit trail, and the spend and rate ceilings enforced before dispatch.
- Marketing, newsletter and re-engagement templates require an unsubscribe link, and four compliance toggles are on by default: unsubscribe links, List-Unsubscribe headers, auto-suppression of hard bounces, and auto-suppression of spam complaints.
- Pre-send filtering
- A raw recipient list is reduced to the sendable count by removing invalid numbers, duplicates and suppressed contacts — each counted, so the reduction is explicable.