China Agency Handover for Tourism Businesses

An overseas tour operator changes its China marketing agency. The incoming team receives the social account logins and a folder of finished posts. Then a traveler asks about a deposit, a published itinerary needs updating and nobody knows which version of the Chinese pickup instructions was approved.

In this hypothetical handover, the files arrived but the working knowledge did not. The business needs to keep serving customers while responsibility changes. The useful question is whether the next team can continue the sales and service work already in progress.

The short version: agree the handover around live customer work, editable content, the running Mini Program and campaign commitments. Give each item a receiving person and a practical acceptance check. Establish who answers enquiries during the change, verify the incoming team's access, and close the outgoing team's permissions when their work ends. Account ownership is only one part of continuity.

Start with the customer work that cannot wait

Set a clear point at which the incoming team takes responsibility for new enquiries. Also decide who finishes conversations already underway. A date in a notice does not settle a booking that began before it and continues afterward.

For a tour business, request a usable record of unresolved enquiries, quoted offers, confirmed departures, pending customer changes and refunds still requiring action. Each record needs enough context for the receiving person to act: what was agreed, what remains open and who is responsible. Keep a request for availability separate from a confirmed reservation.

Consider a traveler who has paid a deposit and asked to move a tour date. The receiving team needs the original booking reference, the payment record, the change request and its current status. A chat screenshot showing “we will check” leaves the next person guessing whether anyone contacted the operations team.

Our guide to moving Chinese enquiries into a booking system covers that connection. During a handover, check that agreed details have reached the system your delivery team uses. Transfer customer information through the authorized business systems and access needed for the task, rather than copying every conversation into a general marketing folder.

Separate account control from the ability to operate

Our account ownership guide covers registration and administrator control. Here, the additional task is to identify what each person can actually do after the change.

Ask the incoming publisher to open the content workspace, the customer-service person to locate an assigned enquiry and the developer to access the Mini Program project. An administrator login is not proof that those working permissions or files are available.

Create a short register naming each account or service, its business contact, the receiving person and the access they need. Include hosting, the booking connection, advertising tools and payment reporting where they form part of the arrangement. Record services supplied through the outgoing agency separately, so nobody mistakes a continuing supplier relationship for something already transferred.

Keep passwords and other secrets out of the general handover document. Use the business's approved method for access, and have the responsible person arrange any necessary credential changes. UK government guidance on protecting business accounts recommends reviewing access held by agencies and removing accounts or logins no longer needed. Apply that review to the actual services involved, without interrupting customer work through an unplanned access change.

Get the content needed for the next update

A folder of published images proves what appeared, but may not let anyone correct it. Request editable Chinese copy, the approved product facts behind it and the files needed to revise material included in the agreed delivery.

For a tour page, preserve the current itinerary, exclusions, pickup details and approved terminology. Mark which copy is published and which is an unfinished proposal. The incoming team should be able to find the version that customers currently see without searching a chain of messages.

For Xiaohongshu and Douyin, connect each published post with its caption, media files and product destination. Where video production is included, agree delivery of the available source footage, edits, subtitles and project files needed for future work. Establish any third-party dependencies or exclusions before assuming a video can be re-edited elsewhere.

Keep permissions alongside the assets they cover. Photographer credit, customer permission and a creator collaboration's agreed uses are different records. Receiving a file does not establish permission to reuse it in paid advertising or on another platform. Have the incoming publisher identify usable material and flag anything awaiting confirmation.

One practical check is a real seasonal change. Can the new team update a tour description and the related social copy using the delivered sources? If they still need the outgoing writer to identify the product or locate the approved wording, the content handover needs more work.

Check the Mini Program beyond its visible pages

A Mini Program that opens normally can still depend on services managed by the outgoing team. Ask for a description of the running arrangement: the current release, the project files included in delivery, hosting, product data, booking connections and support contacts.

The document should distinguish what the business receives from what remains a licensed or supplier-operated service. A custom build and a subscription storefront may have different deliverables. Agree those specifics for your arrangement rather than treating every build as a source-code purchase.

Have the incoming technical team compare the delivered project with the version in use. Can they identify how product information is updated, where enquiries or orders go and who handles failures? Record unresolved defects and changes still awaiting approval. A download link labelled “final” answers none of those questions.

Keep acceptance close to the customer journey. Use an approved test method to check that a traveler can open a product, submit the intended request and receive the expected response. If payments are involved, coordinate the appropriate verification with the payment provider and responsible operator. The handover should establish who can investigate an order problem without asking the traveler to contact the former agency.

Close campaign and payment work explicitly

Identify campaigns still scheduled or running, their destination pages, remaining commitments and the person responsible after the change. Decide which continue, which pause and which need revised material. A scheduled post can promote an offer the incoming team was never told about.

For KOL or KOC collaborations, record agreed deliverables, publication status, outstanding approvals and the contact handling follow-up. Include the confirmed usage terms for content. Keep promised work separate from completed work so the incoming team does not count a planned video as an asset it already has.

For payment-related administration, reconcile pending refunds and unsettled items with the records available to the operator. Name the person who will follow each open item through. A final agency invoice does not close a customer's refund request.

Preserve the campaign reporting periods and metric definitions. Separate recorded orders and payments from enquiries and estimated marketing contributions. Cross-channel attribution remains incomplete; a new agency should not inherit an unexplained revenue total and present it as measured campaign performance.

Accept the handover through tasks

Use a shared record to agree what is delivered, what is excluded and what still has an owner. A compact acceptance table makes the remaining work visible.

Record the result of each check and the person accepting it. Mark missing work as open; do not hide it in a general “handover complete” email. If a supplier dependency cannot move, agree whether it continues or needs replacement and how that affects customers.

Finish with the permissions review and a named route for remaining questions under the agreed support arrangement. The outgoing team should know when its responsibilities end. The incoming team should know which unresolved items it has accepted. Both need the same version of that record.

Where CN1X fits

CN1X can assess the material needed to continue Chinese content, Xiaohongshu and Douyin activity, Mini Program operations and CRM through our services. The scope should identify what is available, which dependencies continue and what needs rebuilding before a new team takes responsibility.

Share your current channels and the work still in progress. We can define a practical receiving scope around the product and customer journey, so a change of agency has a clear starting point for the next operator.