SCYTIAN
Menu

PLATFORM / FORMS

Filled in on the spot. Signed. In your system before you drive off.

A link on your website, a form on a technician’s phone, or a button inside the record you are looking at. It opens with what you already know, checks what gets typed in. Send is where the work starts.

Get your agent
Operations{{ status }}
CHAT

{{ typed }}

{{ agentText }}

1He opens it on site
Service report17:42 · ▂ 1 bar
{{ phone.step }}
{{ f.k }}already there{{ f.v }}
Customer signature
{{ phone.btn }}
{{ phone.note }}
2He presses Send. This happens.
{{ r.t }}{{ r.h }}{{ r.d }}
3Before he leaves the car park
JOB #4417 · HOTEL MERIDIANWork, parts and 3 photos on the recordclosed
REPORT · PDFsigned, attached · 2 × F-140 booked out
To: facility@hotelmeridian.com17:42

Your service report for boiler room B is attached, signed on site by your facility manager.

{{ foot3 }}
Message Operations…

{{ foot }} · a form is a trigger, not an inbox

WHERE THE FORM LIVES

Four places. Same platform. Always a record at the end.

A form for somebody in gloves is not the one on your website, nor the button on a record inside your system. Four sets of decisions, one result.

ON A PHONE

In the field, one bar of signal

Opened from the job link. Three short steps, a signature, Send. It does not lose what he typed if the signal drops.

technicians · drivers · inspectors
ON YOUR WEBSITE

A link or an embed for customers

An order form, a claim, a request. Opens with what you know about them if they came from an e-mail you sent.

customers · partners
INSIDE A RECORD

A button on the thing you are looking at

Sitting on a deal, an order, an employee. Everything the record knows is already in the form.

office · back office
IN THE CHAT

Asked by the agent when it needs to

A few questions in the conversation, answered in place. No form to find, no link to keep.

anyone in the office

WHAT PEOPLE REPLACE WITH THEM

service protocolswork ordersholiday requestspurchase requestsclaims and complaintshandover recordssite check-instimesheetsonboarding dataorder formsand more

THE DIFFERENCE THAT MATTERS

It checks the fact, not the format.

Any form tool can insist a number is a number. None can know the job you typed was closed in March, because none can see your records. This one can, and says so while the person who knows the answer is still standing there.

CHECKSagainst your records
!Job number4413closed in March. Did you mean #4417, today, same site?
✓TechnicianM. Carterassigned to this job
!Parts used4 × filter F-140two were booked out to this job. Where are the other two from?
✓Hours on site3.5within the usual range for an annual service
!Photosnonethis contract needs them. The warranty claim is refused without
Two stopped it, one asked. Caught at 17:41, while he is still standing there, not on Thursday by somebody in accounts.

It fills in what it can look up

The link carries the job, so site, customer and contract are in before he starts. Not to make the form look short, but so the company name is not spelled a fourth way.

One bar of signal is enough

Boiler rooms, cellars, yards. It is a page, not an app that has to sync. If the send does not go through it keeps what he typed and never sends twice.

Three short steps, not one long page

Nobody scrolls a wall of fields with gloves on. A few things at a time, ending on a summary he can check.

WHEN IT RUNS

Send is not the end of the form. It is the start of a process.

A submitted form is one of the five things that can start a run. So everything on the other pages applies to it: a document, a write into your system, a question to you, a line in the timeline.

SERVICE REPORTField → customer → books

“When a technician submits it, build the report, send it for signature, close the job and book out the parts.”

Form sentReport builtSigned & e-mailedJob closed, parts out
HOLIDAY REQUESTOne question to the right person

“When somebody asks for leave, check the team calendar; if two are already off that week, ask the manager, otherwise approve and book it.”

Request sentCalendar checkedManager askedBooked in HR
CLAIM FROM A CUSTOMERWeb form → decision → reply

“When a claim comes in from the website, find the order, check the warranty; under 200 € replace it and tell them, otherwise put it in front of me.”

Claim on the webOrder & warranty foundYou decide over 200 €Customer replied

every run shows up in the timeline, with its cost · the other four triggers →

THE LIMITS

What these forms are not for.

Not a marketing tool

Landing pages, surveys, lead capture with a cookie banner: a different job with good products for it. These forms start work inside a company that already has the customer.

Bad input fails loudly

If something required is wrong or missing, Send does not quietly succeed and produce an empty document downstream. Whoever sent it finds out in the moment, field named.

It does not become your system

Answers do not live in a form tool for you to export later. They are written into the record they belong to, on the platform you already use.

Name the paper somebody fills in outside the office and types up when they get back.

Your Operations agent arrives with the form built, by the next working day.

Get your agent