Start with the terms that cause rework
Every outsourced support team develops private vocabulary: the client's shorthand for a customer type, a product line, a status, or an exception. When that vocabulary lives only in chat, a new specialist spends the first month guessing. Build a glossary from the terms that already cause rework. The goal is not a dictionary of the business; it is a short list of words that change what someone does.
Review the last twenty returned tickets, corrected reports, or reopened cases and highlight the words that were misunderstood. Look for terms with more than one meaning inside the client's own materials. A word like active customer or priority order can differ by team. Those ambiguous terms belong in the glossary before any polished definition.
Define each term with an example and a non-example
Write each entry as a definition, an example, and a non-example. The definition says what the term means in this client's work. The example shows a real record with identifying details removed. The non-example shows a nearby case that does not qualify. The pair is what prevents a specialist from applying the term too broadly.
Keep the definition short enough to read during a task and specific enough to settle a question. Avoid copying marketing language or internal jargon that the specialist cannot verify. If the term depends on a system field, name the field and the allowed values. A glossary entry that points to the authoritative field is more useful than a paragraph of history.
Assign an owner and a review date
Give every entry an owner and a review date. The owner is the person who can settle a dispute about the meaning, not necessarily the person who wrote the entry. Review dates matter because products, policies, and labels change. An unowned glossary slowly becomes a museum of old terms.
Record the source of each definition, such as a policy page, a system field, or a signed SOP. When two sources disagree, note the conflict and the owner who resolved it. That note prevents the next specialist from reopening the same argument. The glossary should show its authority, not just its content.
Put the glossary where the work happens
Put the glossary where the work happens rather than in a separate folder nobody opens. Link it from the SOP, the queue description, and the onboarding checklist. If the team uses a knowledge base, create one searchable page and keep the canonical version there. A glossary that requires three clicks is already fading.
Use the same terms in saved replies, labels, and reports. Inconsistent language between the glossary and the queue teaches the specialist that the document is optional. When a label changes, update the glossary in the same change. The vocabulary and the work should move together.
Test it with a new specialist
Test the glossary with a new specialist before the first live case. Ask them to classify five real records using only the definitions and examples. Watch where they hesitate and which term they misapply. Their hesitation is better evidence than a readability score.
Ask an experienced specialist to review the same five records and compare the answers. Where the two disagree, the entry is probably ambiguous. Rewrite the definition or add a non-example, then test again with a different set. The glossary is finished only when two people can apply it the same way.
Retire terms that no longer match the business
Retire terms that no longer match the business, and say so in the change note. Keeping a dead term with a warning is sometimes necessary for old records, but it should not sit beside live definitions without a label. Mark historical terms clearly and remove them from saved replies. A glossary with obsolete entries slows everyone down.
Review the whole glossary quarterly and after any major product or policy change. Bring one ambiguous term to each review rather than reading the document line by line. Ask the client to confirm the terms that affect customer promises. The review should end with one clearer entry and one owner.
Handle terms the client cannot define
Some terms matter to the work but the client has never written a definition. Do not invent one quietly. Ask the client's process owner to describe a real case and a nearby case that does not qualify. Turn that description into a draft entry and send it back for confirmation. A confirmed definition is safer than a clever one the client has never seen.
If the client cannot decide, record the ambiguity and the temporary rule the team will use. Put a review date on it and name the person who will resolve it. The glossary can hold an open question as long as the question is visible. Hidden assumptions are what cause the next return.
Keep a change log for saved replies
Saved replies and glossary entries drift apart when one changes without the other. Keep a short change log that records the term, the old wording, the new wording, and the reason. Link the log entry to the saved reply or SOP that changed. A specialist who inherits the queue can then see why the language shifted.
Review the log during the quarterly glossary review and remove changes that were never adopted. A change that exists in the log but not in the templates is a false record. The log should describe the live vocabulary, not every draft someone considered. Keep it short enough that people actually update it.
If the queue and decision rights are already defined but need a steady operator, outsourced operations support can turn approved examples, decision lines, and review rules into a draft your manager can check. The manager still owns exceptions and final approval.
For the next step, compare this workflow with Plan coverage for Philippine holiday weeks and Set rules for direct customer contact by an assistant. For access and oversight, use the authoritative planning reference alongside your own policy.
