Running your business WhatsApp as a team

For many service businesses, WhatsApp is the front door. Customers send a photo of the problem, ask for a price, confirm the visit and send the payment screenshot, all in one thread. That convenience turns into a problem the moment the business outgrows one person: the number lives on one phone, the history leaves when that person does, and nobody can tell whether a message has been answered.

This guide covers how to run a business WhatsApp number as a team.

One number, shared

Customers should message the business, not a person. That means one business number, visible to everyone who serves customers, rather than technicians and salespeople using their personal numbers.

Personal numbers feel faster at first. They cost you later: the enquiry that went to a technician who was on leave, the customer who followed a salesperson to a competitor, the price nobody else knew had been quoted.

Decide who owns each conversation

A shared inbox without ownership is worse than none, because everyone assumes someone else replied. Give every conversation a state and an owner:

• Open conversations need a reply. Each one is assigned to a person.
• Snoozed conversations are waiting for something, such as the customer's photos or a date, and come back on their own.
• Closed conversations are done.

Review "open and not assigned" several times a day. It should usually be empty.

Talk to each other beside the conversation

The second most common WhatsApp failure is the forwarded screenshot: a salesperson screenshots a customer message into a staff group to ask a technician a question. Now the context is split across two chats and the customer's data is in a group it should not be in.

Use internal notes on the conversation itself instead, visible to the team and never sent to the customer. The question, the answer and the customer's thread stay together.

Turn conversations into records

A conversation is not a lead, a quote or a booking. When a message becomes business, create the record, a lead, a quotation or a visit, with the chat attached, so the rest of the company can act on it without reading the thread.

Know the rules of the official API

If you connect through Meta's official WhatsApp Business Cloud API, one rule shapes your workflow: you can send free-form messages only within 24 hours of the customer's last message. After that, Meta requires pre-approved template messages. Plan for it:

• Reply to enquiries quickly, while the window is open.
• Ask for the details you need (address, photos, preferred time) in the same exchange.
• For reminders days later, such as an upcoming visit or an overdue invoice, you need templates or another channel.

If you add an AI agent, give it a short leash

An AI agent can answer the same five questions you get fifty times a day: prices for standard services, opening hours, whether you cover an area. It should not improvise on anything with consequences. Good guardrails:

• Let it answer only from your own documents and product list.
• Let it take a callback request rather than make a promise.
• Hand over to a person on request, and whenever it is unsure.
• Make it easy for staff to pause it for a single conversation.

How Orbit handles it

Orbit's WhatsApp inbox connects a number by QR code or the official Cloud API and puts every conversation in a shared inbox with open, snoozed and closed views, assignment, stages and internal notes. A conversation becomes a lead in one click, and quotations and invoices can be sent over WhatsApp from the record. The optional AI agent answers from your knowledge base with a limited set of customer-safe actions, and can be set to Auto, Paused or Off for each conversation.

Orbit does not send WhatsApp template messages yet, so on the Cloud API, replies after the 24-hour window are not possible from Orbit.