Coordinate customer arrangements before confirming the plan
For field and customer-service teams preparing customer-facing arrangements for planned work.
Fictional example: Alder Reach Utilities is planning a neighborhood water-main inspection. Use the handoffs below to align the known impact, access conversation, and customer message; the example is not approved local policy.
Match the conversation to what is known
Illustrative situations for deciding what to clarify or hand off.
- No interruption is expected The field coordinator shares the planned work window and the basis for the current expectation. Customer service uses only the approved message for that situation. If the expected impact changes, pause the commitment and return the question to the operational owner.
- An interruption may occur Do not turn an uncertain impact into a definite start time, duration, or restoration promise. Ask the relevant operational owner what can be communicated, then use the approved wording for the confirmed situation.
- Premises access needs clarification Customer service identifies the unresolved access detail and arranges a suitable conversation through the established route. If access cannot be confirmed, hand the question to the accountable operational role before treating the arrangement as settled.
Worked handoff: a shared entrance question
A coordination example—not a work order, appointment, or customer notification.
- For the fictional Alder Reach inspection, the field coordinator proposes a Tuesday coordination window of 09:00–11:00. The customer’s access note names a shared entrance but does not identify who can confirm that arrangement.
- Customer Service keeps the window provisional and asks the accountable property contact to clarify the entrance arrangement through the established route.
- The property contact confirms that a different team controls the entrance. Customer Service passes that ownership detail to Field and Asset Operations instead of treating the earlier note as confirmation.
- Field and Asset Operations takes the unanswered access question to the identified role. Until that role confirms the relevant details, Customer Service makes no appointment or service-impact commitment.
The handoff preserves one clear open question: which authorized role can confirm access for the proposed window?
Coordination reference
Authored example for orientation only; not a live work queue, source of record, or approved local procedure.
| Condition | Next coordination action | Accountable role |
|---|---|---|
| Service impact known | Share the confirmed impact with customer service; use the approved message for that situation. | Field and Asset Operations |
| Service impact uncertain | Hold impact or timing commitments; request clarification from the operational owner. | Relevant operational owner |
| Access confirmed | Record the arrangement through the established work process and align the customer conversation. | Customer Service |
| Access unresolved | Identify the open access question and hand it to the accountable operational role before confirming an arrangement. | Customer Service with Field and Asset Operations |
Who owns each part of the coordination
Role-based responsibilities in the fictional example. Use the organization's established correction and escalation routes; no individual contact is implied.
Keep commitments within confirmed boundaries
For regulated, safety-critical, or sensitive questions, use current domain-owner-approved local material. This page does not establish policy, entitlement, local applicability, or an operational approval.
Do not promise a service impact, appointment, access exception, or outcome until the accountable team has confirmed the relevant details. When a question remains open, state what is unknown and route it through the established escalation path.
Content ownership: Field and Asset Operations owns this fictional example. Send a guide correction through the established operations route, naming the arrangement or reference that needs clarification.