White-label support needs a clear answer to who acts when the receptionist fails. A promise of “ongoing support” can hide disagreements about monitoring, client communication, business-rule changes, and third-party outages.
Define support scope around incidents and routine operations. Include failed actions, access loss, unavailable staff routes, usage questions, configuration changes, and vendor issues. Separate response time from restoration time.
Map each incident to an authorized owner
Technical staff may diagnose a failed write but lack authority to approve a dispatch or reconnect a client's account. The agency may own client communication while the client owns pending customer work.
Record coverage hours, alert routes, acknowledgment expectations, escalation, and what the service does outside coverage. Avoid guaranteeing recovery that depends on an external vendor or unavailable client administrator.
Work through a fictional Sunday outage
A client's CRM rejects writes on Sunday. The support plan allows technical triage and suspension of remote actions, but the client administrator must restore access. The agency coordinates the incident update, and the client's office handles urgent pending requests.
The agreement should identify those roles and degraded behavior before the incident. Otherwise, the developer may be expected to perform business operations while the client assumes the agency is monitoring every call.
| Support item | Boundary to document |
|---|---|
| Monitoring | Which signals are watched and when |
| Response | Who acknowledges and within what commitment |
| Recovery | Authorized actions and external dependencies |
| Customer follow-up | Client or agency operating owner |
| Routine changes | Included limits and change process |
Test the support path with a real rehearsal
Trigger a controlled fictional failure and verify alert delivery, access, decision authority, and queue recovery. A document that names an unstaffed inbox does not establish support readiness.
Broad support can make the service easier for clients to operate but requires staffing and commercial terms that reflect the responsibility. Narrow support is sustainable only when clients clearly own the remaining work and have usable procedures.
Review the boundary after material scope changes. Direct booking, payment, or multiple locations may add support responsibilities absent from a request-only service. See agency and developer roles for the responsibility map.
Questions about support scope
Does a response commitment guarantee a fix?
No. State both clearly and account for vendor, access, and business-approval dependencies.
Should prompt updates be unlimited support?
Define included maintenance and the threshold for new workflow scope rather than relying on an ambiguous promise.
What should clients receive?
Coverage hours, incident contacts, supported actions, degraded behavior, their responsibilities, known dependencies, and a practical route for unresolved work.