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

# Taking action with Nova

> Ask Nova to edit bookings, resend confirmation emails, transfer entries, and manage discount codes. Nothing happens until you approve it.

<Info>
  Actions are available when your dashboard user has edit access for the
  organization. If your access is view-only, Nova can still answer questions but
  won't offer to make changes. See [User
  access](/docs/getting-started/user-access) for how permissions work.
</Info>

Nova can do more than answer questions. It can make changes for you, which is
useful when a participant emails you with a request: a typo in their name, a
missing confirmation email, or a transfer to a friend. Instead of finding the
booking and clicking through the dashboard, describe what you need in a Nova
chat and approve the change when Nova presents it.

Nova can take these actions today:

<CardGroup cols={2}>
  <Card title="Edit a booking" icon="pen">
    Fix a participant's name, date of birth, contact details, and more.
  </Card>

  <Card title="Resend a confirmation email" icon="envelope">
    Send a booking confirmation to the participant again.
  </Card>

  <Card title="Transfer an entry" icon="right-left">
    Start a transfer to a friend, another race, or another event.
  </Card>

  <Card title="Manage discount codes" icon="tag">
    Create new discount codes or delete existing ones.
  </Card>
</CardGroup>

Nova uses the same approval step for other changes it can make, such as
[setting goals](/docs/nova/goals), scheduling
[email digest reports](/docs/nova/email-digest-reports), and creating
[email campaigns](/docs/nova/email-campaigns).

## How approvals work

Nova never acts on its own. When you ask for a change, it prepares the action
and shows you an approval card in the chat before anything happens.

The card is labeled **Approval required** and names the action, such as
**Edit Booking** or **Create Discount Code**. It lists exactly what is
changing, field by field, so you can check the details before committing.
Click **Approve** to run the action or **Reject** to stop it.

A few things to know:

* **Approval is per action.** If Nova proposes three changes, you get three
  cards and decide on each one separately. There is no "always allow".
* **You can keep chatting first.** An unanswered card doesn't expire. You can
  ask Nova follow-up questions and come back to approve or reject it later in
  the conversation.
* **Rejecting is safe and reversible.** Nova is told you declined and won't
  run the action. You can always ask again with different details.
* **The card stays in your history.** Approved and rejected cards remain in
  the conversation, stamped with the decision, so you have a record of what
  was changed and what wasn't.

For some actions, such as resending an email, the card first shows
`Checking what this would change…` while Nova looks up the exact record under
your permissions. If it can't find the record, the card tells you not to
approve and the **Approve** button is disabled. Ask Nova to look it up again.

## Editing a booking

Ask Nova to update a participant's details on a booking, for example "Change
the date of birth on booking ABC123 to 2 April 1990". Nova can edit:

* First name and last name
* Date of birth
* Gender
* Email address
* Phone number
* Address
* Emergency contact name and phone number

Nova can only edit fields that exist on that event's booking form, and a
gender value must match one of the options your form offers. If a booking has
several participants, Nova asks which participant you mean before proposing
the change.

Edits are recorded as made by you, the person who approved them. After an
edit, Nova's own reporting data can take up to around an hour to reflect the
change, so don't be surprised if a report you run straight afterwards still
shows the old value. The booking itself is updated immediately.

## Resending a booking confirmation email

Ask Nova to resend a booking confirmation, for example "Resend the
confirmation email for booking ABC123". The email always goes to the
participant's email address on file. It can't be redirected to you or anyone
else. If you don't name a specific participant, every participant on the
booking receives their own confirmation.

The approval card shows the exact recipient addresses before you approve, so
you can confirm the email is going to the right person.

Only booking confirmation emails can be resent through Nova. For other
transactional emails, see
[Transactional emails](/docs/email-communications/transactional-emails).

## Transferring an entry

Ask Nova to transfer a participant's entry. There are three kinds of transfer:

* **To a friend.** Nova needs the friend's first name and email address.
* **To another race** within the same event.
* **To another event.**

Nova starts the transfer. It doesn't complete it. The participant or the
person receiving the entry finishes the transfer through the normal transfer
flow, including paying any transfer fee you have configured. Your event's
transfer settings still apply, so the action fails with an explanation if that
transfer type is switched off, the transfer window has closed, or a transfer
is already in progress for the entry.

## Creating and deleting discount codes

Ask Nova to create a discount code, for example "Create a 20% code called
SPRING20 for the Spring Trail Run, valid until the end of March, limited to
100 uses". Nova can set:

* The code itself and a description
* A percentage discount or a fixed amount off
* A maximum discount value for percentage codes
* Total usage limit and per-person usage limit
* Whether the code is for first bookings only
* Start and expiry dates
* Which events or occurrences the code applies to

<Warning>
  If you don't specify a usage limit, Nova creates the code with a limit of one
  use in total. If you want a code many participants can use, say so, for
  example "limited to 500 uses". Every code Nova creates has a total usage
  limit. To create a code with unlimited uses, create it in the dashboard
  instead.
</Warning>

Some discount code options can't be set through Nova, including affiliate
commission, stacking with other codes, per-entry discounts, restrictions to
specific ticket types, and bulk code generation. For those, manage your codes
directly in the dashboard. See [Discount codes](/docs/event-setup/discount-codes).

You can also ask Nova to delete discount codes, up to 50 at a time, by their
exact codes. Deleting a code stops it working immediately and removes it from
your active list.

<Warning>
  Deleting a discount code can't be undone. There is no restore option, and you
  can't create a new code with the same code string afterwards. If you only want
  to stop a code temporarily, set an expiry date on it instead of deleting it.
  Nova will remind you of this before it asks for your approval.
</Warning>
