Controls you can point at.
When someone asks what happened, you can show them exactly.
Trust controls decide who on your team can do what, what needs a second pair of eyes before it reaches a customer, and how you prove afterwards what happened. In a product that can message customers on your behalf, these are not administrative details. They are the difference between automation you can hand to a team and automation you have to watch.
- One workspace cannot see another
- Three roles, narrowed further per person
- You approve the exact message that goes out
- Every action logged, and nothing in that log can be changed
How it works.
- 01
Your data is separated underneath
The separation does not depend on the software asking only for your records. It is enforced below the software, so it holds even when something above it has a bug.
- 02
Roles set the shape
Owner, administrator and operator carry different powers over settings, integrations, publishing and approvals.
- 03
Restrictions narrow it further
On top of a role, one person can be restricted further: masked personal details, contacts limited to their own, no data export, no settings access.
- 04
Everything is written down
Sends, approvals, assignments, connections, exports and deletions are all logged with who did it and when, and nothing in that log can be changed afterwards.
Separation that does not depend on the software
Software that has to remember to ask only for your records is one missing line away from a leak. Here the separation is enforced underneath, so it holds even when the software above it is wrong.
- No other business can read a message, a contact or a file in your workspace
- The separation holds even when the software above it has a bug
- A request for a workspace you do not belong to is refused, not narrowed
Roles and restrictions
Three roles keep the model understandable. Restrictions handle the real world case where one operator should see less than another.
- Owner, administrator and operator
- Mask phone numbers and email addresses per person
- Limit an operator to the contacts they are responsible for
- Restrict data export, contact deletion, settings and integrations
Approvals that hold you to the exact message
An approval is not a note saying somebody agreed. You approve the message that goes out, so change a word afterwards and it comes back to you.
- You approve the exact message, not a summary of it
- The reviewer and their note recorded against it
- Approvals expire instead of sitting open and sending later
- Campaigns, sequences, automated sends and team replies all covered
A record you can check
Every consequential action is logged with who did it and when. Nothing in that record can be edited or deleted afterwards, and it is checked for tampering.
- Nothing in the record can be changed or removed after the fact
- An action and its record are saved together, so neither can exist alone
- Checked nightly, and readable inside the product at any time
Separation between brands and teams
Workspaces are the boundary. A business with several brands, regions or locations keeps them apart.
- Create, switch, rename and delete workspaces
- Members and roles per workspace
- Channels, contacts and reporting scoped to one workspace
What it does not do.
Access is managed inside each workspace. Otobiz does not connect to your own identity provider.
There are three roles plus per person restrictions. You cannot define a role of your own.
An administrator can send a campaign without a second approver, so choose who holds that role carefully.
Common questions
How is my data separated from other businesses?
- The separation is enforced beneath the software, so it holds even when something above it has a bug.
What roles are available?
- Owner, administrator and operator, with per person restrictions layered on top for masking, contact visibility, export and settings.
Can I hide customer phone numbers from an agent?
- Yes. Personal details can be masked for one person while they still work the conversation.
What is recorded?
- Sends, approvals, assignments, status changes, AI switches, channel connections and disconnections, exports, merges and deletions, each with who did it and when.
Can the record be edited?
- No. Nothing in it can be edited or deleted after the fact, and it is checked nightly, so a change made any other way would be detected.
What does an approval actually guarantee?
- That what went out is what you reviewed. Change a word after approval and it comes back to you, and an approval expires on its own.
Is single sign-on available?
- No. Otobiz does not connect to your own identity provider. Access is managed inside each workspace with roles and per person restrictions.
What happens when someone leaves the team?
- Remove them from the workspace. What they did stays in the record, and their open conversations can be reassigned by filtering on them.
Every question in one place, answered once.