> ## 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.

# Connecting Social Intents to Neo

> Copy your Social Intents Account ID and API token, save them in Neo, and send each chat to your PSA

You connect Social Intents once at the MSP level, with the Account ID and API token of your Social Intents account.

## 1. Copy the Account ID and API token

In Social Intents, an admin opens **Settings** → **API & Webhooks** → **REST API**. The page shows your **Account ID** and your **API token**. Copy both. Keep the token out of email and chat: anyone who has it can read your chat transcripts.

Neo calls Social Intents at `https://api.socialintents.com/v1/api` with the Account ID and token as Basic auth.

## 2. Add them in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Social Intents card, under Customer Success.

**2. Save the Account ID and token**

Paste the Account ID and the API token and click **Save settings**. Neo checks them against Social Intents before saving, so a wrong pair is rejected straight away.

## 3. Turn Social Intents on per agent

Open the agent, go to the Integrations section, and pick an access profile for the Social Intents block, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Chats** | Disabled, Read Only | Answered and missed chats and offline messages, with the full transcript and each visitor's name, email, phone, IP address and location. |
| **Leads** | Disabled, Read Only | Captured leads: name, email, phone and page. |
| **Widgets** | Disabled, Read Only | Your widgets' ids, names and time zones. |
| **Webhooks** | Disabled, Read / Write | Register or remove a webhook. A webhook sends every later transcript of the widget to the URL you give, so registering one always asks a technician, in every profile. Neo registers only an https URL. |

The **Read Only** profile is enough to read chats, missed chats, offline messages and leads.

## 4. Send each chat to your PSA

Neo starts an agent on a PSA ticket, so each chat reaches Neo as a ticket:

1. In Social Intents, open your widget's settings.
2. In **Transcript Email Address**, add the mailbox your PSA turns into tickets (in Autotask, a mailbox set up in **Incoming Email Processing**). Add it to **Missed Transcript Email Address** too, to get missed chats and offline messages as tickets.
3. Save. Each chat now opens a ticket when it ends. The email comes from Social Intents, so the ticket's description carries the visitor's name and email, and your PSA's email rules decide the ticket's contact, company and queue.

Then give your triggered agent for new tickets its instructions for these tickets, such as the queue and priority for a chat about a given page. It works from the transcript in the ticket and does not read Social Intents on a ticket run, because the chat text is written by a website visitor.

For a user's earlier chats, give an internal chat agent the Social Intents **Read Only** profile; a technician asks it by the user's email. For a callback list, give a scheduled agent the same profile and ask it for the day's missed chats and offline messages.

See [Social Intents API](https://docs.neoagent.io/agents/tools/sales/social-intents-api.md) for what the agent can read and change.


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