# Escouade: the documentation > The documentation of Escouade and its family (Meet, Mail, Social, Tools): 25 pages in Markdown. In French: https://escouade.io/docs/llms.txt. --- Source: https://escouade.io/en/docs/index.md # Escouade documentation > Escouade reads what your company already writes, links it to your customers and your deals, and makes it available to your team and to your AI agents. This documentation explains how to use it, page by page. ## The family, one line each | Application | Address | What it does | |---|---|---| | **Escouade** | | The workspace: the chat, the CRM, the Library, the ingestion of emails and documents, the agents' control centre. | | **Meet** | | Your meetings recorded, on video calls and in the field, with their minutes filed in the deal they concern. | | **Mail** | | Mailboxes on your domain for your team and your agents, prospecting, and follow-ups in the same thread. | | **Social** | | Your team's LinkedIn posts, prepared, approved, then published by each person from the extension. | | **Tools** | | Thirteen office tools in the browser: PDF, photo, vector, text, spreadsheet, slides, video… | One account opens the whole family, , and one invoice pays for it. Prescriptio, the public data of the French building sector, is the publisher's other brand; its documentation is on . ## Where to start 1. **Open an account**: signing up asks for the SIREN number of an active French company and an email address. See [The Escouade account](https://escouade.io/en/docs/compte.md). 2. **Choose a size**, or stay on Free: every feature is in every size; only the number of users and the usage allowance change. See [Sizes](https://escouade.io/en/docs/tailles.md). 3. **Connect your sources**: your Gmail or Outlook mailboxes, a Google Drive, your documents. See [Connectors](https://escouade.io/en/docs/connecteurs.md). 4. **Connect your assistant**: Claude or ChatGPT reads and writes in Escouade through its MCP connectors, with your rights. See [The family's MCP servers](https://escouade.io/en/docs/mcp.md). ## For a developer or an agent - Every page of this documentation exists in Markdown, at the same address with `.md` appended: [/en/docs/compte.md](https://escouade.io/en/docs/compte.md), for example. - [/en/docs/llms.txt](https://escouade.io/en/docs/llms.txt) gives an agent the map of the documentation; [/en/docs/llms-full.txt](https://escouade.io/en/docs/llms-full.txt) gives it in a single file. - The family's MCP servers are on [a single page](https://escouade.io/en/docs/mcp.md), with their addresses and their tools. - Meet has a read-only REST API and signed webhooks: [Meet for developers](https://escouade.io/en/docs/meet/developpeurs.md). Mail has its own, with its own documentation, in French for now: [the Mail documentation](https://escouade.io/en/mail/docs/index.md). - Mail's SDKs, command line and examples are public: [GitHub](https://escouade.io/en/docs/github.md). ## Hosting and data Escouade online is hosted in France. A company that wants to keep everything in-house takes [Escouade hub](https://escouade.io/en/docs/escouade/hub.md): Escouade, the data and the AI on its own server. What is exposed, signed and kept is set out in [the privacy policy](https://escouade.io/en/privacy) and the list of [subprocessors](https://escouade.io/en/subprocessors). A question this documentation does not answer? Write to : a person will reply. --- Source: https://escouade.io/en/docs/compte.md # The Escouade account > One account, at , opens the whole family: Escouade, Meet, Mail, Social and Tools. It holds your organisation, its members, its size and its invoice. There is no password: you prove your email address each time you sign in. ## Signing up Signing up opens an **organisation** for a company that exists and is active: 1. Enter the company's **SIREN** number (the French company identifier). Escouade checks its control digit, then asks the public French company register: the register must know it and list it as active. 2. Enter your **email address** and type in the six-digit code sent to it, or go through Google (below). 3. Accept the [terms and conditions](https://escouade.io/en/terms) in force. The organisation starts on **Free**, and you are its owner. You choose a [size](https://escouade.io/en/docs/tailles.md) when you need one. - **A SIREN number holds a single organisation.** If the company is already signed up, the sign-up is refused: ask its owner to add you. - **The free trial happens once**: once per SIREN number and once per company email domain. A second company signed up with an address on the same domain (a subsidiary, a holding company) starts on Free, without a trial. A public email provider (Gmail, Orange…) does not count as a company domain. See [The trial](https://escouade.io/en/docs/utilisation-et-facture.md#essai). - **Sign-up closed or size full**: opening happens in stages. When sign-up is closed, or the size you want is full, your request (the company, the verified address, the size) goes on the waiting list, and an invitation reaches you by email, in order of arrival. The invitation link works once, for that company, that address and that size. A request is kept for twelve months after its last change. ## Signing in There is no password. You prove your address in one of these ways: | Method | How | |---|---| | **Code by email** | A six-digit code, valid for 10 minutes, five attempts, single use. | | **Continue with Google** | For a Gmail or Google Workspace address: Google vouches that it is yours. An address from elsewhere opened as a Google account receives a code by email instead. | | **Continue with Microsoft** | [coming soon] | Whatever the method, you are found by your address: the same account, the same organisations. If your account has a second factor, the code from your authenticator app is asked for next. Signing in counts for the whole family: once signed in, Meet, Mail, Social, Tools and Escouade recognise you without asking for another code. ## Signing out "Sign out", from any application of the family, goes through the account: it closes its own session and those of the other applications. You leave the whole family at once. ## The account pages | Page | What you do there | Who | |---|---|---| | **Usage** | The daily and weekly allowances, the credits, the trial. See [Usage and invoice](https://escouade.io/en/docs/utilisation-et-facture.md). | Any member | | **Members** | Add or remove a member, change their role. | Owners and administrators | | **Organisation** | The name, the billing address. | Owners and administrators, to change them | | **Connectors** | The MCP addresses to connect in Claude or ChatGPT. See [The family's MCP servers](https://escouade.io/en/docs/mcp.md). | Any member | | **API keys** | They will arrive with the family's public API. Until then, assistants connect through the connectors, with your sign-in. | Any member | | **Billing** | Invoices and their payment, the payment method, buying credits. | Owners and administrators | | **Profile** | Your first name, your last name and your language. | Each person, for themselves | In Escouade, the same pages open without leaving the workspace, in Settings › Account and subscription. ## Roles An organisation has three account roles: - **Owner**: everything, including naming or removing another owner. An organisation always keeps at least one owner. - **Administrator**: members, the organisation, billing. - **Member**: enters the family's applications and reads the account pages, except billing. These roles say who manages the organisation. What each person sees and changes in the Escouade workspace is set separately, by the workspace's roles: see [Access and roles](https://escouade.io/en/docs/escouade/acces.md). The first time they enter Escouade, a member arrives with the role the account gives them; a person removed from the organisation can no longer enter. ## Several organisations One person can belong to several organisations, with a role in each. The family switcher, at the top of each application, shows the current organisation and its size, and switches to another without signing in again. ## Language Your language, English or French, is set at your first sign-in from your browser; after that, you change it yourself, on the Profile page. The family's applications follow it. The account pages themselves are in French for now. ## Closing an organisation Closing an organisation marks it closed; its invoices and accounting records are kept, as the law requires. A person who has not signed in for three years is erased by the purge, as the [privacy policy](https://escouade.io/en/privacy) says. --- Source: https://escouade.io/en/docs/tailles.md # Sizes > Escouade comes as a single plan, with no price per user and none per module. Escouade, Meet, Mail, Social and Tools are in every size; from one size to the next, only the number of users and the usage allowance change. ## The four sizes | | Free | Essential | Pro | Max | |---|---|---|---|---| | **Price, excl. VAT, per month** | €0 | €19 | €60 | €249 | | **Users** | 3 | 3 | Unlimited | Unlimited | | **AI included** | None beyond the trial | The base allowance | About 3 times Essential | About 4 times Pro | | **Document storage** | 500 MB | 5 GB | 20 GB | 50 GB | | **Your data model** | Fields you can add | Fields you can add | Your own objects | Your own objects | | **Your assistant, through MCP** | Read and write | Read and write | Read, write and integrator | Read, write and integrator | Prices exclude tax: VAT not applicable, article 293 B of the French tax code (CGI). The ratios between sizes and the figures given as markers are indicative: they are recalibrated on actual use. Beyond the allowance, [credits](https://escouade.io/en/docs/utilisation-et-facture.md#credits) take over, without changing size. ## Feature by feature ### Escouade: CRM, documents, agents | | Free | Essential | Pro | Max | |---|---|---|---|---| | Records | 5,000 | No limit | No limit | No limit | | Gmail or Outlook mailboxes connected | None | 1 | All | All | | Questions to the chat | About a hundred quick questions in the trial, then credits | The base: about 1,000 quick questions a month | About 3 times Essential | About 4 times Pro | | Intelligence levels | Quick | All | All | All | | Voice | None | The base: about 15 min a month | About 4 times Essential | About 4 times Pro | | Reading files and searching by meaning | About fifty pages in the trial, then credits | No limit | No limit | No limit | ### Meet | | Free | Essential | Pro | Max | |---|---|---|---|---| | Meetings recorded | One 2-hour meeting in the trial, once | The base: about 10 h a month | About 2.5 times Essential | About 4 times Pro | | One hour in Meet's rooms | Counts as a third of an hour | A third of an hour | A third of an hour | A third of an hour | ### Mail | | Free | Essential | Pro | Max | |---|---|---|---|---| | Mailboxes on your domain | 1, which receives and writes only to you | 3 | 15 | 50 | | Emails sent per month, from your domain | None | The base: about 800 | About 2.5 times Essential | About 5 times Pro | | Unsubscribe and suppression list | Included | Included | Included | Included | ### Social | | Free | Essential | Pro | Max | |---|---|---|---|---| | Profiles that publish | 1 | 5 | 25 | 100 | | Profiles followed | No extra charge | No extra charge | No extra charge | No extra charge | ### Tools The thirteen tools of [Tools](https://escouade.io/en/docs/tools.md) are in every size, Free included: they run in your browser and consume nothing. ## Free Free is made for driving Escouade from your own assistant: Claude or ChatGPT, connected through MCP, reads and writes in it. It includes no Escouade AI, except the [free trial](https://escouade.io/en/docs/utilisation-et-facture.md#essai), once: a 2-hour meeting, about a hundred quick questions, about fifty pages read. Beyond that, credits, from €10. ## Changing size, cancelling - **Changing size** will be done from the account's Billing page. Until then, write to . - **Cancelling** means going back to Free: the days already used remain due, nothing more, and no data is deleted. Each day is paid at the size in force that day: see [The invoice](https://escouade.io/en/docs/utilisation-et-facture.md#facture). ## Guided onboarding Optional, one-off: **€600 excl. VAT**. It covers setting up your workspace, importing your data, one connected mailbox and an hour of getting started. Beyond that, support and training are charged by the day, **€500 excl. VAT**. ## On your own server To keep Escouade, the data and the AI on a server in your name, there is [Escouade hub](https://escouade.io/en/docs/escouade/hub.md): a licence, an integration, and AI with your own keys. Prices and their details, up to date: [the pricing page](https://escouade.io/en/pricing). --- Source: https://escouade.io/en/docs/utilisation-et-facture.md # Usage, credits and invoice > You pay for usage, not for people. Each size gives a usage allowance, followed as a percentage over the day and over the week; beyond it, credits take over if you have switched them on. A single monthly invoice covers the whole family. ## The Usage page The account's Usage page, on , shows what your organisation has consumed, read from the meter the moment you open it: one gauge per feature and per window, with its percentage, when it resets and, at the pace of the last 24 hours, when it will be full. In Escouade, the same page opens in Settings › Account and subscription. An alert shows when a gauge reaches **80%**. ## The allowances | What is counted | How | Windows | |---|---|---| | Questions to the chat | Per question; a question at a more thoughtful level counts for more than a quick one. | Day and week | | Meet meetings | To the second. One hour in Meet's rooms counts as a third of an hour. | Day and week | | Voice | To the second. | Day and week | | Emails sent by Mail | Per email. | Month | | Reading files | Per page. No limit in the paid sizes. | | The windows follow Paris time: the day resets at midnight, the week on Monday, the month on the 1st. A week's allowance is roughly a quarter of a month's, and a day's a third of the week's: a week cannot be emptied in a single day. Something already started is never cut off halfway: a meeting that runs past the allowance goes to the end, even if the gauge goes above 100%. A meeting is paid for once: its transcription is included in its time. ## The free trial On Free, the free trial replaces the allowance, once: - one **2-hour** meeting (6 hours in Meet's rooms, which count as a third); - about **100 quick questions** to the chat; - about **50 pages** read; - no voice. It is shared by the whole family and is never renewed: what has been used does not come back, even after a spell on a paid size. It is granted once per SIREN number and once per company email domain, at sign-up. The Usage page shows what is left. ## Credits Beyond the allowance, or beyond the trial on Free, credits take over: - they are bought in **packs of €10, €25 or €50 excl. VAT**, on the Billing page; - a pack is valid for **12 months**; - they serve every feature of the family; - credits offered by the publisher are used before credits bought, then the pack that expires first; - they are only used **if the organisation has switched them on**, and within the **monthly cap** it has set: never more than that cap beyond the allowance, per calendar month. Without credits switched on, or once the cap is reached, an action that goes beyond the allowance is refused, with the reason. ## The single invoice An organisation receives one invoice a month, for the whole family: - **The size**: Essential, Pro or Max, billed in arrears and to the day. A month's invoice is issued at the start of the following month; each day is paid at the size in force that day. The line names the whole family, since the size opens Escouade, Meet, Mail, Social and Tools. Free is not billed. - **Credits**: each pack is paid for when it is bought, then appears, marked as paid, on the invoice of the month in which it was paid. Payment goes through Mollie: the first purchase sets up a mandate, by SEPA direct debit or by card, on which the following months are collected. A refused direct debit is retried once, three days later. Each invoice is numbered without gaps (one series per calendar year), carries the buyer's company name, SIREN number and address, and the statement "TVA non applicable, article 293 B du CGI" (VAT not applicable). Once issued, it never changes: it reprints identically from the Billing page, as printable HTML. A size offered by the publisher has no line; credits bought are still billed. --- Source: https://escouade.io/en/docs/escouade.md # The Escouade workspace > Escouade is the family's workspace, at . It reads your emails and your documents, links them to your customers and your deals, and turns them into a shared memory that your team questions in the chat and that your agents read with your rights. ## Opening your workspace An organisation signed up to the [Escouade account](https://escouade.io/en/docs/compte.md) opens its workspace the first time it signs in to . The workspace arrives ready: the standard objects and their links, the chart of accounts, the journals, the VAT rates and the starting ingestion templates. The organisation's members enter on their own, with the role the account gives them. ## What is inside | Screen | What you do there | Page | |---|---|---| | **The chat** | Ask a question about a customer, a deal, a document; the answer cites its sources and can prepare a change. In writing or out loud. | [Chat, voice and agents](https://escouade.io/en/docs/escouade/chat-et-agents.md) | | **The CRM** | Contacts, companies, opportunities, deals, quotes, invoices, tasks: records linked to one another and to your emails. | [Objects and records](https://escouade.io/en/docs/escouade/fiches.md) | | **The Library** | Every file filed in the folder of its deal, read, scans included, and found again by what it says. | [The Library](https://escouade.io/en/docs/escouade/bibliotheque.md) | | **Ingestion** | What comes in (emails, Drive, uploads), how it is sorted and linked, and what awaits your decision. | [Ingestion](https://escouade.io/en/docs/escouade/ingestion.md) | | **The control centre** | The agents' proposals, each with its reason and its source, to approve or reject. | [Ingestion](https://escouade.io/en/docs/escouade/ingestion.md#a-traiter) | | **Artefacts** | Your documents, interactive pages, drawings and code, with their versions. | [Chat, voice and agents](https://escouade.io/en/docs/escouade/chat-et-agents.md#artefacts) | | **Dashboards** | Built from your records, team by team. | [Objects and records](https://escouade.io/en/docs/escouade/fiches.md#tableaux-de-bord) | | **Settings** | The data model, roles and access, connected accounts, the MCP servers, the account and subscription. | [Access and roles](https://escouade.io/en/docs/escouade/acces.md) | ## The path of an email 1. **It arrives**: from a connected Gmail, Outlook or IMAP mailbox, with its attachments. 2. **It is read**: the text, PDFs, scans, Word, Excel and PowerPoint documents. 3. **It is classified**: as a document, a record, a dated fact. 4. **It is linked**: to the contact, the company and the deal it concerns. 5. **It enters the memory**: the chat and your agents find it again, and cite it. What Escouade cannot settle on its own becomes a proposal, which awaits your decision. ## Your assistant, connected Escouade has three MCP servers: read, write and integrator. Claude or ChatGPT connects to them with an address and your sign-in, and acts with your rights: see [Escouade's MCP servers](https://escouade.io/en/docs/escouade/mcp.md). ## The family switcher At the top of the sidebar, the family switcher leads to Meet, Mail, Social, Tools and Prescriptio without signing in again, and shows your organisation and its size. In the settings, "My suite" says what your size gives you of each application, with a button to open it. ## Exporting your workspace An administrator downloads a complete archive of the workspace, through a link valid for 15 minutes. A free workspace with no activity for six months is warned by email thirty days before it is archived, and can still export its data. --- Source: https://escouade.io/en/docs/escouade/fiches.md # Objects and records > Escouade's CRM organises your company into **objects** (contacts, companies, deals…) and each item into a **record**. Records are linked to one another, to your emails and to your documents, and your agent keeps them up to date with you. ## The standard objects A new workspace arrives with the objects of a business, and the links between them: - **Contacts** and **companies**: one record per person and per company, with everything that concerns them. - **Opportunities** and **deals**: each with its amounts, its stages and its files; the pipeline shows them by stage. - **Quotes** and **invoices**, with their lines, the chart of accounts, the journals and the VAT rates. - **Tasks**, **notes** and **meetings**, attached to the records they follow. - **Documents**, filed in the [Library](https://escouade.io/en/docs/escouade/bibliotheque.md). - **Goals**: the target figure, what it measures, its period, its owner, and what it tracks. - **Lists**: contacts and companies brought together, with where they came from; a record joins a list through a simple, dated link. ## A record A record shows its fields, then what surrounds it: - **linked records**: a contact's company, a company's deals, an opportunity's tasks; - the **timeline**: dated facts, emails, meetings, files; - the **history**: who changed which field, when, with the value before and the value after. A change made by an assistant says where it came from: the connector, the chat, the integrator or an artefact. A deleted record goes to the **bin**, from which it can be restored. ## The pipeline Opportunities and deals move through stages, which you name the way you work. Views show what is active, what is waiting for a follow-up, what is at stake this week. ## List views An object's list has its tabs (for example, on deals, the schedule and the margins; on invoices, the accounting). In Settings › Data model, an object's "List view" card hides a tab, brings it back, changes their order or returns to the standard. Each tab follows the right to read its object. A menu entry can carry the name your company uses: "Accounts" instead of "Invoices", for example. Renaming is done where the menu is arranged, in the settings; the object's list keeps its name. ## The data model Add a field, a stage, a view: the CRM follows the way you work, with no development. On **Pro** and **Max**, you create your own objects. The integrator does the same through its MCP server: see [Escouade's MCP servers](https://escouade.io/en/docs/escouade/mcp.md#integrateur). ## Importing Importing a CSV file is included in every size. Escouade can also start alongside your current CRM, with your emails, then take over your records when you decide. ## Searching The magnifying glass, at the top of the sidebar (shortcut Ctrl K), searches everything at once: records, documents, emails. The chat, for its part, answers a question and cites its sources. ## Dashboards A dashboard is built from your records: active deals, documents to review, this week's tasks, team by team. Each person only sees what their rights allow. ## Records kept up to date An email arrives: Escouade recognises the sender and attaches it to their company and to the deal it concerns. An unknown contact becomes a proposed record, with its source. Every proposed creation and change awaits your decision, and an applied decision can be undone. See [Ingestion](https://escouade.io/en/docs/escouade/ingestion.md). --- Source: https://escouade.io/en/docs/escouade/bibliotheque.md # The Library > The Library is Escouade's document management: every file is filed in the folder of its deal, read, scans included, then found again by what it says. A question finds its answer, and cites the file. ## Every file in its place An attachment arrives with its email: Escouade classifies it, attaches it to the deal and the contact it concerns, and files it in the right folder. What it cannot settle becomes a proposal, in [ingestion](https://escouade.io/en/docs/escouade/ingestion.md). You can also upload your documents yourself. ## Read, scans included Escouade reads PDFs, scanned or not, Word, Excel, PowerPoint and OpenDocument files, CSVs and email attachments. Reading runs on our server, in a queue: what you upload goes before background work, and a large import takes a few days instead of being refused. The quality of a scan blocks nothing: a plan, a scanned table or an almost blank page is read, classified and filed. A "Scan quality to check" alert then names the pages and the reason (almost empty page, hard-to-read text, amount to check, scanned table of figures), on the document's record and in the assistant's answers. On the paid sizes, reading files and searching by meaning are not limited; only storage depends on the size (5, 20 or 50 GB). On Free, the trial reads about fifty pages, then credits take over, with 500 MB of storage. ## Find by content Search finds by exact words as well as by meaning. "What delivery time did we agree?": the answer cites the file and the passage, and the document opens in one click. ## Rights Each person only sees the documents within their scope: those their role reads, those of the mailboxes they read, those shared with them. The answers of the chat and of assistants respect the same rights. See [Access and roles](https://escouade.io/en/docs/escouade/acces.md). ## Sources In the Library, Options › Sources shows where documents come from, and when each source was last read. - **Google Drive for the workspace**: a Drive connected for the whole company synchronises the folders you choose. A file joins the deal whose code appears in the name of one of its folders, in a sub-folder named after yours; a folder with no known deal code keeps its path. Each document says where it came from ("Google Drive · Folder/File.xlsx"). - **The master context**: from its page, "Connect Google Drive", then the folders to synchronise. The exports your management software drops there every day arrive on their own, about ten minutes after they are updated. An export dropped again under the same name stays the same document, with a new version: nothing piles up, the history is kept. You choose which roles can read them. - **Google Drive for me**: a personal Drive is read in your own chat; it never synchronises to the workspace. - **Escouade Tools**: what you save in a [Tools](https://escouade.io/en/docs/tools.md) tool arrives in the "Tools" folder, under your rights; each tool reopens its files from the Library. A source is shared with chosen roles, rather than with the whole workspace or no one. ## Where documents are kept Online, each workspace keeps its documents in its own storage, in France, within the limit of its size. With [Escouade hub](https://escouade.io/en/docs/escouade/hub.md), they stay on your server. --- Source: https://escouade.io/en/docs/escouade/ingestion.md # Ingestion > Ingestion is the path that turns an email or a document into knowledge about your company: it arrives, it is read, sorted, linked to its records, then remembered. What Escouade cannot settle on its own becomes a proposal, which awaits your decision. The module opens from the "Ingestion" entry of the menu. Its bar follows the path of an email: **Overview**, then **Sources › Rules › Decision model › LLM analysis › To review**, then **Health** and **Settings** for those allowed. ## Sources The Sources page shows where data comes from: - from Escouade: each mailbox you read, each Google Drive of the workspace, uploads to the Library; - from connected applications and services: Meet, whose minutes arrive through the family relay, or supplier invoice software. For each source: its status, what it brought today and over seven days, and its last arrival. A silent mailbox goes to the top. A mailbox is connected in Settings › Accounts, where its ingestion is switched on: see [Connectors](https://escouade.io/en/docs/connecteurs.md). ## Sorting, in a cascade Every email goes down three levels, in order, and stops at the first one that can settle it: 1. **Rules**: the ingestion rules and the decision tree (what is decided for each email, its outcomes, the catch-up). A rule settles without hesitation what always comes back the same way. 2. **Decision model**: a model that learns from your past decisions, with two thresholds per question, set on its screen. It learns from the decisions, ground truths, datasets and extractions the screen shows. 3. **LLM analysis**: a language model votes three times; the decision is taken when the quorum is reached. The screen shows how far the vote agrees with history. What no level settles goes to **To review**. The Overview shows, over a period, who settled things: the rules, the model, the analysis, or a member of the team ("Human approvals"). ## To review: the control centre To review gathers everything that awaits a human decision: **proposals**, **documents to re-read**, **questions** and the **review queue**. The badge in the menu shows the count. A proposal is a change an agent wants to make: - create a record, update a field; - link an email to its deal, classify a document; - create a task, complete a timeline. Each one says why, cites the email or document that gave rise to it, and gives a confidence score. **Approve** applies it; **reject** sets it aside. An applied proposal can be undone, and the control centre keeps track of what was decided. ## Rules, when the answer is always the same When a proposal keeps coming back and you always approve it, make it an "Always apply" rule. It stays visible, and you can remove it. Some filing operations apply without waiting: filing an attachment in its folder, linking an email to its deal. ## Health Health holds the ingestion alerts. The "Silent mailbox" alert counts in working hours: a mailbox that is quiet in the evening or at the weekend does not ring; "Critical" is reserved for a synchronisation that has truly failed. --- Source: https://escouade.io/en/docs/escouade/chat-et-agents.md # Chat, voice and agents > Escouade's chat answers from your records and your documents, and names them. You can talk to it out loud. Agents, for their part, prepare the work: every change they propose awaits your decision. ## The chat Ask a question about a customer, a deal or a document: the answer draws on your records and your files, and cites them. When the information is missing, the answer says so. The chat can also prepare a change (a delivery date, a record to create), which you apply or not. It answers with your rights: it only reads what you read. ## Intelligence levels The chat has four levels, from the fastest to the most thoughtful: **Quick** (Rapide), **Standard**, **Reasoning** (Réflexion) and **Expert**. A question at a more thoughtful level uses more of the allowance. Free only has the Quick level; the paid sizes have them all. The models that answer are named in the chat and in the settings, with their origin and where they run. ## Voice mode The "Voice mode" button, next to the microphone, turns the conversation into a spoken exchange: the orb comes alive as the assistant listens, thinks and answers. It is the same chat, with the same tools, the same rights and the same conversation: each exchange is written into it, and you find it in writing when you finish. When the assistant has to search, it says so, then answers. Voice is included in the paid sizes (about 15 minutes a month on Essential), not on Free nor in the trial. ## Artefacts An artefact is a document, an interactive page, a drawing or some code that you keep. Artefacts have their own page in the menu. - In the chat, the assistant creates an artefact when the answer lends itself to one or when you ask, and picks it up again: "add a column" saves a new version of the same artefact. - Each artefact keeps its versions: you look back at a past version and can restore it. - An artefact is **private**, administrators included, until you share it: with a member, a team or the whole workspace, read-only. It can be pinned to the menu, renamed, put in the bin and restored. - An interactive page runs in an isolated frame: it reads neither your session nor the workspace's data. If it wants to read or write in the CRM, an "Allow" banner asks you on its first call; it then acts with your rights, and every write is signed and logged. If it offers a file, a banner gives its name and size, and nothing is saved without your click. - A page created in Claude is sent into Escouade by the connected assistant (one more version if it is already there), up to 4 MB per version, and works as is. ## Automations An automation has a trigger (a schedule, an email, a file received), steps and a result: a summary of the deals every morning, a check on every file received, a report every week. They are built in the tool, with no code. ## Agents Agents read your emails and your documents and prepare the work: a record to create, a deal to update, an email to link. Each proposal comes with its reason and its source, and awaits your decision in [To review](https://escouade.io/en/docs/escouade/ingestion.md#a-traiter). ## Your own assistant If you already use Claude or ChatGPT, connect it to Escouade: it reads your records, your documents and your emails there, and writes there, with your rights. On Free, that is the way to drive Escouade. See [Escouade's MCP servers](https://escouade.io/en/docs/escouade/mcp.md). --- Source: https://escouade.io/en/docs/escouade/mcp.md # Escouade's MCP servers > Escouade has three MCP servers. Your assistant (Claude, ChatGPT, or any MCP client) connects to them with an address and your Escouade account sign-in, and acts with your rights: it reads what you read, writes what you can write, and every write carries your signature. ## The three servers | Server | Address | For | Sizes | |---|---|---|---| | **Read** | `https://app.escouade.io/mcp` | Searching, reading and summarising records, documents and emails. | All | | **Write** | `https://app.escouade.io/mcp/ecriture` | Creating and changing records on behalf of the signed-in member; every write is logged. | All | | **Integrator** | `https://app.escouade.io/mcp/integration` | Setting up the model, the objects and the workspace, as an administrator would on screen. | Pro and Max | The three connect side by side: read first, write when the assistant has to act, the integrator for configuration. ## Connecting a server **In Claude** (claude.ai, and the desktop app, which picks up the account's connectors): 1. Open [Claude's connectors](https://claude.ai/settings/connectors), then "Add custom connector". 2. Give it a name ("Escouade read", for example) and paste the address. 3. "Connect": sign in with your Escouade account, choose the organisation, allow. In a Claude Team or Enterprise organisation, an owner adds the connector; each member then connects to it themselves. **In ChatGPT**: its settings, then the connectors, with developer mode switched on; create a connector with the address and OAuth authentication, then sign in with your Escouade account. ChatGPT's labels change often: only the address matters. **In Claude Code**: ```sh claude mcp add --transport http escouade https://app.escouade.io/mcp ``` then `/mcp` in a session to sign in. The addresses of all the family's servers are also on the account's Connectors page, and on [The family's MCP servers](https://escouade.io/en/docs/mcp.md). ## The tools On `app.escouade.io`, the tools carry the `escouade_` prefix. On an [Escouade hub](https://escouade.io/en/docs/escouade/hub.md) instance, they carry the instance's name. ### Read | Tool | What it does | |---|---| | `escouade_trouver` | Searches everything at once (records, documents, emails, dated facts), by words and by meaning, with filters, and returns a selection. | | `escouade_selection` | Reads the rest of a selection, or narrows it, without running the search again. | | `escouade_consulter` | Opens an item by its identifier: its summary, its full record; for a document, its text, a search within the document, its neighbouring passages or a download link. | | `escouade_relations` | What surrounds a record: linked records, timeline, files, emails, and the history (who changed what). | | `escouade_modele` | Describes the objects and their fields, read afresh at each call: it is the reference when the model has changed. | The read server says on whose behalf it answers ("Connecté en tant que …", signed in as): a real call shows whether the connector was connected under the right account. ### Write | Tool | What it does | |---|---| | `escouade_ecrire` | Creates, changes, links, unlinks, puts in the bin and restores records. A creation sets its links in the same call. Each call carries a unique key: replayed, it does not write twice. | | `escouade_envoyer` | Sends an email from your connected mailbox, with an optional blind copy, then attaches it to the chosen records and leaves a "Follow-up sent" note on them. | | `escouade_journal` | The log of writes made by assistants: who wrote what, when, through which route, with what result, most recent first. It is read by an administrator. | | `escouade_modele` | An object's fields, to read before writing. | | `escouade_artefact` | Sends a page created in Claude into Escouade, or a new version of it, then shares it with a member. | Identifiers come from the read server: the write server does not search by text. A refusal names the problem: the assistant corrects its call rather than guessing. **Sending emails is closed by default.** An administrator opens it role by role, in Settings › MCP, Write tab ("Envoyer des courriels", send emails). Claude asks for confirmation before each send, and a send never goes out twice under the same key. ### Integrator | Tool | What it does | |---|---| | `escouade_superviser` | Ingestion: the traces, the "To review" queue, the scenarios, the thresholds, the alerts, the decision model's test bench. | | `escouade_parametrer` | The data model and every setting of the workspace, through the same functions and the same safeguards as on screen. It also tests a person's access, lists Claude's connections, shares a record or a mailbox. | | `escouade_ecrire` | The data of any object. | | `escouade_modele` | The objects and their fields. | | `escouade_artefact` | The workspace's artefacts. | The integrator is the configuration server: an administrator sets through it what they would set on screen, without touching the database. It is included from **Pro**. ## Under which rights - **Through Claude, each person has exactly their rights in the application**: what their role, their groups and their exceptions open to them, and none of what is withdrawn from them (a hidden field stays hidden). - The MCP server settings are added on top, in Settings › MCP: which roles have which server, at which level, object by object. - Every write carries the signature of the signed-in member and leaves a line in the log. - A Claude connection **unused for 14 days is erased** on its own; each use extends it. When you come back, Claude simply asks for your consent again. ## The call log Every call to the MCP servers (read, write, integrator), refusals and abandoned calls included, is kept for **six months**: who, from which device, which tool, which result. An administrator reads it through the integrator. ## The protocol The servers speak MCP over Streamable HTTP. Authorisation follows the OAuth part of the MCP specification: a client only needs the address; it discovers the authorisation server through the protected resource metadata, and the person signs in through the Escouade account. --- Source: https://escouade.io/en/docs/escouade/acces.md # Access and roles > Each role sees its own scope: the objects it reads, those it changes. The chat, the agents and the assistants connected through MCP respect exactly the same rights as the screen. ## Two levels of roles - **In the Escouade account**: owner, administrator or member. These roles say who manages the organisation, its members and its invoice. See [The account](https://escouade.io/en/docs/compte.md#les-roles). - **In the Escouade workspace**: the workspace's roles say what each person sees and changes in the data. A member enters the workspace with the role the account gives them, then a workspace administrator adjusts it. ## A role's rights For each object (contacts, deals, invoices…), a role can **read**, **create**, **change** and **put in the bin**, or not. A role can also have **hidden fields**: margins, for example, stay invisible to those who should not see them, on the record, in lists, in the chat and through Claude. A screen follows the right to read its object: the Accounting tab of invoices opens to whoever reads invoices, the deals' schedule to whoever reads deals. Beyond their role, a person can receive rights through a group or through an exception in their name; what is withdrawn from them stays withdrawn. ## Sharing The "Share" button opens a record or a mailbox to a role, a person or a team, at a given level; the share can be changed or removed. Artefacts are private until their author shares them, administrators included. ## Mailboxes An email is read by whoever reads its mailbox. A mailbox can be: - **personal**: connected by a person, for themselves; - **the workspace's**: a shared mailbox or a Drive, connected for the workspace in Settings › Accounts. The departure of the person who connected it stops nothing. Those who manage the workspace's mailboxes and Drives can reconnect them, disconnect them and switch on their ingestion. A member who still has personal mailboxes connected cannot be removed from the workspace: the screen says which ones to move to the workspace first. ## Shared connectors A shared connector (a workspace Drive, invoice software, electronic signature, Meet…) is connected once for the whole company. Who manages it (connecting it, configuring it, disconnecting it, offering it in the chat) is set role by role on its card; by default, administrators. Other members see it, without being able to change it. ## Assistants and MCP servers Through Claude or ChatGPT, each person has exactly their rights in the application. The MCP server settings are added on top, in Settings › MCP: which roles have read, write and integrator, at which level, object by object, and who can send emails through the assistant. See [Escouade's MCP servers](https://escouade.io/en/docs/escouade/mcp.md#sous-quels-droits). Deleting a role also removes it from the settings that named it: MCP access, sending emails, connectors, default role. ## Checking access The integrator MCP server tests a person's access, without changing anything: what they read, create, change and put in the bin, object by object, the fields hidden from them, the mailboxes they read and their MCP servers. For a record, it says whether they see it and, if not, why: the bin, their role, or an email from a mailbox they do not read. It also lists the Claude connections still valid, account by account, and flags a connector connected under a shared mailbox's account. --- Source: https://escouade.io/en/docs/escouade/hub.md # Escouade hub > Escouade hub is the edition of Escouade on your own server: the CRM, the documents, the agents and the three MCP servers, the data and the AI, installed on a server in your name. Your data stays with you. ## What is included - **Escouade**: the CRM, the Library, ingestion, the chat, the agents, automations, and the three MCP servers (read, write, integrator). - Installing and configuring the server, configuration within the agreed scope, ingestion of the agreed context, setting up backups. - **Six months of updates.** ## What is not - **Meet, Mail, Social and Tools**: they are taken as an online subscription, as for all our customers. Your Gmail and Outlook mailboxes, for their part, connect to your instance. - Taking over data from a third-party tool, quoted separately. - Hosting and AI consumption: the server is in your name, and the AI runs with your own keys, with the providers of your choice, with no allowance. - Training and needs beyond the scope, server administration, custom development. ## The price | | | |---|---| | **Licence** | €8,000 excl. VAT, with no usage term, with six months of updates | | **Integration** | At least €3,000 excl. VAT, set in the quote according to your context and processes | | **Per user** | €0: you hire without changing plan | | **Maintenance, after six months** | Under €900 excl. VAT a year, optional: it extends the updates | | **Training and support** | €500 excl. VAT per day, on request | Prices exclude tax: VAT not applicable, article 293 B of the French tax code (CGI). We sign a licence agreement together before any installation. Without maintenance, your installation keeps running with the version it has, and your data stays accessible. ## What differs from the online edition - **An instance never depends on the online Escouade account**: it has its own sign-in and its own accounts. The family switcher only appears there if the publisher switches it on. - **The MCP tools** carry the instance's name instead of `escouade_`: on an instance named "hub", `hub_trouver`, `hub_ecrire`… The addresses follow your server's: `https:///mcp`, `/mcp/ecriture`, `/mcp/integration`. - **AI providers** are set in Settings › AI › Providers, with your keys: the chat's language model and the voice of voice mode, for example. ## Installation We install and configure Escouade on a server in your name. How long it takes depends on the access to be approved and the volume of data to take over; we specify it during scoping. To talk about it: , or [the pricing page](https://escouade.io/en/pricing#achat). --- Source: https://escouade.io/en/docs/meet.md # Escouade Meet > Escouade Meet, at , opens video rooms, joins your usual video calls and records your meetings in the field, then writes the minutes: the decisions, the actions, who takes them on. The minutes join the deal and the contacts they concern. Meet is included in every size. Robotmeet becomes Escouade Meet: a connector already connected to `robotmeet.fr` keeps working. ## Recording a meeting - **In Meet's rooms**: each meeting has its room, opened in the browser, with no software to install. One hour in these rooms counts as a third of an hour against your allowance. - **On a video call elsewhere**: the bot joins the meeting through its link, at the scheduled time, from the calendars you follow, whether you are there or not, including when a customer or a partner organises it. It covers five video platforms. For an impromptu meeting, paste its link. It appears in the list of participants, followed by your name, or under the name you give it in your settings. - **In person**: the phone recorder has participants' consent confirmed, then records. It keeps the recording on the device until it is sent, and works without a network after a first online opening. See [The apps](https://escouade.io/en/docs/meet/applications.md). If a waiting room is on, the organiser must admit the bot: until they do, nothing is recorded, and the meeting's page says so. An email tells you when the minutes are ready. ## Participants' consent Informing participants and obtaining their consent is the organiser's job, whether present or not; the bot's visible presence does not replace it. - In person, the recorder asks you to confirm that consent before starting. - On a video call, the bot announces itself in the meeting chat: if someone replies "no" there, it stops recording and leaves. This is not possible on a platform where it cannot write in the chat, nor when the platform closes the chat to it. - From the meeting's page, you remove it on every platform; the organiser can remove it like any participant. - By default, the organiser of a meeting you do not organise receives an email, once, telling them the bot will come and how to refuse it. ## Calendars Meet reads your Google and Outlook calendars, or Microsoft 365, without ever changing them, and you choose which calendars it follows. No Google or Microsoft password is entered in it. ## The minutes At the end of the meeting, the minutes are ready, in French: what was decided, what has to be done, and by whom. Five templates write them according to the meeting: | Template | For | |---|---| | General | Any meeting. | | Team meeting | Team and follow-up meetings. | | Customer meeting | Needs, objections, commitments, next step. | | Recruitment | An interview: factual, with no personal judgement, and without deciding for you. | | Site meeting | Building site meetings and on-site reviews. | They are written by an AI model from the text of the transcription: the audio is not sent to it. Actions keep their owner and their deadline, and can become tasks attached to the deal. You re-read them, correct them, send them. ## The transcription The transcription is timestamped and says who is speaking. You rename voices, find a passage to the second, and export it as text or subtitles. No accuracy rate is promised: quality depends on the sound, the number of voices and the trade's vocabulary, and the full transcription stays next to the minutes to check a sentence. ## Asking and finding Ask a question about your meetings: the answer cites the meeting it comes from. Search finds by meaning as well as by exact words; when the information is missing, the answer says so. Minutes also enter Escouade's memory, where the chat finds them. ## Sharing Each meeting stays private until you share it; sharing can be withdrawn at any time. The minutes go to participants through a viewing link, without the transcription, your personal notes or the audio. They export as PDF, Markdown, text, subtitles or JSON. ## Your data By default, nothing is deleted: meetings, transcriptions and minutes are kept without limit. You can choose 30 days, 90 days or one year in the settings. Audio and video are kept as long as the meeting. A deleted meeting spends seven days in the bin, then all its copies are erased. Minutes, transcriptions and recordings belong to your company. The details: [consent, retention and privacy](https://escouade.io/en/software/meet/privacy). ## Price and cancellation Meet is included in every size, with no per-user price; your organisation's members are invited from the Escouade account. The free trial includes one recorded meeting of up to two hours, once per organisation; after that, each size gives an allowance, and credits take over beyond it. See [Sizes](https://escouade.io/en/docs/tailles.md#meet). Cancelling means going back to Free: the days already used remain due, nothing more, and no data is deleted. ## Your assistant and your tools Your assistant questions your meetings through Meet's MCP server, with a separate permission for transcriptions; it can prepare an action, which you confirm. A read-only API and signed webhooks serve your own tools. See [Meet for developers](https://escouade.io/en/docs/meet/developpeurs.md). Meet's help, with its frequently asked questions: [escouade.io/en/software/meet/help](https://escouade.io/en/software/meet/help). --- Source: https://escouade.io/en/docs/meet/applications.md # Meet's apps > The same space for your meetings, in the browser, on the phone and on the computer. Here is what installs today, and what is in preparation. ## In the browser, everywhere The Escouade Meet space opens in the browser, on the computer as on the phone: your meetings, their minutes, search and the chat. Video rooms open there too, with nothing to install: . ## The phone, with the web recorder The web recorder installs on the home screen of an iPhone or an Android phone: . - On iPhone: in Safari, Share, then Add to Home Screen. - On Android: in Chrome, Install app. After a first online opening, it also works without a network, and keeps the recording on the phone until it is sent; sending does not delete the local copy, and an interrupted recording can be recovered. In beta: keep the screen on and the app in the foreground, up to **60 minutes** per recording. ## The Windows app, in beta It records your video calls and your meetings from the computer. Capture happens on your machine: no participant is added to the meeting. It handles video calls from the main platforms, in their desktop app or in Chrome and Edge depending on the platform, and your in-person meetings. | | | |---|---| | Version online on 20 October 2026 | 0.4.4, of 14 October 2026 | | System | Windows 10 or 11, 64-bit | | Installer | 139 MB, no administrator rights needed | | SHA-256 fingerprint | `20aa0e041225c9574d444442f55fcef4bfc6ee9e996c41c3d1e97b11db3e0361` | | Download | | Open the downloaded file: the app installs, then opens. To uninstall it: Settings, then Apps. This version is not signed yet: if Windows shows "Windows protected your PC", choose "More info", then "Run anyway". First check that the file's fingerprint is the one in the table: ```sh certutil -hashfile SHA256 ``` ## In preparation These apps are in development and not yet distributed: none can be downloaded today. - **iPhone**: record a meeting, mark a moment and attach context to the meeting. - **Apple Watch**: start from the wrist and keep track of important moments. - **Android**: the recorder and the library from the phone. - **Mac**: capture from the computer and access to meetings. The website page, kept up to date: [escouade.io/en/software/meet/apps](https://escouade.io/en/software/meet/apps). --- Source: https://escouade.io/en/docs/meet/developpeurs.md # Meet for developers > Meet has a read-only REST API, signed webhooks and an MCP server. Keys, webhooks and connected assistants are managed in Meet's space, account menu "Développeurs" (`/developpeurs`). The REST API, the keys and the webhooks are **read-only**: nothing there creates, changes or deletes a meeting, minutes or an action. A key only reads the meetings its owner owns, outside the bin; never those other members share with their teams. ## API keys A key is created in Développeurs › Clés, with a name and at least one permission. Its value is shown **once only**, right after creation. It has the form `rmk_` followed by an eight-character public identifier, a `_` and a secret; only its fingerprint is kept. It can be revoked at any time, for good. An account has at most 20 active keys. | Permission | Opens | |---|---| | `meetings:read` | The list and details of meetings: title, date, status, origin, calendar context. | | `reports:read` | Minutes: summary, key points, decisions, open questions, chapters. | | `actions:read` | The actions in the minutes: owner, deadline, "done" status. | | `transcripts:read` | Transcriptions, with a permission of their own. | | `usage:read` | The month's time, through the MCP server (`get_usage` tool). | ## The REST API Base address: `https://meet.escouade.io/v1`. Authentication: `Authorization: Bearer rmk_…`. Responses in JSON, dates in RFC 3339 (UTC). Any method other than `GET` receives `405`. The API sends no CORS headers: it is called from a server, never from a web page, where a key must not live. | Resource | Permission | Returns | |---|---|---| | `GET /v1/meetings` | `meetings:read` | `{"data": [meeting…], "next_cursor": "…" or null}` | | `GET /v1/meetings/{id}` | `meetings:read` | `{"data": meeting}` | | `GET /v1/meetings/{id}/report` | `reports:read` | `{"data": minutes}`, without the actions | | `GET /v1/meetings/{id}/actions` | `actions:read` | `{"data": [action…]}` | | `GET /v1/meetings/{id}/transcript` | `transcripts:read` | `{"data": {"meeting_id", "segments": […]}}` | ```sh curl -s https://meet.escouade.io/v1/meetings?limit=5 \ -H 'Authorization: Bearer rmk_…' ``` ### List and pagination `GET /v1/meetings` returns the most recent meetings first. Parameters: `limit` (1 to 100, 20 by default), `cursor` (the `next_cursor` value of the previous page, as is), `status` (a status below). `next_cursor` is `null` on the last page. ### A meeting | Field | Content | |---|---| | `id` | The meeting's identifier. | | `title` | Title. | | `status` | Public status (below). | | `starts_at` | Start; for a phone recording, when it was sent. | | `scheduled_end_at` | Scheduled end, for a calendar meeting; otherwise `null`. | | `origin` | `calendar` (connected calendar), `link` (pasted link), `phone` (recorder), `desktop`, `manual` (meeting noted in Meet). | | `platform` | `meet`, `teams`, `zoom`, `webex`, `goto`, `in_person`, `desktop`, `other`. | | `organizer_email` | Organiser known from the calendar, otherwise `null`. | | `context` | Calendar description as plain text (1,200 characters at most), otherwise `null`. | | `has_transcript`, `has_report` | A transcription, minutes exist. | | `updated_at` | Last change. | | `participants` | `{"email", "name", "response", "organizer"}`, organiser first; `response` among `accepted`, `tentative`, `declined`, `pending`, `unknown`. | Never: the video call link, a file path, an internal technical identifier. ### Statuses | `status` | Meaning | |---|---| | `planned` | Scheduled. | | `joining` | The bot is joining the meeting or waiting in the waiting room. | | `recording` | Recording in progress. | | `processing` | Transcription and minutes being prepared. | | `transcript_ready` | Finished with a transcription, without minutes. | | `report_ready` | Finished with minutes. | | `completed` | Finished without transcription or minutes. | | `failed` | Processing did not succeed. | | `missed` | Missed. | | `unsupported` | Platform not supported. | ### Minutes, actions, transcription - **Minutes**: `meeting_id`, `template`, `summary`, `key_points`, `decisions`, `open_questions` (each `{"text", "source_seconds"}`), `chapters` (`{"title", "summary", "source_seconds"}`). No minutes yet: `404 not_ready`. - **Action**: `id` (stable key), `title`, `assignee`, `due` (free text as spoken, may be `null`), `completed`, `source_seconds`. - **Transcription**: `segments` of `{"start", "end", "speaker", "text"}`, in seconds; `speaker` is `null` when the speaker is not known. ### Errors and limits Error body: `{"error": {"code": "…", "message": "…"}}`; for a `403`, `required_scope` as well. | HTTP | `code` | When | |---|---|---| | 400 | `invalid_parameter` | `limit` or `status` outside the allowed values. | | 400 | `invalid_cursor` | Unreadable cursor. | | 401 | `unauthorized` | Key missing, unknown or revoked. | | 403 | `insufficient_scope` | Missing permission. | | 404 | `not_found` | Meeting that does not exist, belongs to another account or is in the bin. | | 404 | `not_ready` | No minutes or transcription yet. | | 405 | | Method other than `GET`. | | 429 | `rate_limited` | More than 120 calls per minute for the key, or from the same IP address for the API and MCP combined. `Retry-After` header. | | 500 | `internal_error` | Service error. | ## Webhooks Destinations are managed in Développeurs › Webhooks: an **HTTPS** address reachable on the Internet, the chosen events, at most 10 destinations per account. | Event | Sent when | |---|---| | `meeting.transcript_ready` | A transcription is saved (it may be empty if nobody spoke). | | `meeting.report_ready` | The minutes are saved. | | `meeting.processing_failed` | The recording or the transcription did not succeed. | The body carries only the essentials; the title and content are then read through the API, with a key: ```json {"id": "evt_…", "type": "meeting.report_ready", "created_at": "2026-10-20T09:41:07Z", "data": {"meeting_id": "…", "status": "report_ready"}} ``` ### Verifying the signature The headers follow the [Standard Webhooks](https://www.standardwebhooks.com/) convention: - `webhook-id`: the event's identifier, **the same on every retry**; - `webhook-timestamp`: the moment, in Unix seconds; - `webhook-signature`: `v1,` followed by the HMAC-SHA256, in base64, of `{webhook-id}.{webhook-timestamp}.{body}`, keyed with the `whsec_…` secret without its prefix, decoded from base64. Verify in constant time, refuse a timestamp more than 5 minutes off, ignore a `webhook-id` already processed. The secret is shown once, when the destination is created. ```python import base64, hashlib, hmac, time def verify(secret, headers, body): key = base64.b64decode(secret.removeprefix("whsec_")) message = "%s.%s.%s" % (headers["webhook-id"], headers["webhook-timestamp"], body) expected = base64.b64encode(hmac.new(key, message.encode(), hashlib.sha256).digest()).decode() if abs(time.time() - int(headers["webhook-timestamp"])) > 300: return False return any(hmac.compare_digest("v1," + expected, s) for s in headers["webhook-signature"].split()) ``` ### Delivery Your endpoint replies `2xx` within 10 seconds. Otherwise, a retry goes out after 30 s, 2 min, 10 min, 30 min, 1 h, 3 h then 6 h: **8 attempts at most**, then the event is marked abandoned. A delivered or abandoned event can be resent from the page, with the same identifier. No redirect is followed. A paused destination accumulates its events, which go out when it resumes. ## The MCP server Address: **`https://meet.escouade.io/mcp`**, over Streamable HTTP, without sessions. An assistant connects through OAuth, with the address alone; a program, with an `rmk_…` key in `Authorization: Bearer`. Twenty-one tools: eleven **read**, five **prepare** an action and five are reserved for the assistant's views. | Read tool | Permission | What it returns | |---|---|---| | `search_meetings` | `meetings:read` | The meetings matching a search. | | `get_meeting` | `meetings:read` | A meeting. | | `get_report` | `reports:read` | Its minutes. | | `get_action_items` | `actions:read` | Its actions. | | `get_transcript` | `transcripts:read` | Its transcription. | | `get_today` | `meetings:read` | A day's meetings, and the open actions with `actions:read`. | | `get_robot_status` | `meetings:read` | Where the bot stands in a meeting. | | `list_action_items` | `actions:read` | The actions of recent minutes, filtered by owner or status. | | `search_passages` | `transcripts:read` | The passages matching a search, by meaning or by exact word. | | `ask_meetings` | `reports:read` and `transcripts:read` | The answer to a question, with its sources; `found` is `false` when the information is missing. | | `get_usage` | `usage:read` | The month's time: included, used, remaining. | ### Prepare, then confirm An assistant connected through OAuth can **prepare** an action; it is only carried out once **confirmed** by the person, in the assistant's view or on a Meet page. Never through an API key, never through the REST API. | Tool | Permission | What confirmation will do | |---|---|---| | `send_robot` | `meetings:write` | Sends the bot into the video call, now. | | `stop_robot` | `meetings:write` | Removes the bot from the meeting. | | `create_meeting` | `meetings:write` | Notes a meeting in Meet, with no video link and no calendar invitation. | | `update_action_item` | `actions:write` | Ticks or unticks an action in the minutes. | | `share_report` | `reports:share` | Sends each recipient a viewing link to the minutes, valid for 7 days. | A prepared action waits for 10 minutes. What leaves Meet with no way back (an email sent, the bot sent through a pasted link) can only be confirmed on the Meet page. No deletion, no payment, no sending of a transcription or recording by this route. ### OAuth authorisation Meet follows the authorisation part of the MCP specification: OAuth 2.1, public clients, mandatory PKCE S256, dynamic registration and client metadata documents. The consent page lists permissions in two groups, **Read** and **Act**; only the four meeting reads are ticked by default, nothing that acts. The access token lasts an hour and is renewed; Développeurs › Serveur MCP lists the connected assistants, with "Revoke". ### Connecting the assistant - **Claude**: Settings › Connectors › "Add custom connector", name "Escouade Meet", address `https://meet.escouade.io/mcp`; "Connect", then your Escouade account, the permissions, "Allow". - **ChatGPT**: in developer mode, a connector with the same address and OAuth authentication. - **Claude Code**: ```sh claude mcp add --transport http escouade-meet https://meet.escouade.io/mcp ``` A connector already connected to `https://robotmeet.fr/mcp` keeps working; moving to the new address means connecting it again, then revoking the old one. --- Source: https://escouade.io/en/docs/mail.md # Escouade Mail > Escouade Mail, at , opens mailboxes on your domain, for a person or for an agent, sends your prospecting campaigns and follows up in the thread of the conversation, until someone replies. A reply stops the sequence, and joins the contact's record. Mail is included in every size. Subagent becomes Escouade Mail: the API keeps its address, `https://api.subagent.fr`, and connectors already connected keep working. ## Its full documentation Mail has its own documentation, written for agents as well as for developers: mailboxes, messages and threads, drafts and their approval, campaigns, sending rules, domains, keys, the HTTP API, webhooks and the reference of every tool. It is in French for now; its English translation is in preparation. - [escouade.io/mail/docs](https://escouade.io/en/mail/docs/index.md), in French. - For an agent: [/mail/docs/llms.txt](https://escouade.io/en/mail/docs/llms.txt) ## What it does - **Mailboxes** on your domain, for a person or for an agent. The agent writes, receives and replies with its own address. - **Nothing leaves without you, when you want it so**: a message can require approval; it then waits, as a draft, for a human to re-read, correct or refuse it. An agent never approves its own messages. - **It reads without obeying**: what a third party writes reaches the agent marked as untrusted data, never as an instruction. - **Prospecting**: a campaign brings together a mailbox, an audience and one to four steps, with up to three variants to compare. Emails leave from your domain, spread over the day, with warm-up for a new domain. Every first message carries an unsubscribe link. - **Follow-ups in the thread**: a follow-up replies to the previous message; as soon as the recipient replies, the follow-ups stop for them, and for their company. - **Sending rules that protect your domain**: a new mailbox ramps up in stages; a mailbox that bounces too much stops. See [the sending rules](https://escouade.io/en/software/mail/deliverability). - **Linked to the CRM**: every reply joins the contact's record and their deal in Escouade, and a campaign launched from Escouade takes its recipients from your contacts. Mail writes to one person at a time, at a human pace: no bulk sending, no transactional emails. ## Connecting it | Who | Address | How | |---|---|---| | Your assistant (Claude, ChatGPT) | `https://mail.escouade.io/mcp` | A connector, with your Escouade account. | | An autonomous agent | `https://api.subagent.fr/mcp` | An `sak_…` key of its own; without a key, it signs up by itself. | | Your code | `POST https://api.subagent.fr/v1/{operation}` | The same key, the same operations as MCP. | An agent's key never carries the right to approve: that right stays with humans. Step by step, in French: [Brancher mon agent](https://escouade.io/en/mail/docs/brancher.md). ## By size Free: one mailbox, which receives and writes only to you. Essential: 3 mailboxes on your domain; Pro: 15; Max: 50. See [Sizes](https://escouade.io/en/docs/tailles.md#mail). Your Gmail and Outlook mailboxes do not change: they connect to Escouade, which reads them and links them to your records. Mail adds mailboxes; it does not make you leave yours. ## The public tools The Python SDK, the TypeScript SDK, the command line, the agent recipes, the Claude Code plugin and the examples are public, under the MIT licence: see [GitHub](https://escouade.io/en/docs/github.md). --- Source: https://escouade.io/en/docs/social.md # Escouade Social > Escouade Social, at , prepares the posts of each of your LinkedIn profiles, in that person's own voice, has them approved, and measures what they bring. Each employee publishes themselves, in one click, from the extension: Escouade never publishes or sends anything on their behalf. Social is included in every size. Advoq becomes Escouade Social. ## A space, its profiles A Social space belongs to a brand: its team, its profiles, its approval workflows, its data. Each employee has their LinkedIn profile there, under their own name; the company keeps a consistent line. The space's roles are **administrator** and **analyst**; an employee connects through the extension. ## Everyone in their own voice A post is written from the past texts of the person who signs it: their tone, their length, their topics. You re-read it, adjust it, submit it to the workflow. Your Claude or your ChatGPT can write it for you, through [Social's MCP server](https://escouade.io/en/docs/social/mcp.md). A prepared item can be a **post**, a **private message** or a **comment** under another author's post (1,250 characters at most). ## The approval workflow Each post follows a workflow: steps, their approvers, any one of whom is enough or all of them, and deadlines. When a deadline passes: a reminder, a tacit approval or a hand-over to another approver. The employee can be one of the steps. The workflow is frozen when the post is submitted: what is in progress does not change. Private messages and comments are prepared and approved the same way; a workflow can target comments only. ## Published by the employee An approved post arrives in the employee's [Chrome extension](https://escouade.io/en/docs/social/extension.md), which prepares it in LinkedIn, text in place. They add their images, re-read and publish it themselves. Once it appears, the post is matched with the one the extension collects, and its results come back into Social. ## The calendar The team calendar shows what is planned, what awaits approval, what is in the extensions and what has appeared, by week or by month, profile by profile. A sync is requested in one click, for one person or for the whole team; you see whether the request has been seen, and each person's last collection. ## What each voice brings Posts, observed impressions and engagement, per employee, over the same period and with the same indicators, filtered by period, profile or team. Everything exports as CSV, and the calculation method is written under each view: a missing value stays unknown, never counted as zero. ## The profiles you follow Follow the profiles and pages of your customers and prospects: their posts join their records, and you know what to talk about before calling. Following a profile costs nothing. ## Brand groups A company that speaks under several brands gives each one a space, then brings them together in a **group**. The group owns nothing: it shows the overview of the brands (30 days, observed totals), a shared calendar, opens each brand without signing in again, creates a brand, attaches an existing space or detaches it. An employee who speaks for several brands connects their extension to the group: they receive the approved posts of each brand that follows their profile, each one marked with its brand ("For …"), and their collection goes to each of them. A group's MCP server exposes a space's tools with a `marque` (brand) parameter: see [Social's MCP server](https://escouade.io/en/docs/social/mcp.md). ## By size Profiles that publish: 1 on Free, 5 on Essential, 25 on Pro, 100 on Max. Followed profiles are not counted. See [Sizes](https://escouade.io/en/docs/tailles.md#social). ## LinkedIn Escouade Social is neither affiliated with nor endorsed by LinkedIn. Each company remains responsible for its employees' compliance with LinkedIn's terms of use. --- Source: https://escouade.io/en/docs/social/extension.md # Social's extension > Escouade's Chrome extension connects each employee to Escouade Social: it receives approved posts, prepares them in LinkedIn, and reports what has appeared. It publishes with you, never in your place. ## Connecting, without a password An administrator sends each employee a link, from their profile card ("Invite the employee"). The link is **single-use and valid for seven days**. Opened with the extension installed, it connects it to the profile: no account to create, no password, no LinkedIn credentials. Only the link's fingerprint is kept; the code sits in the part of the address the browser never sends to the server. A person already signed in to Escouade Social, with a profile attached to their access, sees the extension connect on its own. A link has expired? The administrator sends a new one. ## Publishing: the employee clicks An approved post arrives in the extension, with a notification. "Prepare in LinkedIn" opens the editor, text in place; the employee adds their images, re-reads and publishes themselves. - An approved **private message** opens in the verified recipient's conversation, and is sent the same way, by hand. - An approved **comment**: "Prepare the comment" opens the target post and puts the text in its comment box, without ever submitting it; the employee publishes, then "I commented". Once it appears, the post is matched with the one the extension collects, and its results come back into Social. ## What it reads - The LinkedIn pages the person displays themselves and that their space follows: profiles and company pages. - They are recorded on display, at most once every five minutes per page; a switch in the extension, "Automatic collection", suspends this collection. - An employee only collects their own profile; an administrator, any profile or page the space follows. - On the "People" tab of a followed company page, the extension offers an administrator the members shown; nothing is added without their click. ## What it never does - Publish or send in the employee's place. - Read a LinkedIn cookie. - Browse or scroll the person's tabs. - Read a page the space does not follow. ## Syncing, in its own tab When a sync is requested (one page, or "Sync everything"), the extension opens the pages to collect in a **pinned work tab**, set apart, where it can scroll the page so that LinkedIn displays it. The panel follows progress page by page. The employee's tabs are never touched. ## LinkedIn Escouade Social is neither affiliated with nor endorsed by LinkedIn. Each company remains responsible for its employees' compliance with LinkedIn's terms of use. See [the terms and conditions](https://escouade.io/en/terms). --- Source: https://escouade.io/en/docs/social/mcp.md # Social's MCP server > Your assistant prepares the team's posts, submits them to the workflow, reads the results and the calendar, through Social's MCP server. It acts on behalf of the person who connected it, with their current rights. It never publishes or sends anything: the employee always clicks in LinkedIn themselves. ## The addresses | For | Address | |---|---| | A space (one brand) | `https://social.escouade.io/w//mcp` | | A brand group | `https://social.escouade.io/g//mcp` | `` and `` are the identifier of the space or the group, the one in their address in Social. The "Connections & MCP" page of the space or the group gives the exact address. The old address, `https://app.advoq.fr/…/mcp`, still answers: a connector already connected has nothing to do. ## Connecting **In Claude**: Settings › Connectors › "Add custom connector", paste the address, then "Connect": sign in with your Escouade account and allow. The connection appears in "Connections & MCP" under the name "Claude (OAuth)", from where it can be revoked. **In ChatGPT**: in developer mode, a custom connector takes the same address, with OAuth authentication. **An MCP client that accepts a token**: create a token in "Connections & MCP", read-only or read and write, and pass it as `Authorization: Bearer`. ```json { "mcpServers": { "escouade-social": { "url": "https://social.escouade.io/w//mcp", "headers": { "Authorization": "Bearer " } } } } ``` A collection token, the extension's, cannot query the MCP server. ## The tools ### Read | Tool | What it returns | |---|---| | `linkedin_publications_rechercher` | Collected posts, by profile, period or text. | | `linkedin_publications_statistiques` | Post indicators, by profile or by team. | | `linkedin_publication_historique` | A post's successive observations. | | `linkedin_profils_lister` | Followed profiles. | | `linkedin_collections_lister` | Collections. | | `advoq_agenda` | The team calendar. | | `advoq_preparations_lister` | Prepared items and their step. | | `advoq_synchros_lister` | Requested syncs and their status. | | `advoq_utilisateurs_lister` | The space's users. | | `advoq_circuits_lister` | Approval workflows. | | `advoq_plan_resultats` | The editorial plan's results: planned, approved, published, found by the collection. | | `advoq_abonnement_lire` | The subscription: status, seats, renewal date. | Social's own tools keep their original names, with the `advoq_` prefix. ### Write (read and write token, or OAuth connection) | Tool | What it does | |---|---| | `advoq_preparation_creer` | Prepares a post, a private message or a comment. | | `advoq_preparations_creer_lot` | Prepares a whole plan (100 items at most), all or nothing. | | `advoq_preparation_modifier` | Changes a prepared item. | | `advoq_preparation_decider` | Submits an item, or decides it at its step in the workflow. | | `advoq_profil_ajouter`, `advoq_profil_archiver` | Adds or archives a followed profile. | | `advoq_synchro_demander` | Requests a sync, for one person or for the team. | | `advoq_collection_creer`, `advoq_collection_publication` | Files posts into collections. | | `advoq_circuit_enregistrer`, `advoq_circuit_archiver` | Sets up approval workflows. | The decision history reads "Name (assistant)". What commits money (payment, seats, cancellation) stays an action in Social: the assistant reads it, it does not decide it. ## A group's MCP server A group's MCP server exposes the same tools with a `marque` (brand) parameter, plus `advoq_marques_lister`. When reading without a brand, it answers brand by brand; when writing, the brand is required. ## Views In an assistant that displays them, Social's tools render their view in the conversation: a table, the calendar, buttons that decide in the right brand. A missing value is written "unknown" there. --- Source: https://escouade.io/en/docs/tools.md # Escouade Tools > Escouade Tools, at , brings together thirteen office tools that open in the browser, with nothing to install. They are included in every size, Free included, and what they produce is saved in Escouade's Library. ## The thirteen tools | Tool | What it does | What it opens, among others | Maturity | |---|---|---|---| | **PDF** | Read, annotate, combine, split and secure your PDFs. | PDF, PNG, JPEG | Alpha | | **Photo** | Retouch, crop and lighten your images, layers included. | PSD, PNG, JPEG, WebP, SVG, TIFF, HEIC | Alpha | | **Vector** | Logos, diagrams and illustrations, in vector. | SVG, PDF, AI, EPS, DXF, images | Alpha | | **Layout** | Posters, sheets and brochures, laid out for print. | IDML, PDF, images, DOCX | Pre-alpha | | **Text** | Write, review and format your documents, Word-compatible. | DOCX, DOC, ODT, RTF, Markdown | Alpha | | **Spreadsheet** | Calculate, sort and analyse your sheets, Excel-compatible. | XLSX, XLS, ODS, CSV | Alpha | | **Slides** | Design and present your slide decks, PowerPoint-compatible. | PPTX, images | Alpha | | **CAD** | Draw and dimension your plans, DWG and DXF compatible. | DXF, DWG, SVG | Pre-alpha | | **Mockups** | Design the screens and flows of your apps and sites. | FIG, SVG, images | Alpha | | **Develop** | Develop and correct your photos, RAW included, without touching the original. | RAW (DNG, CR2, CR3, NEF, ARW…), JPEG, PNG, TIFF | Alpha | | **Video** | Edit your videos: cuts, titles, sound and grading. | MP4, MOV, WebM, MKV, audio, SRT subtitles | Alpha | | **Effects** | Animate titles and graphics, composite your visual effects. | Videos, images, SVG, PSD, PDF, AI | Alpha | | **Audio** | Edit and mix your sound, voices and podcasts. | WAV, AIFF, FLAC, MP3, MIDI, MusicXML | Pre-alpha | The maturity is what each original project says of itself. The tools come from free software (MIT or Apache-2.0 licences); their projects, versions and licences are credited in Tools. ## In the browser All the computing happens in your browser: the server only serves the tools' files. The tools run in an isolated frame, on a different address from your session's: their code never sees your sign-in. Tools uses nothing from your allowance and keeps nothing. You enter through the Escouade account, as everywhere in the family. The language follows your account's, otherwise your browser's. Most tools pick it up on their own; a few are set in their own menu, and Audio only exists in English. ## Saving to the Library What a tool saves goes by default to your organisation's [Library](https://escouade.io/en/docs/escouade/bibliotheque.md), in the "Tools" folder, under your rights; each tool reopens its files from there. The tools' own formats are kept as they are. The file only passes through the Tools server, in memory, without being written or logged. With no Library connected, or if it refuses the file, it downloads to your computer. ## Tools' MCP server Address: **`https://tools.escouade.io/mcp`**. Your assistant reads the tools and the Library there, and drops files there, in your name and under your rights. The tools run in your browser: the connector does not run them, it gives the link that opens one. | Tool | What it does | |---|---| | `tools_catalogue` | The list of tools and what they do. | | `tools_ouvrir` | The link that opens a tool, empty or with a document from the Library. | | `tools_documents` | The Library documents the tools can open. | | `tools_dossiers` | The Library folders. | | `tools_enregistrer` | Drops a file into the Library, through the same door as saving from a tool. | It connects like the family's other servers (see [The family's MCP servers](https://escouade.io/en/docs/mcp.md)): an address, then signing in with your Escouade account. Dropping a file needs a separate permission (`tools:write`): the assistant asks for it on the first drop. The organisation is never a parameter: it is the one you chose when signing in. A message carries at most 4 MiB, enough to drop a 3 MB file. --- Source: https://escouade.io/en/docs/mcp.md # The family's MCP servers > Each application of the family has its MCP server, at its own address, and Escouade has three. Your assistant connects with the address alone; signing in goes through your Escouade account, and the assistant acts with your rights, in the organisation you choose. ## The addresses | Application | Server | Address | For | |---|---|---|---| | Escouade | Read | `https://app.escouade.io/mcp` | Searching, reading and summarising records, documents and emails. | | Escouade | Write | `https://app.escouade.io/mcp/ecriture` | Creating and changing records, sending an email, in your name. | | Escouade | Integrator | `https://app.escouade.io/mcp/integration` | Setting up the model, the objects and the workspace. From Pro. | | Meet | | `https://meet.escouade.io/mcp` | Reading your meetings, minutes, actions and transcriptions; preparing an action you confirm. | | Mail | For assistants | `https://mail.escouade.io/mcp` | Your mailboxes, threads, drafts and campaigns, from Claude or ChatGPT. | | Mail | For agents | `https://api.subagent.fr/mcp` | A mailbox of its own for an autonomous agent, with an `sak_…` key. | | Social | A space | `https://social.escouade.io/w//mcp` | Preparing, getting approval, reading a brand's results. | | Social | A group | `https://social.escouade.io/g//mcp` | The same tools, brand by brand. | | Tools | | `https://tools.escouade.io/mcp` | Opening a tool, reading the Library, dropping a file into it. | The account's Connectors page, on , gives the same addresses, and says which ones your size opens. ## Connecting a server **In Claude** (claude.ai, and the desktop app, which picks up the account's connectors): 1. Open [Claude's connectors](https://claude.ai/settings/connectors), then "Add custom connector". 2. Give it a name and paste the address. 3. "Connect": sign in with your Escouade account, choose the organisation, allow. **In ChatGPT**: in the settings, the connectors, with developer mode switched on; create a connector with the address and OAuth authentication, then sign in with your Escouade account. **In Claude Code**: ```sh claude mcp add --transport http escouade https://app.escouade.io/mcp claude mcp add --transport http escouade-meet https://meet.escouade.io/mcp claude mcp add --transport http escouade-tools https://tools.escouade.io/mcp ``` then `/mcp` in a session to sign in to each. A connector only sees what your rights open, and what the organisation's size includes. ## What each server can do - **Escouade**: `escouade_trouver`, `escouade_consulter`, `escouade_relations`… for reading; `escouade_ecrire`, `escouade_envoyer`… for writing; `escouade_parametrer`, `escouade_superviser`… for the integrator. See [Escouade's MCP servers](https://escouade.io/en/docs/escouade/mcp.md). - **Meet**: twenty-one tools, including `search_meetings`, `get_report`, `ask_meetings`, and five that prepare an action to confirm. See [Meet for developers](https://escouade.io/en/docs/meet/developpeurs.md#le-serveur-mcp). - **Mail**: Mail's operations (`send_email`, `list_threads`, `approve_message`…), the same through MCP and through the HTTP API. See [the Mail tool reference](https://escouade.io/en/mail/docs/reference/index.md) (in French). - **Social**: prepare, submit, decide, read the calendar and the results. See [Social's MCP server](https://escouade.io/en/docs/social/mcp.md). - **Tools**: `tools_catalogue`, `tools_ouvrir`, `tools_documents`, `tools_dossiers`, `tools_enregistrer`. See [Escouade Tools](https://escouade.io/en/docs/tools.md#le-mcp-de-tools). ## What holds for all of them - **One sign-in**: the Escouade account's. The assistant never sees your Google or Microsoft password, and there is no key to keep for online assistants. - **Your rights, and nothing more**: each server applies the rights of the signed-in person, in their organisation. - **Writes are signed**: what an assistant writes carries your name and leaves a trace. - **Actions with no way back wait for a human**: an email sent through Escouade's write server (Claude asks for confirmation), an action prepared by Meet, a Social post, which only the employee publishes. Mail, for its part, follows its sending rules and the approval you require on a mailbox. - **Authorisation follows the MCP specification**: OAuth 2.1, PKCE, and discovery of the authorisation server from the address alone. --- Source: https://escouade.io/en/docs/connecteurs.md # Connectors > Connectors plug the tools you already have into Escouade: your mailboxes, your Drives, your software. The other way round, your Claude or your ChatGPT connects to Escouade through MCP. Meet, Mail, Social and Tools have nothing to connect: they open on your organisation through the Escouade account. ## Mailboxes A mailbox is connected in Settings › Accounts: Gmail, Outlook, or any IMAP mailbox. Its emails and their attachments enter Escouade's memory, linked to your records, once its ingestion is switched on. See [Ingestion](https://escouade.io/en/docs/escouade/ingestion.md). | | Free | Essential | Pro | Max | |---|---|---|---|---| | Gmail or Outlook mailboxes connected | None | 1 | All | All | A mailbox can be **personal**, connected by a person for themselves, or **the workspace's**: a shared mailbox, connected for the workspace, which the departure of the person who connected it does not stop. An email is read by whoever reads its mailbox. See [Access and roles](https://escouade.io/en/docs/escouade/acces.md#les-boites). ## Google Drive A Drive connects in two ways: - **for me**: you read it in your own chat; it never synchronises to the workspace; - **for the workspace**: it synchronises the chosen folders to the deals' Library and the master context. Several workspace Drives can coexist. See [The Library](https://escouade.io/en/docs/escouade/bibliotheque.md#les-sources). ## Shared and personal The connectors window sorts them into two families: - **Shared**: connected once for the whole company, such as a workspace Drive, electronic signature or supplier invoice software. Who manages them (connecting, configuring, disconnecting, offering them in the chat) is set role by role on their card; by default, administrators. - **Personal**: which each person connects for themselves, such as their own mailbox or their own Drive. ## The family, with nothing to connect Meet, Mail, Social, Tools and Prescriptio open on your organisation through the Escouade account. In the settings, "My suite" says what your size gives you of each, with a button to open it. Their data reaches Escouade through the family relay: Meet minutes attach to the participants they know, a Mail campaign creates dated facts on the contacts' records. ## Your assistant, on Escouade The other way round, Claude, ChatGPT or any MCP client connects to Escouade and to each application of the family, with an address and your sign-in. See [The family's MCP servers](https://escouade.io/en/docs/mcp.md). ## Escouade hub On an [Escouade hub](https://escouade.io/en/docs/escouade/hub.md) instance, the same connectors connect to your server. Meet, Mail, Social and Tools are taken as an online subscription. --- Source: https://escouade.io/en/docs/github.md # Public repositories > What you use to connect Escouade on your side is open, on the [escouade-io](https://github.com/escouade-io) GitHub organisation, under the MIT licence. The servers, which enforce the rules and keep the data, stay closed. ## Escouade Mail Seven repositories, generated from the operation registry of Mail's server: a tool can neither invent an operation nor forget one. | Repository | What it holds | |---|---| | [`escouade-mail-mcp`](https://github.com/escouade-io/escouade-mail-mcp) | How to connect the MCP server, client by client, with configuration files ready to copy; the server contract: every tool, its schemas, its access. | | [`escouade-mail-python`](https://github.com/escouade-io/escouade-mail-python) | The Python SDK: one method per server operation, same names and arguments as the MCP tools. No dependencies. | | [`escouade-mail-node`](https://github.com/escouade-io/escouade-mail-node) | The TypeScript SDK, for Node: the same operations, typed. No dependencies. | | [`escouade-mail-cli`](https://github.com/escouade-io/escouade-mail-cli) | The command line: one command per operation, from a terminal or from an agent that runs commands; results and refusals in JSON. | | [`escouade-mail-skills`](https://github.com/escouade-io/escouade-mail-skills) | Seven recipes in the Agent Skills format: get started, write, follow replies, approve drafts, send from your domain, prospect, call the API. | | [`escouade-mail-plugins`](https://github.com/escouade-io/escouade-mail-plugins) | The Claude Code plugin: the MCP server, the key and the recipes, installed at once. | | [`escouade-mail-examples`](https://github.com/escouade-io/escouade-mail-examples) | Five examples to run, in Python and for Node: sign up, write, read replies, connect your domain, approve. | The tools only work with an Escouade Mail key. ## Installing ```sh pip install escouade-mail # the Python SDK npm install escouade-mail # the TypeScript SDK npm install -g escouade-mail-cli # the command line ``` The packages under the name `escouade-mail` are on their way; until then, and afterwards too, the old names work: `pip install subagent-mail`, `npm install subagent-mail` and `npm install -g subagent-mail-cli`. The Claude Code plugin installs from its repository: ```text /plugin marketplace add escouade-io/escouade-mail-plugins /plugin install escouade-mail@escouade-mail ``` ## Open, closed - **Open**: what you paste on your side (MCP configuration, SDKs, command line, recipes, plugin, examples). - **Closed**: what decides whether an email leaves (gradual ramp-up, daily quota, working hours, human approval, unsubscribe, circuit breaker), and the servers of Escouade, Meet, Social and Tools. The two references of Mail's server can be read without a key: `https://api.subagent.fr/llms.txt` and `https://api.subagent.fr/openapi.json`. ## The other applications Escouade, Meet, Social and Tools have no public repository yet: you connect to them through their MCP servers ([The family's MCP servers](https://escouade.io/en/docs/mcp.md)) and, for Meet, through its [REST API](https://escouade.io/en/docs/meet/developpeurs.md). --- Source: https://escouade.io/en/docs/questions.md # Frequently asked questions > Short answers to the questions that come up again and again. Each one points to the page that says more. ## Price **How much does one more user cost?** Nothing. No size is paid per user: Free and Essential cover three people, Pro and Max have no limit. See [Sizes](https://escouade.io/en/docs/tailles.md). **What happens beyond the allowance?** If you have switched credits on, they take over, within the monthly cap you have set; otherwise, the action is refused, with the reason. Credits are bought in packs of €10, €25 or €50 excl. VAT and are valid for twelve months. See [Usage and invoice](https://escouade.io/en/docs/utilisation-et-facture.md#credits). **How do I cancel?** By going back to Free: the days already used remain due, nothing more, and no data is deleted. **Do I need a Claude or ChatGPT subscription?** No. Escouade's chat is enough. If you already use Claude or ChatGPT, connect it through MCP: on Free, that is even the way to drive Escouade. ## Data **Where is our data?** In France, with our hosting provider. With [Escouade hub](https://escouade.io/en/docs/escouade/hub.md), it stays on your server. Subprocessors are listed on [the subprocessors page](https://escouade.io/en/subprocessors). **Who sees what?** Each role sees its own scope, and the chat and assistants respect the same rights. See [Access and roles](https://escouade.io/en/docs/escouade/acces.md). **Can we get all our data back?** Yes: an administrator downloads a complete archive of the workspace. Meet meetings export one by one. ## Assistants **Can my assistant change the CRM?** Yes, through the write MCP server, with the signed-in person's rights. Every write carries their signature and leaves a line in the log. See [Escouade's MCP servers](https://escouade.io/en/docs/escouade/mcp.md). **Can an agent act without approval?** Agents' proposals await your decision in To review. Some filing operations apply without review (filing an attachment, linking an email to its deal), as do the "Always apply" rules you have created. See [Ingestion](https://escouade.io/en/docs/escouade/ingestion.md). **Which AI models answer?** The models are named in the chat and in the settings, with their origin and where they run. On your own server, you choose yours, with your own keys. ## Emails **Do our Gmail or Outlook mailboxes stay?** Yes. They connect to Escouade, which reads them and links them to your records. Escouade Mail adds mailboxes; it does not make you leave yours. **Can an email received manipulate a Mail agent?** No. What a third party writes is marked as untrusted data: the agent reads it, it does not obey it. **Is Mail for bulk sending?** No. Mail writes to one person at a time, from a mailbox, at a human pace: no bulk sending, no transactional emails. ## Meetings **Do participants have to be told?** Yes. The organiser tells participants that the meeting is recorded, and obtains their consent. See [Escouade Meet](https://escouade.io/en/docs/meet.md#l-accord-des-participants). **Does the bot join my meetings on its own?** Yes, from the calendars you follow, whether you are there or not. In a waiting room, nothing is recorded until the organiser admits it, and you can remove it at any time. ## LinkedIn **Do I have to give my LinkedIn credentials?** No. The extension connects through a single-use link, valid for seven days: no password, no LinkedIn credentials, no LinkedIn cookie passed on. **Can your assistant publish on LinkedIn?** No. It can prepare posts and submit them to the workflow; it can neither publish nor send. The employee always clicks. Another question: . All the website's questions: [escouade.io/en/faq](https://escouade.io/en/faq). --- Source: https://escouade.io/en/docs/etat.md # Service status > The page [escouade.io/en/status](https://escouade.io/en/status) says, the moment you open it, whether each service of the family is answering. ## What it checks | Service | What is checked | |---|---| | The website | escouade.io itself: it answers, since it serves the page. | | The account | Sign-in and the account pages, at `compte.escouade.io`. | | The application | The Escouade workspace. | | Prescriptio | `prescriptio.fr`. | The check is done server-side, the services in parallel, three seconds at most each, from their public address: it sees what a visitor sees. Its reading is kept for thirty seconds: refreshing the page in a loop probes nothing more. ## The three states | State | Meaning | |---|---| | **Up** | The service answered, in under a second and a half. | | **Degraded** | The service answered, but slowly (more than a second and a half), or a server error did not repeat on the second attempt. | | **Down** | The service did not answer in time, or its error repeated on the second attempt. | The page states each status in text and in shape, not just in colour. It keeps no history. ## Escouade Mail Mail has its own status page, which also says what is in service, feature by feature: [Escouade Mail's status](https://escouade.io/en/mail/docs/etat.md) (in French). ## Reporting an incident A service is not answering, or misbehaving? Write to , with the time and the address concerned.