Messaging Channel Handover Checklist to a New Owner

Changing the person responsible for a messaging channel is not giving someone else a password. It is transferring four things that live in different layers: the access (who can get in and with what role), the tags and contacts (how the database is organized), the quick replies and templates (what goes out in writing to the outside) and the active rules (what fires on its own when no one is watching). If any of those four layers is left half-done, the channel keeps working for a few days and then starts failing in strange ways: messages left unassigned, customers receiving a reply from an old campaign, tags that no longer mean anything.

This page is the checklist to tick off before, during and after the handover. It is meant to be used by the person leaving and the person arriving, in the same session, looking at the same screen. It does not replace the initial setup of a multi-agent inbox: it takes that as done and takes care of moving it from one set of hands to another without breaking it.

How to use this checklist

Go through the stages in order. Each item has a signal that it is OK: it is not enough to say "reviewed", you have to be able to show the result. If an item does not apply to your case (for example, you do not use campaigns), mark it as not applicable and move on; what you cannot do is skip it without having looked at it.

The handover is done with both people connected at the same time, not by email. The person leaving shows, the person arriving repeats the action. If something cannot be shown live, it is not transferred: it is documented, which is something else.

Stage 1: access and roles

This is where you define who can do what. The most common mistake is giving the new person the same username the departing person had: it works until you need to audit who changed a template, and then there is no way to know. Each person has to log in with their own username, even if it means more setup work.

• Check what role the new person has in each layer. On the messaging platform there are usually at least two levels: the one who handles conversations and the one who administers the account. Define which one they need and do not give them the highest level just for convenience.
• Review access to the WhatsApp number: who can change the display name, the photo, the business hours and the away message. This is a different access from the inbox.
• If the channel uses Meta's official API, verify access to Business Manager: the new person has to be able to see the WhatsApp Business account and the templates, not just reply to messages.
• Remove the departing person the same day as the handover, not later. An access that stays open "just in case" is the most common hole.
• Write down in one single place which accesses were transferred and which are still pending. If something cannot be transferred yet (for example, because it depends on a third party), it should be written down with a date, not left in anyone's head.

Stage 2: tags, contacts and database organization

Tags are the channel's operational memory. When someone leaves, the criteria leave with them: tags remain that nobody knows the meaning of, contacts marked with statuses that no longer exist and lists that were used only once. This stage is the most skipped and the most noticeable two weeks later.

• List all active tags and write next to each one what it means and who applies it. If a tag has no clear answer, delete it or merge it with another.
• Look for tags with people's names ("for Juan", "review María") or with old campaign names. They almost always remain and need to be cleaned up.
• Check whether there are duplicate contacts or contacts loaded with incomplete data. You do not need to clean the entire database during the handover, but you do need to know how many cases there are so you do not inherit a problem without warning.
• Verify which tags trigger something automatic (an assignment, a campaign, a reply). Those are the critical ones: if they are deleted, a flow breaks.
• If the channel has a linked contact spreadsheet, confirm that the new person can edit it and that they understand which columns are used for what.

Stage 3: quick replies and templates

Everything that goes out written to a customer has to be reviewed during the handover, because it is what the customer will keep seeing after the person who wrote it is no longer there. A quick reply with the name of someone who left, or with a price that changed, is a mistake that is discovered once the customer has already received it.

• Go through each active quick reply and confirm that the text is still valid: name of the person who signs it, hours, addresses, payment methods.
• Review the templates approved by Meta. The ones in use must still make sense; the ones no longer used should be archived so the new person does not trigger them by mistake.
• Verify who can create and send new templates. If the person leaving was the only one managing them, that permission has to be transferred to someone else before they leave.
• If there are campaigns scheduled for the future, list them with date and content. A campaign scheduled by someone who is no longer there is a time bomb.
• Confirm that the new person knows how a template is approved and how long it can take. Meta does not guarantee a different timeframe of up to 48 hours, so any campaign with a fixed date has to take that margin into account.

Stage 4: active rules and automations

This is the stage that brings the most surprises, because active rules are not visible when you look at the inbox: they are visible when something triggers. An auto-reply by schedule that was set up eight months ago is still working even if no one remembers it. The handover has to make the invisible visible.

