> 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/flosum/landing-page-es/soporte/soporte-al-cliente-de-flosum.md).

# Soporte al cliente de Flosum

Bienvenido al Centro de Atención al Cliente de Flosum, su centro para resolver problemas, acceder a guías de solución de problemas y conectar con nuestros equipos de Éxito del Cliente y Soporte Técnico.

Nuestra misión es garantizar que sus Aplicaciones en la Nube de Flosum funcionen sin problemas, de forma segura y eficiente, ya sea que esté realizando una copia de seguridad, archivando, restaurando copias de seguridad o aprovechando una de nuestras otras aplicaciones en la nube. 

Hemos adoptado **Intercom** para ayudarle a atender sus necesidades de soporte del producto a través del sitio de documentación. Pero si necesita asistencia, solicite a un miembro del equipo de soporte y nos conectaremos con usted a través del chat.

El video a continuación le muestra cómo iniciar una conversación con nuestro Agente Virtual de Soporte. 

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

Continuaremos implementando funcionalidad adicional para mejorar sus necesidades de soporte del producto a lo largo del próximo año.&#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/flosum/landing-page-es/soporte/soporte-al-cliente-de-flosum.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.