Features
Everything Flow does, page by page
Every feature has its own page: what it does, how it works, what you can do, the most frequent questions. Deep dives sit under the feature they belong to.
Flow overview
Preparing the request
-
Flow builder
Building the flow
You organise the request into areas, topics and steps, and for each step you choose what to ask for: one file, several files, a form to fill in, a signature or a question. The flow becomes a template: you activate it for as many clients as you like, without rewriting the list every time.
-
Conditional logic
Conditional logic
One question at the start, such as “Do you have employees?” or “Are you a company or a sole trader?”, and the flow adapts: the steps that matter appear, the ones that do not disappear. One flow, many paths, and no more “skip this if it does not apply”.
Asking for the documents
-
Invitations
Inviting clients and suppliers
Choose the company, the flow and the people: each one receives an email with their own link and uploads without a password or registration. If you need more security, add verification with a code sent to their email.
-
Upload page
The uploader’s page
A single page, with your logo and your colours: progress at the top, the deadline in view, one step at a time. You drag in the file, fill in the form in the browser, sign, and at the end “Send for validation”. It works on the phone too.
-
Deadlines and reminders
Deadlines and reminders
Give the collection a date, or a different date to each part. Flow writes to whoever has not delivered yet, at the right time and in their language, and all you do is see who is missing.
Checking and closing
-
Validation
Document review
An unreadable scan, last year’s company report, the form without a signature: the validator marks it as rejected, writes why, and the client immediately gets the email to upload it again. You can always see what is approved and what is missing.
-
Dashboard and summaries
Tracking collections
No spreadsheets full of ticks, no inboxes to reread. Flow shows you which collections are stuck, which are waiting for a review and which are about to expire, and for each client the exact list of what is missing.
-
Kamzan ecosystem
Files, kSign and Kontacts
Flow is not an island. The request starts from the client’s Files folder, the engagement letter is signed inside the flow with kSign, contacts land in Kontacts, and once the collection is closed the documents go back to Files with their structure.
Alex