• List all auto-replies by schedule and confirm that the hours are still the real ones. This is the first thing that becomes outdated.
• Review the assignment rules: which person or team each new conversation goes to, and what happens when no one is online.
• Verify the transfer rules: in which case a conversation is escalated and to whom. If the person who received the transfers is leaving, that rule is left pointing to nothing.
• Review the active and scheduled campaigns, with the date and person responsible for each one.
• If the channel has AI suggestions that learn from the team's real replies, keep in mind that the learning follows the criteria of whoever replies. A change of person responsible changes the tone of the suggestions over time: it is not a mistake, it is how it works, and it is worth letting the new person know.

Stage 5: testing and closing the handover

The handover does not end when the accesses have been transferred: it ends when a real message travels through the entire flow and reaches the right person. That test is what detects what the lists do not see.

1. 1Write to the channel from a number that is not in the contact database, during business hours.
2. 2Verify that the conversation is assigned to the right person according to the active rules.
3. 3Write outside business hours and confirm that the correct auto-reply is sent.
4. 4Explicitly ask to speak with a person and verify that the handoff reaches the new person in charge.
5. 5Check that the test conversation is labeled as a test and delete it afterward, so it does not mess up the statistics.
6. 6Leave in writing what was transferred, what is still pending and with what date. Have both parties sign it, even if it is a message in the same channel.

What to do when something fails

No handover goes perfectly. What changes the outcome is not avoiding errors, but being clear about what to do with each one. The time it takes to resolve them varies depending on the case, and depends on whether the problem is on your side or on Meta's side.

• If a message does not reach anyone: check the assignment rules first. It is the most frequent problem and it is almost always a rule that points to a person who has been deactivated.
• If a customer receives an old reply: find out where it came from. It could be an outdated quick reply, an archived template that was still being used or a scheduled campaign that nobody paused.
• If the new person cannot see something the previous one could see: it is a role problem, not a platform problem. Check the permission level before escalating.
• If the problem is on Meta's side (a template that is not approved, a number that is not verified): there is no guaranteed timeframe. File the case with the official documentation and let the new person know it may take a while.
• If more than a few hours have passed and the channel is not operating normally, escalate to support with the details of what was transferred and what failed. The more precise the detail, the faster it is resolved, although the exact time depends on each case.
• If the problem appeared after closing the handover: go back to the corresponding stage and review only that layer. Do not redo the entire handover for a one-off error.

Common mistakes this checklist prevents

If the channel runs on a platform with AI suggestions that learn from the team's real replies, there is an extra point for the handover: let the new person know that the tone of the suggestions will change with their own replies. It's not a failure or something that needs to be reset; it's how the learning is designed. What is worth doing is making sure the new person knows that for the first few weeks the suggestions will look more like the style of the person who left, and that this adjusts on its own with use. Wando works this way: the AI suggests and the team approves, and it learns from what the team actually replies.

Frequently asked questions about the handover

The questions that come up most often when the administration of a messaging channel is passed to another person, answered briefly.

• How long does it take? It depends on the size of the channel and how many active rules it has. What does not depend on size is the order: access, labels, replies and templates, active rules, and end-to-end test. Skipping a stage does not save time, it shifts it to the following weeks in the form of hard-to-trace errors.
• Can I transfer the channel without giving access to Meta's Business Manager? You can, but the new person will be limited: they won't be able to see or manage templates, and any campaign that needs a new template will depend on someone else. If the channel uses the official WhatsApp API, access to the Business Manager is part of the handover, not an extra.
• What do I do with labels I don't know the purpose of? Don't delete them at the time of the handover. Archive them or mark them as pending review and ask the person who is leaving before they lose access. A label you don't understand may be triggering an assignment or a campaign, and deleting it breaks a flow that isn't visible.
• How do I know the handover is complete? When a message sent from an external number goes through the full flow and reaches the right owner, both during business hours and outside them, and when there is a written record of what was transferred and what is still pending. The inbox opening is not enough as a signal.
• What happens with campaigns scheduled for the future? It's best to pause them until the new person reviews the content and the date. A campaign scheduled by someone who is no longer there may go out with old information or to a list that no longer applies, and the error is discovered when the message has already arrived.
• Do the channel's AI suggestions reset when the owner changes? No. If the platform learns from the team's real replies, the learning follows the criteria of whoever replies. With the change of owner, the tone of the suggestions adjusts to the new criteria with use. There is nothing to do, but it's worth letting the new person know so they don't interpret it as an error.
• What do I do if a customer receives an old message after the handover? Find the source before correcting: it could be a quick reply that wasn't updated, an archived template that was still being used, or a scheduled campaign that nobody paused. Correcting the text without finding the source makes the problem appear again. If the source is a template or a validation on Meta's side, the resolution time varies and there is no guaranteed deadline.