Treat agency work as a temporary operating arrangement. The handoff is complete when another team can recover the audience logic, messaging decisions, working process, data, and campaign assets without asking the agency to explain them again. A document alone does not keep messaging usable. The receiving team has to keep using the value proposition in its own work, or the reasoning behind the message fades.
Start with an ownership map
Decide what must survive the relationship and who controls it after the work moves in-house. Write the scope down before launch, while both sides still agree on what the work includes.
Organisational memory includes company or team-specific material such as internal documents, policies, shared knowledge bases, CRM data, and proprietary datasets.1 Use that as the scope for the retention plan. Cover the material itself, the decisions behind it, and the place where the receiving team will find it.
Define data ownership within the team before the campaign produces more records.2 Add an owner and a transfer action for each audience file, response record, campaign asset, and working document. Record where each item lives, who may change it, and what the receiving team can reuse.
The service level agreement should address intellectual property and ownership of designs, files, and ideas after the agreement ends.3 Put those terms beside the delivery requirements so the exit conversation is not the first time anyone asks who controls the work.
Separate three types of knowledge in the ownership map:
- The material the agency delivers, such as assets, specifications, insights, lists, and message files.
- The decisions that explain why the agency chose an audience, message, workflow, or response path.
- The operating rights that determine who can edit, reuse, export, or retire each item.
The map is ready when it shows who owns each item and where the receiving team will retrieve it. A folder full of files without those answers is storage, not transfer.
Capture the working knowledge
Capture decisions while the agency is doing the work. Final files show what was produced. The working brief should show how the team uses those files and what to do when a contact responds unexpectedly.
For each call motion, document what the agent should say and do, including the first message.4 Define the goal of the call in the same brief.5
Document each response path separately. The brief should explain how to handle rescheduling requests, how to handle objections, and when the call should end.6, 7, 8 These details carry the agency's operating judgment into the next team.
Preserve the path used to access or generate the customer list.9 Include the inputs, filters, exclusions, and refresh process needed to reproduce the audience. If the campaign uses personalized fields, record the placeholders and the values that fill them when the call is triggered.10
During the transfer, ask the agency to explain each decision in plain language. Move to the asset handoff once the receiving team can describe the audience, message, and response path without reading from the agency's notes.
Transfer assets with their context
Inspect the handoff with the receiving team. Have them open the material, trace its origin, and test whether they can use it without the agency present.
Transfer design assets, specifications, and insights together.11 Apply the same standard to outbound campaign assets by transferring the copy, the rules for using it, the audience logic, the response handling, and the reasoning behind material that performed well.
Keep the ownership map beside the asset register. For each file, record the current owner, permitted use, source material, and person responsible for future changes. This prevents a later team from confusing access with ownership.
Use a short acceptance test before closing the transfer:
- The receiving team can locate each retained asset.
- It can explain why the audience and message were chosen.
- It can follow the response paths without reopening the agency relationship.
- It knows where new records and revised assets belong.
- It can identify the owner when a decision needs to change.
If one test fails, return that item to the handoff queue. Timely file delivery does not pass the test.
Preserve the operating details
Retention depends on the small configuration choices that shape a live conversation. These choices often disappear when teams transfer only the finished copy.
When automation is part of the motion, retain the configuration fields for the agent's name, voice, knowledge, and intake questions.12 The first message is required and is the first thing the agent says when a call is answered.13 Treat it as a controlled campaign asset, with its source, owner, and permitted edits recorded.
Use the conversational guidelines to define how the agent should handle the conversation.14 Keep the operating record with the workflow so the receiving team does not have to reconstruct it from call recordings.
Record the voicemail path in the handoff.15 The default Hang up option disconnects immediately.16 The Leave a message option plays a defined message and supports the same placeholder format.17 Also record what happens when a contact requests a human agent or the automated agent cannot resolve the query, since the call can be configured to transfer in those cases.18
Keep these details beside the campaign assets, where the team will use them. A separate archive may satisfy a transfer requirement while leaving the working process hard to find.
What not to do
- Define data ownership clearly within the team.2
- Resolve intellectual property and ownership of designs, files, and ideas before the agreement ends.3
- Include specifications and insights with the transferred assets.11
- A calling flow should not leave silence after pickup. Recipients often hang up when they hear it.19
- Have enough agents logged in to the call queue.20
Before the agency exits, have the receiving team pass the acceptance test, then approve the handoff. Keep one person responsible for maintaining the pack as the campaign changes.