> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Social Intents API

> Read Social Intents live chat transcripts, missed chats, offline messages, leads and widgets, and register or remove webhooks

An agent with this tool reads your Social Intents live chats: to answer a technician's question about a user's chats, or to list missed chats, offline messages and leads for a callback.

> [!NOTE]
>
> Automatically enabled when you configure Social Intents permissions in your agent workflow. No manual toggle needed.

## What It Does

* Read answered and missed chats, filtered by visitor email, visitor id, widget, tag, chat id and date range: the transcript, the visitor's name, email and phone, the page, the technician and the duration
* Read missed chats and offline messages on their own
* Read captured leads and your widgets
* Register a webhook on a widget for chats, offline messages or leads, and delete a webhook

The agent calls Social Intents through the [Vendor API](https://docs.neoagent.io/agents/tools/vendor-api.md) tool, with `social_intents` as the vendor id. [Sandbox](https://docs.neoagent.io/agents/tools/built-in/sandbox.md) scripts can call Social Intents too, under the same permissions.

## Permission Groups

| Group | Access levels | What it covers |
| - | - | - |
| **Chats** | Disabled, Read Only | Answered and missed chats and offline messages, with transcripts and visitor details |
| **Leads** | Disabled, Read Only | Captured leads |
| **Widgets** | Disabled, Read Only | Your widgets, and the key check |
| **Webhooks** | Disabled, Read / Write | Register and delete webhooks |

## Access Profiles

> [accordion] Read Only
>
> Chats, Leads and Widgets Read Only. No webhook changes.

> [accordion] Helpdesk
>
> Every group on. A webhook change asks a technician first.

> [accordion] IT Admin
>
> Every group on. A webhook sends transcripts out of Social Intents, so a webhook change asks a technician first.

> [accordion] Full Automation
>
> Every group on, with no approval, except registering a webhook, which always asks a technician.

## Safety

* Chat text is written by your website's visitors. The agent treats it as data and never follows instructions in it.
* On a run for a ticket, the agent reads no chats, missed chats, offline messages or leads: the chat text on a ticket is written by a website visitor, and Social Intents filters chats only by what a visitor types. A chat agent and a scheduled agent read them.
* Registering a webhook always asks a technician, in every profile: a webhook sends every later transcript to its URL. Neo registers one only to an https URL, and only for the three events Social Intents documents.

## What it does not do

Social Intents' API documents no call to send a chat message, answer a visitor, change a widget's settings or list the webhooks you registered, so the agent does none of these. Neo does not receive Social Intents webhooks; a chat reaches Neo as the ticket its transcript email opens ([how](https://docs.neoagent.io/integrations/social-intents/overview.md#how-a-chat-reaches-neo)).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.