Owner admin · Custom Page

Too far still books. You cannot filter who.

Default calendars have no staff fields and no kilometre gauge. Here you set the staff object, km router, and a visual booking funnel: pages you add, delete, reorder; service / availability / therapist cards on whichever page you want first; stats per page. Voice walks this funnel. Live URL and Testing URL: https://app.claudiafix.ai/leona.

Checking this location…

Onboarding — how you work

Leona is built for in-home service businesses. It also customizes booking for any service business. Answer once. The page, the widgets, and voice follow this. Clients log in with a code (SMS or email) so the form is complete — HighLevel has no client login.

Are you an in-home service, or does the client come to you?

In-home — staff drive to the client. Kilometres on the staff object. Too far is not a slot. Location — the client comes to us.

If they come to you: more than one site?

Several locations — client types one postal code. We show closest to furthest, plus a map of your sites. Not HighLevel’s long list they have to scroll. Not the in-home region map. One site only — hide the region / postal page

This location

HighLevel calendars have no staff custom fields. Leona keeps a staff object per staff id: services they take, weekly hours, max km they drive per service, gender, insurance receipts, about. Catalog and pay stay on their Service calendars. Source of proof: Coco if installed, else this object.

Staff object (what HighLevel does not have)

This is not a location list. In-home, the first question is how far each person will drive for this service.

Default max drive km on the staff object (per service — too far is not a slot)

Price per service lives on the staff object Weekly hours on the staff object (Coco portal writes this if Coco is installed) Page uses this location’s brand colours from the API — form and pay stay theirs, just nicer

Booking funnel

This is your funnel — not a HighLevel funnel page. HighLevel funnels give stats on GHL pages. Booking is a session (login → km → person → time must stay together). You build the pages here. Clients walk them as a funnel. Each page is also a widget you can drop on any website. Stats: who saw the page, who continued, who booked. Appointments still land on their calendars.

Move service cards, availability, and therapist cards onto whichever page you want first. Delete a page, turn a card off, or copy an iframe for that page only (team page = therapist cards, landing page = availability).

Where they are

Follows onboarding. In-home uses the km router (staff drive). Several sites: one postal code, closest first, a map — not a scroll list of every location.

In-home — street + city + postal, km from each staff’s object One site — client comes here Several sites — one postal code, closest to furthest, map of your locations

Staff and people

Staff before time Price per staff (starting-at from HighLevel team member price). Spa leaves this off Tandem — two calendars, two linked appointments, same start Sequential — one after the other Add another service with another staff on the same appointment (HighLevel native; Spa does not use this)

People as a category

Number of people filters which service categories they see, and can add a custom price per person. You can also name a category that becomes its own logic step (example: “For 1”, then “Couples”) so the next screen only shows what fits.

Number of people filters service categories + per-person option Category as its own page — filter the catalog first, then services (not one messy list)

Extra category names that become a step (comma-separated)

Staff filters — you name the pages

Each row is one page in the booking. Staff object field is the key on the staff object (gender, language, insuranceReceipts, specialty — whatever you stored). Label clients see is yours: “Woman or man”, “Direct billing”, “Speaks French”. You customize it. Km is the distance router — you still pick the words.

Show closest staff first (do not always pin the same first name) Info toggle on the staff card: about + Google reviews on their name

Form, remember clients, pay

HighLevel has no client login. Contacts already have name, phone, address — they still fill the form every time. Leona remembers them: they get a code by SMS or email, they log in, the form is complete. The form is still their HighLevel form. Pay stays on the calendar.

Remember clients — code by SMS or email, then the form is complete Send the login code by SMS Send the login code by email After login, fill name, phone, address, people from the contact URL can pre-select service, staff, coupon Add-ons and variations on the service (sell more than the base hour)

Too far still books. You cannot filter who.

Onboarding — how you work

This location

Staff object (what HighLevel does not have)

Booking funnel

Where they are

Staff and people

People as a category

Staff filters — you name the pages

Form, remember clients, pay

Languages on every widget

Website widgets

Coupon header

Iframe for a website that is not HighLevel