TKFollowUp Flowby Tech Khit

DM-03 · Small-business workflow demo

Every new enquiry gets a clear next step.

FollowUp Flow shows how a small service business can acknowledge customers, assign follow-up work and catch exceptions—without relying on memory.

Start the 10-minute demo See the business problem

Safe demo: fictional data, simulated email and SMS, no external delivery.

Workflow preview

New website enquiry

On track
JL
Jordan LeeHot-water replacement · Como
Priority
  1. 1
    Enquiry capturedWebsite form · 9:02 am
    Done
  2. 2
    Reply preparedAcknowledgement · ready
    Done
  3. 3
    Owner task createdCall back by 11:00 am
    Waiting
  4. 4
    Follow-up scheduledOnly if no reply · tomorrow
    Waiting
✓
Session duplicate check is activeThe same demo event cannot run twice in this browser session.
Under 1 minto prepare acknowledgement
1 ownerclearly assigned
Session-safeduplicate-event simulation
Visible recoverywhen a service fails

The everyday problem

Good enquiries get lost in busy work.

A simple, governed flow helps the owner respond consistently while keeping important decisions human.

01

Inbox memory

Requests sit across forms, email and phones with no single owner or due time.

02

Inconsistent replies

Customers receive different information—or nothing—depending on how busy the day becomes.

03

Silent failures

An automation error can be worse than manual work when nobody can see or recover it.

Interactive workflow lab

Choose a common small-business scenario.

Run the happy path, block a duplicate, then switch on an outage to see safe recovery.

DV-007 · Base demo DM-03

New enquiry follow-up

Acknowledge the customer quickly and give the owner a clear next action.

Ready to run
JL
Jordan LeeComo Property Care
Sample record
Trigger
Website form submitted
Request
Hot-water system replacement
Delivery level
N0 · Preview only
Source
FollowUp sample
1CaptureRecord and validate the trigger
2AcknowledgePrepare the approved message
3AssignCreate the owner task
4WatchSchedule a conditional reminder
5ResolveRecord the visible outcome
Email preview

Customer acknowledgement

Not sent
SubjectWe received your service request

Hi Jordan, thanks for your request about a hot-water system replacement. The team will review the details before confirming the best next step. This is not yet a confirmed quote or booking.

  • Classify the message as operational or commercial.
  • Record consent where commercial messaging requires it.
  • Identify the sender and provide valid contact details.
  • Include and honour unsubscribe or suppression requirements where applicable.
Human control

Owner task

Owner

Call Jordan and confirm access, urgency and property details.

DueToday · 11:00 am AWST
If still open

If the enquiry is still unreviewed tomorrow at 9:00 am, remind the owner.

Visible evidence

Audit history

This browser session
Demo ready

Safe sandbox loaded with fictional data.

What a scoped implementation can include

A reusable core, configured for the business.

This demo shows the pattern. Branding, rules, messages, data, integrations and permissions are confirmed after discovery.

A

Capture & validate

  • Website, CRM or approved system trigger
  • Required-field and consent checks
  • Session-level duplicate simulation
B

Assign & follow up

  • Approved acknowledgement templates
  • Owner task and due time
  • Conditional reminder rules
C

Monitor & recover

  • Visible status and audit history
  • Bounded retry and failure alerts
  • Human approval points
Pricing is confirmed after requirements.

Core: one approved trigger, message preview, owner task and visible result. Optional: provider connections, CRM integration, multi-step rules, durable audit, monitoring and support. No price or production promise is created by this demo.

Request a 30-minute discovery call
Demo boundaries · Version 0.3

Honest by design.