{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/email-dictation-model-alias-cutover","id":"email-dictation-model-alias-cutover","slug":"email-dictation-model-alias-cutover","title":"Recheck Dictated Email Briefs After a Transcription Alias Changes","description":"Campaign engineer whose existing voice-brief requests route to a new model.","dek":"Audio-to-brief semantic fixture with negation, amount and locale assertions.","category":"Email Operations","topics":["Migma","email marketing","campaign governance"],"publishedAt":"2026-10-03","updatedAt":"2026-10-03","lastVerifiedAt":"2026-10-03","readingMinutes":5,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Migma prompt creation and dictation","url":"https://docs.migma.ai/creating-emails/prompt-based-creation?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dictation-model-alias-cutover"},{"title":"xAI October 2 transcription retirement","url":"https://docs.x.ai/developers/release-notes?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dictation-model-alias-cutover"},{"title":"xAI speech-to-text contract","url":"https://docs.x.ai/developers/model-capabilities/audio/speech-to-text?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dictation-model-alias-cutover"}],"wordCount":805,"body":"Recheck the meaning of dictated campaign briefs before they enter Migma when a transcription provider changes the model behind an existing request name. A successful request can conceal a changed upstream interpreter, especially for negation, money, units and spoken corrections.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization; not independently reviewed. Sources checked October 3, 2026. Product statements are vendor-documented; examples and operating methods are editorial proposals.\n\n**Affiliation: Marketing Wiki's commissioning editor maintains Migma.**\n\nMigma's [prompt creation guide](https://docs.migma.ai/creating-emails/prompt-based-creation?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dictation-model-alias-cutover) documents dictation into the prompt box, followed by user review and submission. We recommend that review boundary for voice-led briefs. This article does not identify Migma's transcription provider or claim it uses the xAI service discussed below.\n\n## The October 2 change can keep an old request working\n\nxAI's [release notes](https://docs.x.ai/developers/release-notes?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dictation-model-alias-cutover) say `grok-voice-transcribe-1.0` reached end of life on October 2, 2026, and requests to that name route to `grok-voice-transcribe-2.0` at the same price. That is a dated change relevant to an external audio-to-brief pipeline feeding a marketing workflow.\n\nThe source also claims higher accuracy. We have not measured it and do not infer fewer campaign errors. The operational point is narrower: keeping the old request name does not keep the old model behavior. A transport-only monitor can show success while the transcript changes.\n\nThe [speech-to-text reference](https://docs.x.ai/developers/model-capabilities/audio/speech-to-text?utm_source=marketingwiki&utm_medium=referral&utm_campaign=email-dictation-model-alias-cutover) documents model selection and number, currency and unit formatting when `format=true` is combined with `language`. That makes the formatting configuration part of the campaign input contract as well as the model choice.\n\n## Freeze an audio-to-brief fixture\n\nUse a short, approved synthetic recording whose correct meaning is independently written down. A fictional merchant dictates: “Do not promise free delivery. The notebook is fifteen euros, not fifty. Offer two notebooks; actually, make that one notebook.”\n\nCreate assertions against meaning rather than merely similarity of words:\n\n| Fixture dimension | Expected approved brief | Failure worth blocking |\n| --- | --- | --- |\n| Negation | No free-delivery promise | The exclusion becomes an offer |\n| Amount | EUR 15 | EUR 50 or another unsupported amount |\n| Spoken correction | One notebook | Earlier quantity survives as final instruction |\n| Product name | Approved notebook identifier | Similar-sounding product is substituted |\n| Formatting | Amount and unit remain unambiguous | Locale normalization changes interpretation |\n\nThese sentences and outcomes are synthetic. They are not a measured xAI or Migma transcript. Record the audio revision, expected semantics and who approved the fixture before running any permitted test.\n\nFor multilingual programs, use recordings approved by people who can verify the language and amount. A text-only English translation does not prove the original speech was interpreted correctly.\n\n## Separate transcript quality from campaign authority\n\nKeep three artifacts: audio, raw transcript and approved campaign brief. The transcript records what the service produced. The brief records what the operator permits the email creator to use after checking it against product and offer evidence.\n\nFor the merchant example, a corrected transcript should still be compared with the current price and delivery policy. Speech can be accurately transcribed and still contain an outdated offer. Approval must settle both the interpretation and the business fact.\n\nWhen using native Migma dictation, follow the documented boundary: stop recording, review the words in the prompt box, then submit. When using an external transcription pipeline, make the same review a visible stage before sending its text into Migma. Do not describe an external pipeline as a built-in integration unless it has been verified.\n\n## Audit aliases and normalization settings\n\nFind every configured model name in the external pipeline, including omitted values that use a provider default. Record the documented routing target and observation date. If the API does not expose an executed-model identity, label that field unknown; do not invent it from a successful response.\n\nStore `format` and `language` alongside the model setting. Compare meaningful numbers and units under the intended configuration. A change in punctuation may be acceptable; a change from an exclusion to a promise is not. Define those dispositions before inspecting the new output.\n\nUpdate the configuration deliberately when ready, then retain the raw transcripts for the synthetic fixture. Do not claim rollback to the retired name restores the earlier model when the provider documents automatic routing. A safe temporary fallback may be a manually written and reviewed brief rather than an alias that no longer pins behavior.\n\n## Close the upstream handoff\n\nThe [email model regression suite](/articles/ai-model-upgrade-email-regression-suite) tests the downstream generator and campaign output. This test belongs before that boundary: it asks whether the spoken instruction became the intended text.\n\nNo audio was uploaded, model request sent or campaign generated for this article. Begin by locating one retired or defaulted transcription model name, recording its current routing contract, and requiring an approved semantic brief before its transcript reaches Migma."}