Wire the forms on your site
into your work.

Short and long text, email, a phone field with a country picker, a web address, number, money, date, date with time, a dropdown, single and multiple choice, a checkbox, file upload, an explanatory text and a hidden field all come ready. You build the form by dragging a field and dropping it. Everything you ask has a field of its own.

You take a field from the list and drop it where you want it. You can put two, three or four fields side by side and leave stacking them on a phone to Workinno. Building a form needs no designer.

You split a long form into up to ten steps. The visitor sees which step they are on, the progress bar fills, and a missing field on each step is flagged right there. A long form does not scare the visitor off.

A field appears only when it is needed: pick “business” and the company name is asked, pick “personal” and it is never asked. A field that is not shown is not treated as required and is not submitted. The visitor never meets a question that has nothing to do with them.

The rule for showing a field can run to twenty conditions. Whether all of them must hold or one is enough, you decide. You build a complicated flow in a single form.

You make a field required, set a minimum and maximum length, and pick a ready format such as letters only or digits only. You write the help text under the field yourself. Bad data is filtered out at the moment of sending.

A visitor uploads a plan for a quote or a CV for an application. A file can be up to twenty-five megabytes, the upload percentage is visible and they can cancel it. A document request finishes inside the form itself.

Every uploaded file is checked against its real type and passes the virus scan. You find the file in the Files module, in that form's folder. A file from outside does not get in unchecked.

A contact record is created from the submission. If the same email has come in before, no new record opens and the existing one is used; your old details are not written over. The same person does not pile up twice in the list.

The company is taken from the email's domain, and a second person from the same company attaches to that company. Free email providers do not count as companies. Business requests gather under the right company.

A task opens in the project you choose; you can build form answers into its title and assign an owner and watchers. The uploaded file lands in the task's attachments as well. A request that arrives turns into work the same minute.

A notice goes to your team on one side and an automatic reply reaches the sender on the other. You can use form answers in the subject of both. The sender is not left without an answer.

You define up to five outcomes for a single submission and they are all processed in order. If one fails the others still run, and which one did not happen goes on record. One submission starts several pieces of work.

You map a form field onto a field on the customer card: the “Company” field onto the company name, the “Note” field onto the customer note. Even without mapping, the email and the phone are not lost. The information settles in the right place on the card.

Form submissions land in the same inbox as WhatsApp, Instagram and live chat. You do not switch tabs by where something came from. You handle every request from one queue.

Every submission arrives as new and turns to seen when you open it; you move it on to in progress and resolved. You assign it to a teammate, so who is on it is clear. No request closes without an answer.

The records born from a submission stand beside it by name: which task opened, which customer was created. You click and go straight there. What came out of a request is recorded on the request.

Which page, which link and which ad tag the submission came through is recorded. You do not guess which channel brings work in. You share out the ad budget by measurement.

A field people cannot see sits in the form. Bots fill it in and the submission is quietly dropped; a real visitor notices nothing. Your list does not fill up with fake records.

You turn the verification box on per form, and it is genuinely checked on the server side. If spam is not heavy you leave it off and do not put the visitor through it. You set the level of protection yourself.

You decide how many times one address can send per hour. A per-minute ceiling also runs for the form as a whole. An attack does not lock the form.

You can drop repeats that come from the same email or phone. You pick the window as an hour, a day, a week or a month. You count the same person once.

You paste the line from the builder into your site and the form settles in. It sets its own height and does not jump as the page grows and shrinks. Publishing a form stops being a developer's job.

You embed it in your site, hand out a direct link, open it as a pop-up, print a QR code, send it over WhatsApp or put it inside your support widget. The same form lands in the same record everywhere. Wherever it comes from, you handle the request in one place.

You pick the light, dark or transparent theme and give it your brand colour; the button and focus colour follow. On the transparent theme the form drops its own background and your site's shows through. The visitor does not think they have moved to another site.

You upload a logo and turn showing the form name on or off. The visitor sees whose form they are filling in. The impression of your brand carries on into the form.

You write your thank-you message or send the visitor on to another page. The redirect address is checked twice for safety. The visitor is not left in limbo after sending.

You write your own privacy notice and make the consent box required. A submission that arrives without the box ticked is rejected on the server. The record of consent is kept together with the submission.

You choose the form's language; all system text such as send, next, back and thank you appears in it. The task and the emails born from the form are written in the same language too. A foreign visitor fills it in in their own language.

You write the form's name in one language and it is translated into the others with one button. You present the same form by name on your sites in different countries. You open in a new market the same day.

A property request, a quote, contact, a job application, a customer survey, a booking, an order, an event sign-up, a call-back and a support request all come ready. You can also start from a blank form. Your first form goes live in minutes.

You copy an existing form's fields, settings and theme and open it as a draft. You do not build the form again from scratch for your second branch. Similar forms do not drift apart.

Every submission carries the form definition of its moment alongside it. Even if you change the form later, an old submission still shows correctly which question got which answer. Past records do not change along with the form.

If an active form has had no submission for seven days it is flagged in the list. You learn that the form on your site is broken from Workinno, not from customers not calling. Silence reaches you as a signal too.

If a submission arrived but the email did not go out or the task could not be opened, administrators are notified. You also hear when your monthly submission allowance runs out and a visitor is turned away. There is no such thing as a lost request.

Submissions are forwarded to up to three addresses per form. They are signed for verification, retried three times if they do not arrive, and the result goes on record. Your system outside Workinno gets the same data.

You download the submission list as Excel or CSV, and print it if you like. Who exported it and when goes on record. You download the list ready for a meeting.

The form's thirty-day views, submission count, change against the previous month and completion rate stand on one screen. Whether a form is working is not left to guesswork. Which form works is read off the numbers.

One person sees only the submissions assigned to them, a team lead their team's, an administrator all of them. Exporting and deleting are separate permissions. Customer information is not opened to everyone on the team.

You put the form submissions card on your dashboard and choose how many hours it looks back over and whether it shows only unread ones. A request that comes in does not slip past your dashboard. You see incoming requests while you look at your day.

If a customer has filled in your form before, it appears on the customer's timeline. You see when they asked for what without searching. You go into the conversation knowing what that person wanted.