Solutions / Human-in-the-Loop AI

Where the automation actually stops, in the code, not in a claim.

“A person is always in the loop” is an easy thing for any vendor to say. This page names the specific gates instead: the risk score that has to clear before AutoApply opens a browser session, the confidence threshold a draft has to clear before it can even be generated ahead of time, the click that always has to happen before a draft reaches a funder, and the audit row written every time an agent makes a decision.

Walk through a real approval gateSee the five gates

Five places a person, not the model, decides

Risk-based routing and approval before AutoApply submits
Ten weighted factors — a manual-only portal flag, a legal attestation checkbox, an ask amount well above the funder's historical maximum, missing required documents, an unanalyzed form, and others — produce a 0-100 score. Anything scoring above 50 ("high" or "critical") is routed to a manual queue before a browser session ever opens, and a notification fires for that same band. Items that clear every check still wait for a person to approve the filled form before anything is submitted.
Verification pauses
Identity-verification challenges are left to a person. Detecting a verification challenge, or a page containing a phrase like "verify you're human", stops the run immediately, captures a screenshot, and waits for a person to resolve it and resume.
Draft approval is always a human click
A draft's only forward action in the wizard is Save, which writes it onto a pipeline item, not a submission. Moving a draft into AutoApply requires a person to click Approve or Submit in the Draft Queue — there is no code path that approves a draft without a person. An organization can set a confidence threshold so an approved draft above it skips a second, separate Submit click, but Approve itself is never something the system does on its own.
Agent-authored drafts are structurally blocked from submitting
An agent can generate a full draft with no person writing it, when an organization has opted into that. The code path that creates those drafts fails outright unless it marks the row pending review, and it never sets a submission timestamp — the review screen for those drafts can only dismiss one from the queue, never submit it.
Non-email outreach stops at a drafted task, not a send
LinkedIn messages, call scripts, and physical-mail letters are drafted by Claude from a contact's own record, then logged as a task for a person to send, place, or mail. There is no automated LinkedIn API call, no automated dialing, and no automated mail submission.

The actual per-stage configuration, one setting per capability

This is the real per-organization configuration schema, not an illustration — nine independent settings, every one off until an owner or admin turns it on. A writer or viewer account cannot change any of them.

Opportunity Discoveryauto_research_enabled — off by default
Probability Scoringauto_score_enabled — off by default
Draft Generationauto_draft_enabled — off by default, plus a confidence threshold (50–95, default 70) below which no draft is even generated ahead of time
Funder & Contact Monitoringauto_reputation_enabled — off by default
Relationship Builderauto_relationship_enabled — off by default
Deadline Predictionauto_deadline_prediction_enabled — off by default
Follow-Up Schedulingauto_followup_enabled — off by default
AutoApplyauto_autoapply_enabled — off by default, bounded by a nightly cap (10–400, default 50) on queued items even once on; every filled form still waits for a person's approval
Disaster Response Outreachauto_deploy_disaster_response — off by default; deploying a live outreach campaign is treated as its own explicit opt-in, separate from every other setting

Every agent decision gets a row a person can review

When any of the settings above is on and an agent acts without a person driving it in that moment, the decision is written to an audit trail: which agent made it, what it decided, its reasoning, its confidence score, the action actually taken, and whether that decision is flagged as requiring human review. A flagged row carries the reviewing person’s identity, the time they reviewed it, and their verdict — an actual record, not a log line nobody reads.

Four independent pause switches

Above every other check, AutoApply can be halted at four levels — platform-wide, a specific domain, a specific funder, or a single organization — and each one is checked before an item runs. Stopping one funder’s submissions doesn’t require pausing the whole platform, and a problem traced to one organization doesn’t require touching anyone else’s queue.

Stated limitations

An agent-authored draft still gets created and stored even though it’s structurally blocked from submission — a reviewer still has to actually open the Draft Queue and act on it. Turning on the drafting setting produces more items in a review queue, not fewer things for a person to look at.

The non-email outreach tasks (LinkedIn, phone, mail) track whether a person marked the task complete, not whether the message was actually sent, the call actually placed, or the letter actually mailed outside the platform.

FAQ

Is "human-in-the-loop" a marketing phrase here, or is it actually enforced in code?
It's enforced at specific, separately-gated points: a risk score above 50 routes to a manual queue before a browser session opens; a verification challenge pauses the run and waits for a person; a draft can only reach AutoApply through a person clicking Approve or Submit; and an agent-authored draft is structurally prevented from ever setting a submission timestamp. None of these are settings that can be silently disabled from the outside — they run on every item, every time.
Can we turn everything on and let it run without anyone looking?
Nine settings exist, one per capability (research, scoring, drafting, funder monitoring, relationship building, deadline prediction, follow-up scheduling, AutoApply itself, and disaster-response outreach), and every one of them defaults to off for every organization. Only an owner or admin can turn any of them on. Turning on drafting or AutoApply doesn't remove the approval gates above it — it only lets the earlier stages prepare work without someone manually starting each one. Nothing is submitted until a person approves it.
If an agent makes a decision, is there a record of it?
Yes. Every agent decision is written to an audit trail with the agent that made it, its reasoning, its confidence score, the action it took, and a required_human_review flag. Where a person has reviewed a flagged decision, that reviewer's identity, the time, and their verdict are recorded on the same row.
Who can actually halt AutoApply if something looks wrong?
Four independent pause switches exist — platform-wide, a specific domain, a specific funder, or a single organization — and every one of them is checked before an item runs, ahead of the risk engine and the verification check. An admin doesn't need to disable a whole organization's account to stop one funder or one domain.
Does this page apply to every feature on the platform, or just AutoApply?
This describes the gates in AutoApply, Draft Generator, and non-email outreach specifically, since those are the surfaces where an AI-produced output could otherwise reach a funder, a donor, or a contact without review. Research and scoring stages produce a feed or a ranked list for a person to act on either way, whether or not their own setting is on.
READ THE FULL MODEL
This page covers the gates. Trust and Governance covers the rest.

Security model, data handling, and the platform-wide governance page these gates feed into.

Read the Trust and Governance page

See a real submission clear these gates

Watch the risk engine, the verification check, and the approval click happen on a real application, not a diagram of them.

Walk through a real approval gateSee the full AutoApply page