Task Manager
Automation that knows when to stop and ask.
In most tools, human approval is something you build: a notification here, an approve link there. In Formt it's built in. Workflows run on their own until they hit a step you've marked for judgment, then pause and wait. You review, decide, and they continue.
The inbox
Every pending decision, across every workflow, in one place
Tasks from every active workflow land in one inbox: emails waiting on approval, forms waiting on input, outputs waiting on a second look. Filter by workflow or task type, and a badge in the app nav tells you something's waiting before you go looking.
The right moment
Review what a step is about to do, or what it just did
You turn review on for a step with a single switch, and Formt handles the timing. A step that reaches outside Formt (sending an email, writing to your CRM, posting an update) pauses before it runs, so you approve it first. A step that only generates or calculates pauses after, so you see what it produced before anything downstream depends on it.
The trust dial
Supervise everything on day one. Loosen it as trust grows.
Review is set per step and takes a click to change, so a workflow can start on training wheels and earn its autonomy one step at a time.
Review everything
Turn review on for every step that touches a customer: each email, each CRM write, each document held for your sign-off. The workflow does the work, and you still make every call.
Loosen it, step by step
When approving a step stops feeling like a decision, switch its review off, and keep it on the sends that stay high-stakes. Per step, reversible, one click either way.
Trust, with receipts
Even fully automatic steps stay inspectable: every run records what each step read and produced. Spot-check whenever you like, and switch review back on if something changes.
Bulk approval
Review the batch, not two hundred tasks.
A campaign over a long contact list creates one review task per email. Approving them one by one would erase the time the automation saved, so you don't have to.
Audit trail
Who decided what, and what they were looking at.
Every review is recorded against the run: the reviewer, the decision, the time, and the step data as it stood. When someone asks why an email went out, the answer is on the record instead of in someone's memory.
Use cases
Where a human in the loop matters most
Review earns its place wherever automation's output reaches a customer, a client, or a system of record, and getting it wrong has a real cost.
Email campaigns before they send
AI drafts a personalised email for every contact in the campaign. PRE review holds each one: read a sample, pull any outlier for edits, and bulk approve the rest. Oversight without reading 200 emails one at a time.
See templateLead scoring before CRM write-back
AI enriches and scores leads in Structured mode. POST review shows you the scored output before anything is written to HubSpot, so a bad score on a high-value account gets caught before it pollutes the CRM.
See templateDocument decisions with counsel in the loop
Workflows that extract clauses, flag obligations, or classify risk pause for review before anything acts on the result. The reviewer sees exactly what the AI extracted and what happens next.
See templateClient reports before they go out
Generated financial reports and summaries hold for review before they reach a client inbox. One approval releases the batch; one rejection stops a bad number from travelling.
See templateApprovals inside a running workflow
Form Input tasks pause a run and ask a person for what's missing: a budget sign-off, a scope confirmation, a purchase approval. The moment the form is submitted, the run picks up where it left off.
See templateClaim packets before submission
The claim narrative, filled forms, and merged documentation hold for the owner's review before the packet is emailed to the adjuster. Errors on a high-value claim get caught while they're still cheap.
See templateHow it compares
Review is a checkbox, not a build project
You can assemble approvals in most automation tools: a notification here, an approve link there. Here's what the hand-built version leaves out.
| Capability | Other tools | Formt |
|---|---|---|
| Setup | Design an approval sub-workflow yourself, for each place you want a pause. | Enable review on any step. The pause, the task, and the inbox come with it. |
| Where approvals live | Scattered across email threads and chat channels, one ping per workflow. | One inbox across every workflow, filterable, with a badge when something's waiting. |
| What the reviewer sees | Whatever you remembered to template into the notification. | The step's resolved inputs or actual output, in full, at review time. |
| The decisions | Approve, or don't. | Approve, edit and approve, or reject. One at a time, or in bulk. |
| The record | A scrollback of pings. | An audit trail: who decided, when, and what they saw. |
Try it first