> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/policies/en/after-go-live-best-practices.md). # After Go-Live: Best Practices Manage Apple Wallet and Google Wallet passes after go-live. Find digital wallet documentation, support guidance, analytics, certificate renewal, and administration best practices. ### Welcome to the run-phase The Wallet Crew solution is now deployed and operational. This run phase covers the day-to-day management of Apple Wallet and Google Wallet passes. This guide supports independent digital wallet administration after go-live. It covers documentation, support, analytics, pass configuration, and operational best practices. It brings together the key resources for routine actions and wallet pass monitoring. Support remains the primary contact for unresolved questions and technical issues. The goal is reliable, autonomous management of the Wallet solution. The Wallet Crew team remains available when additional assistance is needed. Two resources support the run phase: * **Documentation**: explains the platform and its procedures. * **Support**: resolves questions and issues not covered by documentation. **Regular check-ins with The Wallet Crew** help assess wallet adoption, analyze early results, and identify growth opportunities. ### Wallet documentation and self-service resources Documentation is the first resource for wallet pass administration. It helps resolve common questions without opening a support request. The Wallet Crew documentation covers the platform's main features and operational procedures. [Access The Wallet Crew documentation](https://docs.thewalletcrew.io/?utm_source=chatgpt.com) #### Essential documentation after go-live **📊 Wallet pass analytics and statistics** The Statistics section tracks digital wallet pass usage and pass performance. 👉 Check this section for: * tracking the usage of your passes; * analyzing downloads and activity; * answering statistics-related questions. [View the Statistics documentation](https://docs.thewalletcrew.io/guides-monitoring/fr/monitor/les-tableaux-de-bord-analytics) **🎨 Wallet pass design and card configuration** The Design / Wallet section explains pass configuration and card display. 👉 Check this section when you want to: * understand the structure of a card; * edit an existing configuration; * verify the elements displayed on a pass; * understand how the different card types work. [View the Design documentation](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/cards-design-colors-images-and-fields) **🔎 Digital wallet terminology** If a term or feature is unclear, the Glossary provides the main definitions used on the platform. [View the Glossary](https://docs.thewalletcrew.io/policies/fr) **🔄 Apple Wallet certificate renewal** The Apple certificate must be renewed every year so that pass issuance continues to work properly. We recommend doing this ahead of time. [View the procedure](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/apple-and-google-wallet/apple-wallet-certificates#certificate-renewal) ### Search documentation with the AI agent The AI agent searches The Wallet Crew documentation when a relevant answer is not immediately visible. [Ask the AI agent](https://docs.thewalletcrew.io/policies/support-options#ask-the-agent-first) ### Wallet pass support The Wallet Crew support team handles digital wallet questions that documentation cannot resolve. [**Access The Wallet Crew support**](https://support.thewalletcrew.io/?utm_source=chatgpt.com)**:** Log in with your credentials to access it. You can create a ticket by clicking this link or by sending an email to: **We recommend contacting support via this link or the email address above rather than reaching out directly to a team member, for tracking purposes.** For example, if the team member is on vacation, your issue can still be handled by another person who has access to the full history. [**Best practices for contacting support**](https://docs.thewalletcrew.io/policies/support-options#ask-the-agent-first) #### Information to include in a support request Complete details help the team diagnose wallet pass issues quickly. The AI agent can summarize a previous conversation or draft a support message. **Be sure to include:** * a precise description of the issue; * the steps needed to reproduce the issue; * the name of the pass / template involved; * the user or pass ID, where relevant; * screenshots or videos, if they help clarify the issue; * the environment involved (staging or production). The more precise your request, the faster the support team's diagnosis will be. #### When to contact Wallet support Contact support when: * you encounter unexpected platform behavior; * a feature isn't working as expected; * you've identified an error or bug; * you need help understanding behavior that isn't explained in the documentation; * you can't find the answer to your question in the documentation; * you need technical assistance. #### Documentation or support? | I don't know how to edit an element of a card | 📚 Documentation | | --------------------------------------------- | ---------------- | | I want to understand a feature | 📚 Documentation | | I want to view my statistics | 📚 Documentation | | I'm experiencing unexpected behavior | 🎫 Support | | A feature seems to no longer be working | 🎫 Support | | I think I've found a bug | 🎫 Support | | I can't find the answer in the documentation | 🎫 Support | ### Digital wallet administration best practices #### Validate changes before saving An error message, especially a red warning, indicates a configuration element needs correction or review. Do not force the save. Before proceeding: 1. Check the message displayed and the element involved. 2. If you understand the source of the error, make the necessary correction. 3. If the cause is unclear, contact support before saving. Saving a configuration despite an error can cause unexpected production behavior. Changes can be managed independently. Contact support before saving when an error appears. #### Assign an internal wallet owner Designate an internal contact to centralize business-team questions and requests about The Wallet Crew solutions. This person can assess needs, answer common questions, and liaise with support when needed. This approach streamlines support communication, prevents duplicate requests, and gives teams a clear contact. ### Key takeaways After go-live, day-to-day Wallet solution administration can be managed independently. For each question, follow this path: 📚 Documentation → 🎫 Support → 🤝 The Wallet Crew Team Documentation provides the required information and procedures. Support helps when a situation needs analysis or intervention. ### Improve wallet adoption after go-live Going live with a digital wallet is the first step. Track wallet pass adoption and usage to identify further opportunities. The Wallet Crew can schedule a follow-up meeting to analyze wallet usage, assess adoption, and plan next steps. A digital wallet does more than display a card or ticket. It can become a customer engagement channel through personalization, notifications, real-time updates, targeted offers, and journey-based automation. The goal is an active wallet programme that supports customer loyalty and engagement. Contact The Wallet Crew to explore the next stage. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.thewalletcrew.io/policies/en/after-go-live-best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.