> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/in-person-event/app-best-practices/app-entry-ticket/communication-flow-app-entry-ticket.md). # Communication flow: App = Entry ticket To support this communication flow, we provide ready to use best practice email templates. These can be found in your Admin panel under **Communication** and then **Mail scheduler**, and can be scheduled to ensure attendees receive the right message at the right time. Below is a short overview of the key communications attendees will receive, from registration confirmation through event day entry. {% hint style="info" %} Our default onboarding mail flow promotes App = Entry tick {% endhint %} #### Registration confirmation A (app not live yet) **Name of mail template:** Registration confirmation (app not yet live) Sent immediately after registration if the app is not yet available. Sets expectations by informing attendees that their ticket will become accessible inside the app once it launches. #### Registration confirmation B (app already live) **Name of mail template:** Registation confirmation (app is live) Sent immediately after registration if the app is already available. Informs attendees they can download the app right away and access their entry ticket directly via the “My Ticket(s)” button. #### Registration confirmation C (app already live + Ticket re-assignment) **Name of mail template:** Registation confirmation (live + ticket reassign) Sent immediately after registration if the app is already available. Informs attendees they can download the app right away and access their entry ticket directly via the “My Ticket(s)” button. They are also informed that they can re-assign their ticket under the My ticket(s) button. #### App launch announcement (7 days before event) **Name of mail template:** Attendees - Invite app (7days before) Sent when the app becomes available. Directs attendees to download the app, log in, and access their QR ticket from the app home screen. #### Reminder emails before the event (Day before event) **Name of mail template:** Attendees - reminder mail app (day before) Scheduled reminders for attendees who have not yet logged into the app. Encourages early access and reduces last minute ticket questions. #### Event day mail (2 hours before event opens) **Name of mail template:** Event Day App Sent on the morning of the event. Provides all attendee’s a final push to download the app and access to their QR code within the email as a backup, ensuring smooth entry even if they have not logged into the app yet. --- # 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://knowledge-base.letsgetdigital.com/in-person-event/app-best-practices/app-entry-ticket/communication-flow-app-entry-ticket.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.