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

# Reward customers for replying

> Offer a gift card for answering, paid from your own Tremendous account. Boom checks who qualifies and you approve every reward in Drafts.

More customers answer when there's something in it for them. With rewards, a
journey offers a gift card for replying ("answer 3 quick questions and get a
MX\$100 gift card"), Boom checks each conversation against your rule, and the
ones that qualify wait in **Drafts** for someone on your team to approve. Only
then is the gift card ordered and sent.

The money never passes through Boom. Rewards are paid from **your own
Tremendous account**, and the customer picks how to redeem it from the options
for its currency, such as Amazon, PayPal or, in USD, a prepaid Visa.

> [!NOTE]
>
> Every reward is approved by a person. There is no automatic sending yet.

## Before you start

| You need | Where |
| - | - |
| An **Owner** or **Admin** to connect Tremendous and approve rewards | Members can see rewards but can't send them |
| A **Tremendous account**, connected and approved | Settings › Rewards |
| **Funds** in that account | Tremendous, from **Add funds** |
| For rewards sent on WhatsApp: an approved **reward message** | Settings › Rewards |
| A **journey** that talks to your customers | Journeys |

## 1. Connect Tremendous

1. Go to **Settings › Rewards** and choose **Connect Tremendous**.
2. Tremendous opens its sign-up in a new tab. Create the account with a work
   email and your legal business name (the one on your tax registration).
3. Tremendous runs a compliance review, which typically takes a few business days. The page
   shows **Under review** and updates itself when they finish.

When the review passes, the page shows your account and its **Available
balance**. One Tremendous account is connected per organization. The teammate
who connects it is the one who manages funds in Tremendous; everyone else sees
who manages it.

If Tremendous rejects the account, the page shows their reason and what to
change before you choose **Try again**.

## 2. Add funds

Rewards are paid from the account's balance. Choose **Add funds** next to the
balance to open Tremendous and top it up.

Boom keeps an eye on it for you:

* The balance in **Settings › Rewards** turns amber when it can't cover the
  rewards waiting for approval.
* In **Drafts**, a pending reward shows a warning when the balance falls short.

> [!TIP]
>
> Turn on auto-reload or a low-balance alert in Tremendous, so a campaign never
> stops because the balance ran out. An approval the balance can't pay is
> refused by Tremendous and the reward is not sent.

## 3. Create the reward message (WhatsApp only)

On WhatsApp, the reward link is sent with a message template that WhatsApp
reviews first. You need one on each WhatsApp account that sends rewards.

1. In **Settings › Rewards**, find **Reward message on WhatsApp**. It appears
   once Tremendous is connected, with one row per WhatsApp account.
2. Choose **Create** on the account your journey sends from.
3. The row shows **In review** until WhatsApp approves it, which typically
   takes about a day, then **Ready**.

The message is in your organization's language (Settings › Language): English,
Spanish or Portuguese. If WhatsApp rejects it, the row shows **Rejected** with
WhatsApp's reason and a **Try again** button. Creating it needs the same
permission as connecting Tremendous.

Sending the reward by **email** doesn't need a message: Tremendous emails the
gift card to the customer.

## 4. Add a Send reward step to your journey

In the journey builder, add **Send reward** (under **Rewards**) where the
customer has earned it, usually after the conversation that asks your
questions. Then fill in:

| Field | What it does |
| - | - |
| **Amount** and **Currency** | USD from 1 to 2,000, or MXN from 1 to 20,000 |
| **Who qualifies** | A rule in plain words, checked against the conversation. For example: "The customer answered the three questions about their last order." Leave it empty to reward everyone who reaches the step |
| **Delivery** | **WhatsApp link, in the conversation** or **Email** |
| **Approval** | **Review each one in Drafts** |

Connect its three outputs: **Reward sent**, **Not eligible** and **Error**.
**Rejected** is optional; a rejected reward ends the run if it isn't connected.

**Mention the reward in your first message.** That is what gets people to
reply. The builder reminds you when the journey's first message doesn't
mention it.

Write the rule about what the customer did, never about what they thought.
"Answered the three questions" is fine; "said they liked the product" makes the
reward depend on a positive opinion, which review platforms and consumer law
treat as buying reviews.

## 5. Set a budget (optional)

Each campaign or initiative with a reward step gets a **Rewards** page in its
sidebar. Under **Budget**, choose **Set** to cap what it can spend. An approval
that would go over the budget is refused, and the reward keeps waiting in
Drafts. The budget uses one currency, the same as the reward step.

The same page shows what has been **Sent** and what is **Waiting for approval**.

## 6. Approve rewards in Drafts

When a customer qualifies, a reward draft appears in the initiative's
**Drafts** tab. Once a reward is waiting, the tab shows **All**, **Messages** and
**Rewards**: open **Rewards** to see only rewards. Each one shows the amount, who gets it, your **Who qualifies**
rule, Boom's one-line reason, and the last messages of the conversation.

* **Approve and send** orders the gift card from Tremendous and sends it.
* **Reject** sends nothing.
* In the **By template** view, **Approve all…** approves every reward from the
  same step at once.

Approving spends money, so it needs permission to send rewards: Owners and
Admins have it.

## What the customer gets

* **WhatsApp:** a message with their reward link, in the same conversation.
* **Email:** an email from Tremendous with the link.

The link opens Tremendous's redemption page, where they choose from the options
for the reward's currency: in USD a prepaid Visa, Amazon, PayPal or a bank
transfer; in MXN Amazon México, PayPal, Google Play, Uber or Uber Eats, and Razer
Gold (each with its own minimum amount).

## Rules Boom applies

* **One reward per person per enrollment.** A second reward step, a loop back
  through the step, or a reward someone already sent takes **Not eligible**,
  and nothing is ordered.
* **Every reward is reviewed.** Nothing is ordered before someone approves it.
* **Email delivery needs an email.** Customers without one take **Error** and
  get nothing; the builder warns you before you publish.

## When a reward doesn't go out

The customer's journey timeline says why. The common reasons:

| Timeline says | What to do |
| - | - |
| No connected Tremendous account | Connect it in Settings › Rewards |
| No approved reward template | Create the reward message in Settings › Rewards, or deliver by email |
| No WhatsApp number to send from | Give the journey a WhatsApp number to send from, or deliver by email |
| The reward template is on another WhatsApp account | Create the reward message on the account the journey sends from |
| The customer has no email | Deliver on WhatsApp, or collect the email first |
| Tremendous refused the order | Usually the balance, sometimes the account itself. Check both in Tremendous, then enroll the person again |
| The customer already has a reward | Expected: one reward per person per enrollment |

## API and MCP

Reward steps are part of the journey definition, so you can add one with the
journey tools over [MCP](https://docs.useboom.ai/use-mcp.md) (`SEND_REWARD` in
[Journeys](https://docs.useboom.ai/journeys.md)). Pending rewards are drafts on the `REWARD` channel:
list them with `drafts_list` and approve or reject them with `drafts_decide`,
with the same permission check as the app.

## Not covered yet

Rewards pay in USD or MXN only, and every reward needs a person to approve it.


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