Skip to content
  • There are no suggestions because the search field is empty.

What email templates are available in Grip Manage?

This article provides an overview of the different emails that are being sent from Grip Manage and when they are sent.

Grip Manage sends various system-generated and manual emails to attendees, sponsors, and other users. These emails serve different purposes depending on the user type, their registration status, and the event flow.

Screenshot 2025-08-29 at 14.42.03-1

Below is a comprehensive overview of all email types currently supported in Grip Manage, including their purpose and trigger conditions.

📧 Attendee Emails

Email Name Description When is it Sent?
Order Confirmation Confirms a successful ticket purchase. Includes general event information, next steps, group purchase details, refund policies, and FAQs. Automatically sent upon ticket purchase.
Ticket is Active Notifies attendees that their ticket is now active and usable. Provides a link to view or update registration details. Automatically sent after ticket confirmation.
Beacon Connection Notification Alerts both attendees when a connection has been established via their event beacons. Automatically sent upon creation of a beacon connection between two users.
Pass Selection Register Sent when a sponsor registers a person (e.g., speaker, client, staff) through the Sponsor Portal. Functions similarly to the "Ticket is Active" email. Automatically sent after submitting a Pass task with a new person via the Sponsor Portal.
Subevent Application Confirms that a user’s subevent application has been received. Includes links to update their application and view all events. Automatically sent when a new subevent application is submitted.
Subevent Submission Notifies the user that their subevent submission has been received and is pending approval. Includes links to view and update the submission. Automatically sent after submission of a subevent that requires approval.
Subevent Application Accepted Informs the user that their application to attend a side event has been accepted.  
Subevent Attendee Application Rejected Informs the participant that their application to a side event has been declined.  
Subevent RSVP Confirmation Confirms a user has RSVP'd to a side event.  

📧 Sponsor Emails

Email Name Description When is it Sent?
Portal Access Email Provides sponsor users with login/authentication details for the Sponsor Portal. May also include support contact details. Automatically sent when “Portal Access” is toggled under EMS > Companies > Contacts. Can also be sent manually via EMS > Companies > Contacts > Actions > Email > Welcome Email.
Welcome Email Introduces sponsors to the event and Sponsor Portal, including basic event and onboarding details. Sent manually from EMS > Companies > Contacts > Actions > Email > Welcome Email.
Task Due Batch Reminder Notification Periodic reminder summarizing all pending and in-progress sponsor tasks. Automatically sent based on configured time intervals. Requires initial setup.
Task Due Notification Sent when a task reaches its due date and remains incomplete. Automatically triggered when a task is due.
Task Overdue Notification Notifies sponsors that a task is overdue. Automatically triggered after the due date passes.
Task Submission Notification Confirms that a sponsor task has been submitted. Automatically triggered upon task submission.
Reminder Task Notification A reminder about a specific task or deadline. Manually configured and sent as needed.

When you are happy with your email template selection, make sure you configure parameters and domain, as well as define your target audience. Don't forget to tick 'Enable' whenever you feel emails are ready to start going out. 

Screenshot 2025-08-29 at 14.54.23

Editing Emails:

Remember that you can always adjust emails communication, voice and tone, as well as visuals manually. 

ScreenRecording2025-08-29at15.00.21-ezgif.com-video-to-gif-converter

 

🛠️ Adding a QR Code to the Order Confirmation Email

To display a unique QR code for each ticket in a confirmation email, you must use a ticket loop. This ensures the system generates a QR code per ticket in the order.

Steps to Add a QR Code:

  1. Open Email Configuration
    Go to Event Settings > Email Configuration and select the Order Confirmation email template.

  2. Insert a Ticket Loop

    • Click the plus (+) icon.

    • Select "Loop" to create a repeating section for each ticket in the order.

 

  1. Add the QR Code

    • Inside the loop, click the top plus (+) icon.

    • Select "QR Code (Default Person ID)".

  2. Add a Description (Optional)

    • Still within the loop, click the same plus (+) icon.

    • Select "Text" and add a short label such as:

      • "Your Ticket QR Code"

      • "Show this code at entry"

  3. Add Additional Tags (Recommended)

    • Click the lower plus (+) icon (below the QR code).

    • Add helpful details such as:

      • QR code for: ${ticket.email}

      • Registration ID: ${refNumber}

  4. Preview the Email

    • Use the preview option to ensure the email displays one QR code per ticket.

    • Remove any unnecessary QR codes or placeholder text to keep the message clear.