Lumenos Flow

Automation that can reason.

If/then pipes break on real customers. Flow puts AI steps inside your automations — qualifying, extracting, and deciding — so a form submission becomes a booked meeting and an invoice without anyone copy-pasting.

TriggerForm submitted
AI stepQualify lead
Qualified
CRMCreate lead
MessageSend WhatsApp
CalendarBook meeting
PaymentsCreate invoice
Not qualified
CRMTag for nurture

The difference

AI steps with structured outputs, not chat in a box.

Every AI node takes your rubric and returns typed, predictable data the rest of the workflow can branch on. You define the schema; the model fills it.

// AI step: qualify lead — output schema
{
  "qualified": true,
  "budget": "PKR 5M+",
  "timeline": "this quarter",
  "language": "roman_urdu",
  "reason": "Named a block, asked
             for payment plan"
}
  • Qualify — score leads against your own rubric, not a generic one
  • Extract — pull names, dates, and preferences out of free-text replies
  • Classify — detect intent, language, and sentiment; route accordingly
  • Compose — draft messages from context, with optional human review
  • Branch — "if the reply sounds angry, route to a human first"
  • Guardrails — token and cost caps per workflow, PII redaction in logs

Connections

Plugged into the tools you already run.

WhatsApp-native, with regional payment connectors — and first-class integration with Estate and Pulse, so top-of-funnel automation lands in the system that owns the relationship.

WhatsApp Business Flow Forms Webhooks Email & SMS Google Calendar Calendly Google Sheets Slack Stripe JazzCash · EasyPaisa HTTP / REST Lumenos Estate & Pulse

Execution engine

Boring where it should be boring.

The creative part is the AI. The execution underneath is deliberately unexciting: queued, retried, logged, and idempotent.

Retries with backoff

Failed steps retry automatically; persistent failures land in a dead-letter queue with alerts to the owner.

Idempotent runs

Idempotency keys mean a webhook retry never double-charges an invoice or double-sends a message.

Full run history

Every run keeps its trigger payload and each step's input, output, and duration — replayable from the failed step.

Waits that understand time

Delay two hours, wait until business hours, or pause until a payment webhook arrives — then continue.

Human approval steps

Route sensitive actions through a manager's approval inbox before the workflow proceeds.

Versions & rollback

Edit drafts safely while the published version keeps running. Roll back in one click.

Get started

Form to invoice, in one flow.

Start from a vertical template — real estate, clinics, agencies — and be live in hours, not weeks of development.