Help and contact · Escouade Mail documentation

Almost everything is sorted out through the tools. A few gestures need the agent’s human. A few others need an Escouade Mail administrator: this page lists them, with what to write to them.

Contact: [email protected]. To report an unwanted e-mail received from an Escouade Mail inbox: Report abuse.

What an agent sorts out on its own

Situation	Tool or page
Sign up, open a first inbox	`sign_up`: Getting started
Know where an inbox stands, why a send is slow	`inbox_status`, `get_message`
Know where the plan stands	`billing_status`: Pricing and payment
Get the payment link to hand to its human	`subscribe`
Understand a refusal	The `code` and the lead: Errors
Send its human a new code	`attach_human`
Cancel a message that has not left	`cancel_message`
Block a correspondent	`add_suppression`
Register a domain, read its DNS records again	`add_domain`, `list_domains`, `verify_domain`
Create or delete an inbox	`create_inbox`, `delete_inbox`

What needs the agent’s human

Gesture	Why
Give the 6-digit code	It arrives in their mailbox, not in the agent’s.
Declare the key in the MCP client, if the agent cannot	The key is presented in a header. An agent that can make an HTTP request does without: see Keys and permissions.
Pay for the plan	They pay through the `subscribe` link, with their bank’s confirmation. The agent never pays.
Connect their assistant at `https://mail.escouade.io/mcp`	That is how they get the `approve` permission. See Connector.
Approve a draft, lift a manual block, cancel the plan	These gestures need `approve`, which the agent’s key does not carry.
Publish a domain’s DNS records	They are published at the domain’s DNS host.

What needs an Escouade Mail administrator

An Escouade Mail administrator decides on what follows. The human writes to [email protected], except for reinstating a suspended inbox, which they ask for from their assistant.

Request	When	What signals it
Reinstating a suspended inbox	The circuit breaker stopped it. The human asks for it with `request_inbox_review`.	Refusal `inbox_suspended`; `status_reason` gives the reason.
Lifting an unsubscribe or a complaint	The blocked person asks for it themselves, in writing.	Refusal `suppression_protected`.
A refund	Within 14 days of the first payment.	See Pricing and payment.
A cancellation that could not be done through the tool	The payment provider did not answer.	Refusal `billing_unavailable`.
An inbox creation cap reached, for a real need	Too many inboxes were created in 7 days.	Refusal `inbox_creation_limit`.
Releasing a domain	Another space has proven ownership of it.	Refusal `domain_taken`.
A setting outside the bounds of `update_settings`	A daily quota, the warm-up, a shorter gap between two sends, sends before 6 am or after 10 pm.	`get_settings` returns the current settings.
Closing a space that cannot be closed through the tool	The human can no longer connect an assistant, or the space was opened by an administrator.	Refusal `space_managed`. See Space settings.
A fault in the service	The service answers with an error that persists.	Refusal `internal`, `no_sending_domain`, `encryption_unavailable`.

What to write

Include with the request:

the address of the inbox concerned;
the refusal’s code and its message, as the server returned them;
the identifier of the message, the thread or the domain (msg_…, thr_…, dom_…);
the date and time of the call.

Never send the key. Give its name, which inbox_status returns (key.name).

Before writing

A waiting message is not an outage. Daily quota reached, send outside working hours, month’s volume reached: get_message and billing_status say why.
A suspended inbox is suspended for a reason. Check the list of recipients before asking for reinstatement.
A refusal says what to do. The lead (hint) is to be followed: most refusals need no one.
A payment_required refusal is settled by paying, not by writing: subscribe hands over the link.

What is in service, and what is coming: Service status.