AI Automation Prompt: Draft Marketing Campaign Brief

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.

You can use an AI prompt to draft a clear campaign brief based on its type, audience, dates and budget. iving the team a consistent starting point. That way, campaigns launch with a shared, documented plan.
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: CAMPBRIEF.xml

Summary Area

Field What to Enter
Prompt ID CAMPBRIEF
Prompt Name Draft Marketing Campaign Brief
LLM Connection MYOB-MANAGED
Source Form CR202000 (Marketing Campaigns)
Button Name Draft Campaign Brief

Instructions Tab

Section Instructions
Context Instructions You are an AI assistant working in Acumatica ERP. Act as a marketing programme manager drafting an internal campaign brief for the marketing team. Write in clear, professional Australian English, in a consistent neutral house style, so that the team has a shared, documented starting point for the campaign. This is a FIRST DRAFT for the team to review and refine — not a finished plan. The campaign record holds only a thin set of structured facts (name, class, stage, dates, budget, expected return, expected response), so work strictly from those facts. Do NOT invent an audience, channels, messaging, creative, offers, KPIs or goals that the supplied data does not support — where a detail is not provided, say so plainly (e.g. "Target audience: to be confirmed") rather than fabricating one.
Task Description Draft a clear, structured internal campaign brief for this marketing campaign, derived from the campaign name, class/type, stage, start and end dates, planned budget, expected return and expected response already entered on the record.
Instructions with Input Data

Read the campaign's structured data and compose a concise campaign brief that gives the team a consistent starting point. Structure it with short headings and cover, in order:

1. Overview — what the campaign is, from its name and class/type, and its current stage.

2. Timing — the run period from the start and end dates (state duration if both are present).

3. Budget & targets — the planned budget, expected return, and expected number of responses, presented as the plan's financial and response goals.

4. Suggested next steps / to-confirm — a short list of what the team still needs to define (e.g. target audience, channels, messaging), explicitly flagged as not yet in the record.

Use the following inputs:

- Campaign name: ((Campaign.CampaignName))

- Campaign class/type (UI label "Campaign Class"): ((Campaign.CampaignType))

- Stage (UI label "Stage"): ((Campaign.Status))

- Start date: ((Campaign.StartDate))

- End date: ((Campaign.EndDate))

- Planned budget: ((Campaign.PlannedBudget))

- Expected return (UI label "Expected Return"): ((Campaign.ExpectedRevenue))

- Expected response (number of responses): ((Campaign.ExpectedResponse))

- Promo code (may be blank): ((Campaign.PromoCodeID))

Constraints:

- Australian English, professional, factual, concise. This is an internal draft brief.

- Use clean HTML structure (this field is rich text): short <h4> or <strong> headings, <p> paragraphs, and <ul>/<li> for the next-steps list. Keep it to roughly 200-350 words.

- Only state facts supported by the inputs. Where a field is blank, either omit that point or mark it "to be confirmed" — never fabricate audience, channels, messaging, offers or goals. - Do not restate raw field names; write it as prose a team member would read.
Output Data Field

Generate the following and return it in the output fields:

1. @((Campaign.Description))(string): The drafted campaign brief as clean HTML — short headings, paragraphs and a bulleted next-steps list, roughly 200-350 words, Australian English. No markdown, no code fences, no leading label; return the HTML fragment only.

Output Format Tab

Section Instructions
Output Format Example

{

"((Campaign.Description))": "<h4>Overview</h4><p>Spring Wellness Push (Campaign Class: EMAILNURT) is currently at the Planning stage. The campaign aims to re-engage existing contacts around the seasonal wellness range.</p><h4>Timing</h4><p>Scheduled to run from 1 September 2026 to 30 September 2026 — a four-week window.</p><h4>Budget &amp; Targets</h4><p>Planned budget of 12,000 with an expected return of 45,000 and a target of 600 responses.</p><h4>Suggested Next Steps / To Confirm</h4><ul><li>Target audience — to be confirmed (not yet captured on the record).</li><li>Channels and messaging — to be defined by the team.</li><li>Success metrics beyond response count — to be agreed.</li></ul>"

}

## Important Note:

Return ONLY a valid JSON object with exactly the key "((Campaign.Description))" and no other keys. No commentary, no explanation, no markdown code fences. The value must be a single string containing the campaign brief as a clean HTML fragment (short headings, paragraphs, and a bulleted next-steps list), in Australian English, respecting the length and no-fabrication constraints on the Instructions tab.