Rebooking and Automation

This standard governs rebooking in the customer record system: the groomer's recommendation at checkout, the needs-rebooking worklist, and the capture of abandoned bookings as leads. It applies to groomers, who make the recommendation at the chair, to front desk staff, who enter it before the customer leaves and work the needs-rebooking list, and to managers, who review follow-up practice. The system provides both sides: the human side, the groomer's recommendation, and the system side: who is overdue, who abandoned, and who to contact. Customer contact under this standard shall respect the opt-in and do-not-contact flags on the record, under the Privacy Policy.

Recommend Next Visit: the human side

At checkout, the groomer says "see me in six weeks." That recommendation shall be recorded so it survives the conversation, using the Recommend Next Visit action on the customer's grooming history. The action records the pet, a recommended date in strict year-month-day format: any other format is refused: and a reason, and creates a rebooking recommendation with status open.

Staff shall build the habit at the chair, not at the desk. The groomer knows the coat, the interval, and the customer; "six weeks" from the groomer carries weight a system reminder does not. The desk's duty is to ensure the recommendation is entered before the customer leaves, because a recommendation that lives only in conversation is gone by the parking lot.

The service record backs this up: each service carries a default rebooking interval in days. When the groomer does not specify, the default is the starting point: but the groomer's judgment prevails over it. A matted dog does not get the standard interval for its breed's usual groom.

The needs-rebooking list: the system side

The needs-rebooking list is the win-back worklist: one row per customer, showing last visit, next appointment, average visit frequency in days, and lifecycle stage. Read it as: people whose average frequency says they should have been back by now, and who have no next appointment. This is the list to work when the book has gaps; every call is to someone the data says is overdue, not a cold call.

Pair it with the lifecycle stages in Customer Lifecycle: at risk with no next appointment is the urgent list; lapsed is the warm list; lost is the "win-back offer or release" list. Pair it also with open rebooking recommendations: a customer with an open recommendation whose date has passed calls for a specific, personal follow-up: naming the pet, the service, and the date it was due: which converts better than any general "we miss you" message.

Abandoned bookings: the leads that almost were

Not every booking completes. When a booking is abandoned with the deposit paid, it is resolved through the deposit machinery: fee application, refund, or customer credit: under the accounting standards. When it is abandoned with the deposit not paid, there is no money to resolve, but there is a person: name, email, pet, and the service and slot they wanted. The abandoned-booking capture moves that person into the customer record system instead of letting the lead die with the session.

The capture rules are strict, because they protect against the two classic failures of lead capture: duplicates and consent violations

• One record per email, without exception. A second abandonment by the same person enriches the existing record; it never creates another. The system already carries duplicates from before this rule; the capture does not add to them. Duplicate handling is governed by Data Management.
• The existing record is enriched, never downgraded. The abandonment context is recorded as a system note naming the originating booking: what service was wanted, for which pet, on what date and time, and that the record's communication preferences shall be honored. The lifecycle stage is never moved backward, and communication preferences are never overridden. The note is written once per booking; a check on the booking reference prevents duplicates.
• New leads start at new lead, with lead source Website where it can be determined. Every sending path checks the record's opt-in flags before sending; capture never opts anyone in.

The follow-up track for these leads is deliberately soft and occasional; the note on the record says so. One abandoned booking is not consent for a repeated campaign. A single well-timed "still interested in that slot?" is the standard, and the opt-in flags govern absolutely.

What automation means today

The scope shall be stated honestly, because the word is easily oversold. The system has the detection side: the needs-rebooking list, funnel events, abandoned-lead capture, and lifecycle scoring: and the sending channel, through communications and email, including the appointment reminder sends. It does not yet have a campaign administration side: no campaign membership records, no send scheduling, and no automation run history. Today's automation is therefore this: the system surfaces who to contact and why, and a person: or a simple reminder job: sends the message.

That means the rebooking habit is still a human habit, and this standard is written accordingly. Staff shall work the needs-rebooking list weekly, enter the groomer's recommendation at every checkout, and treat an abandoned booking as a lead, not a loss. When campaign administration is built, the habits are what will make it effective.

Controls

• No customer shall be contacted under this standard in breach of the opt-in, do-not-call, or do-not-contact flags on their record.
• A rebooking recommendation shall be entered before the customer leaves, or not presented later as if it had been made at checkout.
• An abandoned-booking lead shall receive soft, occasional follow-up only. Repeated automated nudges to such a lead are prohibited.

Records

Each recommendation creates a rebooking recommendation record with status open, the pet, the recommended date, and the reason. Abandoned-booking capture creates or enriches a customer record at new lead stage and writes a system note naming the originating booking. The needs-rebooking list is derived from visit and appointment records and creates no record of its own. These records are kept in the customer record system.

Escalation and review

Managers review open recommendations whose dates have passed, abandoned-lead follow-up, and any contact made against a record's flags. A rebooking fault that the store cannot resolve shall be reported to support@aapawz.com. Legal process concerning a customer record or a contact-preference complaint shall be directed to legal@aapawz.com.