For software and AI agents Taskriz for Software Companies →

Your software does the work. Taskriz gets what it needs from people.

The human interaction layer for business software and AI agents (HITL).

Software and AI agents automate more of the work every month. But the work still stops for people outside your system: the customer who has to confirm, the contractor with the photos, the supplier with the price, the manager who signs off.

Taskriz reaches them, gives them a screen made for exactly what’s needed, and returns their answer to your software as structured data, so the workflow can carry on.

No portal. No app. No account.

Watch how it works (50 sec)

Free to start, with 500 requests a month. No credit card. The people you ask never pay.
Talk to us about a pilot

A Taskriz request to a contractor, Hot Water Job: the gas hot water at 14 Smith St, Richmond won’t light; a map of 14 Smith St with Copy Address and Open in Maps; a Choose Photo button, a box for what they found, a choice of Thu 5, Fri 6 or Mon 9, and access by lockbox, tenant in or call me, then Send.
A job system needs the plumber’s day, access and a photo. Taskriz sends him this, and the answer goes back to the job.
  • Open API and MCP server
  • Live since October 2026
  • Requests sealed to the devices of the person you ask
  • An Australian company
  • Free for the people you ask, always

Reaches the people your software needs through

  • Any browser, phone or computer
  • Email
  • Text message (Australia and the US)
  • ChatGPT
  • Claude
  • Google Chat
  • Slack
  • Your own website

Your software makes one call. Taskriz reaches each person on whatever they use, and the answers come back the same way.

The Human In The Loop Flow

Wherever the work starts, Taskriz reaches
the person and brings the answer back.

How a request flows through Taskriz Work starts in an AI chat, on a website, in Slack, in Google Chat or in the Taskriz app, and each goes into an AI workflow. The AI workflow sends Taskriz a request. Taskriz sends it to the person by email, text message, on a website or in the app. Their answer comes back through Taskriz to the AI workflow as structured data. WHERE WORK STARTS YOUR AI WORKFLOW AND TASKRIZ THE PEOPLE IT NEEDS Request Answers as data AI chat Website Slack Google Chat Taskriz app Email Text message Website App AI workflow Taskriz Answers come back the same way How a request flows through Taskriz Work starts in an AI chat, on a website, in Slack, in Google Chat or in the Taskriz app, and each goes into an AI workflow. The AI workflow sends Taskriz a request. Taskriz sends it to the person by email, text message, on a website or in the app. Their answer comes back through Taskriz to the AI workflow as structured data. WHERE WORK STARTS Request Answers as data AI chat Website Slack Google Chat Taskriz app Email Text message Website App AI workflow Taskriz Answers come back the same way
Work starts in an AI chat, on a website, in Slack, in Google Chat or in the Taskriz app, and each goes into an AI workflow. The AI workflow sends Taskriz a request. Taskriz sends it to the person by email, text message, on a website or in the app. Their answer comes back through Taskriz to the AI workflow as structured data.

How it works

See a request from start to finish.

Northside’s job system needs the plumber’s photos and notes before it can close a job. Taskriz sends Sam the request, Sam answers from his phone with no account or app, and the answer comes back to the job system as structured data. The job system is an illustration; Sam’s request and answer are recorded in Taskriz.

Fifty seconds, no sound: the captions tell the story.
Read the captions
  1. Your software automates the work. Then it needs something from someone outside the system.
  2. Northside’s job system needs photos of the old and new heater, and the plumber’s notes, before it can close the job.
  3. Taskriz sends Sam the plumber a request made for this job, with the address on a map.
  4. Sam answers on his phone: two photos and a note.
  5. The answer comes back as structured data, and the paused job carries on.
  6. Not just maintenance: quotes, approvals, scheduling, documents and decisions.
  7. Any software or AI agent can hand Taskriz the human step, and get the answer back.
  8. Embed human interactions. Not the complexity of building them. The human interaction layer for business software and AI agents (HITL).

The problem

Automation stops
when it needs a person.

Business software and AI agents keep needing something only a person outside the system can give: information, evidence, an approval or a decision. Those people don’t use your product, won’t log in to a portal, and shouldn’t need an account to answer.

  • “Photos and access details before the repair can go ahead.”
  • “A price and a delivery date from the supplier.”
  • “The customer’s confirmation of the booking.”
  • “The owner’s approval of the quote.”

Today that step leaves your product as a call, a text or an email. The workflow waits, and when the answer comes, someone has to read it and type it back in.

Three steps

Reach the person. Give them the right screen.
Return the answer as data.

01

Reach the person where they are

Your product or AI agent asks in plain words, with a line of context, through the API or the MCP server. Taskriz reaches the person by email, text message, Slack, Google Chat or the Taskriz app, under your customer’s business name.

