Common mistakes and their fixes at a glance.

Mistakes and Fixes

MISTAKEFIX
Agent repeats the same question verbatimAdd Zero-Loop Policy. Rephrase and shorten on each re-ask.
Agent treats “hmm”, “accha” as agreementAdd Fillers rule to Interaction Guidelines.
Agent rushes through multiple stepsAdd “Stop and wait” after branching questions.
Agent argues with hostile customersAdd Hostile Callers guardrail. Acknowledge, don’t defend.
Agent ends call without checking if there’s anything elseAdd “Before Closing” guardrail. Always ask one last time.
Variables are undefined when referencedGuard every variable reference. “If [[ variable ]] is set and equals X…”
Conditions are vagueBe descriptive. “If user agrees to pay today” not “if user says yes”.
Too many states createdTarget 2–3. Create a state only if agent must hear from user before proceeding.
Voicemail message includes sensitive detailsKeep voicemail generic: name, org, purpose, callback number only.
Tool is called before its response mattersSequence: Call tool first. Only after response, act on it.
Agent gives up too quicklyUse nudge pattern. Acknowledge → Reframe → Offer alternative → Close gracefully.
Instructions are too prescriptiveWrite behavioral intent, not exact scripts. Let agent find the words.
Variable naming is inconsistentUse lowercase with underscores: callback_time, not callbackTime or Callback Time.
Guardrails are vagueBe explicit. “Never argue” → “Acknowledge, do not argue, move to escalation state.”
Edge cases are discovered after launchList top 5 edge cases before writing prompts.

Quick Checklist Before Launch

  • Purpose is one sentence
  • Call direction defined (Outbound / Inbound)
  • Top 5 edge cases listed and addressed
  • Data flow documented (Start → During → End)
  • Prompt uses instructional, not deterministic language
  • All conditions are specific, not vague
  • Fillers rule added (“hmm”, “accha”, etc.)
  • Stop-and-wait added after branching questions
  • Zero-Loop Policy added
  • States are 2–3 max
  • Each state covers: Purpose, Happy path, Edge cases, Transitions, Termination
  • Variables are referenced with [[ ]] and guarded
  • Disposition variable set at call end
  • Guardrails added: Identity, Hostile, Ambiguity, Confidentiality, Voicemail, Before Closing
  • Tools defined with clear parameters and error handling
  • Tested in Playground
  • Ready to deploy

Next Steps

  1. Start with Understanding the Use Case
  2. Generate a draft using the Prompt-Generation Template
  3. Refine using Writing Good Instructions
  4. Design states with State Instructions
  5. Define Variables
  6. Add Guardrail Blocks
  7. Define Writing Tools
  8. Use this Quick Reference to verify before launch