Work

One system,
shown properly.

No gallery of mockups. Each project is told through the people who use it — the experience first, the machinery second. New case studies appear only when there's real work behind them.

CASE 01 — FLOWDIT · FLOWDIT.COM

One chatbot. Answers, bookings, and support — handled on the page.

Flowdit's visitors arrive with questions — about the product, about support, about booking time. The website now takes care of them directly: no waiting on email, no dead ends, no lost enquiries.

flowdit.com ↗

Context

Flowdit operates a WordPress website where visitors need answers, help, and a way to book time — without waiting on email back-and-forth.

Problem

Website visitors had questions but no instant path to answers, booking, or support. Every enquiry risked delay, repetition, or getting lost.

What visitors experience

  • Answers on the page — no waiting on email back-and-forth
  • Appointments booked inside the conversation
  • Support requests raised as tickets, with details taken once
  • Contact details collected politely — phone number, email
  • Returning visitors pick up where they left off

SystemWordPress · OpenAI · n8n · Zoho · Supabase

How it works

  1. Visitor talks. A question, booking request, or support issue lands in the chat.
  2. Conversation understands. The chat works out the intent and picks the route — answer, book, or file a ticket.
  3. Things get filed. The appointment or ticket is created; contact details are captured alongside.
  4. Nothing is forgotten. Every conversation is stored, so the next visit picks up where the last one ended.

Underneath

Built withWordPress / n8n / OpenAI / Zoho Bookings / Zoho Support / Supabase

Outcome

No verified metrics published for this project. The system is documented here for what it does — not for numbers it hasn't earned yet.

Next case study: yours?

This page grows one real project at a time. If your business runs on repeatable conversations — support, booking, intake — let's talk.

Next step

Let's build something intelligent.

Have a process like this? Describe it in a few lines — I'll reply with an honest take.

Let's Work Together How XIS thinks