> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/referral-program/management.md).

# Management

The four screens you work once your programme is live, and how often each one needs you.

Once a referral programme is running, most of it looks after itself. Four screens are where the exceptions land — and only one of them needs you on a schedule.

| Screen                                                         | What it is for                                                      | How often                                                                |
| -------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| [Referral orders](/referral-program/management/orders.md)      | Approve or reject the orders that need a decision                   | **Weekly.** Flagged orders sit on a 14-day hold, then approve themselves |
| [Fraud center](/referral-program/management/fraud-center.md)   | Read why an order was flagged and close the case                    | Alongside the orders review                                              |
| [Contacts](/referral-program/management/customers.md)          | Find your best advocates, and the loyal buyers nobody has asked yet | When you want growth, not when something breaks                          |
| [Track coupons](/referral-program/management/track-coupons.md) | Trace a discount code from issue to redemption                      | When a referrer asks about a missing or dead code                        |

### The one rhythm that matters

Review flagged orders weekly rather than as a fire drill. A hold that runs out approves itself, so a flag nobody reads protects nothing — and a genuine referrer left waiting usually stops sharing.

Unflagged pending orders need no attention at all; they approve on their own when the review period ends. Spend the time on the flagged ones.

### When something has gone wrong

* A reward has not arrived → [troubleshooting referrals and rewards](/troubleshooting/referral-troubleshooting.md)
* A discount code will not work → [troubleshooting discount codes](/troubleshooting/coupon-troubleshooting.md)

### Related

* [How to control when a reward is issued and revoked](/referral-program/reward-timing.md) — the settings that decide what lands in the orders queue.
* [How to read your referral analytics](/referral-program/analytics.md) — whether the programme is paying for itself.


---

# 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://docs.bloop.plus/referral-program/management.md?ask=<question>&goal=<endgoal>
```

`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.