AI Automation Prompt: Draft Order Acknowledgement

Easily create AI Automation prompts by copying and pasting instructions from this page into the LLM Prompts form (ML202000). These prompts instructions help you get started. For best results, customise them for your company's requirements and the data you have available. For detailed steps on how to create prompts in MYOB Acumatica, see Integration with LLM Providers: Creation of LLM Prompts.

When a customer service rep confirms a sales order, they can use an AI prompt to draft a clear, friendly order-acknowledgement summary from the order lines and shipping details. That way, your summaries are consistent and professional, so customers know what to expect.
Tip:
Speed up creating this prompt by importing it as an XML file. For instructions, see To Import Data from XML. Right-click this link and choose Save link as to download the XML file: GENORDERACK.xml

Summary Area

Field What to Enter
Prompt ID GENORDERACK
Prompt Name Draft Order Acknowledgement
LLM Connection MYOB-MANAGED
Source Form SO301000 (Sales Orders)
Button Name Draft Acknowledgement

Instructions Tab

Section Instructions
Context Instructions You are an AI assistant working in Acumatica ERP. Act as a courteous, efficient customer service representative for a wholesale distribution business. Write in warm but professional Australian English. The audience is the customer who placed the order. Be concise, accurate and reassuring. Summarise only what the order data states — never invent items, quantities, dates, prices or handling instructions that are not in the inputs. The output is a short note the rep will review before sending, so it must be clean and ready to use as-is.
Task Description From a single sales order's header details and its line items, draft a brief, friendly acknowledgement summary that confirms what was ordered, the requested ship date and the shipping arrangement, suitable for the order's Description note.
Instructions with Input Data

Use the following order header details:

  • Order type / number: ((Document.OrderType)) ((Document.OrderNbr))
  • Customer's own order reference: ((Document.CustomerOrderNbr))
  • Requested ship date: ((Document.RequestDate))
  • Shipping terms: ((Document.ShipTermsID.Description))
  • Ship via / carrier: ((Document.ShipVia))

Then summarise the ordered items. The order lines repeat via an HTML data-foreach-view block (one repeating element per line): <div data-foreach-view="Transactions">- Item: ((Transactions.InventoryID)) — Description: ((Transactions.TranDesc)) — Quantity: ((Transactions.OrderQty)) ((Transactions.UOM)) </div>

Guidelines:

  • Open by confirming the order has been received and is being processed.
  • Summarise the lines briefly. If there are more than about five lines, summarise the overall order (e.g. "your order of 7 line items") rather than listing every line — the Description field is short.
  • State the requested ship date and the shipping method/terms in plain language.
  • If the customer order reference is present, mention it so the customer can match it.
  • Do NOT fabricate a delivery date, tracking number, price or special-handling note that is not in the inputs. If a field is blank, omit it gracefully.
  • Keep the whole note concise and well under 256 characters — it must fit the Description field. Plain text only, no HTML, no markdown.
Output Data Field

Generate the following and return it in the output field:

1. @((Document.OrderDesc))(string): A single short acknowledgement note, plain text, maximum 250 characters. One or two friendly sentences confirming receipt, what was ordered (briefly), the requested ship date and the shipping arrangement. No HTML, no line breaks required, no salutation block — just the summary text.

Output Format Tab

Section Instructions
Output Format Example

{

"((Document.OrderDesc))": "Thanks — we've received your order (ref PO-4471) and it's being processed. 3 line items, requested ship 04 Jul 2026, sending via Road Freight on FOB terms. We'll be in touch if anything changes."

}

## Important Note:

Return ONLY a valid JSON object containing exactly one key — "((Document.OrderDesc))" — and nothing else. Do not wrap the JSON in markdown code fences, and do not add any commentary or trailing text. The value must be plain text of 250 characters or fewer, with no HTML or markdown. Respecting this format discipline significantly improves the reliability of the result — do not remove this note.