Skip to content

At home on your website. Connected to your work.

Install an assistant for your visitors, then connect your workspace to the AI tools your team uses. Choose the setup that fits the task.

Connect your workspace to Claude and other AI applications.

Use Sairo’s remote MCP connection to find visitor conversations, review knowledge and work on follow-ups from a compatible AI application. Sign in to Sairo and choose a workspace, website scope and read or write access.

This connects your team’s workspace operations. The website widget is installed separately using the script and platform guides below.

Add the snippet from your workspace.

Open the website’s installation page in Sairo and copy its generated snippet. Add it to the shared page layout or an approved custom-code area so it loads on the intended pages.

The script is hosted at sairo.app and uses the public site key to load the correct assistant. The widget loads asynchronously and keeps its component styles inside Shadow DOM.

Check what your CMS allows.

A custom website, WordPress installation, or site builder can host the widget when its plan and configuration permit third-party JavaScript. Use the CMS’s current instructions for adding site-wide scripts.

Sairo does not require a native CMS plugin, and this page does not claim a dedicated WordPress, Shopify, Webflow, or Wix integration. Content security policies and consent tools may need an explicit allowance for the widget and its requests.

Let the assistant reach a system you run.

A website can register up to ten actions: an HTTPS endpoint you own, with a short description of when to use it. The assistant may run at most two in a reply, and answers only from what they return, so an order lookup or a stock check reaches the visitor as evidence rather than as a guess.

Sairo accepts only addresses that resolve to public hosts, and re-checks that when the call is made rather than only when it is saved. Every call is recorded with the address, what was sent and what came back, for your team to read. You build and maintain the endpoint; Sairo does not host it.

A REST API for the work you automate.

Websites, conversations, leads and saved answers are readable and writable with a bearer key, so an agency can report across clients or push a lead into its own CRM without a person copying it. Read and write are separate scopes.

A key is stored as a hash with a short visible prefix: you can recognise it in a list, and nobody can read it back. Revoking one takes effect immediately.

WhatsApp, when the service supports it.

Sairo can answer messages sent to a business WhatsApp number with the same assistant, the same knowledge and the same refusal to guess, inside WhatsApp’s 24-hour reply window. The window is recorded and checked rather than discovered as a failed send.

This is built but not available in the current hosted service, because no Twilio account is connected to it. Contact Sairo before planning a rollout around it, so you are told the real date rather than a hopeful one.

Review the production installation.

Confirm that the widget appears only where intended, the correct business name and branding are shown, and replies are grounded in the right website.

Check keyboard operation, focus, page overlays, zoom, and mobile layouts. If live chat is enabled, test its online, offline, waiting, connected, and ended states on the published site.

Find your website platform.

See what your website can answer.

Try a sample, review the result, and decide what comes next.