Short answer: for an MP3 or WAV speech-to-text API upload, put a durable, provider-neutral intake record between the file and the CRM; that is the fastest integration to recover when a regional request or action write fails.

Keep the original MP3 or WAV, record the region and request contract beside it, and make every downstream action replayable. The fastest integration is the one that can lose a transcription request without losing the call or inventing a follow-up.

Keep it boring.

The queue is the contract.

At 3 a.m., I do not trust a green dashboard that says transcription_success=true . I want to know which call was accepted, which audio bytes were actually sent, what region processed them, and whether the CRM write happened once. That is the operational question behind a simple speech-to-text upload.

The useful boundary is a durable intake record.…