Assign conversations and next actions

Separate four kinds of responsibility

1. Channel connection: the workspace can receive or send through the provider.
2. Team-inbox route: the correct operational group receives new work.
3. Conversation assignment: one person is accountable for the next decision.
4. Next action: the specific future step and, when needed, its due time.

When teams treat these as one thing, work can be “in Support” but owned by nobody, or assigned to a Member with no clear action.

Assign at the moment of acceptance

Assign when a person has accepted responsibility, not merely when they have looked at the thread.

1. Verify customer identity, team inbox, and current state.
2. Decide whether you can own the next decision.
3. Choose Assign to me or select the authorized teammate who has accepted it.
4. Set priority and timing based on the commitment.
5. Write or record the concrete next action in the appropriate workflow field or linked record.
6. Confirm the assignee appears on the conversation and in the expected queue.

Managers can use team workload evidence when rebalancing, but capacity should not override required skill, access, or continuity.

Write an actionable next step

Use verb + object + dependency + time:

• “Send revised quote after finance confirms discount; tomorrow 09:00.”
• “Confirm replacement dispatch with warehouse; today 16:00.”
• “Review customer's tax document after upload; next business day.”

Avoid “follow up,” “check,” “pending,” or “someone reply.” Those phrases identify anxiety, not executable work.

Choose the right place for the commitment

An internal note can explain a decision, but should not be the only place a due commitment exists.

Handoff without losing context

Before reassigning:

1. read the current conversation and linked record;
2. state what is complete and what remains;
3. preserve the current customer promise and due time;
4. name the reason the new owner is appropriate; and
5. confirm the new owner has access and acknowledges the handoff.

Example: “Buyer requested a GST correction; quote v3 is current and delivered. Reassigned to Nisha for finance-approved revision by tomorrow 11:00.”

Use unassignment carefully

Unassign only when the item is deliberately returning to a staffed triage queue. Do not use unassignment to indicate absence, uncertainty, or “not mine.” If the team responsible is wrong, fix routing and assign a transition owner while the route is corrected.

Pending, snooze, and ownership

Pending describes a waiting state. Snooze moves work to tomorrow morning and pauses the SLA through the recorded bulk action. Neither removes accountability. Verify the owner and Next time after using them, and follow the team's policy before pausing a customer-response commitment.

Prevent ownership failure

• Review Unassigned at defined intervals, not only when a customer escalates.
• Set an alert or operating review for SLA-risk work without an owner.
• Reassign before a planned absence.
• Disable departed members only after their active work has a new owner.
• Avoid assigning large batches solely to make the unassigned count zero.
• Use saved views for monitoring; use a team inbox for a true responsibility/policy boundary.

Measures that matter

Track median time to first owner, percentage of active work assigned, age of unassigned items, handoffs per resolved case, overdue next actions, and reopen/rework after resolution. A fast assignment is useful only if the owner can actually complete the customer outcome.