Separate owner and provider journeys

Clear before the request. Visible through completion.

Explore the planned journey: owners compare care fit and request a provider; independent providers decide whether to accept.

Workflow preview · live bookings are not open
Care workflow showing staff check-in, feeding completion, a photo update, and an owner message

Illustrated care workflow; actual updates require an authorized visit and connected services. Open full-size care artwork

01

Search and compare

Location, dates, service, pet needs, home environment, actual availability, capacity, full pricing, policies, and dated trust signals.

02

Request and confirm

The intended booking flow includes private messages, a meet-and-greet, a clear price and provider acceptance. A request is not a confirmed booking; live payment and booking services are not open.

03

Follow and rebook

Explore care updates, report cards, task records and support. Actual records require an eligible booking and authorized participants. Reviews become available only after qualifying care.

Interactive experience map

Follow one side of the booking.

Explore the intended states and control boundaries. This explains the product model; it is not a live booking or account flow.

Owner journey · Search

Describe the care—not just the city.

Enter location, service, dates, pets, care needs, environment preferences, and whether you want a meet-and-greet.

Who controls it
The owner defines the request and can change or stop it.
What stays visible
Only eligible supply with current availability, capacity, complete price, policies, and dated trust signals.
Next clear action
Compare up to three qualified options or keep searching.

Interactive booking-state contract

A request is not a confirmation.

Follow only permitted next states, including distinct cancellation, payment, service-failure, safety, dispute, refund, and payout paths.

Workflow simulator · no booking or payment created
Current state

Draft

Owner prepares pets, dates, service, needs, environment, and policies.

Capacity action
No capacity hold
Price history
Every accepted change creates a versioned snapshot; earlier versions remain auditable.
Status evidence
Actor, reason, timestamp, and idempotency key belong to each transition.
Allowed next states
After confirmationSee how the privacy-first care session works.
Explore Active Care