An exported workflow is only one part of a client handover. The client also needs control of the phone entry point, credentials, business rules, pending requests, and the process for repairing a failed booking.
Define the handover boundary in writing. State which assets transfer, which services remain hosted by the agency, and who handles future incidents. If a component cannot be exported, document how the client can replace or operate it without relying on someone's memory.
Package configuration and operating knowledge
Create an asset register containing the location identity, workflow names, calendar mappings, field definitions, notification recipients, and external service dependencies. Separate secrets from ordinary configuration. Transfer access through the approved account or secret-management process rather than placing tokens in a shared document.
HighLevel documents installation and authorized location selection in its OAuth guide. Use that supported authorization path when a new operator needs an independent connection. Confirm the intended account rather than treating a copied credential as ownership transfer.
Include the approved prompt, business rules, known limitations, deployment instructions, and an explanation of how action outcomes are recorded. The client needs to understand why a request is pending, not just where to find the transcript.
Rehearse the first incident before signing off
For a fictional dental practice, the acceptance exercise includes a new appointment request, a caller cancelling mid-conversation, a scheduling timeout, and an unavailable transfer destination. Staff inspect each resulting record and explain the next action without help from the agency.
| Handover item | Reviewable evidence |
|---|---|
| Phone routing | Client can identify the active destination |
| Calendar mapping | Test appointment lands in the intended calendar |
| Access ownership | Named client administrator can reconnect |
| Pending requests | Every unresolved item has an owner |
| Failure response | Client follows a written recovery procedure |
This exercise often reveals dependencies an export cannot show, such as an agency employee receiving failure alerts or a third-party subscription billed to a departing contractor.
Set a clear transition cutoff
Record when operational responsibility changes. Reconcile in-flight calls around that moment and decide who finishes them. Keep a short support window with defined contact hours and escalation routes if that is part of the agreement.
The tradeoff is preparation time. A bare export is faster to deliver, but it leaves the recipient unable to judge whether the workflow is functioning. Avoid claiming that an export recreates every vendor setting; verify the actual import and document manual steps.
For related ownership boundaries, use voice CRM integration as a review aid.
Questions about client handover
Should old credentials be revoked immediately?
Revoke departing access after replacement access is tested and the transition plan permits it. Track any remaining agency access explicitly.
What belongs in the final acceptance record?
List tested scenarios, resulting record identifiers, unresolved limitations, acceptance owner, and the date responsibility changed.
Can handover happen without moving accounts?
Yes. Ownership and operating responsibility can change within an existing location. The access review and witnessed operational tests still matter.