Skip to content
Sahil Swain
← All work
Prototype — no client relationship claimedPrototype

Customer Follow-Up & Review Workflow

Business automation demo

A small workflow that helps a business follow up with customers after a completed service and makes it easier for customers to leave genuine feedback.

What problem existed?

Small service businesses finish a job and then lose the thread: no structured follow-up, no consistent review request, no record of what was sent to whom.

Context / constraints

  • Prototype / business automation demo. Synthetic customer data only.
  • Not a client deployment and not affiliated with any specific business.

What was built

  • A deterministic workflow: service completed → customer recorded → follow-up scheduled → neutral review request → event tracked.
  • An event log that makes every step inspectable.

Architecture

  • A linear, inspectable state flow. Each customer moves through the same steps, and every transition is recorded as an event.

Scroll horizontally to inspect the diagram at a readable size.

Key engineering decisions

  • Every customer receives the same neutral review request.
  • Review requests are never gated or suppressed based on predicted sentiment.
  • Demo runs on deterministic synthetic fixtures — no backend, no real customer data.

Validation / tests

  • Workflow transitions are covered by unit tests, including an explicit assertion that no sentiment-based gating exists.

What is deliberately not claimed

  • Not a client project. No business is a client of this demo.
  • No revenue, conversion, or review-volume outcomes are claimed.

Interactive demo — runs directly on this page

follow-up-workflow · demoPrototype · synthetic data
  • Alex Morgan

    Home cleaning · Service completed

    1. Service completed (next)
    2. Customer recorded (pending)
    3. Follow-up scheduled (pending)
    4. Neutral review request sent (pending)
    5. Event tracked (pending)
  • Priya Nair

    Lawn care · Service completed

    1. Service completed (next)
    2. Customer recorded (pending)
    3. Follow-up scheduled (pending)
    4. Neutral review request sent (pending)
    5. Event tracked (pending)
  • Daniel Osei

    Window washing · Service completed

    1. Service completed (next)
    2. Customer recorded (pending)
    3. Follow-up scheduled (pending)
    4. Neutral review request sent (pending)
    5. Event tracked (pending)

Event log

  1. No events yet — advance a step.

Policy: every customer receives the same neutral request. Review requests are never gated or suppressed based on sentiment.

Source

  • Source repository — not yet publicly available

Want this kind of system built for your workflow?

Start a project