How to Set Up Email Routing Rules for Support Teams

Email routing is the traffic control system for your support inbox. Without it, every incoming message lands in a single pile where agents manually sort, decide who should handle it, and hope nothing gets missed. With routing rules, conversations are automatically directed to the right team or agent based on criteria you define.

This guide walks you through setting up routing rules that keep your support workflow organized, fast, and fair.

What Are Email Routing Rules?

Email routing rules are automated instructions that determine where incoming support conversations go and who handles them. When a new email arrives, the routing engine evaluates it against your rules and takes the specified action: assigning it to a team, tagging it, setting a priority level, or directing it to a specific agent.

Routing rules operate on conditions and actions. Conditions define the criteria (the email is from a VIP customer, or the subject contains "refund"). Actions define what happens when the criteria are met (assign to the billing team, tag as "urgent").

Why Email Routing Matters

• Faster first response. When conversations are assigned instantly, agents can start working immediately instead of waiting for someone to triage the queue.
• Right expertise, right away. Routing billing questions to billing specialists and technical questions to technical agents means customers get accurate answers faster.
• Fair workload distribution. Round-robin routing ensures no single agent is overwhelmed while others sit idle.
• Reduced human error. Manual triage is prone to mistakes, especially during high-volume periods. Automated routing is consistent and tireless.
• Better metrics. When conversations are properly categorized and routed from the start, your reporting data is cleaner and more actionable.

How to Set Up Email Routing Rules

Step 1. Map your support categories

Before creating rules, define the categories that conversations will be routed to. These should align with how your team is organized and the types of questions you receive.

Common routing categories:

• General support. Product questions, how-to inquiries, and general help.
• Billing and payments. Invoices, charges, refunds, plan changes, and subscription management.
• Technical support. Bug reports, error messages, integration issues, and API questions.
• Account management. Password resets, account access, data requests, and privacy inquiries.
• Feature requests and feedback. Product suggestions, enhancement ideas, and usability feedback.
• Urgent or critical. System outages, data loss, and security incidents.

Each category should map to a team or queue in your support tool. If your team is small (under five agents), you might only need two or three categories. Larger teams can support more granular routing.

Step 2. Choose your routing strategies

There are several routing strategies, and most teams use a combination:

Round-robin routing. Incoming conversations are distributed evenly across available agents in rotation. Agent A gets the first conversation, Agent B gets the second, Agent C gets the third, then back to Agent A. This ensures fair distribution regardless of conversation type.

Skill-based routing. Conversations are routed to agents based on their expertise. A billing question goes to an agent tagged with the "billing" skill. A technical question goes to an agent with the "technical" skill. This improves resolution quality because agents work on topics they know well.

Load-based routing. Conversations are assigned to the agent with the fewest open conversations at that moment. This accounts for the fact that some conversations take longer than others and prevents overloading agents who are already busy.

Priority-based routing. High-priority conversations (from enterprise customers, or tagged as urgent) skip the normal queue and go directly to a senior agent or a dedicated priority team.

Channel-based routing. Chat conversations go to one team; email conversations go to another. This works when you have agents who specialize in synchronous (chat) versus asynchronous (email) communication.

In TidySupport, you can combine these strategies. For example, billing emails are routed to the billing team (skill-based), then distributed among billing agents by load (load-based), while VIP customers bypass the normal queue (priority-based).

Step 3. Define your routing conditions

For each rule, define the conditions that trigger it. Common conditions include:

By email address. The simplest rule: messages sent to billing@ go to the billing team, messages to support@ go to general support. This works well if you have dedicated email addresses for different functions.

By keyword. Scan the subject line or message body for specific words:

• "Invoice," "charge," "refund," "payment" → billing team
• "Bug," "error," "broken," "not working" → technical team
• "Cancel," "downgrade," "close account" → retention team

By customer attribute. Route based on the customer's plan, tenure, or account status:

• Enterprise plan customers → dedicated account team
• Trial users → onboarding specialist
• Customers with open escalations → the agent who previously handled them

By sender domain. Route emails from specific company domains to a dedicated account manager.

By language. If you support multiple languages, route based on the detected language of the message.

Write out each rule in plain language before configuring it in your tool. For example: "IF the email is sent to billing@ AND the customer is on the Enterprise plan, THEN assign to the Enterprise Billing team with priority High."

Step 4. Set up priority levels

Not all conversations deserve the same urgency. Define priority levels and tie them to your routing rules:

Urgent / P1. System outages, data loss, security incidents, or enterprise customers with critical issues. Target: 30-minute first response.

