Prepare customer support triage for a new team member by giving the smallest required access, teaching one queue map and escalation path, practicing on non-live examples, and reviewing early decisions before the person sends independently. Access to the inbox is not the same as readiness to handle every customer or action.

Define the role and boundaries first

Write the new user's responsibilities: channels covered, products supported, working hours, languages, customer segments, and actions they may take. Separate view, assign, reply, export, refund, delete, configure, and administer permissions. Intercom's teammate permissions guide treats conversation access, reassignment, exports, settings, applications, and rule management as distinct capabilities. Grant only what the starting role needs.

If the user will see sensitive conversations, identify the approved teams and data categories. Intercom's conversation access guidance describes limiting access to assigned conversations, team conversations, or selected inboxes, with unavailable details redacted. Test the new account itself; an administrator's view does not prove the new user's boundaries.

Teach the queue map

Create a one-page map of intake channels, team inboxes, unassigned queue, urgent queue, billing or account queue, spam handling, and follow-up states. Define what "new," "open," "pending," "waiting on customer," and "closed" mean in this workspace. Add the default destination when a ticket does not match a specialty rule.

Intercom's team inbox guidance explains manual, round-robin, and balanced assignment. Help Scout's routing guidance says automatic routing considers active status and assignment limits and leaves conversations unassigned if nobody is eligible. Show the newcomer how to find those unassigned items and who owns the queue during low coverage.

Document escalation thresholds

Use concrete categories: immediate safety risk, account takeover, privacy request, payment dispute, legal demand, vulnerable person, suspected fraud, widespread outage, abusive content, and ordinary product questions. For each, name the destination, notification method, information to preserve, and actions the new user must not take. Keep emergency and legal contacts current and verified.

Teach the difference between an internal note and a customer reply. Explain when to transfer, when to add a teammate, and when not to duplicate an external response. Do not use a saved reply for a case that needs diagnosis, consent, or individualized legal or financial wording.

Provide approved tools without hiding judgment

Give access to current knowledge articles, status pages, troubleshooting checklists, approved saved replies, refund or cancellation policy, and account-verification steps. Mark the document owner and last review date. A macro should prepare repeatable fields or phrasing, not make a consequential decision on the agent's behalf.

Help Scout's workflow introduction distinguishes automatic background rules from manual workflows a user deliberately applies. Begin the new user with manual, reviewable assistance where possible. Zendesk's trigger overview notes that conditions and actions can interact across triggers, so trainees should know that an assignment or status change may activate other rules.

Practice before using live customer records

Create synthetic cases covering routine routing, an ambiguous request, missing account data, an angry customer, suspected security risk, a full team queue, and a message sent to the wrong address. Ask the trainee to classify, assign, draft, escalate, and explain the evidence used. Review the result without sending.

Then use a supervised live phase with a small queue and a named reviewer. Require review for external replies and high-impact changes until the person demonstrates consistent handling. Track misroutes, unnecessary escalations, missed risks, duplicate replies, and use of unapproved promises.

Verify availability and handoff behavior

The new user should know how presence affects routing and how to hand off at shift end. Help Scout's status guidance explains that active or away status affects automatic routing while manual and workflow assignments can behave differently. Practice setting away status, reassigning owned work, leaving an internal note, and confirming that urgent items still have an owner.

Complete a readiness check

Before independent triage, verify login recovery, multifactor authentication where required, conversation access, queue visibility, status, assignments, internal notes, draft replies, escalation, and shift handoff. Record who approved readiness and which restrictions remain. Schedule a review after the first week and after any major workflow change.

Good onboarding makes the safe path obvious. The new teammate knows what they can see, what they can decide, where uncertainty goes, and who remains accountable when automation or documentation is not enough.

Sources

  1. Teammate Permissions: How to Control Workspace Access — Intercom Help
  2. Limit Teammates' Access to Conversations — Intercom Help
  3. Organize Team Inboxes — Intercom Help, July 6, 2026
  4. Use Routing to Automatically Assign Conversations — Help Scout Support
  5. Get Started With Workflows — Help Scout Support
  6. About Zendesk Triggers and How They Work — Zendesk Help
  7. Manage Your Status and Availability — Help Scout Support

Related reading