Bezeq
Overview
Section titled “Overview”| Field | Detail |
|---|---|
| Industry | Telecommunications |
| Country | Israel |
| Channel | Voice |
| Initial delivery | 120 days (initial implementation) |
| Primary use case | Internet technical support, technician scheduling, and service upgrades |
Business challenge
Section titled “Business challenge”Legacy IVR and earlier generic AI tools were insufficient for high-volume, complicated troubleshooting. Routine issues still burdened agents and often required technician visits.
AI solution
Section titled “AI solution”A voice agent diagnoses connectivity and infrastructure issues, follows automated resolution workflows, books field-technician visits when needed, and can present relevant upgrades. Multilingual support is described by Wonderful.
Technical implementation & delivery
Section titled “Technical implementation & delivery”Integrated with ISP service and support workflows; the public case study does not identify the specific CRM, telephony platform, models, or infrastructure. The published rollout period is 120 days.
Results & KPIs
Section titled “Results & KPIs”| Metric | Reported result | Measurement scope / context |
|---|---|---|
| Initial interaction volume | 6,500 in first 6 weeks | Initial deployment; not all company calls |
| First-attempt resolution | Approximately 75% | Of cases handled in the described agent scope |
| Conversation duration | 40% shorter | Comparison basis not described in detail |
| Customer sentiment | 15% higher | Vendor-reported sentiment, not a documented CSAT study |
| Wait time | Instant pickup vs. queues exceeding 5 minutes | For the AI-supported call path |
Key takeaway
Section titled “Key takeaway”A credible example of transactional telecom voice AI: diagnosis and field-service actions matter more than replacing IVR prompts alone.