A support answer should connect each instruction to an approved knowledge record whose product version, audience, region, and effective date match the ticket. Retrieval rank is not authority: an older article may score higher while describing behavior that has changed. If the current guidance conflicts with a trusted system status, surface the conflict rather than selecting the more convenient sentence. The assistant can draft steps from the reviewed record, but a human or test environment should validate any claim about what the product will do after the user clicks a control. Keep the article revision ID in the case packet.
Make this comfortable
Support prompts: answer from current product guidance
Operational case
Aster Console v4.2 counts pending invites against a 47-seat allocation. An older v4.1 article describes only active seats and appears first in semantic search. Tenant N-47 runs v4.2, so the assistant selects the current article and compares it with the entitlement service. The dashboard shows 46 active seats, but that number alone does not establish spare capacity. The reply explains why an existing pending invite can occupy the remaining place, without linking the customer to an obsolete instruction.
Tenant product: Aster Console v4.2
Knowledge revision: seats-v4.2-r3, active + pending
Obsolete candidate: seats-v4.1-r1, active only
Selected guidance: v4.2 after entitlement check
Conflict: stop and review, do not guessPerformance and review cost
Retrieving K candidates is dominated by index search; filtering them by version and effective date is O(K). The filter can reduce recall, so record when no compatible article exists and send the gap to a specialist. A short current answer is cheaper to support than a long answer assembled from mixed versions, especially when product behavior changed between releases.
Common Mistakes
- Do not use the highest-ranked article without checking its version.
- Do not treat dashboard active seats as the full allocation rule.
- Do not paper over a conflict between knowledge and current account state.
Connected lessons
- Prompt engineering applications
- Prompt Engineering
- Retrieved evidence: reconcile versions and conflicting facts
- Retrieval prompts: rerank only authorized, current evidence
- Support prompts: reconstruct ticket identity and chronology
- Support prompts: route by issue and verified urgency
- Support prompts: verify entitlement and requester authority
- Support prompts: ask only the question that changes the next step
- Support prompts: separate reply, handoff, and resolution
- Project: handle Aster seat activation ticket T-47
- Customer-support case decisions
prompt engineering
customer support