Draft a support reply from an approved policy

Prepare a reply that a support employee can review quickly. This workflow uses supplied text; it does not read a helpdesk or send a message on your behalf.

Prepare the input

Provide the customer message, current policy excerpt, and any verified account facts that are necessary and appropriate to share. Label each source. Remove unrelated private details. Include the policy date so an old version is not mistaken for the current rule.

Run the workflow

Ask the assistant to extract the request, identify the relevant rule, and draft the reply. Keep policy exceptions separate. If the account information is missing, the draft should ask for the next useful detail rather than claim the request has been processed.

Prompt to copy

Customer message: [text]. Approved policy: [text and date].
Verified facts: [facts or none].
Identify the request and the policy section that applies.
Draft a short, helpful reply using only those facts.
List missing information and any exception needing a person.
Do not promise a refund, change an account, or send the reply.

Review a worked example

Illustrative message: “My order arrived damaged; please refund it.” If the policy requires an order reference and review of damage evidence, the draft can explain that next step. It cannot say the refund is approved. Check the tone, policy reference, and absence of invented account facts.

Check whether the reply answers the customer’s actual question before adding policy explanation. A technically accurate paragraph can still ignore the request. Keep the next step specific and achievable. If a policy has two possible interpretations, put the ambiguity in the reviewer note rather than selecting the more convenient interpretation for the business.

Use it again

Save the reviewed output format and replace the policy when it changes. Track which drafts need substantial rewriting. For a connected queue or transaction workflow, discuss custom integration. See Bot for the personal preparation direction.