HUME API MIGRATION WORKSHEET
Reviewed October 9, 2026. Free planning resource; production usage is not free.
This worksheet is not an account export, portable voice model or tested migration.
No provider/account actions were performed to prepare it. Keep secrets out.

1. DEADLINE AND OWNERS
Hume notice published October 2, 2026:
TTS / EVI access ends November 13, 2026 at 12:01 a.m. EST.
Account data permanently deleted after November 13.
Verify notice: https://dev.hume.ai/voice/changelog
Business owner:
Technical owner:
Data/voice permission reviewer:
Internal decision date before deadline:
Fallback owner and operating hours:

2. SCOPE
Application/environment:
[ ] TTS component only  [ ] EVI full conversation  [ ] Both
Existing endpoint/version/configuration ID:
Where callers enter (browser/telephone/other):
Upstream recognition/reasoning ownership:
Session-time overrides and where configured:
Critical dependency / business outcome / replacement owner:

3. PERMITTED DATA INVENTORY
Asset | Existing reference | Why needed | Permission/retention basis
Destination/access | Status | Retrieval date | Reviewer
Status: identified / retrieved / reviewed / unavailable / intentionally excluded.
Voice metadata and usage restrictions:
Original recordings already lawfully held and approved for proposed new use:
Saved EVI config/prompt/tools/turn/interruption/event/timeout settings:
Session overrides:
Chat/group IDs and configuration associations:
Permitted history/events and relevant business records:
Records unavailable because retention was disabled:
Pagination/completeness review and unresolved retrieval questions:

Reference only, no request executed here:
Saved voices: GET /v0/tts/voices?provider=CUSTOM_VOICE
https://dev.hume.ai/voice/docs/voice/management
History/event routes and retention limits:
https://dev.hume.ai/voice/docs/speech-to-speech-evi/features/chat-history
A voice metadata list does not export a reusable voice model.
No verified automatic Hume import, clone portability or bulk audio export.
Ask Hume support about unclear supported retrieval.

4. REPLACEMENT CONTRACT
Existing component/behavior | New component/control | Gap | Owner | Evidence
Voice/provider-specific ID:
Speaking instructions/audio format/playback stop:
Recognition/language/turn commit:
Business instructions/approved knowledge:
Tool input/schema/permission/result/error/duplicate prevention:
Session context/retention:
History/recording destination and access:
Voice change caller-review requirements:

5. FICTIONAL SUPPORT CASE
Caller: Unit N,L,four,one. Sorry,four,seven. It started stopping yesterday.
Please have someone call me back.
Expected: confirm NL47 and callback, collect issue, leave staff review pending.
Do not claim repair, warranty, appointment or external request completed.
This expected result is a criterion, not an observed provider result.

6. BURKI DRAFT PREPARATION
Assistants -> draft -> Voice -> Model and provider choices
Conversation engine: Standard pipeline · advanced provider choices
Within same panel: Advanced speech recognition -> chosen provider/model/language
Speech settings -> Advanced voice stack -> Voice provider / Voice model /
Assistant voice. Use a permitted voice belonging to that provider, not Hume ID.
Reviewed instructions and separate action connections:
Readiness/credentials/Usage & billing checked:
Saved config reference/date (if actually saved):
No selector/saved draft proves provider execution or task acceptance.

7. ACCEPTANCE RECORD
Case | Date/config/version | Attempt status | Audio/transcript | Task receipt
Expected | Observed | Unresolved gap | Reviewer
Clean request:
Corrected identifier:
Interrupted response:
Unavailable action connection:
Incomplete request:
Include failures. Review actual caller-heard response and business record.

8. COST AND CUTOVER
Rate/account date | Unit | Expected quantity | Subtotal | Exclusions
Old service during overlap:
New speech/recognition/reasoning:
Telephone/platform/storage/tools:
Authorized test budget and owner:
Fallback after provider deadline (must not depend only on retired API):
Traffic/routing change owner and acceptance evidence:
Post-switch caller and staff follow-up verification:
Final decision and date: