how to give agents search over past resolutions

TL;DR

Your team has already solved almost every ticket that comes in. The knowledge is just trapped in closed tickets nobody can find. Put a search box over past resolutions inside the agent workspace, strip the PII, and rank solved tickets by recency. Agents who search before answering stop re-deriving the same fix, and new hires ramp in weeks instead of months.

The query

how to give agents search over past resolutions

Use this when

• Agents solve the same problem three different ways
• New hires keep asking senior agents for old fixes
• Solved tickets contain answers nobody can find
• You want a cheap first step before building a knowledge base
• Resolution quality changes depending on who is on shift

Not for

• Customer-facing help center search
• Training data for a chatbot
• Compliance or legal discovery over tickets
• Replacing a knowledge base you already maintain

Steps

1. Decide what counts as a resolution

Index closed tickets that have a solve event and a real final agent reply. Exclude abandoned tickets, spam, and anything closed by automation with no answer. If there is no actual answer in the thread, it is noise in search results, not signal.

Expected output: a clear inclusion rule, like status solved plus a non-empty final reply.

2. Strip the PII before indexing

Remove names, email addresses, phone numbers, account IDs, and anything personal hiding in attachment filenames. Do this on a copy, never on the source ticket. One sloppy index becomes a privacy incident the first time an agent screenshots a result.

Expected output: a sanitized copy of each ticket with personal fields removed or masked.

3. Index the conversation, not just the subject

Ticket subjects are useless. Nobody searches "help please" and finds anything. Index the full thread: the customer's description, the troubleshooting steps, and the final answer. Weight the agent's final reply highest, since that is what the next agent actually wants to read.

Expected output: full-text search where the resolution ranks above the complaint.

4. Put search where agents already work

A separate tab dies unused. Embed the search in the ticket sidebar or the reply composer, pre-filled with the current ticket's subject. If it takes more than two clicks, agents will not use it, no matter how good the index is.

Expected output: search lives inside the agent workspace, one click from the ticket.

5. Teach the two-query habit

Train agents to search twice: once with the customer's words, once with the technical term. Track how often a search happens before a reply, and share the wins in standup. Search is a habit, not a feature, and habits need visible payoff.

Expected output: rising search-before-reply rates and agents sharing what they found.

Variant phrasings

search resolved tickets knowledge base

Same five steps. If the real goal is a formal knowledge base, promote the best search hits into articles instead of stopping at search.

how to reuse past ticket answers

Steps 3 and 4 carry this. The difference is emphasis: if the same answer repeats weekly, make it a macro, not a search query.

ticket history search for support agents

Same steps, but this phrasing usually means agents want the full customer timeline, not just resolutions. Add a per-customer history view alongside the resolution search.

Why it happens

Every ticket gets solved once and forgotten. Without search, the team's knowledge lives in senior agents' heads, so every hire re-learns it from scratch and every answer varies by who picks up the ticket. Search over resolutions turns individual memory into team memory, with no process change beyond the habit of looking first.

Edge cases

• Old resolutions go stale: rank by recency and flag answers older than a year for review before reuse.
• Sensitive accounts: exclude NDA or VIP ticket categories from the index entirely, not just from results.
• Agents copy-paste without adapting: train that a past resolution is a starting point. The current ticket's context still rules.
• Search returns nothing: that is data. Log the miss. It is your next knowledge-base article or your next macro.
• Multilingual tickets: index in the original language and translate the query, or you will miss half your history.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_exGP4ePHWvPRiLRzzDpAqQ