When the visitor is asking you to do something—not merely to chat—you need type, timing, and details. A generic request form helps US and UK sites stop funneling every ask into a single ‘message’ box.
Owned by the coordinator, not a shared hello@.
After copy, make the select match reality.
Link it from every ‘how to ask us’ paragraph.
So repeat asks are visible.
People search ‘request form’ when they need a blank that can mean access, a callback, a document, or a visit. The request pack already has type, preferred date, and details. That is the whole point: the row looks like work, not like a guestbook.
If you already know the ask is a demo, a refund, or a sample, use those specific generators so labels match. This page is the fallback when the programme is unique.
Date-less requests sit at the bottom of the pile because nobody knows when they matter.
Rename the select options after copy to match your real work: access, document, visit, other.
ServiceNow is a destination. HTML is how small teams start.
One URL you can print on a poster.
Jira Service Management and similar once you have SLAs. Feed them from this form at first.
Unstructured. You will re-ask the date.
Still real in US and UK offices. Offer this as the default.
Internal microsites are often static on purpose. Put the form live, restrict the domain, and export CSV for the coordinator.
Mention ZIP or postcode in details only when the request is on-site. Do not require it for a document ask.
Contact is a message. A request includes type and a date because you will do work.
Not built in. A human reads the row.
URL or file field after copy.
Write it on the page. The form will not enforce it.