Pet sitter website design: meet and greet first

A pet owner with a trip coming up does not want a sitter they have never seen. They want to know who will open the door, whether the dog settles in a stranger's home, and what happens when the dog gets anxious. A site that opens on a calendar of sittings answers none of that. The owner picks a date, fills in the pet profile, uploads vaccine papers, and only then learns that the first step is a meeting with no open slot for two weeks. Some leave at the upload. Others book a sitting because it was the only thing they could pick, and the meeting never happens.

• Does a meet and greet slot appear in the first calendar, not hidden behind a sitting?
• Does the postcode check run before the pet profile, so a far address stops early?
• Does the vaccine upload accept a phone photo, including HEIC and JPG files?
• Does the error text name the file types and size the form accepts?
• Does a booked meeting send a confirmation to the owner's own email address?

Start from the sitter's homepage on a phone, the way a local owner would. The button most sites show first is Book a Sitting, because that is what the sitter sells. A meet and greet is a short visit to the house before the first stay, and on many sites it lives in a second menu or in a line of small print. The owner taps the big button, picks a date that fits the trip, and only later finds that the first thing they need is a meeting. If the calendar offers sitting dates before any meet and greet slot, the owner has committed to a stay they never agreed to.

A service area check is cheap to build and costly to get wrong when it runs late. Some sitter sites ask for the pet's name, breed, age, feeding notes and medication before they ask where the owner lives. An owner who lives just past your usual radius fills in every screen and is then told the address is outside the area. That is an order problem, not a form problem, and it sends the owner elsewhere with no explanation. Test it on purpose: enter a postcode you do not cover on the first screen, then again on the last one. If the refusal only appears on the last screen, move the postcode field to the start.

The vaccine record is the step most owners cannot finish on the spot. The record is a PDF on a laptop, or a photo on a phone that was never sent to anyone. Phone photos can be saved as HEIC, a format some upload fields reject. If the field shows only a generic invalid file message, the owner cannot tell whether the problem is the file type, the size or the name, so they close the tab. Upload a phone photo of a vaccine card yourself and read the error. Then check whether the form names the accepted file types before the upload, and whether it keeps the rest of the owner's details when the upload fails.

How a signup flow test works

The first run finds the screen where the owner stopped. The fix might be a reordered calendar, a postcode field moved up, or an upload that accepts photos. Run the same owner with the same dog again to see whether a meet and greet slot now appears. Repeat it when you add a cat or exotic service, when your calendar syncs with another tool, and before you point a new local ad at the booking page.