Drift alerts
The SSO article's OpenID Connect section now lists the SAML settings by mistake — the OIDC values IT needs are gone
The "Open ID Connect (OIDC)" section is now a word-for-word copy of the SAML section directly above it: same sign-in URL example (https://samlp.example.com/login), same X.509 signing certificate row, same Entity ID (urn:auth0:wellsaidlabs:XXX-saml), same ACS URL ending in -saml, and the same line "firstname, lastname, email — must be included in the SAML response." An Enterprise IT team setting up OIDC has nothing correct to work from, and every value on the page points them at a SAML connection instead. The four OIDC-specific values (Issuer URL, Client ID, Redirect URL, Initiative login URL) were published on this page as recently as the July 26 scan and disappeared in the July 31 rewrite.
The admin onboarding guide still says the heart icon adds a voice to Team Voices — it's now the bookmark icon, and the heart saves to personal Favorites instead
Two voice articles were rewritten on August 1 to split the two icons apart. Building Your Team Voices List now says "Click the bookmark icon on the voice card to add it to Team Voices," and Favoriting a Voice adds the note "Each voice card also has a bookmark icon next to the heart. That one adds the voice to Team Voices, a shared list for your team — it's separate from your personal Favorites." A new admin following this onboarding guide clicks the heart, and the voice lands in their own Favorites rather than the shared team list they were setting up. This page also still says "Choose a voice and style you wish to favorite from the Explore or All tabs" — the All tab was dropped from both rewritten articles.
The July 30 lock-out date has passed, but both migration articles still describe it as something that might happen
Today is August 3 — the July 30 transition happened between last week's scan and this one. Both articles still read as advance notice: this one asks "What happens if you don't migrate by July 30," and Legacy Studio Migration FAQs says "You can keep editing and rendering in legacy projects normally up until July 30" and "If a project does become view-only on July 30." A customer opening a locked project today can't tell from either article whether the lock is expected or a fault. This is the same pattern as the existing finding on the June 1 migration launch article (51253958068755), but a different date on two different pages.
The retakes article still counts downloads one-by-one, but plans are now measured in minutes — a 3-minute take uses 3 minutes, not 1 download
Understanding Your Download Limit was rewritten on July 29 and now says "Your allowance is the total number of finished audio minutes, not the number of downloads," with per-download counting described as "Legacy download-count plans" that "are no longer offered." The pricing page prices every current plan in minutes (Starter 20 minutes/month, Pro 180 minutes/month, Business 2,880 minutes/year/user). A Starter customer reading this page would expect a 12-minute narration to cost them one download, when it actually spends more than half their monthly allowance.
The Emotional Presets FAQ answers a different question than the one it asks — and reverses last week's answer without saying so
The question is "Can I apply more than one preset to a section?" but the answer talks about applying presets across multiple sections — a different thing. Read literally, it also contradicts the rest of the page: the Removing a preset steps describe a single Reset icon that returns the voice to its default, which only makes sense with one preset per section. Until the July 31 rewrite this FAQ answered "No. Only one Emotional Preset can be active per section at a time. Applying a new preset replaces the previous one."
Combining Sections calls 48 kHz "the highest supported sample rate" two lines after explaining what happens to 96 kHz files
Two FAQs above this one on the same page deal with 96 kHz files: "Files rendered at 96 kHz are limited by total file size" and "The 96 kHz files will be downsampled in the combined output." The pricing page lists Enterprise sample rates as "24 kHz, 48 kHz, 96 kHz." An Enterprise customer reading this FAQ could reasonably conclude 96 kHz isn't offered. This line carried over unchanged when the article was renamed from Using the Combine Tool on August 1.
Sonny G. retirement notice is still written as a future event, but the May 20, 2026 retirement date has already passed
Article 51806828542099 (last updated 2026-06-29, unchanged in word count from the prior crawl) still reads 'On May 20, 2026, Sonny G.'s voice will be retired from the WellSaid Voice Library' and 'On May 20, 2026, Sonny G.'s voice will no longer be available to generate new audio or edit existing audio.' The stated date has already passed. This is the same future-tense-past-date staleness pattern already flagged on the Legacy-migration preview article (51253958068755), but on a different page, and it is not present in the carried-forward finding set for this scan.
Legacy-migration preview article still uses future tense for the June 1, 2026 migration that has already gone live, and promises a guide "in June" that is already published
Article 51253958068755 (last updated 2026-06-05) still reads 'Starting June 1, 2026, you'll be able to migrate legacy projects', 'Migration is not automatic. Starting in June, you'll be able to migrate projects one at a time', and 'We'll be sharing a complete migration guide in June.' The stated date has already passed. Migration is already live: the companion guide 51751205121299 (published 2026-05-15) uses present tense ('you can migrate your legacy projects') and the dated timeline table lists 'June 1, 2026 — Migration opens.' Readers are told migration is a future capability and that a complete guide is still forthcoming, when both already exist. Same future-tense staleness pattern as the carried-forward May 20 findings (Sonny G. / Tobin A.) but on a different page and date, so not a duplicate of any carry-forward.
Tobin A. plan-restriction notice is still written as a future change, but the May 20, 2026 date has already passed
Article 47141067116947 (last updated 2026-06-29, unchanged in word count from the prior crawl) still reads 'Starting May 20, 2026, Tobin A. will only be available on managed Business and Enterprise plans' and 'If you're on a self-service Business plan, here's what changes on May 20'. The stated date has already passed. Same future-tense-past-date staleness pattern as the Sonny G. retirement notice and the Legacy-migration preview article; not present in the carried-forward finding set for this scan.
Security page commits to WCAG 2.1 accessibility compliance "by 2025" — a deadline that has already passed
This page (https://www.wellsaid.io/features/features-security; the prior /features/security page was removed). Its Accessibility section reads 'We are committed to meet WCAG 2.1 and other national standards, working towards compliance in these areas by 2025.' The stated date has already passed. The rest of the section is forward-looking ('working towards'), so the page implies the WCAG 2.1 goal is still in progress past its own deadline. Not present in the carried-forward finding set.
Customers running low on minutes are told add-on packs are still coming and to contact Support — but add-ons shipped in July and can be bought self-serve
This pricing FAQ, last updated 2026-07-21, still answers "I'm running low on downloaded minutes" with "Add-on minute packs are also planned for a future release. Contact Support if you need additional minutes in the interim." Add-ons launched two weeks earlier: the article Adding More Minutes to Your Plan (published 2026-07-07) says "Add-ons let you purchase extra minutes without upgrading to a higher plan tier" and walks through buying one from Account Settings, and the July 2026 release notes announce them. Customers who hit their limit are being sent to Support for something they can buy themselves in three clicks.
The new intro promises every voice is tagged with a speaking style, but more than half the list is tagged "(Partner)" — a voice model, not a style
The intro paragraph added to this article this week says the list covers voices "each tagged with the style it supports — Narration, Conversational, Promo, or Character". Of the 205 voices listed, 109 are tagged "(Partner)" instead — every Arabic, Chinese, Czech, Danish, Dutch, Italian, Japanese, Korean, Persian, Polish, Portuguese, Swedish and Turkish voice, plus most Spanish, French and German ones. Partner is a voice model, not a style: Creating Audio at Different Sample Rates says "Standard and Partner voices always render at 24 kHz", and Exploring Languages, Accents, and Styles says "Voices are organized into four speaking styles" with no Partner among them. Someone looking for a Conversational Spanish voice can't tell from this list which Spanish voices offer one.
The pricing page dropped WAV and OGG downloads from the Pro plan this week, but the getting-started guide still tells everyone to pick .mp3, .wav, or .ogg
The pricing page's Export formats row now reads "MP3MP3MP3, TXTMP3, WAV, OGG, TXTMP3, WAV, OGG, TXT" across Trial, Starter, Pro, Business and Enterprise — the Pro column changed from "MP3, WAV, OGG, TXT" to "MP3, TXT" this week. This guide, rewritten on 2026-07-25, still says "Choose a file format: .mp3, .wav, or .ogg." with no plan condition, and Downloading Sections and Projects says "OGG and WAV are available on Business and Enterprise plans; MP3 is available on all plans." A Pro subscriber following the getting-started steps will look for a .wav option that their plan no longer offers.
The new caption article says captions come in two formats, then offers three — and the pricing page lists only SRT and VTT
This article, republished on 2026-07-27, opens with "Captions are available in two formats depending on where you plan to use them" and a "SRT vs. VTT" section, but the download steps then say "Select an option: SRT, VTT, or TXT." Two other articles updated this week agree there are three — Getting Started with WellSaid Studio offers "caption files (.srt, .vtt, .txt)" and Creating Audio at Different Sample Rates refers to "downloading captions (SRT, VTT, TXT)". The pricing page's comparison table still lists "Caption file downloads .SRT, .VTT" for every paid plan, so a customer checking what their plan includes gets a different answer than the help article gives them.
The rewritten Respellings article still sends readers to a "Pronunciation Library" while using the newer Replacements wording in the same steps
This article was rewritten again this week (1,167 to 584 words, updated 2026-07-28) and still mixes the two names. It says "Respellings are created inside the Replacements panel" and "Click on + New replacement in the Smart Toolbar", then "Saved respellings go to your Pronunciation Library", "Save the entry to your Pronunciation Library" and "re-save it in the Pronunciation Library". The Guide to Replacements, updated the same week, tells readers to "Open Libraries in the left navigation" — so two freshly-updated articles name the same place differently. A reader following these steps looks for a "Pronunciation Library" that isn't labelled that way in the product.
API free-trial length is stated two different ways: the Help Center says 14 days, the product website says 7 days
This Help Center article (updated June 29) says 'Enjoy a 14-day trial period to explore and test our API capabilities.' The public API page at wellsaid.io/text-to-speech-api says 'Signing up for an API trial is free and easy. You'll have 7 days to try out all of our features.' Both describe the same API trial, so a developer comparing the two can't tell whether it's 7 or 14 days.
Support article promises chat replies 'within 1 hour', but the pricing page says Business chat is a 4-hour SLA (only Enterprise/Priority is 1 hour)
This Help Center article (updated 2026-07-06, changed this week) lists chat as available for Business and Enterprise customers and, under 'Response and resolution times', states 'Chat: Within 1 hour during open hours.' The pricing page (https://www.wellsaid.io/ai-voice-pricing) instead promises Business 'Email (1 business day SLA) and Live Chat (4 hour SLA during business hours)' and reserves the 1-hour figure for Enterprise: 'Priority Chat (1 hour SLA during business hours)'. A self-service Business customer reading the support article expects a 1-hour chat reply that the pricing SLA doesn't guarantee. Not present in the carried-forward finding set.
Screenshot shows legacy 'MY LIBRARY' page with green 'NEW WORD' button that no longer exists
The library page is now called 'Libraries' and the primary action button to add a replacement is 'New Replacement' (not 'NEW WORD'). Per the terminology rubric, 'PRONUNCIATION' has been renamed to 'Replacements' product-wide.
Article body references navigating to 'Pronunciation from the left menu' but live Studio left-nav now uses 'Libraries' (see right-rail-voices.png reference showing 'Open libraries' and 'New replacement' instead of 'New word'). Related article 39113078033555 text explicitly says 'select New Replacement' when adding from the library, confirming the current button label.
'SEE ALL AVATARS' button -- current UI says 'see all voices'
Current Studio UI labels the link 'see all voices' and the panel copy says 'voices' throughout. 'Avatars' terminology has been fully deprecated.
Corroborated by existing WellSaid Mode B audit: 'Article says See All Avatars -- live UI says see all voices'. Current-app capture confirms no 'Avatar' terminology anywhere in the voice picker or right rail.
Narration says 'voice avatar' -- product renamed to 'voices'
Re-record or caption: 'select the voice from our Voices panel'. WellSaid has deprecated 'avatar' terminology throughout Studio -- individual items are now 'voice cards', not 'avatars'.
Mode B audit (2026-04) and current-app capture both confirm Studio no longer uses 'avatar' anywhere in visible UI. A fossil remains in the voice-variant combobox's aria-label ('Select avatar variant') but that is an accessibility-only drift -- sighted users never see 'avatar'.
'Current / Future BETA' version dropdown has been restructured
The narrator says 'select the current version of Studio' but the Current/Future BETA dropdown was replaced by three radio cards under 'Choose your Studio experience' — 'WellSaid Studio (recommended)', 'Legacy Studio - Standard', 'Legacy Studio - Global'. The 'current' option was demoted to 'Legacy Studio - Standard' (which is what this tutorial actually demonstrates). A viewer following along will not find a 'current version' selector.
Current-app capture: 'New project' modal shows three radio cards -- 'WellSaid Studio' (RECOMMENDED), 'Legacy Studio - Standard', 'Legacy Studio - Global' (with additional language dropdown).
Narration says 'voice library' -- panel renamed to 'Voices'
Re-record or caption: '...from our Voices panel...'. The voice selector dialog is now titled 'Voices' (confirmed in current-app capture).
Corroborated by existing WellSaid drift: 'Article says Voice Library -- dialog is now titled Voices'.
'NEW PROJECT' button renamed to '+ New' + chooser menu
The button is now labeled '+ New' and clicking it opens a chooser menu with three items (Project / Folder / Workspace) before opening the modal. New users watching the tutorial will look for 'NEW PROJECT' and not find it.
Current-app capture of the projects home shows '+ New' button in the top-right; a second capture shows the popover menu with Project/Folder/Workspace options.
Narration says 'enter a client name' -- field renamed to 'Description'
The field is now labelled 'Description (optional)' and the placeholder reads 'Client name, project subtitle, etc.' -- 'client name' is now just one example of what to enter, not the field's purpose. Re-record or caption accordingly.
Current-app capture of the New project modal.
Right rail: 'PRONUNCIATION' section replaced by 'Replacements'
The right rail no longer contains the voice picker or the phonetic pronunciation form. The current rail is titled 'Project > Replacements' with Personal/Team toggles, an 'Open libraries' button, and a 'New replacement' affordance. The pronunciation concept evolved into the broader Replacements + Libraries feature.
Current-app capture of the editor right rail.