HomeFeaturesTeam

Team

Several people, one number.

A shared WhatsApp number is a shared responsibility. Birsend’s answer is narrow permissions, accounts an admin can create outright, and a record of who did what — so a team of four can share one line without anybody guessing.

16 areas
each with view and change
3 roles
ready to use, plus your own
Per-area
permissions, not per-screen

What you get

Create accounts for colleagues, decide exactly what each role may touch, and keep track of the work the team owes each other.

Accounts you create yourself

Set a colleague’s name, address and password and hand it over. No invitation email to wait for, no link that expires unread.

Roles you can actually read

Sixteen areas, each with “see it” and “change it”. Admin, Agent and Analyst ship configured; add your own groups beside them.

A shared task list

Assign work to a person with a due date, add notes as it progresses, then complete or cancel it. Nothing here reaches a customer.

Nobody answers twice

The inbox shows who is already in a conversation and lets you hand a thread over, so two people do not reply to the same customer.

Work filed by client

Running campaigns for other businesses? Attribute each one to a client and keep the history straight, years later.

Sessions you can revoke

See every signed-in device on an account and sign the others out. Changing a password does it automatically.

How it works

01

Adding somebody takes one form

You type their name, address, password and role, and the account exists. They sign in immediately. There is no invitation state to chase, and no half-created member sitting in the list for a fortnight.

  • The password is shown back to you once, so you can pass it on
  • Removing somebody revokes every session and API token they held
  • Their messages, notes and campaigns stay attributed to them
02

Permissions that describe consequences

Each area says what granting it actually lets somebody do — “Connect a model and hold its API key. This spends the account’s money” rather than “manage AI”. A permission you cannot understand is a permission you grant by accident.

  • Turning on “change” turns on “see” with it, because the other combination is a broken screen
  • An admin cannot remove their own ability to manage the team — the next screen would be read-only for everybody
  • A role can be narrowed after it is created, and narrowing sticks: new permissions are not granted retroactively
03

Tasks, for the work that is not a message

A call to return, a list to check, a supplier to chase. Tasks are assigned to a person, carry a due date and a thread of notes, and close as either done or cancelled — a distinction that still means something a year later.

  • The list is shared, not personal. “Mine” is a filter, not the default view
  • Overdue is computed from today, so it cannot go stale
  • Notes are append-only: a correction is a new note, and the thread reads as what was actually said

What it does not do

The honest list. We would rather you found this here than three weeks into a trial.

  • There is no outbound mail on this platform, which is why accounts are created outright rather than invited. It also means no password-reset email — an admin sets a new password.
  • Tasks have no contact, number or consent attached. Nothing on that screen can reach a customer’s phone, and that is deliberate.
  • Seats are limited by your plan.

Questions

Can I stop an agent from seeing the reports?

Yes. Reports are their own area, because whoever can open them can see the shape of the whole business. Turn it off for a role and the screen and the endpoint both refuse.

What happens to somebody’s work when they leave?

Their sign-in stops working and their sessions are revoked. Everything they wrote — messages, notes, campaigns, log entries — keeps their name on it.

Cookies

The site runs what it needs to work, including the Crisp chat bubble. Google Analytics is the one thing we will not load unless you agree to it.