Set it up in Workspace settings#
Open Workspace settings -> Request form. The page is organized into:
- Publish for the token, live link, and publish toggle
- Fields for the title, button text, description, success title, and success message
- Brand for theme, logo, and palette
- Embed / API for the iframe snippet, API guide, and API keys link
The operating subtype, setup template, and default operating view you choose during workspace setup also affect how intake is framed inside the workspace after the request arrives.
What the public form collects#
The current website form asks for:
- Name
- Phone
- What do you need done?
- Details
- any extra setup-template questions your workspace adds
- availability windows
- availability notes
The customer must provide at least one contact method and either a complete availability window or availability notes.
Each submit attempt carries a browser-generated submission key. If the network drops after Zelio accepts the request, retrying or reloading the form in the same browser tab returns the same Work Item instead of creating a duplicate. The browser clears the attempt key after the intake flow finishes. Zelio creates or reuses the matching Customer record and stores email and phone values through the protected Customer contact store; Work Item party references use the Customer ID rather than a raw email address or phone number.
Choose how to publish it#
| Option | Best for |
|---|---|
| direct link | quickest launch |
| iframe embed | keeping visitors on your site |
| custom build with API keys | a site flow the standard form cannot cover |
Copy the iframe snippet from Workspace settings without changing its Zelio
path. Zelio permits framing only on the published /request route, and the
website that embeds it must use HTTPS. Other Zelio pages stay blocked from
third-party frames. Use the direct link when the customer website cannot serve
HTTPS.
Test these before you publish#
- the live link opens the right workspace form
- the brand colors and logo look right
- the success screen says what should happen next
- the extra questions are actually useful to the team
- a real test submission lands in the workspace
Decide who owns follow-up#
Once the form is live, make sure someone owns:
- checking new requests in Activity
- contacting the customer when details are missing
- routing the request into Documents, Work, Employees, or Accounting when needed