Advanced Prompt Engineering

Advanced System Prompt — Annotated // ① IDENTITY You are Maya, senior consultant at Bloom Agency. // ② SCOPE + PERSONA Your goal: qualify leads for our web design service. Be warm and expert. // ③ CONDITIONAL LOGIC If visitor asks about pricing: give range then invite to book a scoping call. If visitor says "I need it urgent": highlight our 2-week express track. // ④ LANGUAGE RULES Always use short sentences. Never use jargon. Max 2 paragraphs. // ⑤ CONVERSION TRIGGER After answering 2 questions: invite to book a free 20-min call: https://cal.com/bloomagency/discovery // ⑥ FALLBACK If unsure: "Great question — let me connect you with our team: hello@bloomagency.com"

Advanced prompt engineering goes beyond basic persona and tone settings. It's the practice of crafting system prompts that give the AI nuanced, conditional instructions — producing dramatically more precise, consistent, and conversion-optimised behaviour. This guide covers the techniques used by top-performing agents.

Beyond basic prompts

A basic prompt sets persona and tone. An advanced prompt adds:

  • Conditional logic — "if visitor says X, do Y"
  • Staged conversion triggers — push the CTA after specific conversation milestones
  • Role boundaries — explicit rules about what the agent will and won't discuss
  • Language rules — vocabulary constraints, sentence length, formality level
  • Persona depth — backstory, communication style, specific phrases to use or avoid

Conditional (if/then) logic

You can instruct the AI to behave differently depending on what the visitor says. This creates personalised conversation flows without complex code:

If a visitor mentions budget concerns, acknowledge empathetically then shift to ROI:
"I understand budget is important — many of our clients said the same 
before they saw the results. Would it help to walk through the numbers together?"

If a visitor mentions urgency ("I need this quickly / ASAP / urgent"):
Highlight your express delivery option immediately.
"We offer a 2-week express track for time-sensitive projects — 
shall I share more details?"

If a visitor asks about a competitor:
Never disparage competitors. Instead say:
"I can't speak to how others work, but I'm happy to walk you 
through exactly what we offer and how we approach [topic]."

Staged conversion triggers

Instead of pushing the booking CTA immediately, you can time it to feel more natural:

After answering the visitor's first question: give a helpful, complete answer only.

After the second question OR if the visitor asks about price/timeline/getting started:
Bridge to the booking CTA: "Would it be useful to hop on a quick 20-minute call? 
I can give you a much clearer picture in 20 minutes than I can in chat. 
Here's my calendar: [link]"

This feels far more natural than immediately pushing the CTA after every message.

Vocabulary and language rules

Precise language instructions prevent common AI bad habits:

  • "Use plain English. Never use jargon unless the visitor uses it first."
  • "Keep all responses to 2–3 sentences unless the visitor explicitly asks for more detail."
  • "Never start a response with 'Of course!', 'Certainly!', or 'Absolutely!'" — these feel robotic and over-eager
  • "Use the word 'we' not 'I' when referring to the company."
  • "Never say you're an AI unless directly asked."
💡
Iterate relentlessly The best system prompts are never "finished" — they evolve based on real conversation data. Read transcripts weekly, spot patterns in weak responses, and add specific instructions to address them. After 8 weeks of iteration, a well-maintained prompt produces remarkably consistent, on-brand output.

Testing prompts systematically

When making significant prompt changes, run a side-by-side test. Ask 10 identical questions with the old prompt, then 10 with the new prompt. Score each answer set. Only deploy the new prompt if it clearly outperforms the old one. This prevents accidental regressions where a change that fixes one issue creates another.