Home services
When an inquiry arrives, is the expected owner visible?For owner-operated and small service teams handling estimates, appointments, and service handoffs.
Illustrative Managed CORE workflow record
IK-0427 Illustrative workflow Not customer data
- Evidence
- Intake status visible
- Custody
- Routing owner documented
- Human action
- Response confirmation open
System status Human response pending
The responsibility boundary
Visibility can clarify the handoff.
It cannot complete the human action.
Managed Lead Intake uses the Managed CORE method to separate what the system can show from what an IsoKelvin operator or client team still needs to confirm. That distinction is the operating model—not a disclaimer added afterward.
System evidenceIntake, route, status
Observable states inside the managed workflow.
Human responsibilityConfirm, respond, decide
Actions owned by the operator or client team.
Workflow anatomy
One continuous path.
Four distinct states.
The system makes the intake path easier to inspect. Custody becomes explicit. The final state remains open until a person confirms it.
- 01System evidence
Intake
A submission enters the managed workflow.
- 02System evidence
Routing
The configured route is visible for review.
- 03Custody
Owner
A routing owner is documented.
- 04Human action
Next action
The team confirms what happened next.
Illustrative workflow record
Inspect the intake state, custody, and next action.
This semantic example shows the fields an operating review uses; its synthetic values are not customer data.
Managed CORE Lead workspace
IK-0427 Current review state
Illustrative estimate request
A visible owner. An intentionally open response state.
- Source
- Public intake path
- Captured
- Today 09:42
- Routing owner
- Client operations Seat 1
- Human state
- Confirmation open
System evidence
What the workflow can show
- Intake acceptedPublic intake path
- Notification status recordedProvider delivery not verified
- Routing configuration visibleManaged CORE route
- Routing owner documentedTeam confirmation required
- Human response not yet confirmedReview remains open
Operating contexts
Fit begins with the handoff—not an industry label.
Compare three intake patterns by entry path, custody point, client workload, and the operating question a pilot would review.
B2B services
Can the team see what entered the workflow and how it was routed?For teams where demo or contact inquiries move through a shared inbox, operating queue, or named sales handoff.
Paid traffic
Does the captured inquiry context reach a visible owner?For teams sending paid traffic to a public landing page and reviewing the source context captured by its form.
Managed Lead Intake pilot
Know what is delivered.
Know who owns the work.
The operator-led pilot applies Managed CORE to one agreed public intake path. It produces a configured workflow, visible operating states, documented custody, and review notes—not a CRM, SaaS product, automated qualification or routing service, or replacement for the client's response and downstream systems.
Pilot deliverables
- One agreed public intake path configured into CORE
- A lead inbox view of received intake and available status
- A documented route and accountable client owner
- A launch verification record and operating-review notes
Responsibility split
- IsoKelvin provisions CORE, coordinates intake setup, configures the agreed route, and facilitates reviews
- The client approves the intake path, routing decisions, and accountable owner
- The client confirms human responses, qualification, exceptions, and downstream action
Month-one decision gate
- Review setup, launch verification, and operating observations during month one
- Continue only if the intake path is inspectable, route and owner stay documented, and open exceptions have a named next action
- Continue under separately agreed scope and terms; otherwise pause or end the pilot with no automatic continuation
Review cadence
Setup. Launch check. Month-one decision.
Each review has a distinct purpose: approve the path and owners, verify observable states with synthetic data, then assess the month-one success gate.
- 01
Setup review
IsoKelvin and the client confirm the first intake path, captured context, route, accountable owner, and human-confirmation procedure.
- 02
Launch verification
A synthetic test checks intake acceptance, inbox visibility, the stored route, documented ownership, and the status the system can show.
- 03
Month-one review
IsoKelvin and the client review operating observations and exceptions, then choose to continue under agreed scope and terms, pause, or end the pilot.
Managed Lead Intake review
Name the first intake path.
Then test the operating fit.
A fit review confirms the proposed path, responsibilities, and decision gate before any pilot scope or commercial terms are agreed.
Intake review request
Share the intake path you want reviewed.
The existing IsoKelvin request flow is retained here. Initial review does not require passwords, CRM administrator access, or customer lists.
The request shares context for review. Fit, timing, scope, responsibilities, and any next step are confirmed separately.