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

# Flosum Customer Support

Welcome to the Flosum Customer Support Center, your hub for resolving issues, accessing troubleshooting guides, and connecting with our Customer Success and Technical Support teams.

Our mission is to ensure your Flosum Cloud Applications run smoothly, securely, and efficiently, whether you’re performing a backup, archive,  restoring backups, or leveraging one of our other cloud applications.&#x20;

We have adopted **Intercom** to help you self-serve your product support needs through the document site.  But if you need assistance, ask for a support team member, and we will connect with you via chat.

The video below shows you how to start a conversation with our Virtual Support Agent.&#x20;

{% @arcade/embed flowId="V9GGrYJ7QcZwTP1L59Y4" url="<https://app.arcade.software/share/V9GGrYJ7QcZwTP1L59Y4>" %}

We will continue to roll out additional functionality to improve your product support needs throughout the next year.&#x20;


---

# 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.flosum.com/support/flosum-customer-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.
