> For the complete documentation index, see [llms.txt](https://help.digitalwallet.cards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.digitalwallet.cards/push-notifications/how-it-works/how-long-does-it-take-for-push-messages-to-be-received-by-our-customers.md). # How long does it take for push messages to be received by our customers? Push messages typically are delivered within a few (20-30) seconds. However, Android and iOS handle the messages differently. Sometimes if the user has the card open or uses the phone, a message may not automatically trigger. Unfortunately, this user experience is controlled by Apple and Google and is beyond our control. A simple way to check if the message has been received is to check the ‘Latest Updates’ section on your Customer’s card. If the phone has already received and processed the message, you will see it there. Please note that **card preview will not receive push updates**. These passes are simply there to allow you to test how your design looks on a phone. --- # 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://help.digitalwallet.cards/push-notifications/how-it-works/how-long-does-it-take-for-push-messages-to-be-received-by-our-customers.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.