Skip to content
Otobiz
Sign in

Several clients, one login, separate data.

Every client gets their own workspace, and you move between them without logging out.

An agency running messaging for clients needs two things a tool built for one business cannot give: strict separation between one client's data and another's, and one place to work from. Otobiz gives each client its own workspace, with its own connected channels, contacts, answers, and record of what was sent, sealed off from every other client, and lets one login move between them.

What usually goes wrong.

One client's data leaking into another's
A shared account or a shared spreadsheet is a single mistake away from a client seeing something they should not. Separation has to be enforced somewhere lower than a dropdown in the interface.
A login per client
Ten clients means ten accounts, ten password resets, and a new starter who cannot work until somebody remembers all of them.
No record of who approved what
When a client asks why a message went out, an agency needs an answer better than a memory. Without a record of who decided and exactly what went out, that conversation is uncomfortable.
Junior staff with senior permissions
The person handling day-to-day replies does not need to export the contact list, delete records, or change the channel connections.

What Otobiz does about it.

A separate workspace for every client

Each client's messages, contacts, and files sit in their own workspace, and no other client's workspace can reach them. The separation is enforced in the database, not by the screen you are looking at.

  • No client can see a message, a contact, or a file belonging to another
  • The separation holds even if something above it goes wrong
  • Each client's channel logins stored encrypted and tied to their workspace

One login, many workspaces

Create workspaces as you take clients on, and switch between them from the top of the interface. A workspace you are not a member of is refused outright rather than quietly narrowed.

  • Switch clients without switching accounts
  • A client workspace you do not belong to is refused, not narrowed
  • Invite a teammate into one client's workspace without the others

Roles and per-person restrictions

Owner, admin, and operator cover the usual split, and one person can be restricted further: hide contacts they are not assigned, mask phone numbers and email addresses, block data export, block deletion, block settings and integration changes.

  • Three roles, with approvals limited to owners and admins
  • Per-person restrictions on export, deletion, settings, and integrations
  • Contact visibility and personal data masking per person

A defensible record per client

Every consequential action is logged, per client workspace: what was sent, to whom, who approved it, and when. Nothing in that record can be edited or deleted afterwards, so a client question has an answer with evidence behind it.

  • One unbroken record per workspace
  • Checked nightly, and readable inside the product at any time
  • Approvals record the reviewer and the exact message approved

A report you can hand to the client

Each client workspace reports on itself: what came in, what was answered, how fast, and what a campaign cost. It is a report you can send on without editing it first.

  • Volume, response time, and campaign results per client
  • Meta's message charges shown against the client's own account
  • Exportable, so it goes in your own monthly pack

What matters most here.

Common questions

Is one client's data really separated from another's?

Yes. One client's workspace cannot reach another's, and the separation is enforced beneath the software, so it holds even when something above it has a bug.

Can one person work across all our clients?

Yes. One login can belong to many client workspaces and switch between them, with access to each one checked every time.

Can we white-label the product?

No. Each client works in a workspace under the Otobiz name, and there is no reseller arrangement.

Can we bill our clients through Otobiz?

No. Billing your clients is your relationship with them. Each workspace reports its own usage so you have the numbers to bill from.

How do we stop a junior from exporting a client list?

Restrict that person. Data export, contact deletion, settings changes, and integration changes are each their own restriction, and contact details can be masked.

Who owns the WhatsApp account, us or the client?

The client. Connection runs through their own Meta business, and the account, number, and templates stay with them if they ever leave.

Can we prove to a client what was sent and who approved it?

Yes. Every send is logged with the approver and the exact message that went out, and you can read that record at any time.

How many workspaces can one login have?

There is no per-user cap. You create a workspace per client and switch between them.