See which reminder channels will actually send

Pressing Send reminder used to offer SMS on nothing more than "this client has a phone number". If your business SMS switch was off, or you were out of credit, the dialog offered it anyway, said "Reminder sent", and nothing left.

The dialog now asks first. A channel that cannot send stays visible but greyed, with the reason on it — no mobile on file, SMS is switched off for your business, not enough credit. Those send you to three completely different places, so none of them is hidden behind silence.

Send by email and text in one press

Channels are multi-select now. Email and SMS is one press, not two, and the boxes start on what can actually send — so the usual case is still a single click.

Every reminder on the booking, with what happened to it

The drawer keeps a history: each reminder, each channel, and its outcome. A send that was blocked says which gate blocked it. Until now "did the customer get the reminder?" had no screen that could answer it.

A second reminder on a different channel now sends

Send by email, then within five minutes send by SMS: the second one used to be swallowed as a duplicate. The screen said "Reminder sent" and the text never left. Picking both in one press was never affected — only two separate presses collided. Fixed.

A reminder that was collapsed as a genuine duplicate now says Duplicate — not resent in the history, instead of showing red as though it had failed.

Rescheduling a booking keeps that booking's own answers

Rescheduling or rebooking looked up the pet's saved profile for its answers. But the answers that belong to a single visit — how the coat was last time, when it was last groomed — are deliberately never saved onto the pet. So every one of them came back blank, and the whole week showed no available times on a booking that had already been paid for.

Both now rebuild from what the booking itself recorded at the time it was priced. Anything you have since changed on the pet — a new size, a new breed — still wins; the booking's own record only fills the gaps.

Quick replies write the name for you

A quick reply was fixed text, so anything that needed a name had to be written generically. Four merge fields now work inside one: {{customerFirstName}}, {{customerName}}, {{businessName}} and {{petNames}}.

They fill in the moment you pick the reply, in the composer, so you read exactly what the client will receive before you press send. A client with two dogs gets both names. Insert the fields from chips in Settings → Quick replies.

Ask the AI receptionist about one groomer

"Is Ava free next week?" could only ever be answered with an offer to call back. The receptionist can now check one person's week and answer it.

Two things it used to get wrong are gone with it. A groomer who had left, or was on leave, was still named to callers as available — then her week came back empty. And a service you had not published could be offered by name. Neither happens now.

An empty week that was narrowed to one person is also reported as that, instead of telling the caller you are fully booked all week when other groomers were free.

Every system email redesigned

All 125 emails Seglo sends have been rebuilt on one set of components. The heavy dark frame that mobile Outlook drew around them is gone at the source, so it is gone everywhere rather than in the clients that honoured the override.

Mail Seglo sends in its own name — credits, payroll, phone number and gateway alerts, the settlement report — now carries a Seglo header instead of borrowing your business identity. The booking request email leads with what happened and the five facts that identify the request, rather than a column of labels.

Fixes

A blocked channel that stayed ticked. Opening Send reminder before the check finished ticked every channel the client could theoretically receive; SMS then rendered greyed, still ticked, and impossible to untick — and Send posted it anyway. The selection is now re-checked against what can send, every time.
A reminder that had been switched off. Turning the reminder off on your notification settings page killed the manual Send reminder action, while the automatic reminder kept sending. The manual action never had to honour that switch.
A stale login on the customer portal. A returning customer whose sign-in had expired landed on a page that could not load, with no way to reach sign-in. They now go to sign-in.
The visit timeline before check-in. A booking with no recorded stage drew an empty bordered box above it. It now shows the four milestones as upcoming.

For your public page

The Seglo Phone pages now list the full feature set and explain private verification codes — the codes your banking and delivery apps text you, and how they reach the right person on a number the whole team shares.

Get Started

Open any booking and press Send reminder. The channels that can send are ticked; anything greyed tells you why. Under it, the history shows every reminder that booking has already produced.

Questions? Reach us at support@seglo.ai, or use the chat on any seglo.ai page.

Last updated: September 5, 2026

See which reminder channels will actually send — and what happened to the ones you sent