One booking request per visit, not one per pet

A customer booking two dogs used to arrive as two requests and two notifications, and you had to accept each one separately without any sign they belonged together.

One row, every pet on it

A multi-pet request is now a single row with the pets named inline and a 2 pets chip. Accept or Decline acts on the whole visit in one press. The sidebar count and the dashboard banner count visits, so the number you see is the number of decisions you have to make.

Decline says declined, not cancelled

There was no Decline button on desktop at all, and the one on mobile ran the cancel path — so a customer whose request you turned down was told their appointment had been cancelled. Declining is now its own action on both, and the customer is told their request was declined. The reason you type stays internal; the customer never sees it.

Requests that run out of time get their own wording too, instead of being described as cancelled. Neither declined nor expired requests count towards your cancellation rate in Reports any more.

The request email stops asking the customer to confirm

A request waiting on your approval used to email the customer "Please confirm your booking" with a Confirm button that did nothing when pressed — they had nothing to confirm. The email and text now read "Booking request received … we'll be in touch shortly", with a button that opens the request. In-app and push already said this; all four now match.

Assigned staff also start receiving booking notifications — that routing had been going nowhere.

Choose which booking questions must be answered

Every question on your profile form was optional, with no control to change it. Open Clients → Profile fields and use a question's menu to Require an answer. Required questions show a Must be answered tag next to the label, on your preview and on the customer's form.

A blank answer no longer counts as an answer

A required question a customer skipped once dropped off the list permanently and never came back — the form recorded that the question had been shown, not that it had been answered. Unanswered means outstanding now, until it's answered. And a question with no price attached that hasn't been answered comes back in the Optional section rather than disappearing.

Picking an existing pet stops skipping the questions

Choosing a pet you already had on file sent the customer straight to Review, past any question you'd marked required. And when there is genuinely nothing to ask, the customer no longer stops at an empty details step to press Continue on a blank page.

Customers keep their own name

Anyone booking through the public page could end up saved as Guest Customer. The record was created at the pet step, before the funnel asks for a name, and the real name typed a moment later was never written back.

Names are now written once, with the real name, when the booking is placed. An existing customer still showing a placeholder name is corrected automatically the next time they book — a name you typed yourself is never overwritten.

Pets draw their own breed

Every pet on the schedule, the front desk board and the booking page fell back to the same generic dog illustration. The illustration was only reading the platform's own breed list, and every real shop stores breeds against its own question — so it never matched. Pets now show the breed you have on file for them, on every screen.

Say what your shop is good at

Add specialties on Settings → Profile: up to five tags from a grooming list, shown as chips on your public booking page and included in what search engines read about you.

Adding none shows nothing at all — no chip row, nothing published. A specialty says what you do well; it is deliberately not a list of what you accept, which is why there are no breed tags.

A booking confirmation email that leads with the confirmation

The subject line now says what happened — "Confirmed: Full Groom at Happy Paws" — instead of a generic heading, and the service, date and time sit together where they can be read at a glance. The design matches your booking page rather than the old cream template, and the button goes straight to the booking.

Notification buttons open the app

The button in a business notification email used to guess at send time which device would open it. It now decides when you press it: on a phone with the app installed it opens the app on the right screen, on a phone without it the mobile site, and on a computer the full page.

Two of those emails had been sending you to the customer's own booking link instead of your schedule, and four phone-line emails pointed at a fixed address that ignored where you actually were.

Fixes

Incoming calls that never rang. Calls to a number set up on the older phone path were looked up against a table that had nothing in it, so nobody's phone rang and the call dropped through to the AI receptionist or voicemail without a word.
Change pet on the public booking page. Swapping the pet changed the name but left the previous pet's answers, breed and price in place — so the booking was priced for the wrong dog. The button is gone; remove the pet and add the right one, which re-asks the questions the way a correct swap always had to.
"More about {name}" on the pet details page. The heading printed the placeholder instead of the pet's name, and a Cantonese customer booking more than one pet fell back to English. It now reads "About Lulu".
A pending booking pretending to be confirmed. It shows its real progress — Sent, then Waiting, then Notification — instead of the confirmed styling.
Calendar cards cutting off text. Fifteen-minute slots clipped the bottom of the wording.
Standing notes read as a diary. They now read as instructions to follow on every visit, which is what they are for.
The booking page on a small screen. The summary, estimate card, answered details and question drawer were laid out for a wide screen.

Get Started

Open Bookings → Requests — a multi-pet request is one row now, with Accept and Decline acting on the whole visit.

Then open Clients → Profile fields and mark the questions you actually need answered before a booking goes ahead.

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

Last updated: September 4, 2026

One booking request per visit, not one per pet