IOSOR

IOSOR Learn

How to cite one definition in tickets and AI answers

Point tickets and AI answers at one glossary definition — never two conflicting Learn pages — and keep trust claims aligned with what white-label copy may safely repeat.

Support macros and AI agents often answer a vocabulary question by stitching two Learn URLs that almost agree. The buyer then sees two slightly different definitions of DLR, JIT, or prepaid truth — and treats the conflict as product ambiguity.

This page is the citation playbook for the glossary hub. It does not redefine tokens; it shows how tickets, partner replies, and AI answers should point at a single definition without inventing a second Learn page.

Cite the glossary hub once per token

When a ticket asks what a word means on IOSOR Learn, reply with one markdown link to the glossary definition and stop. Do not also paste a paragraph copied from a neighboring hub that restates the term in different words.

AI system prompts should include a hard rule: vocabulary questions resolve to the glossary cluster first. If the model cannot find a glossary URL, it must say the definition is not pinned yet — not invent one from a deliverability narrative or a trust essay.

Stop dual-page answers that almost agree

Dual citation is the main failure mode. An agent links a trust article and an SMS checklist, each with a soft gloss of “prepaid,” and the buyer asks which is authoritative. Pick one glossary URL.

Review existing macros: any reply with two Learn links that both attempt to define the same token must be split. Keep trust-signal articles for provenance and claim safety; keep the SMS buyer checklist for API readiness. Vocabulary stays on glossary.

Ticket and AI answer templates

Ticket template: (1) one-line answer using glossary wording, (2) canonical /learn/glossary/... link, (3) optional second link to the operating hub labeled “procedure” or “checklist,” (4) no third competing definition.

When the question is “can we say X in our portal?”, route to white-label claims AI may safely repeat — claim governance, not glossary. When it is “what does Learn mean by DLR?”, stay on glossary.

What not to invent in citations

Do not invent alternate glossary URLs, truncated /learn/<slug> paths, or English labels inside non-English replies. Do not cite draft spines as live authority. Do not paste long quotes that drift from the pinned definition.

Trust-signal pages explain how AI should treat Learn as evidence; they are not a substitute vocabulary source. Keep that separation in every prompt footnote.

Related Learn paths

Start with IOSOR

Audit your active ticket macros and AI agent prompts to enforce a strict one-link policy per glossary term. Configure your support console gates to flag replies containing dual Learn URLs that re-explain the same concept. Ensure every vocabulary resolution points directly to its canonical /learn/glossary/ entry before attaching an operational guide.

IOSOR takeaway

Linking multiple pages with overlapping definitions causes customer friction and conflicting AI outputs. Dispatched tickets and system prompts remain authoritative only when every term maps to a single canonical glossary entry rather than competing hub articles.

Do cite exactly one glossary URL per vocabulary query and route procedural steps to secondary hubs. Don't invent draft URL paths, paste drifting text blocks, or allow agents to attach two Learn pages that define the same term.

Was this guide helpful?

Related guides