High / P2. Billing errors, account access issues, or bug reports affecting productivity. Target: 2-hour first response.

Normal / P3. General questions, how-to inquiries, and feature requests. Target: 4-hour first response.

Low / P4. General feedback, non-urgent suggestions, and informational inquiries. Target: 1-business-day first response.

Configure your routing rules to set priority automatically based on keywords, customer tier, or email address. Then configure your SLA rules to enforce response time targets per priority level.

Step 5. Create a fallback rule

Every routing system needs a fallback for conversations that do not match any rule. Without one, unmatched conversations sit in limbo.

Your fallback rule should:

• Assign unmatched conversations to a general queue visible to all agents.
• Optionally notify a team lead so they can manually triage if needed.
• Apply a "needs-triage" tag so you can track how many conversations miss your routing rules. A high miss rate means your rules need refinement.

Step 6. Configure your rules in the support tool

Now implement the rules you designed. In most shared inbox tools, the configuration process involves:

1. Navigate to the routing or automation settings.
2. Create a new rule with a descriptive name (e.g., "Billing - Route to Billing Team").
3. Define the conditions (email address, keywords, customer attributes).
4. Define the actions (assign to team, set priority, add tag).
5. Set the rule's position in the evaluation order (rules are typically evaluated top to bottom, first match wins).
6. Save and enable the rule.

In TidySupport, routing rules are configured in the inbox settings and can be applied across both email and chat channels. Rules support multiple conditions with AND/OR logic, and you can preview which conversations would have matched before activating the rule.

Step 7. Test your routing rules

Before relying on your rules for live traffic, test them:

• Send test emails that match each rule and verify they are routed correctly.
• Send test emails that should match multiple rules and verify the priority order works correctly.
• Send test emails that match no rule and verify the fallback catches them.
• Send test emails from different customer tiers and verify tier-based routing works.

Common issues found during testing:

• Overlapping rules. Two rules match the same conversation, and the wrong one wins. Fix by adjusting rule order or adding more specific conditions.
• Overly broad keywords. A keyword like "help" matches almost every email, routing everything to the wrong team. Use more specific phrases.
• Missing fallback. Conversations that match no rule disappear into an unassigned void. Always have a catch-all.

Step 8. Monitor and refine over time

Routing rules need ongoing maintenance:

Track routing accuracy. Monitor how often agents reassign conversations that were routed to the wrong team. A high reassignment rate indicates rule problems.

Review the fallback queue. If many conversations land in the fallback, your rules have gaps. Analyze what they have in common and create new rules to cover them.

Adjust for team changes. When agents join or leave, or when teams are reorganized, update your routing rules accordingly.

Analyze routing performance. Compare response times and CSAT across different routing paths. If billing-routed conversations have significantly worse metrics than general-routed ones, investigate whether the billing team needs more resources or better tools.

Review your routing rules quarterly as part of your overall support process review.

Common Mistakes to Avoid

• Creating too many rules at once. Start with 3 to 5 broad rules and add specificity as you gather data. Over-complicated routing causes more problems than it solves.
• Using overly broad keywords. Words like "help," "issue," or "question" match almost everything. Use specific phrases or combine keywords with other conditions.
• Forgetting the fallback. Every conversation must go somewhere. An unmatched conversation with no fallback is a conversation that nobody handles.
• Not testing before launch. Rules that look correct in theory may behave unexpectedly in practice. Always test with sample data.
• Setting and forgetting. Your product, team, and customer base change over time. Routing rules that worked six months ago may be wrong today.

FAQ

What is the difference between routing and assignment?

Routing determines which team or queue a conversation goes to (e.g., billing team vs. technical team). Assignment determines which specific agent within that team handles the conversation. Routing is the first step; assignment is the second.

How many routing rules should I create?

Start with 3 to 5 rules covering your main categories (billing, technical, general). Add more as your team grows and your categories become clearer. Too many rules create conflicts and make troubleshooting difficult.

What happens when a conversation matches multiple routing rules?

Most tools process rules in order and apply the first match. Some allow priority weighting. Test your rules with sample conversations to ensure they do not conflict, and define a fallback rule for conversations that match none.

Can routing rules work across email and chat?

Yes, if your support tool supports it. TidySupport applies routing rules across both email and chat channels, so you only need to configure them once.

Should I route by customer tier or by topic?

Ideally, both. Use a layered approach: first route by customer tier (VIP customers to the priority team), then by topic within that team (billing questions to the billing specialist). Most routing engines support this kind of hierarchical logic.