Assign Transfer Close Tickets: Practical Wapilot Guide

In this series — Part 2 of 6 (Inbox & Team). · Previous: Shared WhatsApp Inbox Guide: Manage All Chats i… · Next: Labels, Notes & Canned Replies: Speed Up Agent… · Series start

Before you start: If you skipped earlier steps, read Shared WhatsApp Inbox Guide: Manage All Chats i… first so nothing here feels confusing.

Shared inbox without ownership means everyone thinks someone else will reply.

Duplicate answers, silent unassigned chats, and transfers without context create customer restarts. WhatsApp ticket workflow turns chats into accountable work items.

In this guide, you'll discover assign, transfer, and close best practices, SLA habits, and an ownership cheat sheet for Wapilot teams. As a WAPilot team that coaches ticket hygiene weekly, we see “please handle” transfers waste more time than slow typing.

One primary owner per open chat. Notes before transfer. Close only when the question is answered and no promise hangs.

Inbox foundation: shared WhatsApp inbox. Roles: team roles. Campaign spikes: bulk campaigns.

WhatsApp ticket workflow makes ownership explicit: one primary agent per open chat, notes before transfer, and close only when the customer outcome is real—especially on campaign spike days.

Why does WhatsApp ticket workflow matter for teams?

Sources: Meta's Cloud API get-started guide and messaging limits overview. Clear ownership speeds first response, prevents duplicate replies, creates accountability, and gives managers backlog visibility. Treat chats like tickets on the shared inbox.

How should assign, transfer, and close work?

Assign when a chat needs an owner, skills match, load is uneven, or a campaign spike hits. Unassigned shouldn’t sit long. On transfer: short internal note (what’s done + what’s needed), right agent, confirm visibility, don’t disappear mid-promise. Close when answered, next step done or scheduled, and no hanging promise.

Attributed example, from a WAPilot logistics workspace (2026): requiring a one-line note before transfer cut “restart from zero” complaints and shortened resolution time on order chats.

1. Claim or assign every active thread
2. Keep one primary owner
3. Note before transfer
4. Confirm new owner sees it
5. Close only when resolved

Rule sources: Meta Cloud API get-started and messaging limits docs. Wapilot assignment tools coordinate humans; Meta does not define your SLA.

What SLA habits keep unassigned from rotting?

First-response targets during business hours, hourly unassigned review, extra staffing on campaign days, and end-of-day checks for silent urgents. Write the SLA and train on it: quality rating suffers when replies languish after ads.

What does the ownership cheat sheet look like?

New unread → assign/claim. Needs specialist → note → transfer → confirm. Resolved → note + label → close. Bot stuck → handover with context. How we know: WAPilot ticket coaching weekly reflects real multi-agent Cloud API ops—not phone-forward folklore.

Don’t close just to clear the queue while the customer waits. Managers watch agents who only pick easy chats.

WhatsApp ticket workflow fails quietly when unassigned chats age out of sight. Hourly review during business hours—and more often on campaign days—keeps promises alive. First-response targets only matter if someone owns the thread before the timer starts.

Transfers without notes force customers to re-explain. That restart feeling drives frustration even when both agents are skilled. Require a short internal note as policy, not a suggestion. Confirm the new owner sees the chat before you walk away.

Closing is a customer outcome, not a personal inbox cleanup trick. If a promise is hanging, keep the ticket open and scheduled. Managers should watch cherry-picking: easy FAQs cleared while complex order chats rot is how SLAs look fine and revenue suffers.

Write ownership rules for bot escalations the same way you write them for human transfers. Escalation without an assignee is just a louder unread pile. Ticket discipline turns the shared inbox into a system customers can trust across shifts.

Make WhatsApp ticket workflow measurable: first response time, unassigned age, transfers without notes, and premature closes. Review outliers weekly. Coaching beats blame. When campaign days hit, pre-assign capacity the way you pre-approve templates—ownership is part of send readiness, not an afterthought once unread explodes.

Bot escalations inherit the same rules: assign immediately, leave context, keep one primary owner. Escalation into a void is just a louder unread queue with angrier customers attached.

FAQs

Who should assign chats—manager or agent?

Both: managers route and balance; agents claim intentionally when policy allows.

When is it OK to leave a chat unassigned?

Almost never for long—review unassigned on a set cadence.

What’s the difference between transfer and close?

Transfer changes owner while work continues; close ends the ticket after resolution.

Does a bot-to-agent handoff reset the window on a shared number?

No. One customer thread, one service window. Two brands on one Cloud API line share that clock—split numbers before you scale support and promos on the same line.

Recap: one owner, notes on transfer, close when done, SLA habits. When ready, start a free trial and grow on official Cloud API.