Migrating off Amazon Connect Voice ID
Voice ID has reached end of support. Here is how IdentityCall replaces speaker verification and identification, with an API and call analysis you did not get before.
Last updated: June 2026
Amazon Connect Voice ID is end-of-life
According to AWS, Amazon Connect Voice ID closed to new customers on May 20, 2025 and reached end of support on May 20, 2026. Existing deployments must move to another speaker-recognition provider. Verify the current status in AWS documentation before you plan a cutover.
When AWS retired Amazon Connect Voice ID, its own guidance pointed customers to AWS Marketplace partners, most prominently Pindrop, an enterprise-gated vendor with no public self-serve pricing. For teams that adopted Voice ID precisely because it was usage-priced and API-driven, that is a step up in cost and friction.
IdentityCall is built for that gap. It delivers speaker enrollment, verification, and identification through a REST API, at published SMB and mid-market pricing, and adds the call analysis Voice ID never did: transcription, QA scoring, categorization, emotion analytics, and compliance disclosure detection. You replace one capability and gain five.
Amazon Connect Voice ID vs. IdentityCall
| Feature | IdentityCall | Amazon Connect Voice ID |
|---|---|---|
| Status | Generally available | End of support (May 20, 2026) |
| Speaker verification |  | |
| Speaker identification | | |
| Works outside Amazon Connect | API, uploads, own numbers | Amazon Connect only |
| Transcription & diarization | | No |
| Automated QA / call scoring | | No |
| Emotion analytics | | No |
| Compliance disclosure detection | | No |
| AI-cloned voice detection | | Limited |
| Self-serve API & published pricing | | No |
| EU / GDPR data handling | | AWS regions |
Competitor facts (Amazon Connect Voice ID end-of-support timeline and AWS migration guidance) are drawn from AWS documentation as of June 2026. AWS may change timelines or guidance; re-verify against the current AWS docs before making decisions.
Choose IdentityCall if
- You are migrating off Voice ID and want an API-first replacement without an enterprise contract.
- You want speaker recognition plus transcription, QA, emotion, and compliance in one platform.
- You record or upload calls from outside Amazon Connect.
- You need EU/GDPR data handling and transparent pricing.
Consider an AWS-native path if
- • You are deeply embedded in Amazon Connect and need an in-console replacement.
- • You are an enterprise comfortable with quote-based contracts (for example, Pindrop).
- • Speaker biometrics is the only capability you need and call analysis is irrelevant.
Frequently asked questions
When does Amazon Connect Voice ID shut down?
Per AWS, Voice ID closed to new customers on May 20, 2025 and reached end of support on May 20, 2026. After end of support, applications can no longer rely on the Voice ID APIs. Confirm the current status in AWS documentation.
What does AWS recommend migrating to?
AWS directs customers to AWS Marketplace partners for voice biometrics, most prominently Pindrop. Pindrop is enterprise-focused and does not publish self-serve pricing. IdentityCall is an API-first alternative with published SMB and mid-market tiers.
Can I transfer my existing voiceprints?
Voice embeddings are not portable between vendors because each uses a different model. With IdentityCall you re-enroll speakers, typically from the call audio you already retain, which lets you rebuild profiles without collecting new recordings.
Does IdentityCall require Amazon Connect?
No. IdentityCall works through a REST API, direct audio uploads, and its own virtual numbers, so it is not tied to any single telephony platform.
What do I gain beyond speaker recognition?
IdentityCall analyzes every call: transcription with diarization, goal-based QA scoring with reasoning, auto-categorization, per-segment emotion analytics, and compliance disclosure detection, alongside the biometrics you are replacing.
Plan your migration off Voice ID
Talk to us about moving speaker verification and identification to IdentityCall, with call analysis included.
