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.
Four patterns cover most of the work that arrives in a team's shared places. Here's what each one looks like in practice.
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.
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.
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.
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.
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.
Lead intake · flow
→ Route
genuine → Welcome · else → End
→ Follow-up
→ Follow-up
Ends here
And add the next once the first one runs. Where it tends to start:
Accountants & bookkeepers →
Client documents filed per client and year, and answers to the questions that come back every season.
Webshops & retail →
Supplier invoices and delivery notes filed, and customer email answered from your own policies.
Consultancies & professional services →
Client intake, recurring requests, and cited answers for the people facing clients.
We run our own support, sales, and pilot signups on this exact loop, so it behaves the way we tell customers it does.
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.