> ## Documentation Index
> Fetch the complete documentation index at: https://help.taack.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Next Steps

> Give patrons instructions and action buttons after checkout, registration, or a payment-plan deposit.

Use **Next Steps** to tell patrons what to do next: join a group chat, read a kit list, or complete a form. Your message belongs to one event and applies to every ticket type.

Only the event creator can edit Next Steps in the dashboard. It starts off by default.

## Set up your message

<Steps>
  <Step title="Open the event">
    Click **Events**, select your event, then open **Checkout** or **Registration**. Find **Next Steps** below the custom questions.
  </Step>

  <Step title="Add your content">
    Turn on **Show Next Steps**. Enter a **Title** of up to 100 characters. Add a **Description (optional)** for details such as what to bring. You can use paragraphs, bold, italic, links, and lists.

    Under **Buttons (optional)**, click **Add button**. Add a **Button label** of up to 40 characters and a **Button link**. You can add two buttons; the first is the primary button.

    Button links must use HTTPS, an email link, or a telephone link. A description and buttons are optional; a title is required when Next Steps is on.
  </Step>

  <Step title="Choose when to show it">
    For an event that requires RSVP approval, **Show while approval is pending** is off by default. Leave it off to wait until you approve the request.

    Turn it on to also show Next Steps on checkout complete while an RSVP without a payment plan awaits approval. This option appears only for approval-required events, and you must turn on **Show Next Steps** first. It does not show Next Steps in pending-request emails or on ticket pages before approval. Payment-plan requests still wait for approval and a paid deposit.
  </Step>

  <Step title="Preview and save">
    Review the **Preview**, then click **Save Next Steps**. Preview changes do not reach patrons until you save.
  </Step>
</Steps>

## Where patrons see it

When Next Steps is on, eligible patrons see it on the checkout confirmation screen, including embedded checkout and free-order confirmation. It also appears in confirmation and event reminder emails, on their event ticket page in **My Tickets**, and on eligible payment-plan cards.

* Paid and free orders qualify once completed. RSVP requests normally qualify after approval; the pending-approval option adds checkout-complete visibility only.
* Payment plans qualify once the deposit is paid and the plan remains active, past due, or completed.
* Patrons with manually issued tickets and recipients who claim a ticket transfer can also see Next Steps.
* Denied requests do not qualify. Refunded or cancelled tickets and cancelled plans no longer provide access through the attendee screens.

Ticket-page access follows the current ticket holder after a transfer. Next Steps is not shown on the public event page. Patrons can still share your message or destination links, so do not use it as a way to protect confidential information.

## Change or disable your message

Edit your content and click **Save Next Steps**. Patron screens show the latest saved version. Taack does not send a new notification to existing attendees when you edit it.

Emails already sent keep their original wording and button labels. Their tracked buttons lead to the current saved destination while that button still exists. Edit an existing button to keep its tap history; removing it discards its counts.

To hide Next Steps, turn off **Show Next Steps** and save. Your content and counts remain available to turn on again. This cannot remove content from emails already sent or revoke access to an external group or page.

## Read button tap counts

The editor shows how many current attendees tapped each saved button, their percentage of the attendee count, and total taps. You see counts only, not a list of people who clicked.

The attendee count includes current ticket holders and patrons with a deposit-paid plan still in progress. New taps follow the current holder after a transfer. Patrons who no longer qualify drop out of the unique-attendee count; total taps retain the recorded history. Taps made while an RSVP is still awaiting approval do not count toward attendee taps.

You can also read and edit Next Steps through the [Taack connector](/mcp/tools#next-steps). Button tap counts are available in the dashboard.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.