Forms
Build forms that fill your CRM, share them by link, QR code or embed, and work every submission in one inbox
A form collects leads, and each answer can land on a CRM field. Find it under Marketing > Forms. The switch at the top of the page moves between Forms and Submissions. The old Admin address of each page redirects here.
Each row shows the form, its status, its Views, its Submissions and its Conversion. Search by name, or filter by status. Use Load more to reach older forms.
- Published: the form is live and accepts submissions.
- Draft: the form is active but not published. Its public page answers "not found".
- Inactive: the form is deactivated. Its link is off and its submissions are kept.
Expand a row to see a quick snapshot: the funnel for the last 30 days, the share options, and the actions Open builder, View submissions, Duplicate, Deactivate or Activate, and Delete permanently.
Start a new form
Add fields
Choose the settings
Publish and share
- From your CRM lists the Contact and Company fields a form may fill, with their type and option count. Deal fields show there only while Also create a deal is on.
- Options stay in sync. A dropdown bound to a CRM field takes its options from the CRM. Choose All or Some of them. Options you add in the CRM appear on their own when you chose All. If none of its CRM options is left, the dropdown shows the options it saved last.
- Form-only questions keep the answer on the submission and the contact timeline: Short text, Long text, Email, Phone, Number, Link, Date, Dropdown, Single choice, Multi-select, Checkbox, Consent, File upload and Hidden.
- Saves to in the field panel names where each answer goes. Two fields bound to one CRM field get a warning, because the later answer replaces the earlier one.
- Show this field can be Always or Only when another field's answer is, is not, contains a value, or is answered. A hidden question never blocks the visitor and is never sent.
- Hidden fields send a value without showing it: their default, or a value from the link.
- A link can fill in answers. Add the field key, or the CRM field's key, to the link, such as
?email=ada@example.com. A link never ticks a consent box and never adds a file. - Field key: each field shows its key with a copy button. The API and webhooks use it.
- Answer pattern: a pattern set through the API or the assistant shows in the field panel. The form refuses an answer that does not match it. Clear pattern removes it, and a pattern that can freeze the visitor's browser is flagged.
Turn on Pages in the builder's outline, then give each page a title. A form has 2 to 20 pages. The visitor sees one page at a time with a step counter. Next checks only the current page, Back keeps the answers, and Submit shows on the last page. A page whose fields are all hidden by their rules is skipped and leaves the count. A field with no page goes on the first page.
- Add a Consent field and choose its purpose: Marketing emails or Terms.
- The box is never ticked in advance. You can add a link to your privacy notice or terms.
- A marketing consent box can never be required. A terms box can.
- Every submission keeps the exact text and whether the box was ticked, as shown at that moment. A later edit of the form never changes what a past visitor agreed to.
- A ticked marketing box also writes one consent record for the email on the form. An unticked one writes nothing.
- Double opt-in, under Compliance in the Settings tab, sends a confirmation email before the contact counts as opted in. A form with an unticked marketing box sends no such email. It is also not sent while your workspace is on payment hold or locked, while its outbound mail is stopped, or to a new contact marked do not contact. That contact stays not opted in. If the contact's email changes before they click, the old link no longer works. They submit the form again to get a new link. A contact whose address already confirmed a double opt-in is confirmed without a new email.
Choose the mode under Duplicates in the Settings tab. A new form starts on Merge.
- Merge (fill empty fields only): a match gets only its empty fields filled. Nothing is overwritten. A contact matched by phone never gets the visitor's email address. The submission's note says so.
- Always create new: each submission adds a new contact, even when the email matches one you have.
- Skip (keep the submission only): a match adds nothing to the CRM. The submission stays in the inbox with the status Duplicate.
In every mode, a new contact is marked Do not contact when a contact you already have holds its email address with Do not contact.
The match looks at the primary and second email first, then the exact phone number. When no contact matches, it looks for the company by the email's business domain, then by the typed company name. If a match cannot be read, the submission fails and you can retry it, so a returning contact never gets a second record by accident.
- First, route by territory: a lead goes to the members of the first active territory that matches its company, in turn. See Territories for the order and the matching rules.
- The form's own rule applies when no territory took the lead: nobody, one person, or a round robin between the people you pick.
- Owned records keep their owner. A company that already has an owner keeps it, and its contact gets the same owner when it has none. If that owner left the workspace or has a read-only seat, the company keeps them, but the lead stays unassigned for someone to claim.
- An owner who left, or who has a read-only seat, never gets a lead. The lead stays unassigned, and the form's creator or an admin gets one task a day to fix the rule. A teammate with a read-only seat in a round robin or a territory is skipped.
- An unassigned lead becomes one shared row in My Work. Anyone who can edit contacts sees it, and the first to claim it becomes the owner of the contact and the company.
- An assigned owner gets a notification. Team chat channels connected to your workspace also get a New lead post.
The same tab sets default values for new leads: Company type, Status, Priority and Source.
- The thank you screen: set the success heading and message, an optional button, or a redirect address with a delay. You find these under After submission in the Settings tab.
- Confirmation email: off until you turn it on. It sends one email to the person who sent the form, with your subject and text, and it can use
{first_name}and{form_name}. The sender shows as your workspace name followed by "via Laureo". It needs a connected mailbox, because replies go to that mailbox. One address gets at most one email in 24 hours. It is never sent for a submission released from spam, or for a lead that waited for plan room, or to an address that unsubscribed or bounced. - Offer a booking page: after the form is sent, the person can go to a booking page or a routing form you choose. On a booking page their name and email are filled in, and the booking links to the contact. The offer wins over the redirect address and opens after the same delay.
- Also create a deal: each lead gets a deal in the pipeline and stage you choose. The owner is the lead's owner, and the value comes from a number field linked to the deal amount. The form opens no second open deal for the same contact within the days you set, 30 by default.
- Automations and webhooks: a submission fires the Form submitted trigger and the form.submitted webhook.
Shared links and embeds always run a spam check. When the check flags a submission, the visitor still sees the normal success message. The submission is kept aside with the status Spam and the reason, and it does not count toward your monthly limit. If you choose Not spam, it is processed and counts then, and only once. The Settings tab also has a hidden Honeypot field and Submissions per visitor: how many times one network can send the form in 10 minutes, from 5 to 500, with a default of 30.
Click Share in the builder or on a row. A draft shows "Publish this form to turn on its link and embed." in place of the link, the QR code and the embed code. A deactivated form says to activate it first. The custom link, the allowed websites and the social preview stay editable in both cases. With only Forms: view, they show read-only.
The link
- A form with no custom link is served at
/f/plus the short id the product mints for it. So a form always has a working public link, and nothing comes from the form name. - A form with a custom link is served at
/f/your-business-demoinstead. Set it under Custom link on the Share page. Clear the box to go back to the id.
What a custom link may be
- 3 to 60 lowercase letters, numbers and single hyphens.
- Not one of the reserved words that read as ours rather than yours, such as
support,billingorlogin. The rule is the whole link, soyour-business-supportis fine. - Not a link that reads as Laureo, including lookalike spellings.
- Not a link another workspace already holds. Form links are unique across every workspace, and a workspace can claim up to 20 new form links a day.
The QR code
Print it on a flyer, a sign or a business card. Download a PNG or an SVG. Add a source, medium and campaign under Campaign tracking if you want them on each submission. The code always opens the id link, so renaming the custom link never breaks a printed code. Submissions from it show the channel QR code.
The embed
Pick Inline, Popup or Slide-in and copy one line of code. Paste it into your website where the form should go. It needs no API key. Full page is the form's own link, for a button or an email. The form runs in a frame from Laureo, so your page never touches the answers.
<script async src="https://app.laureo.io/embed/forms.js"
data-form="FORM_ID" data-mode="inline"></script>The way the embed shows comes from this code. The Display mode settings in the Settings tab apply only to the older script widget.
| Field | Description | Type |
|---|---|---|
| data-form* | The form id. The Share page fills it in. | attribute |
| data-mode | inline (the default), popup or slidein. | attribute |
| data-height | Inline only. The height in pixels to keep free until the form reports its own, such as 560. Without it the box uses the form's estimate, or 480. | attribute |
| data-target | Inline only. A CSS selector, such as #signup, for the element to mount the form into. Without it the form mounts beside the script tag. | attribute |
| data-title | The frame's accessible name until the form sends its own title. | attribute |
| data-button-text | Popup and slide-in. The label of the button the script adds. The default is Open form. | attribute |
| data-position | Slide-in only. left puts the panel in the left corner. The default is the right corner. | attribute |
| data-laureo-form-open | Put it on your own element, with the form id as its value, and a click opens that form. Add data-mode to choose popup or slidein. With this element on the page, the script adds no button of its own. | attribute |
On a JavaScript or React page
The same keyless script works from code. Replace FORM_ID with the id from the Share page. To open a form from your own button or code, load the script once:
<script async src="https://app.laureo.io/embed/forms.js"></script>
<!-- Any element with this attribute opens the form when clicked. -->
<button data-laureo-form-open="FORM_ID" data-mode="popup">Contact us</button>
<script>
// Or open it from your own code, after the script has loaded.
function openContactForm() {
window.LaureoForms.open('FORM_ID', { mode: 'slidein', position: 'left' })
}
</script>In React, add the script when the component mounts:
import { useEffect, useRef } from 'react'
export function ContactForm() {
const box = useRef(null)
useEffect(() => {
// The box is empty only on the first run, so the form mounts once.
if (box.current.childElementCount > 0) return
const script = document.createElement('script')
script.src = 'https://app.laureo.io/embed/forms.js'
script.async = true
script.dataset.form = 'FORM_ID'
script.dataset.mode = 'inline'
box.current.appendChild(script)
}, [])
return <div ref={box} />
}Forms installed earlier with the older script widget keep working. That widget uses a key that starts with lck_, and the Share page no longer offers its code. Older JavaScript and React code that asks for a key is that widget. Never put a key in a web page: use the keyless script for a new install.
The social preview
Set the title, description and https image address a shared link shows in chat apps and social posts. Empty fields use the form name and your workspace logo.
Under Where can this form be shown? on the Share page, choose Any website (the default) or Only these websites.
- List one website per line, up to 50. Each is matched exactly, so add both acme.com and www.acme.com.
- A listed website uses https. Only localhost may use http.
- A change reaches forms already on a website within a minute.
- On any other site the browser blocks the frame, and the visitor sees "This form can't be shown on this site." with a link that opens the form on its own page.
- The list controls where the form can be framed. The form's own link keeps working, and a verified custom domain can always show the form.
Add the subdomain
forms.yourcompany.com and click Add domain. A workspace has one. The main domain is refused, and so is a name that is a DNS zone of its own, and your own email tracking domain. A domain another workspace uses is refused too. If you own that domain, publish the TXT record the page then shows and add the domain again. If the other workspace has the domain set up, it gives way to yours only while your record is published and its own TXT record is not. The value of that record changes every 7 days: if the page shows a new one, publish the new one. Only people who can edit forms for the whole workspace can change it.Add the DNS records
Press Verify
Laureo connects the domain
- The Share page then shows your domain's link first. The Laureo link keeps working. QR codes keep the Laureo link.
- Laureo checks a verified domain every day. After two failures in a row it stops serving: its form links answer "not found" until you verify it again, and your workspace gets a Forms domain stopped working notification. To verify it again, publish the TXT record the page shows and point the CNAME record at Laureo, then press Verify.
- Keep the TXT record published: the daily check reads it too. If it is missing, the page says since when and shows the record. If it is still missing 14 days later, the domain stops serving and your workspace gets the same notification. If another workspace publishes its own TXT record for the domain and adds the domain while yours is missing, it takes the domain at once, and your workspace gets the same notification.
- Remove domain stops its form links at once. Your forms keep working on their Laureo links. Then delete the CNAME and TXT records, because a CNAME record left in place could later be pointed at someone else's forms.
- For 30 days after a domain is removed before its TXT record was found, it can be added again only once that TXT record is published. The page shows the record with the note that says why the domain was removed. A domain removed after its TXT record was found can be added again at once, with a new TXT record.
- If another workspace took your domain, the page says so and shows a TXT record. Keep the CNAME record: that workspace uses it. If the domain is yours, publish the TXT record and add the domain again. You get it back only while the other workspace's own TXT record is not published.
- A workspace that moves to a plan without custom domains keeps a domain it set up, and can remove it, but cannot set up a new one.
Open Submissions. Search by name, email or company, and filter by form, status, channel and date. The list shows 50 rows at a time, with Load more. The channel is one of Link, QR code, Embed, Pop-up, Slide-in, API, Legacy widget or Custom domain.
- Pending and Processing: on the way to the CRM.
- Processed: the CRM has it.
- Waiting: over the plan limit and kept for later. See Limits.
- Failed: something stopped it. Retry runs it again.
- Spam: flagged and kept aside.
- Duplicate: a form on Skip matched a contact.
Open a row to read the answers, the files, the consent as shown at submit, the source and UTMs, Routed by, any ticket, and links to the contact and company you can open. The actions are Retry on a failed or stuck row, Mark spam or Not spam, and Delete. Select rows to act on several. If some of them cannot be changed, the others still are, and the ones left stay selected with the reason. Export starts a background job that lands in export history. It covers the whole view, or up to 150 selected rows.
A form's row shows its funnel for the last 30 days: Views, Starts and Submits. Full results opens the form's results page, for 7, 30 or 90 days in UTC:
- Funnel: views, starts and submits, conversion, and spam submits, which are not counted. When you mark a submission as spam, or as Not spam, its count moves to match.
- By channel: the same numbers for each channel.
- Drop-off by field: the field a visitor was on when they left without submitting. These are counts only. Unsent answers are never kept.
- Drop-off by page: on a form with pages, how many reached each page and left after it.
On Full results, conversion is submits divided by views, and it never shows more than 100%. Spam, automated views and submissions sent through the API, which have no views, never affect it. For more, the Form submissions source in Reports counts by form, channel, UTM, status and test version.
A view counts once per page load, when a person can see the form. The tab must be visible and at least half of the form's first field must stay on screen for 1 second. A visitor who touches the form first also counts at once. So an inline embed far down a page counts only when someone scrolls to it.
Crawlers, link previews in chat apps, headless browsers, HTTP libraries and uptime monitors are not views. They show apart as Automated views filtered. A program that hides itself as a browser can still count as a person.
- Set up version B on the Test tab. It can change the title, subtitle, button text, success heading and message, the pages, the order of the questions, and a question's label, help text and placeholder. It can leave out optional questions.
- A required question, a consent box, a hidden field, the options, the CRM link and the language stay the same in both versions.
- A form has one test at a time. Set an end date 1 to 90 days away, then click Start test. Version B is locked once the test starts.
- Visitors split about evenly by network, with no cookie, and each network keeps its version for the whole test.
- Each version counts one view per network per UTC day, and the result counts at most one submission per network per UTC day, so one busy office cannot tip it. Automated views and spam are left out. Leads waiting for plan room count.
- Edits to the form change both versions while the test runs. Page and question drop-off mix both versions.
After the end date every visitor sees version A until you choose Use version B or Keep version A. Use version B makes its texts, order and pages the live form, and it removes the questions version B left out. To end early, use Stop and keep version A or Use version B: the test is recorded as Stopped early: no verdict.
Choose the Language in the Settings tab. Buttons, errors and messages follow it. Text you type stays as you typed it, and the form never guesses from the visitor's browser. Arabic and Hebrew forms read right to left. Under System text you can type over any line, or leave it empty to keep the default.
The 35 languages are: Arabic, Catalan, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English, Filipino, Finnish, French, German, Greek, Hebrew, Hindi, Hungarian, Icelandic, Indonesian, Italian, Japanese, Korean, Norwegian (Bokmål), Polish, Portuguese (Brazil), Romanian, Russian, Serbian (Cyrillic), Sinhala, Slovak, Spanish, Swedish, Turkish, Ukrainian and Vietnamese.
- Add a File upload field. It takes 1 to 5 files per answer. Set the largest file to 1 MB, 2 MB or 3.5 MB.
- Choose the accepted files: Documents (pdf, doc, docx, odt, rtf, txt), Images (png, jpg, jpeg, gif, webp, heic, heif), Spreadsheets (xls, xlsx, ods, csv), Presentations (ppt, pptx, odp) or Archives (zip).
- File fields work only on the form link and the embed. The legacy widget and the API send no files. They skip an empty optional file field, but they refuse the whole submission when a file field is required or was sent a value. On a form that they feed, keep file fields optional.
- One network can start 10 uploads in 10 minutes and 50 a day on a form, and a form takes 200 uploads a day.
- Files stay on the submission and never save to a CRM field. They show in the inbox, on the contact timeline, and as From forms rows in the contact and company Files card.
- Clean files count toward your workspace storage. If the storage is full, or a daily upload limit is reached, when someone sends the form, the inbox says the files could not be added and why.
Every file is scanned for malware after the submission is processed. While the scan runs, the file shows Scanning. Nobody can open a file until it shows Ready. A Ready file opens through a link that lasts 60 seconds, for people with Forms view access or who can see the linked contact. A file can also show Blocked, with the reason, for example Blocked: did not pass the malware scan or Blocked: password protected. People who can delete forms can delete one file.
What waiting means
- Waiting for scan: daily limit reached; scans resume on the next day, or Waiting for scan: monthly limit reached; scans resume on the first of the next month. Scans have a daily limit of 40 form files for each workspace, and a monthly limit. The file waits until the limit resets. This wait never expires, and the file is scanned then with nothing for you to do. On the last day of a month both limits reset on the same day, so a waiting file shows Waiting for scan: limit reached; scans resume on the first of the next month.
- Waiting for scan: scanner unavailable. The scanner is down. The file is scanned when it returns. After 7 days of outage the file is removed and shows Could not be scanned, removed.
- A file on a spam row waits until you choose Not spam. After 30 days as spam, the file is removed and shows Could not be scanned, removed. A file on a lead waiting for plan room waits until the lead is released.
Under Submissions in the Settings tab, set Each submission to Add a lead (the default), Create a ticket or Add a lead and create a ticket. Only people who can assign tickets can change this or copy such a form.
- Choose the Queue, Priority and Type.
- Choose the Message field. Its answer is the ticket's description, followed by the form-only answers. A name, email, phone or an answer that fills a CRM field never goes into the ticket.
- The subject is the Subject field's answer, else the Subject text, else the form name followed by request. A field that fills a contact or company field cannot be the subject.
- The form needs a required email field that the person always sees. A hidden field, or a field with a show rule, does not count. The panel offers to add it, and a message field too.
- The visitor sees "Check your email" and gets a link. The ticket waits in pending verification until they open it, then goes to your queue.
- The inbox row shows the ticket and its state, such as Waiting for email confirmation, Open or Solved.
- On Add a lead and create a ticket, a submission with no usable email address still adds the lead, but no ticket is filed. Its row shows Not filed: no email.
- On Create a ticket, CRM fields stay empty, no contact is added and the form cannot hold a marketing consent box. It does not count toward your submissions limit and never waits for plan room.
- A form that creates a ticket sends its own email, so the confirmation email setting does not apply.
How many forms you can have, and how many submissions reach your CRM each month.
| Plan | Forms | Submissions a month | Each added Power seat |
|---|---|---|---|
| Pro | 2 | 1,000 | +2 forms and +1,000 submissions |
| Business | 10 | 2,000 | +5 forms and +1,000 submissions |
| Ultra | Unlimited | Unlimited | Not needed |
- An inactive form still counts toward your form limit. At the limit you cannot create or copy a form until you add a seat, upgrade or delete a form permanently. Every form you have keeps collecting.
- A lead counts once, when it reaches the CRM. Spam never counts.
- Over the limit, a lead is kept and never lost. The form keeps accepting and the visitor sees the normal success message. Above 110% of the monthly limit a new lead shows as Waiting, and the Forms and Submissions pages show how many leads wait. People who can open billing get an Upgrade link, and where a Power seat also helps, a line saying an admin who manages billing can add one through the assistant. Others see a line that asks an admin to do it.
- Waiting leads are processed, oldest first, when you add a Power seat, upgrade or the month starts again.
See Seat Types for what a Power seat adds.
To send answers from your own server, use a workspace API key with the Forms (Submit) scope. A key with only that scope works on every plan. See Send form submissions from your server. An embed needs no key. Keys that start with lck_ keep working on the older endpoints, and you can revoke them on the Legacy form keys page.
- Forms: view opens the forms, their numbers and the inbox. In the builder they read the form: every setting shows disabled, and there is no Add field, Add page or reorder. Without it, each forms page shows one line: your role cannot open it.
- Forms: edit creates, edits, publishes, shares and deactivates forms, and runs Retry and Not spam.
- Forms: delete deletes forms, submissions and single files permanently.
By default Super Admin, Admin, Sales Manager and Marketing can view and edit, and Super Admin and Admin can delete. Change it in Roles & Permissions. Export needs the user management permission. Legacy form keys are for admins.
A person's data export includes the form submissions linked to them. It also includes submissions sent from any of their profile email addresses, up to ten, that are not linked to anyone, spam and failed ones included, with their status and the consent choices given on the form. See Data Privacy. Spam and duplicate submissions follow your data retention settings.
- Deactivate turns off the link and the embed. All submissions are kept, and the form still counts toward your form limit.
- Activate brings the form back as a draft. Publish it to turn its link back on. An older form that kept its published state goes live at once, and the message says so.
- Duplicate makes a copy with its fields and settings, as a draft.
- Delete permanently asks you to type
DELETE. It deletes the form, its submissions and their files for good, and its link stops working. This cannot be undone. To keep the submissions, deactivate the form instead. A form with too much history cannot be deleted in one step, and the dialog says so.