A 90-second end-to-end restaurant contact-form test covering public submission, confirmation, restaurant-side receipt, named ownership, reply verification and a last-known-good log.
What the film covers
- 1. One success message, four separate facts
- 2. Where a working-looking enquiry route actually breaks
- 3. Make the confirmation honest enough to check later
- 4. Leg one: run the public-device send test
- 5. Leg two: prove receipt where you control the record
- 6. Legs three and four: ownership and the return path
- 7. Re-test on change, not on a hunch
- 8. Keep a receipt log so the next failure has a last-known-good date
Read the full articleRestaurant contact form not working: the send-to-receipt test for lost enquiriesA guest opens your website on a phone, fills in the enquiry form for a party of twenty, taps send and sees a thank-you message. From that moment they believe the restaurant has their request, so they stop chasing. If nothing actually reached you, there is no missed voicemail to find, no unread note to spot and no obvious hole in the diary — the only signal the failure produced was a reassurance shown to the one person who could have raised the alarm. By the time it surfaces the evidence has gone too: nobody can say when the route last worked, which change broke it, or how many enquiries passed through the gap. The GOV.UK Design System is blunt about what that screen does on the restaurant’s behalf. A confirmation page exists to reassure users that they have completed a transaction and help them understand what to expect next. That reassurance is a promise, and it is worth exactly as much as the delivery route standing behind it.