Forms, intake, and acknowledgments
A useful form collects the information that changes a quote, schedule, or visit. Build the questions in Forms, test them in Preview, and connect the published form to the appropriate offering or workflow when it is ready.
The example Plumbing visit intake collects a drain problem, service address, photo, access requests, and acknowledgment. A second sample demonstrates a typed signature. Both were saved as local drafts and reopened; neither was published or submitted as a customer response.
Work Order Forms
- Open Forms → Create New Form.
- Give the form a specific name and a short description of why the questions matter.
- Click a field in the palette to add it, or drag it to the intended position.
- Select the field on the canvas to edit its properties.
- Reorder the questions with the field controls or drag handles. Use Section / Page Break when the intake needs several steps.
- Choose Preview and complete a realistic example before publishing.
| Example question | Field |
|---|---|
| What needs attention? | Text Area, required |
| Where is the visit? | Location Input |
| Photos of the issue | File Upload, images only, up to three files |
| Access and special requests | Text Area |
| Before we visit | Statement / Legal Text |
| Confirm the intake details | Initials, required |
Drafts and publication
Changes auto-save as a local draft for the selected SRVZr profile in that browser. Return to Forms and reopen the draft with Edit to verify its fields. A local draft is not the published cloud version and should not be treated as a backup on another device.
The editor's cloud Save action publishes a new form; an existing cloud form can show Update. Review first: this is separate from the local auto-save. An unpublished draft can appear as DRAFT, and edits to an existing cloud form can appear as local modifications.
Publishing a form also does not automatically connect it to every service, rental, or event. Select it in the relevant intake/registration configuration, then test that customer journey separately. See Flow Builder and Build a useful intake form.
Custom Form Fields
Select a field and use General for its Header, Sub Header, and Placeholder Text. Visibility controls determine whether its headings/help text are displayed. Use a concise question for the header and put an example or instruction in the appropriate helper text.
The palette includes text, email, number, phone, text area, dropdown, radio, checkbox, and condition-grid inputs. Sections, groups, and repeating tables organize questions; special blocks support files, dates/times, locations, measurements, maps, and other workflow inputs.
Require only necessary answers
Open the field's Logic tab and turn on Required Field for information the next step cannot proceed without.

Smart Logic can make fields respond to other answers. Preview both branches when adding a condition; a screenshot of the configuration alone does not show that every branch behaves correctly. The verified example uses required fields without a conditional branch.
Give workflow variables meaningful names
Open Variables, set Variable Name, and select the data type appropriate to the value. The issue description uses issue_description with Information (Text).

Keep variable names stable once other work uses them. A question's visible wording and its workflow variable serve different purposes; changing a label should not make a connected template depend on guessing the new name.
Address Collection
Add Location Input, give it a clear header, and tell the customer which address you need. In Preview, search for the address and choose the matching suggestion. Check the selected address and map before continuing.

The example uses a single location. Location properties also expose multiple-location and map presentation options where supported. Use a more specialized map, route, or precise-location block when the work actually needs that information.
An address field helps collect the site; selecting an address does not itself book a technician or verify that the business serves it. Check service coverage and the connected workflow separately.
Photo Uploads
Use File Upload for a customer-selected image. An Image content block displays an image in the form; it serves a different purpose from collecting a photo from the respondent.
- Add File Upload and explain what the photo should show.
- Under General → File Upload Settings, select the allowed file types.
- Set the maximum size per file, maximum number of files, and grid/list presentation.
- In Preview, choose a permitted sample image and confirm its thumbnail.
- Try a disallowed file and check the rejection before publishing.

The populated preview above shows one selected sample photo and 1 of 3 files. The component also checks file count and size; unreadable or unsupported files produce an error instead of a successful selection.
Store as Base64 is a separate configuration option. The example left it off. Selecting a file and seeing its thumbnail proves local preview behavior; it does not prove the attachment was uploaded to its final storage destination or persisted with a customer submission. Test the connected submission path before relying on it for job evidence.
Special Requests
Add a Text Area for details that do not fit a fixed choice: access instructions, preparation, parking, or constraints on the visit. Keep the prompt specific enough for the customer to know what is useful.

Use a structured choice instead when an answer must drive pricing or a fixed workflow branch. A free-text request should be reviewed with the quote and schedule; it does not automatically change the scope or promise the requested time.
Contracts
Combine Statement / Legal Text with Initials or Signature when the workflow needs the respondent to acknowledge specific wording.
Present the terms
Add Statement / Legal Text, edit the content, and choose the presentation style. Legal (boxed, scrollable) is available for a longer statement. The editor supports inserting form values into statements; verify the resulting wording in Preview before using it.
In the intake example, the statement says the form requests an estimate and extra work requires approval. Its Initials block has its own acknowledgment sentence, maximum letter count, timestamp option, and required setting. The preview shows fictional initials AT beside that sentence.
Preview a signature
Add Signature and use its properties for the intended number of signatures and timestamp display. In Preview, draw in the pad or choose Type → enter name → Use. Clear the signature if you need to try again.

Initials capture the acknowledgment wording and time when entered; the signature block captures the signature representation and can include a timestamp. These controls collect input. This walkthrough does not establish customer identity, delivery, acceptance of a published document, or the legal effect of a particular agreement.
Check the whole form
Use the Preview Mobile, Tablet, and Desktop controls to review the intended presentation. Fill ordinary answers, omit a required answer, select an allowed photo, try an unsupported file, and check the selected location. Preview's Submit Form does not create a live customer submission.
After publishing, repeat the test through the actual connected offering. Confirm where the submitted values and attachments land and which work-order details they populate. Keep a local draft, a published form, a connected flow, and a saved customer submission as separate checkpoints.
Troubleshooting
- The form still says DRAFT: check whether you only auto-saved locally or completed the cloud publish action.
- Another device has an older version: local changes are browser-specific until published.
- A heading or helper text is missing: inspect its visibility control in General.
- A photo is rejected: check allowed types, per-file size, file count, and whether the file can be read.
- The preview resets after reopening: preview answers are test input; reopen the draft to verify its question configuration separately.
- The offering shows a different form: inspect the form selected by that offering and the published version it uses.