02

Give them the right screen

Taskriz designs the request for this one job: a map of the address, a camera for photos, a calendar, a choice, a box for the price. Or send your own interface. They answer on their phone or computer, with no app and no account.

03

Return the answer as data

Each answer comes back matched to its question and to your job, by webhook, WebSocket or MCP, whether it takes minutes or days. What happens next is up to your software.

A Taskriz request to a manager, Approve Quote: Northside Joinery’s quote for the Level 3 fit-out, $18,400 ex GST, delivered by Fri 20 Nov; a box for a note to the team, then Approve and Ask a Question buttons.
What the person sees: the quote, the amount and the date, then Approve or Ask a Question.
Request
job-1182-quote
Decision
Approved
Note
“Go ahead, but confirm delivery before the 20th.”
From
Priya Shah, Operations Manager
What your software gets back: each answer with its question, on the request it sent, ready for the workflow to continue.

Answers returned as data,
not messages for someone to retype.

Already have forms?

Keep them. Use Taskriz when you need
something from one person.

Forms are good at open intake: anyone with the link fills them in. Taskriz is for when your software needs something specific from a particular customer, contractor or supplier. It sits alongside your forms, not instead of them.

It goes to the person

Taskriz sends the request to a named person by email or text, and you know who has answered and who hasn’t. A form waits for someone to find the link.

Made for that moment

Each request is built from what you already know, such as the booking or the job, with only the questions that matter and the details filled in. Nobody builds or maintains a form for each case.

Answers come back structured

Free-form answers arrive as text someone has to read and re-enter, and that’s where ingestion errors creep in. Taskriz answers come back as typed fields: a real date, a number, a choice from a list.

It carries on

Your software can send the next request to the same person, on the same thread, based on their answer, days later if needed.

One capability, many workflows

One interaction layer. Many workflows.

Quotes

“Send us a price for the Level 3 fit-out.”

Your product asks a supplier for the price, a delivery date and the quote itself, in one request, and gets all three back.

Approvals

“Approve the quote.”

The owner or manager sees the quote, the photos and the reason, then approves or asks a question. A real decision, with the context to make it, not a bare button.

Scheduling

“Which day can you come?”

A contractor picks a day and says how they’ll get in. A customer who can’t make Tuesday gets the next times and picks one.

Documents and evidence

“We need your insurance before Monday.”

Certificates, compliance documents and before and after photos, from the file picker and camera in the request.

Decisions

“Can you take this job Thursday?”

Offer work to a subcontractor with the address, photos and the time, and get a yes or no back, with the price.

Information and confirmations

“Confirm the address and who’ll be on site.”

A tenant confirms access; a customer confirms the details. Complete the first time, in a form that can’t come back half filled.

Build or embed

Embed human interactions.
Not the complexity of building them.

Drawing a form is the easy part. The work is everything around it: getting the request to someone who has no account with you, by the channel they actually read; keeping it private on the way; holding your workflow’s place while the person takes a day to answer; and handing everything back as data. Each piece is small. Together they are a product, and every team that needs people in its workflow ends up building it again.

  • A form for every kind of request
  • A portal for customers, contractors and suppliers
  • Email, text message and chat delivery
  • An answer screen that works on any phone or computer
  • Encryption to the people it’s for
  • Deadlines, after which a request closes
  • Delivered, read and answered receipts
  • Answers, photos and files back as data

Taskriz is that part, as a service your product calls,
so your team stays on what makes your product different.

How you connect

Connect it the way your product works.

The REST API

For any product or workflow.

Send the questions in plain words, or your own interface, with photos and documents if you need them. Answers arrive as events, by webhook or WebSocket, each with the id you gave the request.

Read the Docs ›

The MCP server

For AI agents.

Connect your agent to the Taskriz MCP server and it can create requests itself, wait for the answer, and carry on with what came back.

Taskriz for Developers ›

Claude and ChatGPT

For the people using them.

Connect Taskriz once, then ask in plain words: “Ask the electrician which day suits for the inspection.” The AI designs the request, sends it, and reports the answer.

How to connect ›

Works with

  • Claude
  • ChatGPT
  • Microsoft 365 Copilot
  • Slack
  • Google Chat
  • Any system, through the API

Human in the loop (HITL) for AI agents

Human in the loop is more
than an Approve button.

Human in the loop (HITL) usually means an agent pausing for someone on the team to click Approve. But the person an agent waits on usually isn’t in its chat: a customer, a contractor, a supplier, a manager on the road. Taskriz gives your agent a way to reach them, wait for the answer, and carry on with what came back.

