Interactive demo — simulated sample data
Guardrails
Northbeam Connect · Demo
RC

Guardrails

The rules that decide who does not get contacted — pick one to see what it enforces, and one account it happened to

Contacts stopped, 30 days
832
each one with a reason on the account
Preferences on file
2
channel-level, not all-or-nothing
On the Do Not Call register
1
never dialled, whatever the play says
832
contacts stopped in 30 days
11
rules, enforced before every step
0
accounts dropped without a reason
EnforcedCalls118 stopped, last 30 days

Do Not Call register wash

Every number is checked against the register before it can be dialled, and re-checked nightly. A listed number is never dialled, whatever the sequence says — an existing-customer exemption still has to be proven on the account, not assumed.

Worked through · Sandover Trades Supply · former customer
On the register, so never dialled — but never hidden either.
Nightly wash
Every number in every audience is checked against the Do Not Call register
Listed
Sandover's number comes back listed, and the consent that came with their old contract ended with it
Held permanently
The account stays in the win-back segment so you can see the size of what you can't work
Counted, not contacted
It appears on the audience with the reason attached, and nobody ever rings it
See it held on the audience

Where the facts come from

A rule is only as good as the record behind it. Consent, contract dates and open faults are read from the systems you already run — by category, never by vendor.

CRM & customer recordTwo-way

Accounts, contacts, owners; activity and outcomes written back

via API
Billing & invoicingRead only

Contract dates, plans, spend and overage — where most segments come from

via API
Outreach numberTwo-way

A dedicated mobile or local number for the agent — not your main line

via API
Email sendingTwo-way

Your own platform on a separate stream, or a domain we provision for you

via API
Calendars & repliesTwo-way

Real availability, so a booked meeting is genuinely booked; replies caught

via API
Support deskRead only

Open faults and closed-ticket sentiment; an open fault pauses outreach

via API
Consent & Do Not CallTwo-way

Register washes and your own preference store, checked before every step

via Scheduled export