Philippines staffing blog ·
Keep a client glossary inside an outsourced help desk
A working glossary that keeps product names, statuses, and customer language consistent across every ticket the desk touches.

Direct answer
Operational guidance
Why a shared glossary matters
A help desk inherits language from the client, the product, and the customer, and those three sources rarely use the same words for the same object. An agent may call a feature one thing while the client's release notes call it another, and the gap widens with every new hire. The customer then reads a reply that sounds confident but names the wrong item, which creates a second question before the first one is answered. A short glossary fixes the vocabulary before it reaches the ticket.
The glossary is not a dictionary of everything the company does, and it should never become one. It is a short list of terms that change how a ticket is read, routed, or answered, plus the aliases customers actually use. Each entry should resolve a real ambiguity that has already caused a wrong reply or a misrouted case. A list built from actual ticket confusion stays small, gets read, and earns its place in the workflow.
Choose the terms worth defining
Start with product names that sound alike, internal status labels, and words the customer uses differently from the client. Add the terms that appear in saved replies and knowledge articles, because those spread an error faster than a single agent can. Ask agents which words they have had to guess in the last month, and write down the exact phrasing the customer used. The answers usually produce a list of ten to twenty terms that matter immediately.
Leave out ordinary words that carry no risk when misunderstood, because a glossary that defines every noun becomes a document nobody opens. Keep one owner for the list and a visible date on each change, so a reader can tell whether the entry is current. The owner decides whether a new term belongs, and that decision should take less than a minute. A short approval path keeps the list from stalling when the product changes.
Write definitions agents can apply
A useful entry names the term, the approved meaning, and the words to avoid, in that order. Add one sentence about where the term appears, such as a billing screen or a welcome email, so the agent can confirm it in context. If the customer uses a different phrase, record it as an alias instead of correcting the customer in the first reply. The agent should be able to match the customer's words to the approved term in a few seconds.
Definitions should describe behaviour, not marketing, because the agent needs to know what the term does to the ticket. Say what the status means for the request, what the customer will see, and what the agent may tell them. Avoid a definition that only repeats the term in longer form or lists benefits the customer did not ask about. A reader who finishes the entry should know what to write and what not to promise.
Place the glossary where work happens
A glossary stored in a folder nobody opens will not change a reply, however accurate it is. Put a searchable copy inside the ticket tool or the knowledge base the agents already use, and link the relevant entries from the saved replies that mention the term. Add the link to the onboarding checklist so a new agent meets it in the first week. The glossary should appear at the moment of writing, not only during training.
Keep the full list in one canonical place and publish copies from it, because copies that drift create two truths and a new source of confusion. When the canonical entry changes, update the linked reply in the same task, and note the change in the ticket tool. The agent should never have to decide which version is current. A single source with dated copies is easier to trust than several folders that look equally official.
Review changes with the client
Product names, plan labels, and statuses change, and the glossary has to follow without waiting for a quarterly review. Review the list when the client ships a rename, changes a customer-facing policy, or retires a feature. Ask the client's product or support lead to confirm the wording rather than guessing from a help article. Record who approved the change and the date so a later reader can trace the decision.
Do not wait for a scheduled meeting if a rename is already live, because customers will see the mismatch before the next review. A short message to the client owner is enough to confirm the new term and the old one it replaces. Then update the entry, the saved replies, and any open ticket that used the old word. The customer sees one consistent vocabulary instead of a transition in progress.
A worked example
A client uses workspace for the top-level account and team for a group inside it, but customers often say account for both. The glossary entry states that account is not an approved term, gives the two correct words, and names the screen where each appears. A saved reply about adding members links to the entry, so the agent sees the distinction before writing. An agent handling a request to add someone to an account now asks which level the customer means.
The entry also tells the agent how to confirm the choice with the customer without sounding pedantic. The ticket note uses the approved words, and the customer's original phrase is kept as an alias for search. Routing improves because the request type matches the actual object, and the next owner does not have to reinterpret the note. The fix took one short entry, one updated reply, and a minute of client confirmation.
Train and audit
Use two real tickets in a team meeting and ask agents to find the term that caused confusion. One ticket should show a good glossary match and one should show a guess that looked reasonable at the time. Rewrite the weak note together using the approved entry, and ask the group what they would search for next time. The exercise is short and produces language the team can reuse immediately.
Add terminology to the weekly quality sample and look for replies that use an unapproved word or an outdated alias. Coach the pattern when it appears twice, and update the entry if the approved word is unclear rather than blaming the agent. Check that new saved replies link to the glossary and that the link still resolves. A small sample shows whether the list is alive or merely filed.
Close the loop
Review the glossary at the end of each month and remove entries that no longer match the product. Merge duplicates, fix definitions that agents still misread, and keep the change log short enough for a reader to scan. An outdated entry is worse than no entry because it looks authoritative and spreads the same error. The list should earn trust through accuracy, not through length.
Share the updated list with the client owner and ask for corrections, especially after a product change. The desk should be able to explain any entry in one sentence, and the client should recognise its own language in the definition. When a term stops causing confusion, mark it as stable instead of deleting the history. The glossary should shrink toward the terms that still decide how a ticket is handled.
Authoritative sources
- ISO 18295-1:2017 customer contact centres
- ISO 9001:2015 quality management systems
- NIST SP 800-53 Rev. 5 security and privacy controls