SimpliServDocs

Build and publish forms

Create forms with fields, layout, validation, conditions, mappings, templates and embedding

→ Open forms

The form builder creates public forms for your website, a QR code or a direct link. A form consists of fields, form settings and design. Every save creates a new version; only the version you set live is publicly visible.

Viewing forms requires Forms → View, creating Forms → Create, editing and publishing Forms → Edit, deleting Forms → Delete. The editor is on its own full-screen page at /dashboard/forms/[formId]/edit.

Create and edit a form

Create the form

Under Forms, click Create Form and enter a name and an optional description. New forms start as Draft.

Drag fields onto the canvas

In the Fields tab you drag a field type onto the canvas or click it. Reorder fields by drag and drop, duplicate or delete them. Click a field to edit its settings. Undo and Redo step back and forth.

Settings and design

In the Settings tab you maintain the form settings, in the Style tab colors, font and appearance. With Preview you check the form at desktop, tablet and mobile width.

Save and publish

Save creates a new version without making it public. The publish button adapts to the state:

  • Publish form – the form has never been live.
  • Set live – the current state differs from the live version; pending changes are saved and set live.
  • Take offline – the current state is already live. After confirmation the form is no longer publicly reachable; existing submissions are kept.

Field types

Basic fields

Text input, text area, email, password, number, phone, URL and serial number (with barcode scan)

Selection fields

Dropdown, multi select, checkbox, checkbox group, radio group, card select, country, vehicle and toggle switch

Advanced fields

File upload, date picker, slider, rating, color picker, signature, PIN and unlock pattern

Layout elements

Divider, page break, text section and appointment

Layout elements have no validation and create no response column. All other fields can get required, length, pattern or minimum/maximum rules depending on their type.

Configure a field

Basic settings

Maintain label, field name, placeholder, description/helper text, width and label position. The field name is the technical identity and is used for mappings and response columns. Change it only deliberately once it is mapped.

Options

Dropdown, multi select, checkbox group, radio group and card select get options. You can set an option as default or hide it without deleting it. The option value is what gets stored – use unique values and clear labels.

Validation

Set required, minimum/maximum length, pattern and number or slider limits only as strictly as the process needs. Rules that are too strict create forms visitors cannot complete.

Conditional logic

With Add Condition you control when a field is shown, hidden, enabled or disabled based on other field values. Test each condition in the preview with a matching and a non-matching selection.

Special fields

  • Appointment – category, weekdays or weekly time windows, duration, lead time and parallel bookings (see Appointment field).
  • Signature – pen color and height; on desktop with full-screen mode.
  • Vehicle – vehicle type, choice of brand and model.
  • Country – default country and selectable countries.
  • File upload – accepted file types, maximum size and number.
  • PIN and unlock pattern – device access data for repairs, e.g. with hidden input.

Mappings

In a field's Maps to section you define where the answer is written: contact field or contact address, ticket field, order field, vehicle field, each also as custom fields, an internal note (hidden from the customer) or a ticket file with tag. A field can have several targets.

Via Mappings you open Review field mappings. There you see unmapped and orphaned mappings (e.g. after renaming a field), have suggestions created with Auto-map with AI and accept them deliberately with Apply suggestions.

Form settings

Form information and layout

Maintain name, description, Location (empty = all locations), whether title and description are shown, and the Form Language: German, English, Spanish, Italian, Turkish, Croatian, Slovenian, Chinese or French. Under Layout you choose form width, label alignment, tenant logo and optionally your own form logo.

Success screen and buttons

After submitting, the form shows a success title and description, optionally a new-response button and the submitted data. If a Redirect URL is set, SimpliServ redirects to that page instead. Under Buttons you change the submit button text and show the reset button and progress indicator.

Templates

  • Confirmation Email Template – sent to the respondent after submitting, provided they enter an email address.
  • Document Template – rendered as a PDF, offered for download on the success screen and attached to the confirmation.
  • File document at the customer – stores the filled-in document including signatures in the customer's files.
  • Shipping label – if a carrier is connected, customers get a prepaid label, always or only for a specific answer (e.g. "Send in device"), right away or only after the request is accepted.

Security

Spam protection protects against bots: Off, Invisible or Visible, each with Google reCAPTCHA or Cloudflare Turnstile as provider. With Restrict embedding you allow embedding only on listed domains (wildcards like *.example.com possible); this takes effect on publish.

Sharing and sidebar

After publishing, the action menu offers Copy form URL, QR code and Embed as well as export as a file. For form tracking you need the script widget. With the permission Administration → Settings → Edit you can use Pin responses to sidebar to put a form's responses into the sidebar for the whole team.

Version history

Version History lists all saved versions with time, author and field list; the live version is marked. For each version you can:

  • Restore as Draft – loads the version into the editor; it is only saved on the next save.
  • Set Live – makes exactly this version public.
  • Delete Version – only for versions that are not live.

Submissions are kept independently of versions. Only delete a form if its submissions and public links may go away too.

How is this guide?

On this page