Taskpath
One governed loop · four kinds of work

Where Taskpath goes to work

Documents in a shared folder, email in a shared mailbox, signups from a form, and questions about your own policies. Each becomes a task. The AI does one step at a time, and a person approves what leaves the building or can't be undone.

The four patterns

Four patterns, one loop

Four patterns cover most of the work that arrives in a team's shared places. Here's what each one looks like in practice.

Process

Documents filed the way your archive already does it

Drop a document in a shared intake folder. Taskpath reads it and proposes a name and a folder, learned from the archive you already have. A person approves; anything unusual waits with a reason.

Invoices and receipts

Read, named and routed to the right supplier or year folder. The fields it uses are quoted from the document itself, so a guess can't slip through.

Letters and contracts

Filed next to the documents like them. When it isn't sure, it says why and leaves the decision to a person.

Forms and system events

Form submissions and signed webhooks become tasks with the key fields pulled out, ready for the next step.

Respond

Email answered with a cited draft, sent when you approve

Support and sales mail lands as a task with a reply drafted from your own knowledge. You approve or edit it, and it goes out from your own mailbox, in the same thread.

Support questions

Refunds, delivery dates, how something works: a draft that cites the policy it comes from.

Sales inquiries

Pricing, fit and availability, answered from the sources you approved, ready for a person to send.

Shared mailboxes

Every message to info@, hello@ or orders@ becomes a task with an owner, so nothing gets lost in the pile.

Reach out

A new lead answered, and the follow-up handled

Outreach only to people who asked for it. A person approves every message, and the follow-up stops the moment someone replies.

Welcome and follow-up

A signup is screened for spam, sent to your CRM, and a welcome is drafted for approval. If there's no reply in three days, a follow-up is drafted; a reply cancels it.

Brief

Cited answers from your own knowledge, or an honest “I don’t know”

Point it at your documents and get answers with their sources. If the sources don't say, neither does Taskpath.

Team answers

“What’s our policy on X?” gets a cited answer from approved documents, or a plain “I don’t know”.

Prep briefs

A short, cited briefing on an account or a topic before a call or a reply.

Onboarding

New colleagues get grounded answers instead of interrupting senior staff.

Nothing is a black box

See exactly what each workflow does

Every automation shows its own steps: the sources it reads, the branches it takes, and, in amber, exactly where it stops and waits for a person.

  • ✓ Readable by the people who own the process, not just engineers.
  • ✓ Human-approval steps are part of the flow, not a setting you can forget.
  • ✓ Describe a change in plain language; the flow is validated before it's ever active.

Lead intake · flow

  1. screen Screen

    → Route

  2. deterministic branch Route

    genuine → Welcome · else → End

  3. deliver Welcome ⏸ Waits for approval to send

    → Follow-up

  4. wait Wait ⏸ Waits (timer)

    → Follow-up

  5. deliver Follow-up ⏸ Waits for approval to send

    Ends here

Built for

Most teams start with one process

And add the next once the first one runs. Where it tends to start:

Every use case, safely governed

The same guarantees apply to all of it. They're built in, not settings.

We run our own support, sales, and pilot signups on this exact loop, so it behaves the way we tell customers it does.

Which one fits your team?

We take on a small number of pilots, one process at a time. Tell us the one you'd start with, or see how it works first.