Toast notification UX: how 30 SaaS products confirm a change

By Screenrove editorial · 22 October 2026

Toast notification UX across 30 SaaS products: where 16 put the toast, the one with Undo, silent saves, status pickers and Canny's notify-voters prompt.

We caught 16 products showing a toast after a change inside a record or on a settings page, and only one of them, Evernote, put an Undo button in it. Nine of the 16 put the toast in the bottom-right corner, two still open with a generic "Success!", and six other products confirm a change with no toast at all. That is how toast notification UX looks across the detail views and settings pages we captured this autumn.

Below: status pickers, toasts, settings save states, and the status change that emails your users. 30 products, all linked.

Status pickers: four ways to show the same few words

Status is the field people change most in a task detail, and its picker is the first feedback you get. Four products, four answers.

• Softr renders each option as its coloured chip, TO DO blue, IN PROGRESS yellow, IN REVIEW amber, DONE green, under a plain "None". The chip in the closed field matches the chip in the list.
• Smartsheet lists five plain words (Not Started, In Progress, In Review, Blocked, Complete) with a blue tick on the current one, and outlines the whole Details column in blue while the field is open (see the screen).
• Superlist does the same job for priority with three rows: coloured bar icons for red High, violet Medium and blue Low, each with a keyboard hint from 1 to 3. Until you pick, Priority is a dashed pill, so the empty field reads as an invitation.
• Jira takes status out of the field list entirely. It is a blue "In Progress" button in the header, beside the sparkle "Improve Story", above a Details panel of 10 fields (see the screen). Its menu lists only the three states you can move to, as lozenges, followed by Add status, Edit status and View workflow (see the menu).

Softr and Superlist teach state through colour that repeats on every board. Smartsheet relies on words and a tick. Jira relies on placement, and its menu leaves out the current state, so every row is a real move. Only Superlist adds keyboard hints.

Toast notification UX inside a record

Nine detail-view screens from eight products confirmed a change with a toast:

Seven of the eight name the object that changed. Plane leads with "Success!", then repeats itself, while the new comment already tops the timeline stamped "0s".

The best toasts arrive with a visible change on the page. In Sentry, "Issue resolved" lands as Resolve becomes a green-tick "Resolved" label and an outlined "Unresolve". In Sanity, the pill above the name flips from green Public to yellow Private. The toast is the receipt; the page is the proof.

Two toasts do more than confirm. Tana explains scope: "References in other workspaces are still there." Evernote names the deleted note, links Trash and offers Undo while the next note opens.

Some screens skip the toast. Favouriting in Recraft just fills the heart white; Dribbble tints its like and save buttons pink; Glide simply shows the saved text. For a small, reversible toggle, the button state is the confirmation.

How settings pages confirm a save

Settings are where products disagree most. We found seven save models:

1. Instant switch, instant toast. Fillout has no Save button under Form behavior: flipping Auto-jump pops "Settings updated" in the bottom-right corner. Cap does the same at top centre but restates the result: "New recordings will start private".
2. Button plus toast. Gumroad drops a mint "Changes saved!" at top centre as "Update profile" fades to a disabled pink. Maze ("Changes saved", top right), Lucidchart ("Your changes have been saved.", bottom left), ElevenLabs ("Name updated", bottom right) and Gamma ("Success!" over "Workspace updated successfully.", top centre) do the same. Gamma's "SW" initials logo had not caught up with the new name.
3. Buttons that wake up. Kittl's "Save Settings" sits pale grey while nothing has changed, and on the team page "Save changes" is solid black once the name differs (see it). Runway's Confirm turns the same electric blue as its Upgrade button, then greys out again beside a "Changes saved" toast (after).
4. Save inside the field. GitBook puts a dark "Save ↵" chip inside the Display name input. Saving it empty produced the rawest message we saw: "\"body.title\": expected at least 2 characters", an API field name, with no error on the field.
5. Dirty-state footer. Descript shows a sticky dark "Update" footer only after you edit (before). On save it vanishes without a toast, and the new drive name appears in the modal's nav heading and in the sidebar switcher (after). Lovable pairs an "Unsaved changes" pill with Cancel and Update, and flags an empty name inline: "Workspace name is required", "0 / 50 characters".
6. Save on blur. Voiceflow's Agent info card has no button and showed no toast; after a rename, the switcher at the top of the sidebar already showed the new name.
7. Confirm in copy. Jitter lets a sentence do it: the "Your plan" line names the renamed workspace in bold.

One setting is about toasts themselves. Checkly's Configuration page has a "Notifications timeout" slider from 5 s to 20 s, with "10 s (default)" marked, explaining that it sets how long "notification toasts will remain visible before automatically disappearing". It is the only toast-duration control we spotted.

Status changes that should reach other people

Canny treats a status change as news. Setting an idea's Status to a blue "Planned" pill opens an email composer right in the details rail: the subject is already filled with the idea's title, the body says "Write email message", "Send email" is greyed out, and an "Include voters" checkbox sits underneath, unticked. Below that, Canny notices the public side has not moved: "Portal status is set to Open", with Skip or Go to Portal view.

In Portal view, a status note ("Scheduled for the November release of the library.") gets its own Save button and two checkboxes, "Notify voters" and "Notify users tracked internally", both unticked in our capture. Worth copying: the offer to notify appears at the moment of change, inside the record. And Canny keeps internal and public status apart and flags when they disagree, so Planned internally is not a promise to customers by accident. The cost of opt-in is that silence is the default.

What to steal

• Name the object in the toast. "Feature flag saved" and "Project renamed" tell you what happened; "Success!" makes you check.
• Change the page first, toast second. Sentry's Resolved label and Sanity's Private pill are the real confirmation; the toast is the receipt.
• Put Undo on anything destructive. One of 16 toasts did. A named object plus Undo, as in Evernote, beats a confirmation dialog for reversible deletes.
• Skip the toast for small toggles. A filled heart is enough, as Recraft and Dribbble show.
• Pick one save model per page and make it visible. Instant switches, waking buttons or a dirty footer all work.
• Translate validation errors. Never show users an API key like "body.title". Put the message on the field, as Lovable does.
• Make status pickers teach. Reuse the status colour everywhere and add number keys.
• Offer to notify people at the moment of a status change. Canny's inline composer is the pattern for anything customers wait on.

How we counted

All screens were captured in desktop browsers with research accounts between September and October 2026. A vision model recorded each screen's attributes, and each one can be checked on its screen page; we then opened every screenshot cited here and checked the copy by eye. A toast counts only if it was on screen when we took the screenshot, so a product whose toast had already faded, or appeared later, may count as silent. Positions are relative to the full browser window. We capture what we saw, not A/B test results, so none of this says which approach converts or retains better.

Browse the full detail views with comments and activity, or the notification settings we captured. To pull these references into your editor, connect the Screenrove MCP server and ask your agent for toasts, status pickers or save states from the products above.