Structuring WhatsApp numbers across HubSpot teams

Most teams start with WhatsApp on whatever phone is at hand. Then a second salesperson joins, support wants in, and one day someone leaves with a handset full of customer conversations. We've been there…

Polser adapts to how your team works, not the other way round. But the decision comes first: before you invite anyone or connect a first number, decide how your team will be organised around WhatsApp. That choice shapes everything that follows, from who sees which conversations to how enquiries get routed.

In most cases, you've already answered a version of this question in HubSpot when you set up your teams, owners and pipelines. Your WhatsApp structure should mirror it.

Across our customers, three models come up again and again.

1. One number, shared by the team

Best for: a support desk or an inside sales team sharing the load.

One WhatsApp number, several people behind it. Work is divided with conversation assignees (who takes which chat) and labels (to organise and find conversations). Customers see one consistent identity, and nothing depends on who happens to be online.

Treat it as a shared inbox, not a shared phone: with everyone on the same line, clear assignment is what keeps chats from falling through the cracks.

2. One number per department

Best for: organisations running WhatsApp across marketing, sales and support at once.

Each department owns its number and the team that works it. Visibility is usually left open, because context is valuable: a support agent who can read the sales thread knows exactly what was promised. And when an enquiry lands in the wrong place, you transfer the chat to the right department, history included.

Customers get clear entry points: one number to buy, another to get help.

3. One number per person

Best for: sales teams where reps own the relationship.

Each rep works from a dedicated number and their own contacts. Visibility is restricted so every user sees only their assigned numbers: clean, private, separated per person. For the customer, it feels like messaging their account manager directly. For you, the number belongs to the company, not to the phone in the rep's pocket.

How to choose

Three quick questions:

• Do customers relate to a person or a team? A person points to model 3; a team to model 1 or 2.

• How many functions talk to customers on WhatsApp? More than one points to model 2.

• Should colleagues see each other's chats? Shared context favours 1 or 2; privacy favours 3.

You don't have to pick one forever. Many teams blend them, for example a shared support line alongside personal numbers for the sales team.

Where Polser fits in

With our native HubSpot integration, every conversation, file and voice note lands on the HubSpot contact record. Marketing, sales and service work from the same history, no matter which number the customer messaged. And with no SIM cards or handsets to manage, reassigning a number when someone leaves takes a click, not a migration.

Ready to configure yours? Our Help Center guide walks through the setup step by step, or book a demo and we'll map your HubSpot structure to the right WhatsApp setup with you.