A small implementation you can inspect

From request text to a record you can review.

A hypothetical intake task: someone reads a request and copies the details into a list. This bounded example makes the transformation visible—and leaves the approval with a person.

Demonstration using sample data—not client work. Rules-based, not an AI model.

Working demonstration / synthetic dataRules-based, not AI

A request. A review. A deliberate approval.

Demonstration using sample data—not client work. Only the three bundled synthetic requests are available: no private data entry or uploads. Nothing is sent to external tools or saved as a persistent business record. Approved examples exist only in this page’s memory; reset or reload clears them.

Choose a synthetic request

Select a sample, review the extracted fields, then approve. The incomplete sample cannot be approved. Changing the selection discards the pending review, not already approved examples.

01 / Source text

Requester: Sample coordinator A
Organisation: Example workshop
Request: Arrange a laptop setup
Priority: normal

02 / Reviewable record

Review not started: Select “Review sample” to run the field rules.

Interactive controls need JavaScript. The source sample and explanation remain readable below.

03 / Approved examples in memory

No approved examples.

JavaScript is off. This demonstration reads labeled lines such as “Requester:” and “Request:”, trims their values and checks that both are present. A person reviews before approving. The third synthetic sample omits the requester, so approval is blocked. No record is created without JavaScript. You can still read the guide to connecting existing tools or explore workflow automation.

What actually runs

Simple rules.
Visible limits.

The parser reads lines labeled Requester, Organisation, Request and Priority, trims their values and maps them into fields. Requester and request are required. Priority accepts low, normal or high; other values fall back to normal. Unrecognized lines are ignored.

“Review sample” runs those rules. “Approve record” adds a valid reviewed example to an in-memory list, once per sample. It does not contact another system. The incomplete example demonstrates a blocked approval, not an automatic guess at missing information.

This is not a general email parser, an AI assistant, a production integration or evidence of client results. A real workflow would need agreed data access, permissions, error handling, duplicate rules, monitoring and a responsible person for exceptions.

Read: connect existing tools or buy a system?

Start with the handoff that gets in the way.

Describe the task without sharing passwords, private customer records or confidential documents.

Talk through your problem Explore workflow automation