Own project · technical work sample

From a conversation to an editable enquiry.

A workshop example showing how a visitor can describe a request, review the extracted details and decide whether to hand it over. Built and demonstrated as a CYVARIX project, not work for a client.

The problem this example explores.

A free-form message may contain useful details in several places. This example brings vehicle, concern, urgency, requested timing and contact together in a reviewable summary. The person can correct it before handing it over.

These are design goals, not measured customer results. No revenue increase, time saving or conversion lift is claimed.

Three real views of the flow.

Screenshots captured on 27 October 2026 using fictional data. The interface is in German; the captions explain each step.

**The initial intake** The demo begins with a clear message field and five empty information groups. People can use an example or describe their own fictional enquiry.

**Correction before handover** The test name was changed to Alex Muster. The email address and the other captured details remained in the summary. The send action stays separate from correcting a field.

**The separate email-format preview** This is the public email-format preview, with its own fictional sample data. It is not an inbox receipt from the preceding screenshot and opening it sends no email.

How it is put together.

Interface: TypeScript, React and Next.js provide the dialogue, summary and correction controls.
Server processing: a Next.js API route processes the input and checks structured data. The conversational path uses an AI provider.
Review: the visitor checks the captured values. A complete summary alone does not trigger the email handover.
Handover: explicit confirmation uses the server-side webhook path to n8n and the configured Microsoft 365 email workflow.

The demo runs on Vercel; the public CYVARIX website is deployed separately. Service credentials remain on the server. This description is not a security certification.

What has actually been checked.

On 27 October: enter the built-in fictional example, review all five groups and change the name while keeping the email and other details.
On 27 October: open and inspect the separate email-format preview. No email was sent during this screenshot session.
On 26 October: a corrected demo enquiry was received and checked in the CYVARIX mailbox. The existing video describes that earlier run.

Those checks demonstrate specific observed flows. They do not establish permanent deliverability, customer acceptance, physical-device coverage or a client deployment.

Earlier 60-second screen recording, German labels →

A smaller version may be enough.

For a real first project, a conventional form with agreed fields, validation and one email destination may be the right fit. The AI conversation, workshop-specific logic and other integrations are not automatically included.

Describe one concrete task →Scope and collaboration details →