# Set up Support

This page makes Support able to receive conversations. Widget copy and help-center articles are separate: [Write the widget copy](https://www.saasco.com/docs/support/copy.md) and [Populate the knowledge base](https://www.saasco.com/docs/knowledge/agents.md).

## 1. Use the Saasco MCP

If Saasco is not connected, read https://www.saasco.com/docs/mcp.mdx and follow the steps for this client. Sign in, allowing "Create and change data in your projects". Search with `saasco_search_tools`, then run the tool with `saasco_execute_tool`.

Pass project id `YOUR-PROJECT-ID` on every project tool. On a connection scoped with `?projectId=`, omit `projectId`. If a write tool is missing, re-authorize.

## 2. Install the SDK

The widget loads from the Saasco SDK. If this repo does not call `saasco.init()`, follow [Setup for coding agents](https://www.saasco.com/docs/sdk/agents.md) first.

## 3. Trust the site, then turn the widget on

Ask which origins the widget should appear on. Call `support_updateSupportWidgetSettings` with those bare hostnames (`example.com`, no scheme or path). Subdomains of a listed host are included.

Ask before turning the widget on. That is `support_updateSupportWidgetEnabled` with `enabled` true. Leave both AI agents at their default unless they say otherwise.

## 4. Support email, if they want it

Ask whether customers should also email them. If yes, ask for the hostname and the local part (`support` makes `support@` that host).

Call `domains_listDomains`. Create the domain with `domains_createDomain` if it is missing, then `domains_activateEmailReceiving` with that `domainId`. That turns receiving on.

Call `domains_getReceivingConfig` with the same `domainId`. Add its `records` — the MX rows — and follow [Add DNS records](https://www.saasco.com/docs/domains/dns.md). Wait until they say the records are saved, then call `domains_verifyEmailReceiving` once. If it is still pending, say so and stop.

When receiving is active, call `support_updateSupportMailbox` with `supportDomain` set to that hostname and `supportLocalPart` set to that local part. Do not change who is notified.

Do not rotate the messenger secret, turn on identity verification, connect outside tools, or paste a secret.