> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/services-and-support/wll-support/how-do-i-contact-support.md).

# How do I contact support?

## Contacting WLL Support

You can contact WLL Support for assistance with:

* Product & API questions
* Technical issues, downtime and bugs

For account and billing queries, please contact your account manager.

### Email us <a href="#raise_a_ticket" id="raise_a_ticket"></a>

You can contact WLL Support via email: <support@whitelabel-loyalty.com>

### Call us (P1 only) <a href="#call_us" id="call_us"></a>

If you are experiencing a P1 level issue representing a complete loss of service or where a significant feature is completely unavailable and no workaround exists, please call our 24/7 service desk line as soon as possible:

* :flag\_gb: **UK number:** <kbd>+44 (113) 320 6800</kbd>
* :flag\_us: **US number:** <kbd>+1 (650) 629 3747</kbd>

If your call is not answered on the first attempt, please leave a voicemail with your name, contact number, email address and a description of your issue. A support agent will respond within your defined SLA timeframe.


---

# 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://kbase.whitelabel-loyalty.com/product/services-and-support/wll-support/how-do-i-contact-support.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.