Provide a shared foundation

Include an approved description, current product status, relevant visual assets and clear contact routes. Explain the audiences and use cases the partner should prioritise. Distinguish facts they can state from questions that require confirmation. Avoid expecting partners to assemble their message from scattered presentations. A coherent kit reduces the chance that planned features or informal conversations become public promises.

Create an update channel

Name the person responsible for changes and tell partners how to identify the current version. Include a route for questions and proposed local adaptations. Review examples of actual partner communication to find recurring misunderstandings. The kit should support informed local communication while preserving the accuracy of the underlying offer. It is not enough to send a folder once and assume every future message will remain aligned.

Imagine this

Hypothetical example

A hypothetical territory partner receives approved identity-product messaging and a separate availability note for financial features. When a programme changes, the central owner updates the note and explains what must change in local materials. The partner does not infer new coverage from a general roadmap slide.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.