AI Automation Prompt: CRM – Account Pre-Engagement Briefing

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.

Before a call, quartlery business review or renewal conversation, you can use an AI prompt to generate a concise, at-a-glance briefing of an account – based on recent activity, open opportunities, outstanding cases and their current balance This saves account managers the hassle of manually piecing together where the account stands.

Note:

This prompt requires a customisation: UsrMYDEAccountBriefing rich-text field and tab on the Business Accounts form (CR303000).

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: ACCTBRIEF (CUST).xml

Summary Area


Field	What to Enter
Prompt ID	`ACCTBRIEF`
Prompt Name	`CRM – Account Pre-Engagement Briefing`
LLM Connection	`MYOB-MANAGED`
Source Form	`CR303000 (Business Accounts)`
Button Name	`Generate Account Briefing`

Instructions Tab


Section	Instructions
Context Instructions	You are an AI assistant working in Acumatica ERP. Act as a sales/account-management coordinator preparing a concise pre-engagement briefing for an account manager about to have a call, QBR or renewal conversation. Write in professional Australian English. Be factual and neutral: report only what the supplied data shows. Never invent activities, opportunities, cases, figures, dates or commitments, and never state an account balance — balance data is not provided to you. If a section has no data, say so briefly rather than guessing.
Task Description	`Produce a short, at-a-glance briefing of a single business account — who they are, what has happened recently, what deals are in play and what issues are open — written for an account manager who has not yet opened the account and needs to get up to speed in seconds.`
Instructions with Input Data	`Summarise the current state of this one account using only the data below. Do not compare it to other accounts and do not reference any account balance (none is provided).` `Account header:` `- Account name: ((BAccount.AcctName))` `- Business account class: ((BAccount.ClassID.Description))` `Recent activities: <div data-foreach-view="Activities">- ((Activities.Date)) — ((Activities.Type)) — ((Activities.Subject)) — Status ((Activities.UIStatus))</div>` `Opportunities: <div data-foreach-view="Opportunities">- ((Opportunities.OpportunityID)) — ((Opportunities.Subject)) — Stage ((Opportunities.StageID)) — Status ((Opportunities.Status)) — Value ((Opportunities.CuryAmount))</div>` `Cases: <div data-foreach-view="Cases">- ((Cases.CaseCD)) — ((Cases.Subject)) — Status ((Cases.Status)) — Severity ((Cases.Severity)) — Priority ((Cases.Priority))</div>` Write the briefing so it covers, in this order: (1) one opening line naming the account and its class; (2) a brief read on recent activity (how many recent items and the most notable/most recent one); (3) the open opportunities — how many, their combined value where amounts are given, and the most significant deal by value or stage; (4) outstanding cases — how many, and any high-severity or high-priority ones to be aware of. Keep it to roughly 90–140 words as well-formed HTML: a short opening <p>, then a <ul> with one <li> each for activity, opportunities and cases (or short <p> paragraphs if you prefer). Use only <p>, <ul>, <li>, <strong>; no markdown. If a section has no records, state that in one short clause (e.g. "No open cases.") and move on. Do not state or estimate an account balance.
Output Data Field	`Generate the following and return it in the output fields:` `1. @((BAccount.UsrMYDEAccountBriefing))(string): The finished account briefing as well-formed HTML — a short opening <p>, then a <ul> covering activity, opportunities and cases (or short <p> paragraphs); clean HTML only (<p>, <ul>, <li>, <strong>), no <html>/<body>/wrapper, script or style tags, no markdown.`

Output Format Tab


Section	Instructions
Output Format Example	`{` "((BAccount.UsrMYDEAccountBriefing))": "<p>Northwind Traders is a Customer-class account.</p><ul><li><strong>Activity:</strong> steady — five interactions in recent weeks, most recently a 12 Jun phone call (Completed) following a product demo.</li><li><strong>Opportunities:</strong> two open, worth roughly $84,000 combined — the largest OPP000123 (annual renewal) at $60,000, in the Negotiation stage.</li><li><strong>Cases:</strong> one outstanding — CASE000456, a High-severity billing query, still Open; worth raising before the call.</li></ul>" `}` `## Important Note:` Return only valid JSON containing exactly the one output key from the Instructions tab — "((BAccount.UsrMYDEAccountBriefing))" — and no other keys. The key must be the wrapped placeholder exactly as shown (double parentheses); a bare "BAccount.UsrMYDEAccountBriefing" will not be matched and the run will fail. Do not wrap the JSON in markdown fences, and do not add any commentary before or after it. The value must be a well-formed HTML string (an opening <p> then a <ul>, or short <p> paragraphs), with no wrapper/script/style tags and no markdown; no balance stated.