Team · permissions · measurement

One number and a whole team on it

A company phone works until two people need to reply at once. Then the silent failures start: a conversation everyone assumes someone else answered, an employee who leaves with the customer history in their phone, and a week of unanswered conversations nobody can count.

  • The team on one number
  • Permissions per role
  • Time to first reply
The inbox
online
Good evening — where has my order got to?
👤 Conversation #482 — assigned to: Mona Assigned by the supervisor
⏱️ Unanswered for 12 minutes The unanswered queue
1Number — with the whole team on it at once
3Figures that measure a team: reply time, what is unanswered, each agent's share
✓History belongs to the company, not an employee's phone

A team on one number needs the WhatsApp Business API; the WhatsApp app does not allow it.

The problem

The failure that shows on no screen

An unanswered conversation does not complain. The customer does not write "you never replied"; they buy elsewhere in silence. So the only list that reveals the loss is the unanswered queue — and it is the first thing missing when a team works from a phone.

How it works

The order to do it in

Move the number to the API

The condition that lets a whole team work one number simultaneously.

Add the team and set roles

An agent does not need to see billing, change settings, or delete a conversation.

Set the assignment

By hand from the supervisor, claimed by the first to open it, or handed to a person by the AI agent when the customer needs one. What matters is that every conversation has one known owner. Or automatically: evenly in turn, to whoever is online, by shifts, or to the least busy — conversation routing.

Watch three figures

Time to first reply, the count of unanswered, each agent's share. Those are enough — more gets read once and then ignored.

What you get

What the system does for a team

An owner per conversation

Assignment stops two people answering one customer, and stops a conversation belonging to nobody.

Permissions by role

Whoever replies sees conversations; whoever manages sees billing and settings. The separation protects the company and the employee alike.

The unanswered queue

The most important screen of the day, to be emptied before closing. Every row is a customer waiting.

Time to first reply

The figure the customer feels. Measure it before and after any change, or you will not know if anything improved.

More than one number in one inbox

A branch with its own numbers, or a sales line and a support line — all in one inbox, each number with its own bot, team and reports.

When someone leaves

Their access is revoked and their conversations and history stay where they are. Nothing leaves with their phone.

Compared

The inbox versus a company phone

A WhatsApp phone ArabyBot
Two people replying at once No The whole team on one number
An employee leaves The history leaves with them It stays with the company
What went unanswered yesterday You cannot tell A queue emptied daily
Permissions Everyone sees everything Each role has its own
FAQ

Questions people actually ask

How many agents can work at once?

On the API the number is limited by your plan, not by the app. On the WhatsApp app it is very few and constrained — which alone is why most stores move.

Can an agent reply from their phone?

Yes, from the platform's app — not from WhatsApp on their own number. The conversation stays on the company number and its history stays in place.

What happens when an agent replies while the bot is running?

The bot should pause the moment a human types in that conversation and resume when it ends. That is behaviour to test yourself before trusting it.

Also asked as: «صندوق وارد موحد» · «منصة تربط الواتس والانستغرام وشات الموقع للموظفين» · «إدارة رسايل العملاء» · «كيف أرتب رسائل العملاء» · «CRM للواتس والانستجرام»

Put your team on one number

Assignment and permissions · the unanswered queue · and time to first reply

Start free