Why was a pre-sales inquiry routed to the shipping support queue?

Occasionally, a ticket lands in the shipping queue that has nothing to do with a shipping problem. Instead, it turns out to be a pre-sales conversation — a prospective customer asking about pricing, product details, or order options. This article explains how to recognize these miscategorized tickets and what to do with them.

What a miscategorized pre-sales ticket looks like

These tickets share a few common signs:

• The contact has no active order number at the time the ticket is created
• The subject line is vague, such as "Order Update" or "Information Request"
• The email thread contains pricing discussions, product comparisons, or invoice requests — not shipping or fulfillment questions
• The ticket may have been created when a prospect replied to a sales email, which caused the system to generate a support ticket automatically
• An automated classifier may have flagged it as a Sales Inquiry rather than a shipping issue

Why this happens

Styku uses an automated ticket routing system. When a contact sends or replies to any email, the system may create a support ticket and attempt to classify it. If the classifier is working from limited information — for example, only the first few emails in a thread — it can misread a sales conversation as a shipping concern, especially if the subject line mentions words like "order" or "update."

In some cases, the contact later does place an order and asks about shipping. At that point, the thread contains both pre-sales and shipping content, which can make correct classification harder.

How to confirm the ticket is a pre-sales inquiry

1. Open the ticket and check for an order number in the thread or ticket properties.
2. If no order number exists at the time the ticket was created, the initial contact was pre-purchase.
3. Read the earliest emails in the thread. If the conversation covers pricing, product features, subscription tiers, or invoice requests, it is a sales inquiry.
4. Check the automated classification note on the ticket. A label of "Sales Inquiry" with high confidence is a strong indicator of miscategorization.

What to do with a miscategorized ticket

1. Recategorize the ticket. Update the issue category in the ticket to reflect the actual topic — for example, "Sales Inquiry" or "Pre-Sales."
2. Route to the sales team. Assign the ticket to the appropriate sales representative or sales queue. If a sales rep is already engaged in the thread, assign it directly to them.
3. Do not close as a shipping resolution. Closing the ticket with a shipping-related resolution note would create inaccurate records.
4. If the thread later includes a genuine shipping question, determine whether to handle it in the same ticket or open a new, correctly categorized ticket for the shipping concern.

Preventing future miscategorization

• When sales representatives conduct conversations via email, they should use their direct email or a dedicated sales inbox — not the support email address — to reduce the chance of sales threads generating support tickets.
• If your team notices a pattern of similar miscategorizations, report it so the automated classifier rules can be reviewed and improved.

If this resolves your issue, no further action is needed.

If the problem persists, contact support and include: the ticket ID, the original ticket category assigned, the contact name and company, a summary of what the email thread actually contains, and whether an order number was present at the time the ticket was created.

Applies to: All Styku configurations — internal support team ticket routing and triage process