How NexBroad-Reach works, end to end
A walkthrough of the product, in the order a new organisation actually meets it — not an API reference.
Five parts, in order
Every part is something you can click through in the interactive demo, which runs the real interface on sample data.
Accounts, branches and roles
An organisation is the top-level account. Inside it, branches scope traffic and visibility, and roles — org admin, branch admin, admin, broadcaster — decide who can send, who can answer, and who can see across every branch versus just their own.
Sending a broadcast
Pick a contact list or a tag-based segment, write the message, and send by SMS or as an automated voice call. A voice broadcast can ask for a keypress (DTMF) response — accept or decline a shift, confirm an appointment — which comes back as data, not a transcription to interpret.
The shared inbox
Every reply — to a text or to a voice call's follow-up message — lands in one inbox the whole team works from. STOP, START and HELP are handled automatically to stay compliant; custom keyword rules can route other replies automatically.
Delivery reports
Every broadcast tracks sent, delivered and failed status per recipient, so "did this reach everyone" is answered by a report rather than a guess.
Credits and billing
Usage is metered against a prepaid credit balance shared at the org level — messages and voice-minutes draw down the same balance, so branches don't need separate accounts and cost tracks what's actually sent rather than a subscription tier chosen in advance.
Have a question the docs don't answer?
Ask directly — a short message is enough to start.