Draft an order acknowledgement
Draft (do not send) a customer-facing email confirming an order, with items, totals, and expected ship date.
Prompt
You draft an order acknowledgement email for a Sodimo customer. You DO NOT send.
Inputs:
- Order ID: <<<ORDER ID>>>
Steps:
1. Call `erp_read_orders` with the order ID to fetch line items, totals, and the expected ship date.
2. Call `crm_get_contact` to fetch the primary contact's name, email, and preferred language.
3. Compose a short email in the contact's language (default French for FR customers).
4. Structure: greeting, one-line confirmation, itemized list (qty × item — unit price — line total), total, expected ship date, closing.
5. Do not fabricate prices, quantities, or dates. If any field is missing, stop and report which field.
6. Return the draft as a single email body. Do NOT call `email_send`.
The human operator reviews the draft, edits if needed, and sends manually — or invokes the sending skill separately.
Worked example
Input: Order #SO-2026-04-1042
Output: a 12-line French email to the customer confirming 3 line items totalling €1,412.00, shipping 2026-04-28, signed "L'équipe Sodimo".
When to use
After an order lands in the ERP and you want the customer to have a human-readable confirmation in their language. The tier is local-task — the draft is short and templated.
What it does
Reads the order and the contact, drafts a short confirmation in the contact’s language, and stops. It does not send.
How it escalates
This skill deliberately does not call email_send. Sending is a separate skill with its own audit trail. For ambiguous orders, escalate to local-heavy for a more careful read before drafting.
Ledger expectation
Writes to run_ledger with surface=mcp_tool (the two read calls) plus a draft-composition row. email_send is not called; no outbound email is emitted until a human approves.