Field Sales
The field is a major part of the distribution system.
Field activation is central to Envoy’s operating heritage. An engagement can coordinate territory planning, address prioritization, rep assignment and household education with digital demand and provider installation workflows. These are engagement requirements, not certification of every current control.
Where this capability fits.
Who it is for
Providers and field operations leaders who need accountable in-person execution inside an approved territory.
The problem
Conversations at the door can lose context at the next handoff. Without identity, address history, dispositions and consent records, follow-up can become repetitive or inappropriate.
The decision
Scope field execution as a major capability within the wider activation model.
How the workflow operates.
Territory → assignment → route
Confirm territory boundaries, representative qualifications and campaign authorization. Apply suppression before prioritization and routing.
Identity → interaction → disposition
Identify the representative and provider relationship, respect no-contact preferences, and record a factual disposition rather than inventing customer intent.
Follow-up → attribution → handoff
Follow up only where permitted. Associate the interaction with the address and source record, then hand an eligible request to the provider workflow.
Installation → activation feedback
Return provider-confirmed outcomes to the market review without publishing private representative rankings or customer records.
Evidence before claims.
Campaign-specific rep identity and authorization, consent, suppression checks, interaction evidence and provider outcomes are required. The current Verify a Rep experience is under review; a displayed result is not proof of identity or current provider authorization.
What gets measured.
Distinguish attempts, conversations, qualified requests and provider-confirmed activations. Review exceptions and complaints alongside conversion rather than rewarding volume without evidence.
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.