Service requests
A service request form for an electrical, plumbing or handyman website and the table its responses land in. The form asks a visitor for their name, email, phone, the service address, how urgent the job is, the problem and a preferred time, and every answer becomes one request you follow from new to scheduled to done, with emergencies routed to their own staff.
Use it when
Use it when a trade business wants its website to take service calls, not just messages, and needs to know at a glance which ones cannot wait. It fits a business that books most jobs from the form and a phone call, and that has someone on call for emergencies. Add it from the site editor's Forms panel or the sidebar's Add; it creates a new Service requests table for the responses, or writes into one you already have when that table holds the same fields.
Use something else when
A business that prices jobs from a description and a size, such as pressure washing, wants the pressure washing quote form: that one asks what and how big, not how soon. A form for general questions is the Contact enquiries form. A business that wants visitors to pick an actual appointment slot is asking for Schedule, not this form: the preferred time here is a wish the business reads.
What it adds or changes
- Website: Service request form
- App: Service requests
Form and responses together · publish your site separately
It brings these with it:
Settings
| Setting | What it does | Default |
|---|---|---|
| Form name | The form's title as visitors see it; every other line of wording is reworded later from the form's settings. | Request service |
| Response workspace | Where responses are kept: a new Service requests table made by this preset's table preset, or an existing table of this business that holds the form's fields. |
How it works
It runs its own built-in automation, called Service requests. Tell staff about a new response: read a new response, choose the staff destinations and email its full details. Empty recipient groups send nobody.
Example
Harbour Electrical, a fictional business, adds Service requests to a draft. A visitor picks both access details and photos, describes the side gate and attaches a photo of the fault. Deselecting photos clears that file selection; leaving access details selected still requires its answer. The office may also add a Store-backed multi-service question without copying its price list. The request is saved as new, with no purchase or appointment implied. Nothing is published or seeded into a live business by this example.
Limits
A visitor picks one urgency and types a preferred time in their own words; nothing books a slot or confirms a time. Photos are available only when the visitor selects I can share photos; then up to six photos (JPEG, PNG, WebP or HEIC, 10 MiB each) can be sent with the request, landing in the business's Drive and showing in Photos, while hidden answers and uploads are refused. The visitor gets no confirmation email; the business reads the request in Service requests and calls back. Staff notices leave only once the table's notification settings name who gets them and a sender is approved. Existing forms and tables keep their wording, fields and views; adding this preset over an existing workspace adds the form without rewriting them. A condition can refer only to an earlier public field in the response table's column order, so an existing workspace must place Anything else to share? before Access details and Photos.
Related
- Service requests: Service calls with an urgency, from new to scheduled to done