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

# Incident management

{% embed url="<https://status.fulfillmenttools.com/>" %}

Follow the steps below to request support from the fulfillmenttools team:

{% stepper %}
{% step %}
**Visit our** [**support portal**](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/4/create/12)

{% hint style="info" %}
You'll need to be a customer to access this portal. If you're using our free trial and need support, reply to the email you received from our team.
{% endhint %}
{% endstep %}

{% step %}
**Summarize the problem**
{% endstep %}

{% step %}
**Describe the problem in detail**

Describe the issue in as much detail as possible, including steps to reproduce if relevant.
{% endstep %}

{% step %}
**Select a priority**

| Incident priority | Description                                                                                                                                                    |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Priority 1        | You can't use our SaaS services, or essential applications aren't executable or create data loss or corruption. This results in a complete loss of production. |
| Priority 2        | You can use our SaaS services, but not all functions are available. This results in a significant reduction in production.                                     |
| Priority 3        | Most SaaS services' functions are functional, with only slight limitations.                                                                                    |
| {% endstep %}     |                                                                                                                                                                |

{% step %}
**Add attachments**

Attach any relevant screenshots or files.
{% endstep %}

{% step %}
**Submit the ticket**

We'll reply to you as soon as possible.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
If the support portal is unavailable, or you haven't had any response from our team and it's a P1, you can call us on our emergency hotline: **+49 221 956 732 10.**
{% endhint %}

You can also use [our feedback form](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/13/create/47) for feature requests or any feedback in general, or [our service request form](https://ocfulfillment.atlassian.net/servicedesk/customer/portal/1/group/11) to be added to our support portal or other service requests.


---

# 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://docs.fulfillmenttools.com/documentation/about-fulfillmenttools/incident-management.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.