Taskriz doesn’t make the decision or take the next action. It gets the person’s answer to your agent or your software, which decides what happens next. Read why an Approve button isn’t enough ›

Built to be trusted

The business’s name on it.
The people you ask in control.

The business’s brand

Each request carries the name and logo of the business asking, with its own footer and links, so the person knows who it’s from.

Private by design

Requests are sealed so only the devices of the person you ask can open them, and notices never contain what was asked.

They stay in control

Anyone you ask can say no, or stop a business reaching them, at any time. That trust is why they answer.

Who’s behind it

Taskriz is made by Appeggio, an Australian company founded by James Ladd after four decades of building software. About us · Security

Security

Personal details stay private,
end to end.

Many form tools store answers where they can be read, and copy them into notification emails. Taskriz doesn’t.

Encrypted to their device

Each request is encrypted end to end to the person’s own device, with keys created on that device, and stored that way, so it opens only there.

Sealed before it leaves

Their answer is encrypted on their device. Taskriz opens it only to check it and hand it to your software; it’s never stored or logged readable.

Nothing personal in the notice

The email or text Taskriz sends never contains the request or any personal details, just a link.

Strong, standard cryptography

HPKE (X25519, AES-256-GCM) with a fresh key for every message, Ed25519 signatures, storage encrypted at rest with AWS KMS, and TLS on every connection.

Not building software?

Businesses use Taskriz directly too.

Use the Taskriz app in your browser now, on any phone or computer; the iPhone and Android apps are coming. Ask anyone from it in plain words, or from ChatGPT or Claude, and put a request box on your website. No developers needed. Get Taskriz › · Website Requests › · For property managers ›

Pricing

Start free. Pay as you grow.

Free

Try Taskriz with your own Agent.

$0 forever

  • 500 requests a month
  • Up to 10 different people reached
  • 1 Agent
  • 20 text messages a month

Builder

For developers shipping an Agent.

US$29 a month

  • 5,000 requests a month
  • Up to 100 different people reached
  • Unlimited Agents
  • 100 text messages a month

Business

For teams and growing products.

US$99 a month

  • 50,000 requests a month
  • Up to 1,000 different people reached
  • Unlimited Agents
  • 500 text messages a month

Software companies

Embedded in your product.

Per request completed

  • A pilot with one of your customers
  • Priced per completed request
  • One integration for every client you connect
Talk to Us

Every plan includes the API, the MCP server and the plugins for Claude and ChatGPT. Each person you send a request to counts as one request; their answers, photos and files are free. Text messages are included while we launch. Less when billed yearly, prices in AUD and EUR too, and bigger plans on request. See Pricing

Questions

What software teams ask.

We already have forms. Why Taskriz?
Forms are good at open intake. Taskriz is for when your software needs something specific from one person: it sends the request to them, made for that moment, and the answer comes back as typed fields your software can take in directly, not free-form text someone has to re-enter. Keep your forms; Taskriz sits alongside them.
What is human in the loop (HITL)?
Human in the loop, or HITL, means an automated workflow or AI agent pauses for a person and carries on with their answer. Taskriz is that human step for the people outside your system: it reaches them, gives them the right screen, and returns their answer as data.
Do the people we ask need an app or an account?
No. Requests open in the browser on any phone or computer, from an email or a text message, or right in Slack or Google Chat. There is nothing to install and no account to create. If they’d like the app, the Taskriz app works in the browser now, and the iPhone and Android apps are coming.
How does the answer get back to our software?
As an event, by webhook or WebSocket, or through get_replies on the MCP server. Each answer comes back matched to its question and to the id your software gave the request.
Does Taskriz make decisions or take actions?
No. Taskriz reaches the person and returns their answer. What happens next is up to your software or your agent.
Does it replace our workflow or orchestration?
No. Keep it. Taskriz is the step where your workflow needs something from a person, and it hands the answer back so the workflow can carry on.
Can we use our own interface?
Yes. Send your own interface as the request, or send the questions in plain words and Taskriz designs the screen.
What does it cost?
Start free, with 500 requests a month and no credit card. Paid plans start at US$29 a month (see Pricing). For software companies embedding Taskriz, we agree pricing per completed request in a pilot. The people you ask never pay.
Is the information safe?
Yes. Each request is encrypted end to end to the person’s own device, and their answer is encrypted on their device before it leaves; Taskriz never stores or logs either readable. The email or text they get never contains the request or any personal details. And everyone chooses who can reach them.

See Pricing · More questions

Ready when you are

Give your software a way to work with people.

Start with one step your product waits on today: the photo, the quote or the approval that still leaves your product as a phone call.

500 requests a month on the free plan. No credit card. The people you ask never pay.