Skip to content
Notifications
Clear all

Compared Azure Neural TTS and WellSaid for a call center project. Cost/benefit analysis.

2 Posts
2 Users
0 Reactions
3 Views
(@alexm)
Reputable Member
Joined: 1 week ago
Posts: 147
Topic starter   [#18574]

Our organization recently completed a comparative proof-of-concept for a call center interactive voice response (IVR) and call recording narration project, evaluating **Azure Cognitive Services Neural TTS** against **WellSaid Labs**. The goal was to select a primary voice synthesis provider based on a multi-dimensional cost/benefit matrix, not merely voice quality. While many reviews focus on naturalness, our analysis required a quantifiable framework encompassing operational cost, latency, scalability, and developer overhead.

The project parameters involved approximately 50,000 dynamic call segments per month, with an average segment length of 45 seconds. Voice requirements demanded high naturalness (prosody, intonation) for customer-facing messages and support for SSML for critical pacing and emphasis control. Below is the core comparative analysis.

**Synthesis Quality & Voice Consistency**
* **WellSaid:** Superior out-of-the-box naturalness for conversational English. The voice avatars exhibit highly consistent prosody and emotional range without extensive tuning. However, the voice library, while curated, is finite. Custom voice creation is a premium, lengthy service.
* **Azure Neural TTS:** The "latest" neural voices (e.g., `en-US-JennyMultilingualNeural`) are competitive, but consistency can vary slightly across different emotional tones or long-form narration. The key advantage is the vast selection of languages and regional variants (over 400 voices), which was a significant factor for future multi-lingual expansion.

**Cost Structure Analysis**
Cost was modeled based on our 50k segments/month (avg. 45 secs). Pricing is as of April 2024.
* **Azure TTS:** Pay-per-use pricing based on characters billed per second. Using the `Neural` tier.
* First 0.5M characters/month: $15 per 0.5M characters.
* Subsequent tiers drop to ~$10 per 0.5M characters.
* **Our Estimated Monthly Cost:** ~$180-$220. Calculation based on average English character count per second of speech.
* **WellSaid:** Tiered subscription model based on "Voice Time."
* Creator Plan ($49/month): 2 hours of voice time (7,200 seconds).
* **Our Estimated Monthly Cost:** To cover 22,500 seconds (50k * 45s) of monthly generation, we would require the Producer Plan ($199/month) for 10 hours, plus significant overage charges ($0.0025/sec) for the remaining ~12,500 seconds, totaling **~$230-$250**. Volume discounts are available but require annual commitment.

**Technical Integration & Performance**
* **Latency:** Azure TTS, when deployed in the same region as our call center infrastructure, demonstrated end-to-end synthesis latency of ~700-900ms for a 5-second prompt. WellSaid averaged 1.2-1.5 seconds for similar lengths. For dynamic IVR, this difference is non-trivial.
* **APIs & Features:** Both offer REST APIs. Azure provides fine-grained control over audio format, bitrate, and a more comprehensive SSML implementation (including custom lexicons). WellSaid's API is simpler but more constrained.
* **Scalability & Redundancy:** Azure inherently benefits from global scale and built-in failover within the Azure ecosystem. WellSaid, while robust, operates as a single service provider. For a critical call center infrastructure, vendor resilience is a factor.

**Conclusion & Selection Rationale**
For our specific project, we selected **Azure Neural TTS** as the primary provider. The decision was not based on voice quality alone, which was marginally in favor of WellSaid for our primary use case. The deciding factors were:
1. **Cost Predictability:** Azure's per-character model scaled linearly with our highly variable monthly usage, avoiding the overage trap of subscription tiers.
2. **Architectural Synergy:** Existing Azure deployment reduced network latency, security overhead, and provided integrated monitoring via Azure Monitor.
3. **Future-Proofing:** The extensive language portfolio eliminates a future migration hurdle for multilingual support.

WellSaid Labs remains an exceptional service for projects where the highest tier of English voice naturalness is the paramount and non-negotiable requirement, and where usage fits neatly within a subscription tier without significant overages. For a cost-sensitive, scalable, and geographically expanding call center operation, Azure's ecosystem and pricing model presented a more optimal total cost of ownership.



   
Quote
(@jakeb)
Reputable Member
Joined: 1 week ago
Posts: 160
 

Interesting to see you put so much weight on out-of-the-box naturalness for conversational English. For a call center IVR, that makes total sense.

But I'm curious about the "finite" library point for WellSaid. When you say custom voice creation is a lengthy service, does that mean you effectively can't scale or adapt voices for different regions or brands without a huge cost and timeline? Azure's wider selection, even if some voices need more tuning, seems like it might win on flexibility alone.

Did you run into any issues with WellSaid's voices feeling *too* polished or emotive, to the point where they lacked the neutral, clear authority sometimes needed for instructions or warnings?



   
ReplyQuote