KoltrixHandling priority customers without a two-tier mess
How to give priority customers faster email support without neglecting everyone else: defining priority, labels, targets, named contacts and honest plan terms.
On this page(9 sections)
- Step 1: Define priority explicitly
- Step 2: Make priority visible in the inbox
- Step 3: Set separate targets, and keep them realistic
- Step 4: Give priority accounts a named contact
- Step 5: Protect everyone else
- Step 6: Be transparent about what each plan gets
- Step 7: Review the list regularly
- Common mistakes
- Bottom line
Every support team eventually has customers who matter more to the business: the account that's a third of revenue, the design partner shaping the roadmap, the enterprise contract with a response-time clause. Treating them faster is reasonable. Doing it without letting everyone else slide is the hard part.
This playbook covers how to define priority, make it visible in the inbox, set targets, and stay honest with the rest of your customers about what they get.
Step 1: Define priority explicitly
"VIP" handled by gut feel turns into favoritism, inconsistency, and agents guessing. Write down what qualifies.
Common criteria:
| Criterion | Example | Notes |
|---|---|---|
| Plan or tier | Customers on your highest plan | Easy to verify; matches what they pay for |
| Contractual commitment | Accounts with a response-time clause | Non-negotiable; you agreed to it |
| Strategic relationship | Design partners, launch customers | Time-limited; review regularly |
| Temporary risk | Accounts in a renewal window or recovering from an incident | Set an end date |
Avoid criteria that agents can't check quickly, like "important logos" or "people the founder knows". If it isn't written down, it isn't a priority rule.
Keep the priority list small. If a large share of your customers are "priority", nobody is.
Step 2: Make priority visible in the inbox
Agents shouldn't need to look up every sender in a spreadsheet. Make priority show up where they work:
- A label such as
priorityortier-1, applied automatically by a rule matching the customer's email domain. - A list of domains maintained by one owner, with a review date.
- A short account note for each priority customer: who the contacts are, what they use, any ongoing issues.
With labels and auto-label rules, as in Koltrix, a rule that tags mail from a priority customer's domain does most of the work. The key is that one person owns the list, adds new accounts, and removes ones that no longer qualify.
Step 3: Set separate targets, and keep them realistic
Priority customers typically get a faster first response. Write targets down for both groups:
| Priority | Everyone else | |
|---|---|---|
| First response, business hours | Within a few hours | Same or next business day |
| Blocking issues | Escalated immediately | Escalated same day |
| Updates on open issues | At an agreed cadence | When there's news |
| Named contact | Yes | Team |
The numbers depend on your team size. What matters is that both columns are commitments you can keep. A priority target that's routinely missed is worse than no target, because it was promised.
Step 4: Give priority accounts a named contact
For most priority customers, the biggest difference isn't speed. It's continuity: talking to someone who knows their account.
- Assign one primary and one backup contact per priority account.
- The primary replies to their threads where possible, even if someone else triages.
- When the primary is away, the backup handles it, with the account note as context.
This also reduces repeated questions. Someone who already knows the customer's setup doesn't need to ask which plan they're on.
Step 5: Protect everyone else
This is where priority programs usually fail. Faster service for some customers means slower service for others unless you plan for it.
Guardrails that help:
- A floor for everyone. The standard target applies to all customers, priority or not, and you track it.
- Priority doesn't jump blocking issues. A non-priority customer whose account is down outranks a priority customer's how-to question. Severity first, tier second.
- Watch the oldest open threads, not just the newest. Non-priority threads can age quietly.
- Rotate priority duty if one person ends up permanently on priority accounts while others drown in the general queue.
A simple rule for the triage pass:
Order of work:
1. Anything blocking, any customer
2. Priority customers, oldest first
3. Everyone else, oldest first
4. Non-urgent priority requests can wait behind blocking issues from anyone
Step 6: Be transparent about what each plan gets
Customers notice differential treatment. Hiding it creates resentment; explaining it rarely does.
- Publish support levels on your pricing page or in your terms: response targets, channels, named contacts.
- Don't promise "priority support" without defining it. Customers will fill in the blank with their own expectations.
- Don't apologize for the standard tier. It's a legitimate offering. Describe it plainly.
When a non-priority customer asks why someone got a faster answer, the honest answer is that some plans include faster response times, and here's what yours includes.
Step 7: Review the list regularly
Priority status should be earned and maintained, not permanent:
- Quarterly: check every account on the list against the written criteria. Remove ones that no longer qualify, such as finished design partnerships or downgraded plans.
- After each renewal: confirm whether the contract terms changed.
- After incidents: temporary priority status for affected accounts should end on a set date.
Tell customers when their status changes, especially if they're losing a named contact.
Common mistakes
- Priority by seniority of the person emailing. A CEO's how-to question isn't more urgent than a user's outage.
- Unwritten exceptions. "Always reply to them within the hour" lives in one person's head and disappears on their vacation.
- Priority for complainers. Rewarding the loudest customers with priority status teaches everyone to complain.
- No exit. Accounts stay on the list long after the reason disappeared.
Bottom line
- Write down who qualifies for priority, and keep the list small and reviewed.
- Make priority visible with labels and a rule on the customer's domain, owned by one person.
- Set realistic targets for both priority and standard customers, and track both.
- Put severity before tier, so blocking issues from anyone come first.
- Be open about what each plan includes; clear terms prevent the resentment a hidden two-tier system creates.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
