Developer Enablement, Customer.io.
Explore with your AI assistant
ChatGPT (opens in a new tab)Claude (opens in a new tab)Perplexity (opens in a new tab)Grok (opens in a new tab)
Opens a new chat with a prompt that points the assistant to this archive. What it writes is its own, not the archive's: check any quotation on its passage page before you rely on it. Or add the archive to your assistant as a connector: https://the-ai-record.com/mcp (how).
Byline author of the Customer.io engineering post on AI pull request approval; listed under Developer Enablement.
Why their word counts: Wrote the post about the team’s own AI review system, so the figures come from the team that built and runs it.
Profile from this source, checked 2026-11-04.
The AI is approving over 60% of all PRs. For those PRs, engineers get feedback in minutes, not hours.
Joey BatesDeveloper Enablement · Practitioner, 
Customer.io
Post: How we taught AI to approve pull requests (not just review them), Customer.io, November 10, 2025, at Results: Speed and cognitive relief.
For PRs that got AI approval, merge time dropped from 3.5 hours to 33 minutes. That's 6.4x faster.
Joey BatesDeveloper Enablement · Practitioner, Customer.io
Post: How we taught AI to approve pull requests (not just review them), Customer.io, November 10, 2025, at Results: Speed and cognitive relief.
We taught AI to approve pull requests for merging. After 500 AI-approved PRs: zero production incidents, and merge time dropped from 3.5 hours to 33 minutes.
Joey BatesDeveloper Enablement · Practitioner, Customer.io
Post: How we taught AI to approve pull requests (not just review them), Customer.io, November 10, 2025, at Article summary.
High-risk PRs that the system flagged for human review took about a day to approve. That's longer than the baseline. This is correct behavior. These are architectural changes, infrastructure modifications, and breaking changes. They need time and human judgment.
Joey BatesDeveloper Enablement · Practitioner, Customer.io
Post: How we taught AI to approve pull requests (not just review them), Customer.io, November 10, 2025, at Results: Safety validation.
Most AI code review tools stop at comments. They suggest improvements, flag issues, and point out problems. We built a system that approves PRs for merging.
Joey BatesDeveloper Enablement · Practitioner, Customer.io
Post: How we taught AI to approve pull requests (not just review them), Customer.io, November 10, 2025, at Problem: The cognitive weight of waiting.
Some changes are beyond automation: architectural decisions, complex trade-offs, and organizational implications. The system recognizes these boundaries and escalates.
Joey BatesDeveloper Enablement · Practitioner, Customer.io
Post: How we taught AI to approve pull requests (not just review them), Customer.io, November 10, 2025, at Lessons learned: Building systems engineers trust.