Connect business data to your AI agent

Choose what the assistant needs

Website and help-center content becomes knowledge the assistant may use in customer answers. Customer profiles and private orders use separate, restricted lookup paths. Do not import private customer records as public knowledge.

The product does not expose the general custom-tool JSON registration and tool-signing-secret workflow previously described here. Use a supported connector or the documented MCP interface instead.

Connect and approve a source

Open Settings → Connections and choose your source. Connect the intended site or store, then use the knowledge/data connection workflow to select and approve public content. Connecting a store alone does not approve every record for AI answers.

Workspace administrators manage data connections. The dashboard uses GET /api/v1/data-connectors to list supported providers and installations. POST /api/v1/data-connectors validates the provider, site ownership and permitted configuration fields. Use the dashboard to collect the correct provider-specific fields rather than copying one generic payload.

Keep private lookup separate

Enable supported order lookup only for the selected installation and test its identity checks. A phone number or an order number supplied by a visitor is not proof that they own an order. Do not let prompts override the connector’s authorization checks.

Use read-only credentials where the connector requires them. Unsupported actions, such as an arbitrary refund or database update, do not become available because an agent instruction mentions them.

Configure the assistant’s job

For phone assistants, use the Phone AI setup to explain the permitted tasks, review the resulting plan and choose the voice. Keep handoff behavior explicit when the caller asks for a person or a required detail is missing.

Task agents are a separate configuration surface. The admin-only /api/v1/ai/agents endpoints report billingMode: preview. Do not treat their displayed quote as a completed purchase or assume they enable unrestricted business actions.

Test before enabling customer traffic

Ask questions whose answers appear in the approved source, then ask a question the source cannot answer. Confirm the assistant acknowledges missing information or hands off instead of inventing an answer.

For customer lookups, test the intended customer, a different customer and an invalid reference. Confirm private data stays within the correct workspace and verified customer scope. Reconnect the source and confirm the same restrictions still apply.

Use an external AI assistant through MCP

For an external AI client, follow the MCP authentication and tool documentation. Grant only the required product permissions and operations. This is a separate interface from installing arbitrary tools inside Message AI.