The support agent finds the right troubleshooting note, plus an internal comment about an unconfirmed cause, a customer-specific workaround, and a discussion of commercial concessions. It combines all of them into a helpful-looking reply containing material the team never intended to send.

A Confluence Community question asks how to expose a customer knowledge base without exposing internal documentation. Agents add an editorial question: permission to read internal material for a job does not make every sentence fit for the customer's answer.

Separate research access from publication choice#

The agent needs internal context to understand an issue. The customer needs the approved explanation and steps they can take. Keep those purposes distinct in the workflow, because a broad retrieval permission does not permit disclosing whatever retrieval returns.

Say an internal note explains that an import error has three causes, and only one is confirmed for the customer's file. The public troubleshooting guide has an approved correction for that cause. The agent uses the internal note to direct investigation, then grounds the customer response in the confirmed condition and approved guidance.

Do not hide information the customer needs to act on, since audience control is no excuse for a vague reply. The response names the affected behavior, the next step, the expected result, and what to do if it fails, within the team's communication rules.

Classify what each source contributes#

Source material	Appropriate use	Review needed before sending
Current customer guide	Explain supported steps	Verify product and version match
Internal investigation note	Guide diagnosis	Confirm facts and wording
Another customer's exception	Identify a question to ask	Establish whether it applies here
Commercial discussion	Inform the account owner	Separate authorization for any offer
Old troubleshooting page	Historical context	Check whether it is superseded

Put the evidence supporting the answer in the internal review packet. The external message links customer-accessible documentation and leaves out private notes, so a reviewer inspects the basis of the answer without the recipient seeing that packet.

Customer access also matters for links and attachments. A link that opens for the employee can fail for the customer or expose more than intended, so verify the destination and sharing scope through the normal process.

Make uncertainty useful#

If the cause is unconfirmed, say what is known and what information would distinguish the possibilities, and ask for the minimum useful diagnostic evidence. Do not send a speculative internal theory as though Engineering established it.

A workaround needs its conditions: the product version, the effect, and any limitations approved by the owning team. Do not generalize from a one-off customer note that resembles the current issue. When no approved answer fits, prepare a focused question for the technical owner.

Keep the customer's original request visible during review, because agents sometimes answer the interesting internal problem and skip the customer's question.

Check the outgoing message as a separate artifact#

Review the final recipients, body, links, and attachments together, since a safe body with an internal attachment is still the wrong message. If the agent revises the reply after approval, inspect material changes before sending.

Test with an internal-only note, a superseded public guide, a customer-specific exception, and a private link. Where approved evidence suffices, the agent still produces a useful response; where it does not, it names the missing decision instead of refusing the whole task.

When a reviewer removes an inappropriate detail, keep the general lesson with its scope, for example “diagnostic hypotheses require confirmation before customer publication.” Never save the customer's private details as a general writing rule.

When the same internal explanation keeps needing customer-safe rewriting, ask the owning team to publish an approved guide the next agent can cite directly. The diagnostic material stays internal, and representatives stop deciding case by case what to share.

Deixic exposes company knowledge to your existing agent over MCP and holds sensitive actions for approval in the app queue or in Slack. The team can save the review method as reusable knowledge and skills.