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

# Simplesat API

> Read your Simplesat survey responses for dashboards and questions, send a survey when a ticket closes, and keep customers and team members up to date

The common uses are a feedback dashboard (CSAT score, its trend, ratings per technician and company, the latest comments) and an agent that emails the contact a survey when their ticket closes.

> [!NOTE]
>
> Automatically enabled when you configure Simplesat permissions in your agent workflow, or on a dashboard.

## What It Does

* Search survey responses for any period, filtered by rating, sentiment, technician, company, customer, ticket or tag
* Score CSAT and NPS for the whole team, per technician or per company
* List negative feedback with the customer's comment, the ticket and the technicians, for a follow-up
* Send an event-based email survey to one customer, linked to the ticket and the technician
* Read your active surveys and their questions
* Create and update customers, one at a time or up to 1000 at once, and team members
* Record a response taken elsewhere, or change a response's answers and tags

## Permission Groups

| Group | Covers |
| - | - |
| Surveys & Questions | Your active surveys (name, metric, type, token) and their questions with their choices. Read only |
| Survey Emails | Send an event-based email survey to one customer, with the ticket and the technician it is about. Write only |
| Responses & Answers | Ratings, sentiment, comments, follow-up answers, tags, the ticket, the technicians on it, and the customer's name, email, company and IP address. Write adds a response or changes its answers and tags |
| Customers | Your Simplesat customers: name, email, company, language, external id, tags, custom attributes and subscription. Write creates or updates them |
| Team Members | Your technicians in Simplesat: name, email, external id, custom attributes and groups. Write creates or updates one by email |

## Access Profiles

| Profile | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed, and no survey is sent |
| **Helpdesk** | Every read | Sending a survey and every change |
| **IT Admin** | Every read, sending surveys, and every change | Nothing |
| **Full Automation** | Every read and write | Nothing |

A dashboard gets read access only, to the groups you grant it.

## Safety Controls

| Control | Behavior |
| - | - |
| **One recipient per survey** | A survey email must name one customer email address, so an approval shows who gets the survey |
| **No repeated sends** | Neo never retries a survey email that may have reached Simplesat, so a customer never gets the same survey twice |
| **Customer updates keep what you leave out** | An update to one customer reads the stored customer first and sends back every field the agent did not change |
| **Bounded bulk upserts** | A bulk upsert holds 1 to 1000 customers, each with an email |
| **Only documented calls** | Neo sends only the calls in Simplesat's API reference and refuses any other path or verb |


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