Skip to content

Customer Order Acknowledgement with Realistic Promise Date

Example prompt: "When a confirmed sales order lands in our Google Sheet, work out a realistic promised ship date from current stock and our standard production lead times, then draft an order acknowledgement email to the customer — post anything that needs sales-team judgement in #sales-ops on Slack instead."

The Problem

Order acknowledgements are the bit of customer service that should happen the same day the order lands but usually does not. The customer wants to know when their order will ship; sales wants to acknowledge it but does not want to commit to a date without checking with production; production does not want to be checked with on every order; the customer follows up two days later asking whether the order was received at all. The compromise is a generic acknowledgement that says nothing about when, which leaves the customer no better informed.

How GloriaMundo Solves It

We build a workflow that watches the sales orders sheet for the moment a new confirmed order lands. A code step walks each line, checks stock-on-hand for the lines that can ship from stock, and applies the production manager's standard lead times for the lines that cannot. The order-level promised ship date is the latest of those. A conditional step decides whether the order needs sales judgement — unknown SKUs, dates the customer asked for that we cannot hit, high-value orders, new customers, non-standard payment terms — and routes those out of the auto-draft path entirely. Orders that pass go to a Gmail draft for the salesperson to review and send. Glass Box preview shows the computed promise date, the flag reasons (if any), and the draft email before anything reaches the customer.

Example Workflow Steps

  1. Trigger (sheet row add): A new row in 'Sales Orders' with status 'New — awaiting acknowledgement'.
  2. Step 1 (integration): Read the SO header, the linked 'Sales Order Lines' rows, the 'Stock' tab, the 'Standard Lead Times' tab, the 'Customers' tab, and the 'Company Settings' tab.
  3. Step 2 (code): For each line, compute line_promise_date — stock path or production path; mark Unknown SKU where it does not resolve. Order-level promised_ship_date is the latest across the SO.
  4. Step 3 (conditional): Evaluate the 'Needs sales review' flags (Unknown SKU, requested-ship-date miss > 2 working days, high-value, new customer, non-standard payment terms) and branch.
  5. Step 4a (integration, auto-acknowledge path): Draft the customer email in Gmail with the line table, line dates, order-level promised_ship_date, and payment terms note; update the SO row status to 'Acknowledged — pending send' and stamp acknowledgement_drafted_at.
  6. Step 4b (integration, needs-review path): Do not draft the customer email; update the SO row status to 'Needs sales review', populate sales_review_reasons with every flag that fired, and route into the daily Slack queue.
  7. Step 5 (integration): Detect the salesperson's send from the Gmail Sent folder by matching the subject 'order [so_number] confirmed' and update status to 'Acknowledged — sent'.
  8. Step 6 (integration): At 10am every working day, post the summary in #sales-ops on Slack — auto-acknowledged-drafted, Needs sales review with reasons, pending-send lingerers, and unresolved Unknown SKU lines.

Integrations Used

  • Google Sheets — the Sales Orders, Sales Order Lines, Stock, Standard Lead Times, Customers, and Company Settings tabs
  • Gmail — drafts the customer acknowledgement and detects the salesperson's send from the Sent folder
  • Slack — the #sales-ops morning summary the salesperson reads with the day's queue

Who This Is For

The salesperson at a small manufacturer who takes orders by email or phone, keys them into the sheet, and is on the hook for the customer reply. This is the workflow for the order-book where most orders are reasonable and a few need a phone call — the workflow handles the reasonable ones with a draft and routes the rest to the salesperson with the reasons spelled out.

Time & Cost Saved

The acknowledgement cycle on a typical day — read the order, check stock, eyeball the production lead time, type a polite email, hit send — is fifteen minutes per order and the kind of work that gets postponed until the customer chases. With twenty orders a week that is five hours of salesperson time, most of it on orders that were always going to be acknowledged the same way. This workflow turns the acknowledgement into a one-minute review of a draft for the routine orders and surfaces the orders that need a phone call as a separate, smaller pile.