Platform · Human in the loop
Where a person decides, the workflow waits
Automation fails at the seams — where a bot's output needs a human decision nobody sees. Forms, tasks and approvals are steps in ElectroNeek workflows, so the handoff is explicit, tracked and logged.
Updated for the October 2026 release.
Process Management · AP workflow
Intake
Invoice batch #221
🤖 Invoice Agent
New vendor W-9
🤖 Docs Agent
Needs approval
Payment run $48.2k
👤 S. Chen — CFO
Credit memo #114
👤 Controller
Done today
214 invoices posted
🤖 Invoice Agent
Month-end pack
🤖 + 👤 reviewed
In one paragraph
ElectroNeek's human-in-the-loop capabilities live inside AI Workflows: approval actions that pause a run and ask in Slack, Microsoft Teams, Gmail or Outlook; a form builder with 16+ question types, conditional logic, multi-page forms and public forms that can trigger a flow; a task inbox where assigned forms wait for a person with email notifications; and a Human Input step for chat. Guest users can be licensed for forms and tasks only. Every approval and input is recorded in the run, so the audit trail is a by-product of the process, not a separate project.
What it does — concretely
Approvals where people already are
Approval steps for Slack, Teams, Gmail and Outlook with the context attached. The run pauses, the person decides, the run continues with the decision logged.
Forms that start and feed flows
Drag-and-drop builder, 16+ question types including signature and file upload, conditional logic, multi-page forms, Markdown. Public forms trigger flows without a login.
A task inbox
Forms assigned to a person land in Tasks with email notifications; guest-user licenses cover people who only approve and fill forms.
Chat as an input
Chat UI and web-form triggers let an agent ask a person mid-run and continue with the answer.
Routing by rule
Document fields that fail validation, agent outputs below a threshold, amounts above a limit — all route to a person through the same steps.
Everything in the run log
Step inputs and outputs, who approved what and when, the agent's reasoning timeline. Audit logs are kept up to 60 months at the account level.
How it works
01
Decide where a human belongs
Payments above a threshold, customer-facing replies, anything regulated. Put an approval or a form there.
02
Route to the right channel
Slack or Teams for operations, email for managers, a public form for the client, the task inbox for a queue.
03
Measure and relax
Watch how often a person changes the machine's answer. Where it is never, widen the autonomy; where it is often, fix the upstream step.
What it doesn’t do (yet)
Stated here so you don’t find out in a pilot. Roadmap items are marked as such.
- —A run paused on an approval is retained for 30 days and cannot resume after that.
- —There is no SLA clock with automatic escalation yet; use a schedule-triggered flow to chase pending tasks.
- —Process analytics are the run dashboard (time saved, runs, active flows) — not cycle-time analytics per step.
Common questions
How is this different from a project-management tool?
Jira or Asana track work people report. Here the work itself runs: agents and bots execute their steps, a person gets theirs, and the process advances when they decide. The task exists because a workflow created it.
Can approvals happen in Slack or Teams?
Yes. The approval step posts the context to a channel or a person, waits, and continues the run with the answer. Email approvals work the same way through Gmail or Outlook.
Can people outside the company fill forms?
Yes. Public forms work without a login and can trigger a flow; guest users can be licensed for forms and tasks only.