Automating Ticket Routing to Key Account Managers for a Horticultural Supply Company
A horticultural supply company's service desk was drowning. Ticket volume was high, the shared inbox had no routing logic, and tickets landed anywhere but with the key account manager who actually knew the customer. We rebuilt the ticketing layer in HubSpot Service Hub, with owner-aware auto-creation, case-type prioritization, round-robin distribution, and naming standards that made the queue searchable.
Executive Summary
Context
A landscape-supply business whose commercial customers each work with a dedicated key account manager. Service requests arrived by email into a conversations inbox, but nothing connected an incoming message to the relationship that already existed, so response times suffered exactly where the accounts mattered most.
What We Built
An automated ticketing system in HubSpot Service Hub: owner properties for account managers, automatic ticket creation from the conversations inbox with assignment to the contact's existing key account manager, case-type-based prioritization, round-robin distribution for unowned tickets, standardized ticket naming, and the training to run it.
Not a fit for teams without named account ownership, service desks running outside HubSpot, or organizations looking for a full helpdesk migration rather than an optimization of an existing Service Hub portal.
The Challenge
Every commercial customer had a key account manager, but the service desk didn't know it. Emails entered a shared conversations inbox and waited for manual triage: someone had to recognize the sender, remember which account manager owned the relationship, create a ticket, and hand it over. At high volume that chain broke daily. Tickets reached the wrong people, urgent case types sat behind routine ones, and inconsistent ticket naming made it nearly impossible to search history or spot recurring product issues. The service team was working hard inside a system that made every request start from zero.
Our Approach
We treated the existing account relationships as the routing table. Owner properties were established for the account management team, so the system could answer the question the inbox couldn't: who already owns this customer? Automation then did the triage. When an email enters the conversations inbox from a contact with an assigned key account manager, a ticket is created automatically and assigned to that manager. Tickets without an existing owner rotate evenly across the team, and priority is set from case type so urgent categories jump the queue. Ticket names were standardized into a consistent format for searchability, and an error log was maintained through rollout to catch and correct automation edge cases. Training sessions closed the loop so the team ran the system rather than around it.
Impact
Tickets Land with the Person Who Knows the Account
Automated workflows filter and assign incoming tickets to the correct key account manager the moment they arrive, removing the manual triage step that caused delays. Response times improved where they matter most: the owned accounts.
Priority Follows Case Type, Not Arrival Order
Case type sets priority at creation, so urgent categories are worked first regardless of when they arrived, and unowned tickets distribute evenly across the team instead of piling on whoever checked the inbox last.
A Searchable Queue Instead of a Naming Free-for-All
A standardized ticket naming format made the queue consistent and searchable. Service staff can find prior tickets for an account or a product issue instead of reconstructing history from email threads.
Ticket Data Became Operational Insight
With tickets structured and consistently categorized, the ticket dataset became analyzable: trends, bottlenecks, and recurring issue types are visible in reporting, and manual processing effort dropped with the automation.
Technical Blueprint
1
When an email enters the conversations inbox and the sender is a contact with an assigned key account manager, a workflow creates a ticket and assigns it to that manager automatically. The routing table is the CRM's existing ownership data, not a separate rules engine to maintain.
2
Ticket priority is set from case type at creation, so the queue reflects operational urgency rather than arrival order. The case-type taxonomy doubles as the reporting dimension for trend analysis.
3
Tickets from contacts without an assigned owner rotate evenly across the service team. Even distribution keeps workload balanced and prevents the shared-inbox pattern where visibility, not capacity, determines who works a request.
4
Ticket names follow a consistent format for organization and search. During rollout, an automation error log tracked misfires, like edge cases in auto-creation, so the logic was corrected against real traffic rather than assumed correct at launch.
FAQ
How do you route tickets automatically when customers already have account managers?
Use the ownership data the CRM already holds. We established owner properties for the account management team and built workflows that check the incoming contact's assigned manager: if one exists, the ticket is created and assigned to them automatically; if not, it enters an even rotation. No parallel routing rules to maintain, no dependence on whoever reads the inbox first.
What stops round-robin assignment from misrouting urgent cases?
Priority and assignment are separate mechanics. Case type sets priority at ticket creation, so an urgent category is flagged before anyone touches it, while rotation only decides who receives unowned tickets. An urgent case from an owned account goes straight to its account manager already marked high priority.
Spice up your inbox
Sign up for our newsletter
Don't worry - we only average, like, two emojis per subject line.
