# Meeting summary
The meeting was with Assurant, represented by leaders in customer experience, contact center operations, and procurement/risk. Assurant is seeking to improve the naturalness and reliability of their voice technology in customer service, particularly to reduce caller frustration and operational costs in their warranty business. The main outcome was a detailed discussion of pain points, success criteria, and procurement process, followed by a live demo of Rhyme’s technology focused on a phone warranty scenario.

## Pain points & concerns
- **Unnatural intonation and robotic pacing**: Causes caller hesitation, especially when customers are upset or in a hurry, leading to requests for human agents and increased hang-ups.  
  *Business impact*: Reduces containment rates, increases agent workload, and negatively affects CSAT. Severity rated 8/10 by Sam.
- **Fragility under emotional or complex calls**: Current solution drops off during emotional or messy calls, requiring human intervention.  
  *Business impact*: Increases operational cost and inconsistency.
- **Risk and rollout complexity**: Concerns about introducing new compliance exposure, compatibility with existing tech stack, and overall vendor risk.  
  *Business impact*: Potential for compliance breaches and operational disruption.
- **Manual effort for edge cases**: Current systems require extensive hand scripting to handle tone and edge cases.  
  *Business impact*: Limits scalability and adaptability, increases maintenance burden.
- **Desire for cleaner, faster deployment and evaluation**: Long integration cycles and unclear success criteria slow down decision-making and greenlighting.  
  *Business impact*: Delays in realizing value and internal alignment.

## Success criteria for the new technology
- **Production metrics improvement**: Demonstrated gains in containment rate, reduction in hang-ups, improved post-call survey results, and stable or improved sentiment analysis.
- **Reliability under stress**: Consistent performance during emotional or complex calls, with fewer handoffs to human agents.
- **Natural, adaptive voice**: More human-like intonation and pacing without requiring extensive manual scripting.
- **Short, measurable pilot**: Ability to evaluate success quickly with clear, agreed-upon metrics.
- **Risk management**: Clear data handling, vendor risk controls, and compliance fencing during pilot.

## Decision process & criteria
- **Process**: 
  - Problem alignment
  - Limited pilot with clear, measurable success criteria
  - If pilot is successful, proceed to security, legal, and standard review
  - Start with a small slice of traffic, not full replacement
- **Stakeholders**: Business sponsor, security, legal, procurement, and operations are all involved in approval.
- **Criteria**: Data-driven pilot results ("proof not promises") are critical for internal alignment and acceleration of approval.
- **Champion/Economic buyer**: Sam (partnership/procurement) is a key stakeholder; business sponsor role implied but not named.

## Timeline
- **Pilot duration**: Not specified, but preference for short evaluation cycles (less than six months).
- **Approval window**: If pilot demonstrates real, measurable improvement, approval can be achieved in "a few months rather than weeks."
- **Urgency signals**: High importance placed on solving the problem (rated 8/10); willingness to "make time" if results are strong.

## Next steps
- [ ] Collect client feedback on voice quality and demo performance — Owner: Colin Heilbut (Rhyme)
- [ ] Define pilot scope, metrics, and risk controls in collaboration with Assurant stakeholders
- [ ] Schedule follow-up to discuss pilot design and address compliance/technical integration questions
- [ ] Provide documentation on data handling, security, and compliance for Assurant review