How to Manage Multiple WhatsApp Numbers per Department

To manage multiple WhatsApp numbers, each number is linked to its own table, so every department runs its own process on its own line while the whole thing sits on one account.

Why a single shared number breaks down

One number works until two different kinds of conversation arrive on it.

Support requests and sales enquiries in the same queue
The wrong team seeing conversations they should not
No way to report on one area separately from another
Routing done by whoever happens to read the message first

One number per process: what it enables

Department	Linked process	What it isolates
Support	Ticket pipeline	SLA tracking and resolution reporting
Sales	Opportunity pipeline	Deal stages and commercial follow-up
Operations	Request pipeline	Internal requests and their approvals

How to configure it in Jestor

Add each WhatsApp number to Jestor through the Meta connection flow.
Link each number to the specific table for that process.
Set permissions so each team sees only its own conversations.
Choose which templates are available on each number's process.
Set a distinct chat background colour per process to tell them apart at a glance.

Why choose Jestor for multi-number WhatsApp?

Jestor supports multiple numbers on the same account, each tied to its own process — so a growing company adds a line rather than reorganizing a shared inbox.

The number in use is displayed at the top of the conversation, which removes the common mistake of replying to a customer from the wrong department's line.

Frequently Asked Questions

How many numbers can I add?

Multiple numbers are supported on the same account.

Can two processes share one number?

No. Each number links to one table. See jestor.com.

Can I tell which number I am using?

Yes, it is shown at the top of the conversation.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,