> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/data-and-go-live/after-go-live.md).

# After Go-live

Running the programme after launch: hypercare, what to monitor, getting support, and making changes safely.

Launch is the start of running the programme. This page covers the first weeks of close watching (hypercare), what to monitor from then on, how to get help, and how to change the programme without breaking it.

## Hypercare (first two to four weeks)

* Agree a daily check-in between the programme team, the integration team and customer service.
* Review the monitors below every day, and the first members' journeys individually: did they get the welcome reward, earn on their first purchase, receive their messages?
* Keep a log of issues and fixes; most problems appear in the first days, at the first month end (leaderboard prizes, monthly limits) and at the first scheduled recalculations (tiers, expiry).

## What to monitor

| Signal                             | Why                                                                                 | Where                                                                                 |
| ---------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Failed API requests by status code | `4xx` means the integration sends bad data; `429`/`5xx` means retries are happening | Integration layer logs                                                                |
| Retry and dead-letter queues       | Events that never reached Open Loyalty                                              | Integration layer                                                                     |
| Webhook delivery and processing    | Missed or failed CRM updates                                                        | Webhook endpoint and worker logs                                                      |
| Unmatched transactions             | Purchases that earned nothing                                                       | Admin Panel transactions list (*Not matched*)                                         |
| Balance reconciliation             | CRM's copy drifting from Open Loyalty                                               | Periodic job comparing balances                                                       |
| Campaign and reward budgets        | A campaign running out early, or spending much more than planned                    | Admin Panel campaign and reward limits                                                |
| Coupon pools and reward stock      | Rewards becoming unavailable                                                        | Admin Panel rewards                                                                   |
| Admin activity                     | Unexpected changes to configuration                                                 | [System logs](https://help.openloyalty.io/administration/settings/admins/system-logs) |

## Getting help

Use the Open Loyalty helpdesk with the right category — **Report an Incident** for outages or data loss, **Bug** for faults, **Support Request** for questions, **Limits Increase** before planned peaks. Include the tenant, the time, the request (without credentials) and the response.

## Changing the programme

* **New campaigns, rewards and rules:** build and simulate on staging, then move them to production as in [Configuration migration](https://help.openloyalty.io/implementation-guide/data-and-go-live/configuration-migration.md). Avoid editing live campaigns in place for anything bigger than a text change.
* **Mechanics that are hard to change later:** milestone goal types on live challenges, badge system codes, tier conditions (members are re-evaluated only on their next activity), wallet expiry rules. Plan these as projects, not quick edits.
* **New integrations:** give each its own admin, role and API key — see [Environments & access](https://help.openloyalty.io/implementation-guide/plan-and-foundations/environments-and-access.md).

## Keeping up with Open Loyalty releases

* Read [What's New](https://help.openloyalty.io/whats-new) each month for changes that affect your configuration or UI.
* The [backward compatibility policy](https://help.openloyalty.io/technical-guide/backward-compatibility-policy) explains how API changes are introduced; make sure your integration ignores unknown fields in responses and webhooks, so additions don't break it.

## Checklist

* [ ] Hypercare owners and a daily check-in are agreed for the first weeks.
* [ ] Monitors and alerts cover API failures, retry queues, webhooks, unmatched transactions and reconciliation.
* [ ] Budgets, coupon pools and stock are reviewed weekly.
* [ ] Changes go through staging and configuration migration.
* [ ] Someone reads What's New every month.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/data-and-go-live/after-go-live.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
