Dog boarding booking form: why requests stall

A boarding request is a promise to reply, so the form has to reach the send button. Owners plan trips at night on a phone, often with the vaccine certificate sitting in an email app. An upload field that does not open the phone's files, or opens them but rejects the file type, ends the request there. Two date pickers that accept a check-out before the check-in, with the error shown only after the last field, read as a broken form. The owner then sends a message to the number on the site, or books somewhere else.

• Can an owner reach the send button without scrolling past a long list of required fields?
• Does the vaccination upload open the phone's files app and accept a PDF from email?
• Does the check-out date refuse any day earlier than the check-in date?
• Does the weight field name its unit, and accept the unit the owner knows?
• After sending, does the page say what happens next and when a reply comes?

Think about what the owner must know to say yes or no. The dates, the dog's size, the vaccination status and any medication decide a yes. The form often asks for much more: a full feeding routine, a vet's phone number, a photo of the dog, a list of past boarding stays, a waiver with a signature box. Some of that matters after a yes, and it can wait for the confirmation step. Every question before the send button is one the owner must answer on a phone. Move the rest after the request is sent, and say that it is coming.

The upload is the most common place a boarding request dies, because it depends on the phone. A file picker may show photos but hide the PDFs that arrive by email, so the owner has to save the certificate to a cloud app first, and many will not bother. Some pickers accept one file type only, and a photo of a certificate saved in a format the picker does not read can be rejected with a message that never names the problem. Test it the way a pet owner would: on your own phone, with a PDF saved from an email. If the upload fails there, it fails for every owner who does not have a laptop nearby.

Two date pickers feel simple until the check-out field accepts a day before the check-in. Some forms let the owner pick a date in the past, or a stay longer than the kennel takes. The error then appears only after the owner has filled the last field and pressed send, so the request looks sent when it was not. The owner sees a red line under a date and no explanation in plain words. Check the rule on the same screen as the date, and show the limit before the owner picks a day that cannot work.

A sent request is only half the job. The owner is handing you a dog, and they need to know the kennel has the request and what happens next. A visitor in a test has an inbox, so the confirmation email to the visitor shows whether the page sent one. Whether your own inbox or booking tool received the request is a separate check, and the test does not read either one. If the page does not say when a reply comes, an owner who gets no word will send the same request to the next kennel on the list.

The first run finds the field that stops the request. The fix changes it: an optional record, a file picker that opens the phone's files, dates checked on the same screen. Run the same owner again and see whether they reach the send button and a confirmation. Run it again after you change the vaccination rule, add a boarding package or move the form to a new page, since any of those can bring the upload back.