A shared WhatsApp inbox needs an operating agreement as well as staff access. Decide who owns each enquiry, how handoffs work and which actions require approval before inviting the whole team.
Define ownership
A customer should not receive conflicting answers from several employees. Assign responsibility for the next response and make that responsibility visible. Shared visibility can help a manager intervene, but it should not leave every conversation owned by everyone.
Prepare roles
List the people who need to answer customers, approve commercial terms, configure integrations and manage access. Give each role the appropriate permissions. Check customer-number visibility and the actual role permissions with a test user before inviting staff.
Use an internal handoff note
A useful handoff note might read:
Customer requests ten units of the specified model. Quantity confirmed; delivery location still needed. A revised price requires manager review. Next action: confirm location before preparing the quotation.
This is a fictional example. It separates facts, missing information and required approval, giving the next person enough context to act.
Configure the human takeover before the trial
In HeidelAI, use the conversation's AI controls to pause AI before replying yourself. The pause menu offers timed pauses and an until-resumed option; Resume AI now returns the conversation to AI when the team is ready. Choose a pause that covers the expected handoff, rather than assuming a single employee reply permanently changes automation ownership.
Use a private Note for internal context, and use Assign work or owner to choose the appropriate person or team. A note explains what needs doing; it does not replace assigning the next response. Inspect the selected destination and its permissions before transferring responsibility. These are product controls to test, not a guarantee that every workspace has the same staff and integrations configured.
See the shared team inbox feature and AI agent overview when defining responsibilities.
Test with two users
Use a permitted test conversation. Have one person clarify the requirement, add internal context and transfer responsibility. Ask the second person to describe the customer's request without consulting the first person outside the system.
If the second person cannot identify the next action, improve the handoff format or workspace setup. Then check a new customer reply arriving during the transfer.
Coordinate AI and people
Define when AI may answer, when it should request clarification and how staff take over. A buyer asking for a human should have a clear route. Avoid parallel automation that keeps replying after a salesperson has intervened.
Review a small queue first
Start with a limited set of conversations. Look for unanswered requests, duplicate replies and ambiguous ownership. Agree on coverage when a colleague is absent. The software can make work visible, but the business still needs a person responsible for the queue.
Once handoffs are reliable, use the CRM buyer's checklist to evaluate your wider sales process. For the next customer touch, review WhatsApp follow-up messages.