Skip to content
⌘K
InboxAsk a human

Step 5: Getting your threads to the right person

Updated by Dustin

With your historical threads migrated and all of your data enrichment in place, the next step is setting up the building blocks that define your triage strategy. In Plain, those building blocks are labels (what a thread is about), teams (who owns it), business hours (when your team is working), and SLA policies (how fast you promise to reply).

What good looks like

What we define as "good" for this step is having the four objects identified above created in your workspace and ready for Step 6 to reference:

  • 5-8 topic labels, each with a short description so Plain AI knows when to apply it

  • One team label (Support) with every teammate in it and auto-assignment turned on

  • One business-hours schedule reflecting your team's normal working week

  • One SLA policy (paused outside of your business hours), ready to be applied to your Enterprise tier

When a new thread lands in Plain and gets the Support label, Plain should hand it to whichever available teammate has the lightest load — if that teammate goes on PTO and sets themselves Away, the rotation should skip them automatically and assign to the next teammate with the lightest load.

What to consider

In Plain, labels categorize threads by topic (billing, bug, onboarding), just like any other support platform. However, a team is also a label, albeit a special one with the ability to attach users to it — applying it signals ownership (if you're coming from Zendesk, think tags for the first kind and groups for the second). If you're naming a topic, make a regular label; if you're naming people who own work, make a team.

It might be tempting to skip around, but we'd recommend doing the steps identified in this guide in order, as each step builds off the previous one.

How to implement

Step 1: Create your topic labels

Labels support up to three levels of hierarchy (e.g. Billing > Refund), though a flat list of 5-8 is plenty to start — you'll revise these over time as you see what customers actually write in about.

  1. Head to Settings (the gear icon in the sidebar) and click on Labels (or press ⌘K and search Manage labels)

  2. Create 5-8 labels for the topics you'll want to filter or report on

  3. Give each label a one-line Description — Plain AI reads this description when choosing labels in workflows, so a description like "Questions about invoices, charges, and refunds" works much, much better than leaving it blank

  4. Leave Apply with AI toggled on for routine topics, and toggle it off for anything that should stay a strictly human decision

Create the Billing label

Step 2: Create one team and turn on auto-assignment

When a thread gets a team label, auto-assignment can distribute it across the members of that team automatically. Unlike strict turn-by-turn round-robin, Plain's auto-assignment checks availability and current workload before picking someone:

  • Availability: teammates whose status is Away, Break, or Offline are skipped

  • Capacity: teammates holding their max capacity of open Todo threads are skipped

  • Least loaded: among everyone left, the teammate with the fewest assigned Todo threads gets the thread

Because auto-assignment triggers the moment a team label is added to an unassigned Todo thread, putting the Support label on a thread is routing it — you don't need a separate assignment step.

To set it up:

  1. In Settings → Labels, click Add team, name the team label (e.g. Support) and click Create new team label

  2. On the team's page, under Auto-assignment, toggle on Auto-assign threads for this team

  3. Set Maximum threads per user to 5 (the maximum number of Todo threads an agent can hold before being skipped), click Save changes, then click Add team member to add each teammate

Create a team and turn on auto-assignment

While you're here, check Settings → Away mode. Users can set themselves Online, Offline, or Away from their profile — Offline is meant for shorter breaks, like lunch, or potentially even longer breaks between shifts like overnights (no new assignments, keeps existing threads), while Away is for PTO.

The workspace-level Away mode setting decides whether going Away unassigns all of that person's open threads immediately, or only unassigns threads that get new activity while they're away. For a small team, we recommend keeping the default setting, Unassign immediately, to keep threads visible in your workspace views vs. potentially being hidden in a user's queue while on PTO.

Turn on away mode

Step 3: Set your business-hours schedule

Business hours tell Plain when your team is working so SLA timers can properly reflect them, and so workflows can tell whether a message arrived out of hours. Set this up before your SLA policy so the policy can reference it.

  1. Head to Settings (the gear icon in the sidebar)

  2. Click on Business hours

  3. Click Add business hours

  4. Give it a name (e.g. Support hours), check the prefilled Timezone (Plain defaults it to your browser's timezone), and adjust the default Mon-Fri 09:00-17:00 hours if needed (days without entries show as Closed)

  5. Click Save

Add your support hours

Step 4: Create one SLA policy

An SLA policy is a named set of response and resolution targets (if you're used to Zendesk SLAs that carry their own conditions, note that a Plain policy has no conditions of its own — it only takes effect once a workflow or a user applies it to a thread). We'll create the policy here and wire up the workflow that applies it in Step 6.

  1. Head to Settings (the gear icon in the sidebar)

  2. Click on SLA policies and click New SLA policy

  3. Name it Enterprise first response

  4. Set First response time to 1 hour (leave the other three targets off to start)

  5. Set Send a notification before target to 15 minutes so the thread flips to Imminent breach before the deadline passes

  6. Under Business hours, select the Support hours schedule from Step 3, then click Create SLA policy. Plain will open the new policy and offers to add it to a workflow — choose Not now, as we’ll be doing this manually later

Create the Enterprise first response SLA policy

If you're on the Foundation plan, SLA policies aren't included — you can skip this step and make a custom view to help make threads that are unassigned easier to locate.

To build it, open Views in the sidebar and click Create view: a new view defaults to Todo, so add Filters → Assignee → Unassigned, check that Display shows Status changed at, oldest first, name it Todo unassigned, and click Save view. Plain saves the new view into your Favorites automatically.

Create the Todo unassigned saved view

Some gotchas to be aware of:

  • Auto-assignment only acts on Todo threads with no existing assignee. If a thread is already assigned to a teammate or to the Customer Agent, adding the team label won't reassign it.

  • If every member of the team is Away, Offline, or at max capacity, the thread stays unassigned until someone frees up or comes back online (at which point their teams are backfilled automatically).

  • A thread can have one SLA policy at a time, or none. Only a reply from a human user achieves a response target — a reply from the Customer Agent doesn't count.

  • Setting a thread to the Waiting for customer status cancels the response time target (you've replied, so nothing is due). Setting it to Paused for later keeps the clock ticking.

How to verify if this step is working/complete

  1. Open an unassigned Todo thread in Plain (we’d suggest sending an email from a personal address, as that bypasses the internal user check and threads made with the Create test thread option are skipped by auto-assignment) and add your Support team label from the Labels row in the thread sidebar. Confirm the Assignee field updates to an online teammate's name without you having to manually change it.

    Label a thread for the Support team
  2. Click the SLA policy row in the thread sidebar and apply Enterprise first response. Confirm the countdown appears in the thread header (hover it to see the First response due by deadline).

    Apply an SLA policy to a thread
  3. Set yourself to Away from your profile, create or reopen a second unassigned test thread with the Support label, and confirm it assigns to someone else on the team (or stays unassigned if you’re the only user in your workspace)

Troubleshooting/FAQ

I applied the team label, but the thread wasn't assigned to anyone.

Plain's auto-assignment only runs at the moment a team label is added to a Todo thread that has no existing assignee, and it skips anyone who is unavailable or at capacity. Here are the three reasons a labeled thread stays unassigned (or stays with its previous owner):

The thread already had an assignee when the team label was applied

  • If a thread is already assigned to a teammate — or to the Customer Agent — adding the Support label won't overwrite that assignment.

  • Try this: In Step 6's routing workflows, either apply the team label before any direct assignment step, or explicitly unassign the thread first when handing work off from the Customer Agent or an individual to a team queue.

Every member of the team is unavailable or at max capacity

  • Teammates whose status is Away, Break, or Offline, or who are already holding their max capacity of open Todo threads, are skipped. If nobody is eligible, the thread waits unassigned until someone frees up or comes back online (at which point Plain backfills their queue automatically).

  • Try this: Set a realistic max capacity (start around 5-10 for a small team so a busy morning doesn't cause the rotation to hang), and make sure teammates use Offline for short breaks and Away (with immediate unassignment enabled under Settings → Away mode) when they're out for the day so their open threads don't block capacity management.

Auto-assignment wasn't toggled on for the team label

  • Toggling on auto-assignment is a distinct step from team label creation and member assignment.

  • Try this: Whenever you create a new team under Settings → Labels, open the team's settings and ensure that the Auto-assign threads for this team setting is toggled on before referencing that team in a workflow.

The SLA timer is still counting down overnight, on weekends, or on a public holiday.

An SLA policy only pauses outside of working hours if it's explicitly linked to a business-hours schedule — and Plain's schedules model a recurring week rather than date-specific holidays.

No business-hours schedule is attached to the SLA policy

  • Targets with Business hours turned off (or no schedule selected) run off a 24/7 calendar.

  • Try this: Create your business hour schedules under Settings → Business hours before creating your SLA policy, then make sure to select that schedule inside the policy before attaching the policy to any of your workflows.

A thread was set to "Paused for later" instead of "Waiting for customer"

  • Replying to a customer or setting a thread to the Waiting for customer status stops the SLA timer, whereas pausing the thread will keep the clock ticking.

  • Try this: Train your team to use Waiting for customer whenever the ball is in the customer's court, and reserve Paused for later for internal reminders where you still owe the customer a reply.

Upcoming public holidays or company-wide shutdowns

  • Because business-hours schedules repeat weekly and don't natively include a holiday calendar, SLA timers will count down on a bank holiday unless you adjust the schedule.

  • Try this: Ahead of a holiday, either adjust that day's hours in Settings → Business hours for the week, or use an LLM / Sidekick to run a short script against the public business hours API (updateBusinessHoursSchedule) to temporarily mark the holiday closed and restore normal hours the next day.

I can't find where to create a team.

In Plain, teams aren't configured on a separate Teams page — a team is a special type of label with members and auto-assignment settings attached to it.

Try this: Head to Settings → Labels when you need to create a team, add or remove teammates from a rotation, or adjust max capacity.

Plain AI applied a label I only wanted humans to use (or isn't applying a label I expected).

By default, new labels have Apply with AI enabled, and Plain AI relies on each label's Description to decide when a thread matches.

Try this: When creating labels in Settings → Labels, write a specific one-sentence Description on every routine topic label ("Questions about invoices, charges, and refunds" rather than leaving it blank), and toggle off Apply with AI on sensitive or internal-only labels (escalated-legal, churn-risk, vip-override) so only a teammate or an explicit workflow rule can apply them.