Forms

A form on this platform is not an inbox. Send is where the work starts.

Four places a form lives

On a phone in the field. Opened from a link that already carries the job, so the site, the customer and the contract are filled in before anyone types. Short steps, a summary at the end, a signature with a finger.

On your website. A link or an embed, for an order, a claim or a request.

Inside a record. A button on the deal, the order or the employee you are looking at, with everything that record knows already in the form.

In the chat. A few questions the agent asks in the conversation when it needs them.

What it checks

Any form tool can insist that a number is a number. This one checks the fact against your records: that the job number exists and is still open, that the parts were booked out to this job, that the contract requires photos. It says so while the person who knows the answer is still standing there.

Required answers are enforced on the server, not only in the browser, so a consent box cannot be skipped by sending the form another way.

What happens after Send

The submission starts a run like any other trigger: a document is produced, a record is written, a question reaches you, a line appears in the timeline. When a job is set to run one at a time, submissions queue and keep their order instead of overwriting each other.