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.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Audit [CRM workflow] against [original requirement] before making changes. Trace the active production campaign version, configured steps, approved templates and existing data. Compare these with [staging configuration] and the implementation already present. Report whether selecting [call outcome] prepares an email for operator approval. Separate code, deployment and configuration findings. Do not send emails or modify production. Propose an end-to-end acceptance test and wait for my approval before implementing a fix.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- u/Admir-Rusidovic
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- 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.
- Human involvement
- 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.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The author specified an operator-approved introductory email after a prospect requested information during a call.
- A lead Claude Code agent coordinated workers, implementation reviews and tests across separate Git branches.
- The author checked the actual production workflow after the development work had been reported complete.
Admir-Rusidovic describes a Claude Code development failure in a SaaS platform. A lead agent coordinated workers on separate Git branches, with code reviews, staging and production releases. The agents reported an outbound calling and email feature complete, but the author's production check found that the intended workflow did not work.
The requirement was specific. After a prospect requested information during a call, an operator should select that outcome, prepare an introductory email, approve it and send it through the CRM. The email infrastructure and approval safeguards existed. Newer campaign rules supported introductory emails. However, the active production campaign still used an older published version without an email step or approved template. Selecting the outcome created a follow-up task instead.
In returned comments, the author says they already used Playwright for authenticated staging and functional user journeys. The gap was therefore not simply a missing browser-testing tool. A newly configured environment could work while an existing production campaign retained older rules.
The author began reviewing acceptance criteria across implementation, deployment, configuration and existing workflows. That review is an intended process improvement, not evidence of a completed repair. The account illustrates how agents can accept earlier completion reports without verifying the original operational requirement.
Who it's for: teams using coding agents can use this failure account to examine whether their acceptance checks cover the configuration and existing data that real operators encounter.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Reddit · u/Admir-Rusidovic
Frequently asked questions
Was the email functionality entirely missing from the code?
No. The author says the email infrastructure, approval safeguards and newer campaign rules existed. The production campaign still used an older version without the required email step or template.
Did the team already use browser-based testing?
Yes. In a returned comment, the author describes using Playwright for authenticated staging and functional journeys. Existing production configuration was not sufficiently covered by the checks.
Does the source confirm that the production workflow was repaired?
No. It reports the failed production behaviour and a review of acceptance criteria, but does not establish that the active campaign was subsequently corrected.
More details
Remaining steps
- The check found an older published campaign version without a configured email step or approved template.
- The author began reviewing acceptance criteria to connect the original requirement with existing production configuration.
About this account
A lead agent coordinated development and workers implemented changes on separate branches with reviews and tests. Their completion reports did not establish that the existing production campaign delivered the required end-to-end behaviour.
Firsthand account by u/Admir-Rusidovic: https://www.reddit.com/r/ClaudeCode/comments/1xb5r8j/one_limitation_im_discovering_with_ai_coding/. Public RSS post and returned comments captured on 23 October 2026; RSS coverage is partial. Body eligibility passed at 0.86. Results are author-reported, not independently reproduced. Suggested prompt by Agents In Use, not the author's original prompt.
Credit: u/Admir-Rusidovic on Reddit
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Git branches · CRM · Playwright · Staging environment
acceptance testing · coding agents · CRM · production configuration · failure account
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.