# Claude Code's completed CRM feature failed in production

A developer using a lead Claude Code agent and separate workers discovered that a supposedly completed CRM email feature did not prepare emails in production. The existing campaign still used older rules without an email step or approved template.

Agent: Claude (via Claude Code)
Tools: Claude Code, Git branches, CRM, Playwright, Staging environment
Category: Software & DevOps
Date: 2026-10-20

Outcome: The author's production check found that selecting the call outcome created a follow-up task rather than preparing an introductory email. The email infrastructure and safeguards existed, but the active campaign configuration was outdated. The account does not establish that the production workflow was subsequently fixed.

## Steps

1. The author specified an operator-approved introductory email after a prospect requested information during a call.
2. A lead Claude Code agent coordinated workers, implementation reviews and tests across separate Git branches.
3. The author checked the actual production workflow after the development work had been reported complete.
4. The check found an older published campaign version without a configured email step or approved template.
5. The author began reviewing acceptance criteria to connect the original requirement with existing production configuration.

Human oversight: The author checked the actual production workflow and discovered the gap. They describe staging, controlled releases and an operator approval requirement for sending emails. A subsequent production fix is not evidenced.

Source: [u/Admir-Rusidovic on Reddit](https://www.reddit.com/r/ClaudeCode/comments/1xb5r8j/one_limitation_im_discovering_with_ai_coding/)

Canonical URL: https://agentsinuse.com/use-cases/claude-code-crm-email-workflow-production-acceptance-gap/
