An agency can receive working code and still be unable to support the client. The missing pieces are often ordinary: which account owns the number, how to change a setting, and what to do when the calendar connection expires.
A handover should make the workflow operable by the people taking responsibility for it.
What is a voice AI project handover?
It is the transfer of the information, access and evidence needed to run the agreed system. Code is one part. Configuration, test results, account ownership and support boundaries belong alongside it.
Agree on the package before development starts. Otherwise, both sides can finish the project with different ideas about what delivery means.
A review-only engagement also has a different handover from a build. Written findings do not imply that the reviewer repaired the agent or certified all of its production behavior.
Leave an account and ownership map
The map should identify the agency or client account that controls each service, who administers it, and how access can be recovered or revoked. It should not contain passwords or API secrets.
For a typical integration, inspect these entries:
| Asset | Handover question |
|---|---|
| Source repository | Can the agreed owner access the code and release history? |
| Phone number and carrier | Who controls routing and billing? |
| Agent deployment | Who can deploy, stop or roll back the service? |
| Model and speech accounts | Who sees usage and can rotate credentials? |
| CRM or calendar connection | Which permissions are granted, and how are they renewed? |
| Logs and stored records | Who can inspect them and manage retention? |
Account transfers and ownership terms need an explicit agreement. A working integration does not establish legal ownership by itself.
Deliver evidence that matches the acceptance criteria
For each agreed scenario, record the starting conditions, fictional input, expected result, actual result and supporting reference. Include failures and unresolved checks.
A useful handover entry might say that a service request was saved and visible to staff, while outbound email delivery remains unverified. That tells the agency exactly which responsibility remains open.
Do not hide an unknown result inside a passed checkbox. If the tester could not inspect the destination CRM, the report can establish what was sent but not necessarily what was saved.
My existing booking-confirmation article addresses the spoken promise. Handover evidence connects that promise to the records the agency will support after delivery.
Document changes someone can make safely
Explain where routine business settings live, which changes require deployment, and how to test each kind. Separate an office-hours edit from a change to integration permissions.
Include a deployment note with version identifiers and the known-good configuration. A recovery procedure should say how to stop an unsafe workflow and route calls to the agreed fallback, not simply instruct someone to redeploy.
For complex application layouts, a small map helps:
Phone carrier -> LiveKit deployment -> Business integration API
|
v
Client CRM
Agency support uses: account map + release note + acceptance evidenceAdapt the service names to the actual build. An attractive diagram with the wrong account boundaries is worse than a plain one that the support team can use.
Set the support boundary before the first client incident
Specify what happens after acceptance: the support period, response expectations, included changes and how additional work is approved. Include responsibility for usage bills and third-party incidents.
The agency-facing scope on my service page follows this approach. A handover review covers agreed evidence; repairs, load testing and ongoing support are separate when they have not been included in the scope.
Questions about agency handover
Does a handover report certify production readiness?
No. It describes evidence for a defined scope. Security, concurrency, language coverage and operational readiness may require additional checks.
Should every integration use accounts owned by the client?
Choose the ownership model deliberately. Some agencies operate managed accounts; others transfer the complete system. Document access, billing and exit responsibilities for the model you choose.
What should happen to temporary developer access?
Agree on what is removed, retained for support or replaced with a narrower role. Record the owner responsible for carrying out those changes.
Before calling a project complete, ask someone on the receiving team to locate the last test result and explain the fallback procedure using only the handover package. Their questions will show what the documents still need.