Illustrative workflow examples

An enquiry becomes a reviewable next step.

Input: “Please arrange a viewing of Property A next Tuesday. Contact me by email only.”

Output: property: Property A; requested day: next Tuesday; channel: email; open questions: exact date, time zone and available time. A draft reply asks for the missing details. No appointment is confirmed.

Acceptance: preserve the channel restriction, flag the relative date and require confirmation of availability before booking.

A small dataset becomes an exception report.

Input: CSV rows R1 and R2 both contain organisation Alpha and sales@example.invalid; row R3 has an amount of 100 but no currency.

Output: one proposed duplicate group retaining R1 and R2 as source references; R3 appears in a missing-currency exception list. No currency is guessed.

Acceptance: every input row remains traceable; duplicate decisions are inspectable; missing values are not silently filled. The address is a reserved example address, not a contact.

A transcript becomes a draft action list.

Input: “We can send the specification. We have not agreed a date yet.”

Output: draft action: send the specification; responsible person: needs confirmation; due date: not agreed; evidence: the quoted sentence. No price, acceptance or deadline is invented.

Acceptance: every action links to its source; unassigned responsibility and dates remain explicit; the participants approve the final outcome.

What these examples establish.

They illustrate the shape of a useful result and its review criteria. They do not demonstrate a live connector, production deployment, measured time saving or client endorsement. A project-specific demonstration should identify its data source, environment and actual limitations.

Define your first step.

Send a brief description of your process and the result you need. Please leave out confidential records. We will agree the data, permissions, scope, acceptance criteria and commercial terms before work begins.