Shriram Finance
less than 3–4 hours — Onboarding Turn-Around-Time (TAT)
Independently reportedBanking & finance · Process automation · Classical ML · In production
Process automation
Yotpo · Enjo
Vendor-reportedTechnology & softwareScaledEnterpriseAI agents
Vendor-reported. The customer is named and the numbers are quoted from the source page, but the account comes from the vendor. No independent confirmation.
Reported by enjo.ai (vendor self-report). Checked against the source page on 2026-09-06. 2 of 2 figures below appear on that page word for word.
The problem
Yotpo needed to replace a failing legacy support tool (Halp) quickly, integrate with Slack and Jira for DevOps, and automate resolution of common internal employee queries to free up engineering bandwidth.
What was deployed
- Vendor
- Enjo
- Products
- Enjo Ticketing for Jira, AI Agents, Agent Studio, MCP server, Enjo Inbox
- Technique
- AI agents
- Build or buy
- Bought off the shelf
- Deployment
- SaaS
- Data used
- internal systems, APIs, operational data, live data from Yotpo's connected systems
- Scale
- 40+ Slack channels
What changed
Each row is quoted from the source. Figures we could not find on the page in those words are marked — they are kept, not deleted, so you can judge them.
100%Adoption ratewithin the first month
“100% adoption - Full team adoption within the first month of deployment, demonstrating strong user engagement and system effectiveness across all 40+ channels.”
Quoted word for word from the source
30% fasterTicket creation timefrom manual workflows with Halp
“30% faster ticket creation - Achieved a 30% reduction in time spent creating and managing Jira tickets compared to manual workflows with Halp.”
Quoted word for word from the source
InstantEmployee query resolution
“Instant employee query resolution - Common employee questions about deployments, system status, and access are now resolved autonomously by the AI Agent via MCP server integration - freeing up DevOps bandwidth for higher-value work.”
Quoted word for word from the source
Zero-downtimeMigration downtime
“Zero-downtime migration - Transitioned from Halp to Enjo across 40+ Slack channels within a strict two-week timeline with no disruption to daily operations.”
Quoted word for word from the source
Difficulties and limits
- Replacing a failing tool (Halp) quickly without disruption
- Integrating effortlessly with Slack while preserving emoji-based actions
- Supporting DevOps second-level support efficiently
- Employees spending significant time navigating internal tools for routine questions
- Repetitive queries draining engineering and DevOps bandwidth
- Answers scattered across disconnected internal services
- When the agent's confidence is low or the request requires human judgment, it escalates cleanly into the Enjo Inbox with full context and a recommended next step.
Sources
- enjo.ai — vendor self-report
Similar deployments
GE Aerospace
Independently reportedManufacturing · Process automation · Classical ML · Scaled
Apollo Tyres
under 10 minutes — Time for root cause analysis
Independently reportedManufacturing · Process automation · AI agents · In production
Broadcom · Moveworks
88% — autonomous IT resolution rate
Independently reportedTechnology & software · Process automation · NLP · Scaled
Amazon · Amazon
10% more — shopper spend
Independently reportedRetail & e-commerce · Process automation · Computer vision · Scaled · 2024
icare · SAS
increased by 15% — accuracy
Independently reportedInsurance · Process automation · Classical ML · Scaled · 2019