Honeycomb <> OneAI: Weekly Sync

Date: 2025-09-04 | Duration: 31.579999923706055 min | Account: honeycomb

External attendees: jan.j@honeycombinsurance.com, jon@honeycombinsurance.com, rafael@honeycombinsurance.com

Summary

This week’s meeting highlighted significant recovery in system performance, with 66 qualified conversions, a notable increase from 21 last week, signaling effective resolution of prior regression issues. A new software release set for Monday aims to further enhance performance. Recent analysis of 89 customer contacts since August 27 revealed an 11% escalation request rate, underscoring customers’ preference for human agents in certain scenarios. Additionally, performance comparisons prompted a shift from the Aaron voice to the Raquel voice, which is perceived as more naturalistic. An ‘escalation requested’ field is being implemented to streamline response management, while a transcription error leading to one escalation has been corrected. The qualification process will also be refined to eliminate redundant questions, addressing customer confusion regarding rates, which are generally expected to be 30% below actual offers, with a 10% threshold limiting escalated case captures.

Key Points

📈 Strong Recovery: System conversions increased significantly to 66, indicating effective issue resolution. 🆕 Upcoming Software Release: A new software release on Monday is expected to enhance performance improvements. 🤝 Customer Preference: 11% of analyzed contacts requested human agents, highlighting a need for personal interaction. 🔊 Voice Transition: The transition from Aaron to Raquel voice aims to provide a more naturalistic experience. ✅ Streamlined Process: Implementing an ‘escalation requested’ field will improve identification and response to needs.

Overview

  • System showed strong recovery with 66 qualified conversions this week, up from 21 last week, indicating effective resolution of previous regression issues.
  • New software release scheduled for Monday expected to enhance ongoing performance improvements.
  • Analysis of 89 contacts since August 27 revealed a 11% escalation request rate, highlighting customer preference for human agents in specific scenarios.
  • Performance comparison indicated more escalations with the Aaron voice, prompting a transition to the Raquel voice, which is perceived as more naturalistic.
  • The implementation of an ‘escalation requested’ field will streamline identification of escalation needs during calls, improving response management.
  • At least one identified escalation resulted from a transcription error, which has now been rectified to enhance accuracy.
  • Qualification process will be refined by eliminating redundant questions, leading to reduced customer confusion.
  • Customers generally expect rates to be 30% below actual offers, with a 10% threshold limiting effective capture of escalated cases.

Action Items

Daniella Block Take note to develop new AI voice option between Raquel and ‘Rolex commercial’ style - more mellow, older female voice (12:43)

Jon Repka Connect with team to update webhook and capture new ‘escalation requested’ field in data pipeline (17:29) Implement automated email follow-up system for escalation cases to improve customer experience (15:48)

Amit Ben Remove ‘expiration date for current insurance’ question from qualification process starting next week (30:35) Provide escalation requested field integration details and specify where to push the data (31:16) Continue monitoring voice performance and collect IVR samples for review with client team (21:55)

Rafael Mintz Follow up on escalation requested field implementation and ensure proper data capture (31:20)