Security & trust
The BE AI agent can draft. A person still owns the case.
Draft-for-review, case ownership, scoped API keys, and outbound screening are how this product keeps humans in the loop — not a claim that the BE AI agent never needs one.
Team & roles
Several people can sit on the same company 04. Roles hide modules you do not want on every login; the inbox stays, because the shared number is the point.
- Multiple logins per company
- Roles that hide whole modules (cases, campaigns, surveys, collaterals, usage)
- Messages / inbox stay available — the shared number is the point
- Usage view for the company
API keys
Keys are credentials for software, not a second login cookie. Shown once, stored hashed, scoped, and optionally fenced to specific service numbers.
- Shown once at creation
- Stored hashed
- Scoped permissions
- Optional allowlist of service numbers
Outbound screening
Every outbound SMS/MMS through the engine is scored for scam phrasing, risky links, and velocity. Over the hold threshold parks the message for admin review; over the block threshold refuses it. Mentioned as trust — not as the homepage hero.
Public customer surfaces
A contact can open a survey or an upload link without a portal login. Those URLs are tokenised; they are not a back door into the desk.
/s/[token]— hosted survey/u/[token]— upload link- Tokenised; no portal login required for the customer
We do not claim a magical “no third-party hop” story. Messages go out over Australian carrier paths; the BE AI agent calls BE AI; media may sit in object storage. The trust claim is narrower: your team owns the case, keys are scoped, and outbound gets screened before it hits the gateway.