Installation & Activation
Close the gap between interest and activation.
Envoy can support request handoff, capacity-aware coordination, rescheduling and exception follow-up within agreed provider workflows. Installation and activation authority remain with the applicable provider and responsible installer.
Where this capability fits.
Who it is for
Providers and operations teams connecting acquisition to provider or installer fulfillment.
The problem
A submitted order may still require qualification, scheduling, access or construction. Counting that order as an activation hides fallout and sets expectations the installer has not accepted.
The decision
Define responsibilities and evidence at every handoff after customer interest.
How the workflow operates.
Request → capacity review
Confirm the provider has accepted the request and identify capacity, site-access or construction constraints.
Preference → confirmed appointment
Collect an appointment preference only where appropriate. A preferred window is not a confirmed appointment; confirmation must come from the provider or installer.
Reschedule → recover exceptions
Record no-access, customer changes, capacity holds and other fallout accurately. Recovery must respect consent and cannot manufacture completion.
Completed install → reconciled activation
Retain installer completion evidence separately from the provider-confirmed activation record. Keep unresolved mismatches open.
Evidence before claims.
Provider order acceptance, appointment confirmation, installer completion and provider activation records support distinct states. Submitted orders are not activated customers, and installation does not by itself prove billing or commission eligibility.
What gets measured.
Review handoff acceptance, time in pending states, rescheduling, completion, exceptions and provider-confirmed activations. Use agreed definitions and observation periods rather than promising an installation date.
Supporting Envoy OS capabilities
In development. Confirm current workflow scope with Envoy; these labels describe the intended supporting capabilities.
Define the next handoff.
Start with the requirement and evidence available. Do not send confidential customer records in an initial inquiry.