A PRACTICAL NOTE · Email workflows

How to apply this guide

Keep requested, approved and issued states distinct in a spoken customer draft.

Start with

Say the precise state and whether a timeline is verified. If there is no confirmed arrival date, leave it out. Use a placeholder for an order reference rather than dictating sensitive payment details.

Check before you finish

Explain whether the customer should wait, check a confirmation email, or contact support again. Do not imply an automatic outcome that you cannot verify.

Evidence to keep: Before sending, verify the recipient, requested action, dates and sign-off in the finished draft. This page’s key limit is: Keep requested, approved and issued states distinct in a spoken customer draft.

Start here

Customers need to know what actually happened. A draft that turns “requested” into “issued” can convey a false promise. Use the status visible in the order record.

Start with the known status

Say the precise state and whether a timeline is verified. If there is no confirmed arrival date, leave it out. Use a placeholder for an order reference rather than dictating sensitive payment details.

Review key verbs before sending

Compare the formatted reply with your original and the status record. Flag “approved,” “submitted” and “processed” if the system uses those words differently.

Give one useful next step

Explain whether the customer should wait, check a confirmation email, or contact support again. Do not imply an automatic outcome that you cannot verify.

Keep exploring