Confirm that you can manage the website.
You need access to the site’s shared template or custom-code settings, plus either its DNS settings or a way to publish a verification file. If an agency manages the site, agree who will make each change.
Start with the public demo if you want to inspect a bounded sample first. A successful demo does not replace ownership verification or your production review.
Verify ownership and review the crawl.
Add the website in your Sairo workspace. Follow the provided DNS TXT or verification-file instructions exactly, then run the verification check.
After indexing finishes, review the source list. Confirm essential facts, exclude stale pages, and write saved answers for questions that need approved wording. Make sure two pages do not publish contradictory policies.
Choose the assistant’s role and install it.
Set the business name, greeting, tone, and goal. If the site should offer live help, enable live chat and assign at least one eligible specialist before testing.
Copy the generated installation snippet into the intended website layout. Use the site key supplied for this website; keep server credentials out of website code. Check that a content security policy or consent tool is not blocking the widget or its requests.
Test complete conversations before launch.
Ask a question answered on a source page and inspect the response. Ask for information the sources do not contain and check that the assistant avoids inventing a detail.
Test lead collection with contact information you control. If live chat is enabled, request a person, send a message while waiting, claim the chat, reply, end it, and repeat with no specialist online. Test the widget with a keyboard, zoom, and the assistive technology relevant to your audience.
- A known answer matches the source
- Missing information becomes a gap
- Live chat preserves the AI transcript
- Online and offline wording is accurate
- Keyboard focus stays usable
Make review part of the handoff.
Assign someone to review the inbox and knowledge gaps. Update the original website when facts change, and review the refreshed content before relying on a new answer.
For agency clients, document who can change configuration and who can contribute content. Clear ownership makes the assistant easier to maintain after the initial installation.
Include Ask Sairo in the maintenance handoff. Demonstrate how to find an incorrect answer, provide the approved wording, review the proposed change and retest it on the correct website.
Use the installation snippet for your site.
Open the site’s installation screen and copy its generated script. The example below shows the format: replace YOUR_PUBLIC_SITE_KEY with that site’s public key. Paste the script once in the shared layout, usually before the closing body tag, or use the equivalent custom-code field in your website builder.
Publish the change, then open the public website in a private browser window. An editor preview is not a reliable check: some platforms suppress custom scripts there. Confirm the launcher appears on all intended pages and does not overlap important controls.
Get your assistant live. Verify, install, and test your first website assistant.
Before you start: Start with a workspace and a website already added. The workspace, visitors and figures shown are fictional examples.
Read the transcript
- Your website. Ready to help.
Already created your workspace and added your website? Let's get your Sairo assistant live.
- Open Get started
Open Get started in the sidebar. Your setup checklist keeps verification, indexing, installation, and testing in one place.
- Verify ownership
Add the supplied verification file to your website, or use the DNS record. Then select Check verification. Ownership must be verified before indexing.
- Index your pages
Select Refresh website content. Sairo reads the verified website and prepares its knowledge. The next step appears when indexing finishes.
- Copy. Add. Publish.
Copy your unique snippet. Add it before the closing body tag, or in your website builder's global custom-code area. Publish, then confirm that you've added it.
- Ask a real question
Open your website and select Ask a question. Try something visitors actually ask, such as: Do you offer free inspections? Then send it.
- Check the answer
Read the answer and its source. In this example, the reply confirms free residential inspections in Franklin County. Test your own important questions too.
- Your first answer, ready for visitors.
Your assistant is ready for a first conversation. Next, keep its answers accurate with confirmed knowledge.
<script src="https://sairo.app/widget.js" data-site="YOUR_PUBLIC_SITE_KEY" async></script>Write a small acceptance test before launch.
Choose real questions with known answers so your review has an objective reference. Keep a record of the source, the expected behaviour, and what actually happened. Repeat the same checks after source, theme, model, or live chat staffing changes.
| Test | Expected result | What to inspect |
|---|---|---|
| Published service question | A concise answer supported by the relevant page | Answer and cited source agree, including conditions. |
| A price not published anywhere | An acknowledgement of the missing information | No invented amount; the team can review the gap. |
| A request to speak to a person | The site’s live queue when enabled, or its configured follow-up path | Online and offline wording matches the site’s actual staffing. |
| Specialist reply | A named reply in the existing widget transcript | Waiting, connected, and ended states are clear. |
| Keyboard-only visit | Usable launcher, message field, handoff, and close controls | Visible focus and a sensible place to resume on the page. |