> For the complete documentation index, see [llms.txt](https://guia.fenicio.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guia.fenicio.help/integraciones-y-herramientas/atencion-al-cliente/shock.md).

# Shock

## Cobertura

* :flag\_uy: Uruguay

## Integración

Shock es una empresa uruguaya que ofrece soluciones de automatización y atención al cliente con inteligencia artificial. Sus servicios incluyen:

* Chatbots 24/7 y chat multiagente por WhatsApp
* Envíos masivos y calificación de leads
* Reservas automatizadas para diversos rubros
* CRM, email marketing y campañas digitales

Ideal para marcas que buscan mejorar ventas, atención y eficiencia operativa.

## Contacto comercial

:person\_in\_tuxedo: Joaquín Rodriguez - <joaquin@shock.uy> - +589 94 197 353

## Requerimientos y proceso para alta

El cliente debe contactar al equipo de Shock para solicitar las IP de conexión con Fenicio. Luego, debe incluir esta información en un ticket dirigido al equipo de soporte de Fenicio y solicitar la habilitación de las mismas para API V1.

## Más información

[Sitio de Shock](https://shock.uy/)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guia.fenicio.help/integraciones-y-herramientas/atencion-al-cliente/shock.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.