Articles in this section

[Admin & Rep Guide] Best practices for AI Content Builder prompts

A good prompt is the difference between a draft you can use and one you throw away. This guide covers what to include, what to avoid, and prompts you can reuse.

 

1. The 4 parts of a good prompt

Most weak prompts are missing 1 of these.

PartWhat to sayExample
The formatWhat shape the output should take"a 5-step checklist"
The readerWho will read it"for a new SDR"
The sourceWhat to work fromAttach the call, then say "from the attached transcript"
The scopeWhat to change and what to leave"rewrite the intro only, keep everything else as it is"

 

2. Prompt patterns that work

These 6 patterns cover most of what people need. Use them as a starting point and adjust the wording to your own content.

PatternExample
Be clear and specificCreate a 5-step onboarding checklist for SDRs focused on lead qualification.
Give contextRewrite this internal product update into a customer-friendly announcement for a Deal Room.
Ground it in a sourceUse the attached discovery transcript to identify the prospect's top 3 pain points.
Say where it goesInsert a short summary at the very top of this Spek, based on the text below.
Refine step by stepThis is good, but make it 30% shorter and more direct.
Ask for structureConvert this paragraph into a comparison table of our Pro and Enterprise tiers.

 

3. Common mistakes

These are the mistakes that waste the most time. Each one has a simple fix.

MistakeWhat happensDo this instead
"Make it look nice"Generic output, because the builder has to guess the layoutDescribe the layout. "A card grid with 4 sections and a clear header."
No source attachedThe builder writes from general knowledge, not your businessAttach a transcript, a Spek, or a web source first
Asking for 5 changes at onceSome get done well, others get missedRun 1 instruction at a time
Not saying what to protectThe builder edits sections you wanted left aloneAdd "keep everything else exactly as it is"
Publishing the first draftWrong facts and figures reach your teamRead it, check the numbers, then publish

💡 Pro Tip: Name a layout style in your prompt. The builder knows your design system, so asking for a card grid, a hero, or a callout gives you an on-brand result rather than plain text you then have to format.

 

4. Reusable refinement prompts

Keep these for polishing almost anything.

GoalPrompt
SimplifyKeep everything the same, but simplify it.
Make it scannableMake this easier to scan for a busy reader.
MobileImprove mobile readability.
Less denseReduce text and increase spacing.
Better groupingGroup related content more clearly.
Add structureTurn the second section into a card grid so it is easier to scan.
Executive toneShorten the intro to 2 sentences and make the tone more direct for an executive audience.

 

5. Best practices

These are the habits that separate people who get good output from people who give up on the tool.

PracticeWhy it matters
Treat the first output as a draftThe builder gets you 80% there. The last 20% is you.
Write the prompt like an instruction to a new hireSay the goal, the reader, and the format. Assume no shared context.
Keep a note of prompts that workedYour best prompts are reusable. Save them in a Spek for your team.
Check facts against a real sourceThe builder can produce confident wrong answers, especially with numbers, dates, and names.
Stay under 1700 charactersThat is the prompt limit. Long context belongs in an attached source, not in the prompt.

 

Was this article helpful?
0 out of 0 found this helpful