> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/es/report-and-run-integrate/identidad-visual/establecer-datos-de-contacto.md).
# Establecer datos de contacto
Configura informaci贸n de contacto, como nombre y n煤mero de tel茅fono, para que aparezca en tus informes publicados.
1. Toca el **icono de informaci贸n 馃泩** en la parte superior de la pantalla de inicio.
2. Despl谩zate hacia abajo para encontrar los datos de contacto, como el nombre, la direcci贸n de correo electr贸nico y el n煤mero de tel茅fono.
3. Toca el dato que quieras configurar. En el siguiente ejemplo, estamos a帽adiendo el **Correo electr贸nico de contacto**.
4. Escribe tu informaci贸n de contacto en el campo de texto.
5. Toca **Guardar**.
6. Los datos de contacto aparecer谩n en la parte superior de tus informes generados.
---
# 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.reportandrun.com/manual/es/report-and-run-integrate/identidad-visual/establecer-datos-de-contacto.md?ask=&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.
