Key points
- Programmatic enforcement (hooks, prerequisite gates) is deterministic; prompt guidance is probabilistic.
- When compliance must be certain (identity check before financial operations), prompt instructions alone have a non-zero failure rate.
- A structured handoff includes customer details, root cause analysis, and recommended actions.
- Multi-concern requests should be split into distinct items and investigated in parallel with shared context.
- A gate blocks a downstream tool (for example
process_refund) until a prerequisite (a verified ID fromget_customer) has completed.
Common misconceptions
- "A strongly worded prompt is as reliable as a hook." It is not; a 2% miss on refunds is still unacceptable.
- "Escalation can just point the human at the chat." Humans often cannot see it and need the facts up front.
- "Handling one concern per turn is fine." It lowers first-contact resolution.
Watch for
Financial or compliance steps enforced only through prompt wording, and vague handoffs with no customer ID or root cause.
Practice Task 1.4
Start with the free 10-question check to see where you stand across all five domains. In CCA Prep Studio, 57 practice items cover this task, each tracked toward your mastery score.