Request
Received- Current handler
- Approved source
- Next action
- Assign owner
- Due state
- Now
How the response layer works
Follow one request from arrival to human closeout.
LumioForge gives an approved estimate or inspection request an owner, a visible next action, bounded follow-up, a reply stop and a named human handoff. Exact sources, timing and touch count stay environment-specific.
One estimate requestIllustrative workflow — not customer data
Lifecycle resolvedOwner
Assigned- Current handler
- Office lead
- Next action
- First response
- Due state
- Ready
First response
Sent- Current handler
- Approved workflow
- Next action
- Watch reply state
- Due state
- Complete
Follow-up
Eligible- Current handler
- System handler
- Next action
- Follow-up 2
- Due state
- Tomorrow
Homeowner reply
Received- Current handler
- Supported reply path
- Next action
- Stop downstream outreach
- Due state
- Immediate
Stop
Stopped- Current handler
- Follow-up 2
- Next action
- No automated send
- Due state
- Resolved
Human handoff
Taken over- Current handler
- Assigned rep
- Next action
- Continue conversation
- Due state
- Action now
Two views of the same request
Your team sees the work. The workflow enforces the boundaries.
The visible operating view and the behind-the-scenes rules stay connected, so an automated action never becomes a substitute for a named owner.
What your team sees
- Owner
- Current handler and named backup
- State
- Received, sent, replied, stopped or closed
- Next action
- What needs to happen and who takes it
- Exception
- A visible alert when the path cannot continue safely
What runs behind the scenes
- Eligibility
- Only the next approved touch can proceed
- Stop rule
- A supported reply, pause or takeover changes state
- Fallback
- Unavailable ownership routes to a named backup
- Closeout
- Booked, closed, paused or not-interested ends intentionally
The decisive state change
A homeowner reply stops eligible downstream follow-up.
On a supported, tested reply path, the reply changes the workflow from automated follow-up to a human-owned conversation. It does not start a disconnected thread or allow the next scheduled message to proceed as if nothing happened.
Illustrative workflow - not customer data
- Before replyFollow-up eligibleOffice backup owns next touch
- Reply receivedStop appliedDownstream outreach is no longer eligible
- Human handoffAction neededAssigned rep continues the conversation
Illustrative workflow - controlled exception
- Required action
- First response Absent
- Current owner
- Office lead Unavailable
- Backup
- Office backup Assigned
- Alert
- Human review Needs attention
Exception path
Missing action becomes owned attention, not silent failure.
When an approved action cannot complete, the intended path is to record the attempt, keep retries bounded where they are safe, and assign the recovery step to a person or backup.
See reliability and control statesWorkflow FAQ
The operating boundaries in plain language.
Does every request source work?
No. Each source needs authorized access, reliable fields, testable reply behavior and maintainable failure handling.
Can a person pause or take over?
The intended workflow gives authorized users explicit pause, reassignment and takeover paths for the tested connection.
Does every company use the same timing?
No. Timing, touch count, owner coverage and supported channels are configured and approved for the company environment.
A clear next step
Start with the public routes, then inspect the response path.
The Request Map documents visible estimate and inspection routes without claiming to know what happens inside your team. Reliability explains the controls behind a supported workflow.