# Sairo public reference
Sairo turns your website into an AI chatbot that answers from your pages and documents, with live chat when a visitor needs a person. It refuses to guess.
This is first-party public product information generated from the same content as the website. It contains no customer workspace records or private conversations. Prices and live allowances are available at https://sairo.app/pricing. Demonstrations and worked examples are illustrative. The accessibility report remains a draft pending manual validation.
## Sairo
https://sairo.app/
Sairo turns your website into an AI chatbot that answers from your pages and documents, with live chat when a visitor needs a person. It refuses to guess.
## Plans and pricing
https://sairo.app/pricing
Current prices, allowances, premium themes and commercial conditions from the active plan catalogue.
## Frequently asked questions
https://sairo.app/faq
Answers about sources, human handoff, corrections, connected applications, setup and plans.
## Performance
https://sairo.app/performance
Dated Lighthouse scores for sairo.app on phones and desktops, the measurements behind them, how the site stays fast, and what the widget costs a customer website.
## Contact Sairo
https://sairo.app/contact
Product questions, support, accessibility feedback, privacy and sales enquiries.
## Connect an AI application
https://sairo.app/connect
The remote MCP address and setup links for compatible applications.
## Frequently asked questions
### What is Sairo?
Sairo is an AI website chatbot and live chat platform for businesses and agencies. It answers from selected website knowledge, lets a human join the same conversation, and gives teams tools to review and improve their assistants.
### What is Ask Sairo?
Ask Sairo is your team’s conversational workspace assistant. It can find visitor questions, inspect knowledge and prepare supported updates to answers, business facts, leads, notes and assistant copy. It follows your existing workspace and website permissions.
### How do I correct a wrong chatbot answer?
Open the conversation and choose “Review with Ask Sairo”, or describe the question in Ask Sairo. Select the website, supply the confirmed correct wording, review the change and test the original question again. An explicit correction can be saved directly when automatic corrections are enabled. Keep the source page current too.
### Can I connect Sairo to Claude?
Yes. Add Sairo as a custom remote MCP connector, then sign in through Sairo’s OAuth flow. Choose a workspace, website access and whether to allow supported changes. Claude Code can use the HTTP MCP connection too. Your client must support the connection method and your account or organisation must allow it.
### What can a connected AI application change?
With write access and the appropriate team role, supported tools can update saved answers, business facts, internal notes, conversation review status, lead follow-ups, source controls and assistant greeting, tone or name. Billing, team administration, arbitrary database access and outbound customer messages are outside the tool set.
### Can I keep an AI connection read-only or disconnect it?
Yes. Leave “Also allow changes” off during connection to limit it to permitted reads. Manage and disconnect applications from Connected apps in your Sairo account. Disconnecting stops future access; it does not delete information already received by the external application.
### What does Sairo use to answer questions?
Sairo uses the website content indexed for the site, confirmed business details, and saved answers. Exact saved answers take priority. Generated replies use relevant retrieved passages, and questions the content does not answer should be recorded as knowledge gaps.
### Can I try it before installing anything?
Yes. The public demo reads a bounded sample of a public website and creates an assistant you can try. Keep this assistant creates a Free workspace and copies that knowledge in, then continues from verification. The demo respects robots.txt and cannot read login-only content.
### Can visitors dictate a question?
When dictation is configured, enabled for the website and supported by the browser, visitors can grant microphone permission and record a short question. The transcription appears in the composer for review before sending. Typing remains available. This is speech-to-text input, not a telephone or spoken-agent service.
### Does signing up create a workspace immediately?
Free, Starter, Pro, Agency, and Agency Growth create an account and workspace when you submit the form. Agency Scale remains a request: the Sairo team reviews it and follows up with an invitation.
### Does Sairo replace the people answering enquiries?
No. It can answer from available content, collect contact details, and hand an enabled site conversation to an assigned live chat specialist. The widget states whether a specialist is currently available, and your team remains responsible for the human response.
### How does Sairo live chat work?
An administrator enables live chat separately for a website and assigns eligible workspace specialists. A visitor can request a person, or an AI escalation can enter the queue. A specialist claims the conversation and replies inside the same widget with the earlier transcript intact.
### What happens when no live chat specialist is available?
The widget says that nobody is available and offers to leave a message for the team. It does not promise an immediate response. The request stays in that site’s queue until an assigned specialist who is Available can join.
### Are live chat messages instant?
Live chat uses a WebSocket connection when it is available, with HTTP updates about every 2.5 seconds as a fallback. Specialists and conversation updates remain in the same transcript, and the widget reconnects the same session after refresh within a browser session.
### Does the chatbot make my website WCAG compliant?
No widget can make that promise for a whole website. Sairo is designed around accessible interactions and targets relevant WCAG 2.2 AA requirements, but the installation and the rest of your website need their own assessment.
### Can an agency manage several client websites?
Yes. Agency workspaces separate clients into projects, with project-scoped permissions and optional content contribution for clients. Available sites and usage depend on the assigned plan and any staff-approved adjustments.
### Do I need a native plugin for my website builder?
No native plugin is required. You need permission to install the script snippet in the relevant pages or shared layout. Compatibility depends on the website builder’s custom-script support, content security policy, and consent setup.
### What happens when Sairo cannot answer?
The assistant should acknowledge the missing information and record the unanswered question. If live chat is enabled, the conversation can enter that site’s specialist queue; otherwise the visitor can use the configured follow-up route.
### How do plans and usage limits work?
Plans define the number of websites, pages per website, monthly page refreshes, and conversations. Free includes one website and keeps a small Powered by Sairo mark. Paid plans add capacity and can hide the attribution. Sairo staff can tailor allowances for a workspace or site where supported.
### Is email required to use the service?
The chat, knowledge, and workspace flows work without an email provider. Invitations can be shared as links. Email notifications and email password recovery require the delivery service to be configured.
### Can I change the model for a client?
Platform staff can set a default model, a workspace default, or a site override, along with a maximum reply-token allowance. The production default uses OpenRouter. Ask your administrator about the options appropriate for your workspace.
### Can I customize the chatbot’s theme?
Pro, Agency, Growth and Scale include six presets and controls for colors, typography, layout and labels. The editor checks contrast and asks you to review risky choices. Required accessible names stay protected.
---
# Useful AI answers. A live specialist when needed.
Canonical page: https://sairo.app/features
Updated: 2026-09-09
Turn the pages you maintain into an assistant your team can review, then let an assigned specialist join the same conversation when a visitor needs a person.
## What is included in Sairo?
Sairo combines website-grounded AI answers, live human handoff, an inbox, leads, knowledge review and analytics. Ask Sairo and OAuth MCP connections help your team maintain supported workspace records. Plan limits and theme options vary.
## Your website is the starting point.
Sairo reads permitted pages, extracts useful business details, and creates searchable knowledge for each website. Website ownership verification unlocks the full crawl; the public demo reads only a bounded sample.
Review included sources, exclude pages that should not inform replies, and add saved answers for questions your website does not address. Exact saved answers take priority over generated replies.
- Page sources and citations
- Confirmed business details
- Saved answers and source exclusions
- PDF, Word, text, Markdown and CSV uploads
- A help centre whose articles are also knowledge
Section: https://sairo.app/features#knowledge
## Keep the conversation connected to the work.
The assistant can collect contact details, record an unanswered question, and hand the same conversation to a live chat specialist when that site enables the feature. Your team can search the inbox, assign conversations, add internal notes, and track a lead through follow-up.
Live availability reflects whether an assigned specialist has set themselves Available. When nobody is available, the visitor is offered an honest team queue rather than an immediate-response promise.
When voice dictation is configured and enabled for a website, visitors can record a short question and have it converted to text in the composer. They can review the text before sending it. Dictation is an optional input method, with typing available throughout.
- Per-site live chat and specialist assignment
- Conversation ownership and lead follow-up
- Knowledge gaps from real questions
- Photo and PDF attachments
- Saved replies and grounded drafts for specialists
- Conversation rating with an optional comment
- [Learn about optional voice input](https://sairo.app/accessibility#dictation)
Section: https://sairo.app/features#conversations
## One site or a whole client portfolio.
Direct businesses get a focused workspace. Agencies can separate clients into projects, limit each person’s access, and apply branding at the appropriate level. Staff can assign plans and set model and usage allowances.
Analytics show conversations and outcomes over time. Use those patterns to decide which pages to improve and where your team should spend its attention.
- [Explore agency workspaces](https://sairo.app/solutions/agencies): Client projects, permissions, and branding.
- [See the widget interaction details](https://sairo.app/accessibility): Keyboard access, focus, and screen reader behavior.
Section: https://sairo.app/features#control
## Help for the team behind the assistant.
Ask Sairo brings visitor questions, website knowledge and follow-ups into a conversation for your team. Describe an incorrect answer, supply the right information, and review the proposed correction. Supported updates keep a change record and can be undone when the record has not changed again.
Prefer to work in Claude? Connect Sairo through MCP and OAuth, choose the workspace and website access, and use the same permitted read and change operations from a compatible application.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/features#workspace-assistant
## Explore each part of the workflow.
Understand what each feature does, how your team uses it, and where its limits are. Follow the work from visitor answers to the tools your team uses to maintain them.
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge): See how Sairo combines indexed website pages, confirmed facts, and saved answers into a controlled knowledge base for your website chatbot.
- [Website chatbot lead capture and follow-up](https://sairo.app/features/lead-generation): Capture visitor contact details with conversation context, then assign owners, track lead stages, and plan follow-up in Sairo.
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat): Enable live chat per website, assign specialists, move visitors from AI answers to a person, and keep one complete transcript in Sairo.
- [Shared AI and live chat inbox for website teams](https://sairo.app/features/conversation-inbox): Review AI and live chat transcripts in Sairo’s shared inbox, filter by site and outcome, assign teammates, and keep internal notes in context.
- [Website chatbot analytics and outcomes](https://sairo.app/features/chatbot-analytics): Track Sairo conversation volume, captured leads, recorded outcomes, and daily trends, with site-scoped reporting and clear metric definitions.
- [Agency chatbot branding and client identity](https://sairo.app/features/agency-branding): Understand Sairo’s agency, project, and site branding controls, including display names, accents, logos, support details, and Sairo attribution.
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps): Use Sairo’s unanswered-question workflow to find missing website information, add approved answers, and check whether the next visitor gets better help.
- [Ask Sairo: AI assistant for your chatbot workspace](https://sairo.app/features/ai-workspace-assistant): Find visitor questions, correct chatbot answers, update website knowledge and manage follow-ups in a conversation with Ask Sairo, with review and undo.
- [Custom chatbot themes with accessibility checks](https://sairo.app/features/chatbot-themes): Customize Sairo with six chatbot themes, colors, fonts, layouts and labels. Preview changes and check contrast before saving.
Section: https://sairo.app/features#feature-library
## Our next focus is releasing the apps.
The current website feature set remains available. New website features are paused while we complete testing, distribution and approval for the iOS, macOS, Windows and Android apps. Maintenance of the existing service continues.
- [Check desktop and mobile app availability](https://sairo.app/apps)
Section: https://sairo.app/features#app-releases
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
- [Plans and pricing](https://sairo.app/pricing)
---
# From your pages to a helpful conversation.
Canonical page: https://sairo.app/how-it-works
Updated: 2026-09-06
Start with a small public demo. Then verify, review, and install an assistant you can keep improving.
## How do I add Sairo to my website?
Try a public-page sample, create a workspace, verify website ownership, review the selected knowledge and install the JavaScript snippet. Test answers and the human handoff before launch, then maintain the source content.
## 1. Try a sample of your website.
Enter your public website address in the demo builder. Sairo checks that the address is safe to fetch, respects robots.txt, and reads a limited number of pages.
The demo helps you judge the answers before installation. Sites that block crawlers, require a login, or depend entirely on browser-rendered content may need changes before their pages can be read.
The preparation screen shows the site-reading progress, then opens a focused demo where you can ask the assistant questions about the sampled pages. No signup or installation is needed for that sample.
- [Try your website in the live demo](https://sairo.app/#try)
Section: https://sairo.app/how-it-works#try
## 2. Verify ownership and review the knowledge.
A workspace administrator adds the website and verifies ownership with a DNS TXT record or a small verification file. The initial crawl is limited by the workspace’s page allowance.
Check important source pages and business details. Add approved answers for common questions, and exclude old offers, irrelevant content, or pages that should not inform the assistant.
Section: https://sairo.app/how-it-works#verify
## 3. Add the widget and test a real journey.
Copy the installation snippet from your workspace into the website’s shared layout or approved custom-code area. The site key identifies the assistant; provider credentials remain on the server.
Try a known question, a question the website cannot answer, and a request for a person. Use a keyboard and a screen reader to check the widget in the context of your own page.
Video walkthrough 01: Get your assistant live (1:13, English narration with captions). Verify, install, and test your first website assistant. Before you start: Start with a workspace and a website already added.
Watch: https://sairo.app/media/walkthroughs/01-get-your-assistant-live.mp4
Captions: https://sairo.app/media/walkthroughs/captions/01-get-your-assistant-live.vtt
Transcript:
- 00:00 Your website. Ready to help.: Already created your workspace and added your website? Let's get your Sairo assistant live.
- 00:06 Open Get started: Open Get started in the sidebar. Your setup checklist keeps verification, indexing, installation, and testing in one place.
- 00:15 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.
- 00:25 Index your pages: Select Refresh website content. Sairo reads the verified website and prepares its knowledge. The next step appears when indexing finishes.
- 00:35 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.
- 00:46 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.
- 00:55 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.
- 01:05 Your first answer, ready for visitors.: Your assistant is ready for a first conversation. Next, keep its answers accurate with confirmed knowledge.
Section: https://sairo.app/how-it-works#install
## 4. Let a specialist join when needed.
Live chat is enabled separately for each site. Choose the eligible teammates who cover it, then set Available when they can help. The desk does not need to stay in the foreground; browser notifications can alert them when a visitor is waiting.
A visitor can ask for a person, or an assistant escalation can enter the same queue automatically. The specialist reads the earlier transcript, claims the conversation, and replies inside the existing widget.
Section: https://sairo.app/how-it-works#handoff
## 5. Review what people actually ask.
The inbox keeps visitor, assistant, and specialist messages together. Lead records and the knowledge-gap report turn conversations into follow-up and content work.
Keep the original website current too. Scheduled refreshes and your content controls help the assistant stay aligned with the information you want visitors to use.
Use Ask Sairo to find a problem conversation and prepare an approved correction, or connect your workspace to a compatible AI application through MCP. Check the saved answer and keep its source page current.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/how-it-works#improve
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [How to add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website)
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
---
# A conversation, given a clear point of focus.
Canonical page: https://sairo.app/brand
Updated: 2026-09-03
The Sairo mark combines a speech form, a deliberate frame, and one tonal signal point. Together they express how Sairo works: listen to the question, stay within the available context, and make the next step clear.
## The idea: conversation with context.
Sairo helps a visitor ask about a website in ordinary language. The logo begins with that familiar exchange, then adds a visible boundary and a single point of attention. The result is a conversation mark with more structure than a generic chat bubble.
That structure reflects the product. A useful answer should come from the information a website has chosen to publish, and it should lead towards a clear answer or a human follow-up. The mark holds those ideas together without trying to illustrate every feature.
Section: https://sairo.app/brand#idea
## The speech shape keeps the exchange human.
The central outline borrows the recognisable shape and tail of a speech bubble. Its open contour leaves room for the visitor’s question, while the horizontal stroke reads like a line of text, an answer, or a source being brought into the conversation.
Four quiet corner forms sit outside the bubble. They suggest a defined field of view: Sairo works within the context it has been given. Their lighter weight keeps the conversation dominant while still making the boundary part of the identity.
### Conversation outline
A direct reference to questions, answers, and the exchange between a visitor and a business.
### Handoff tail
The conversation can lead somewhere: to an answer, an enquiry, or a person who can take the next step.
### Answer line
A small horizontal stroke that evokes written information becoming a clear response.
### Context corners
A restrained frame around the conversation, representing the sources and boundaries that keep an answer relevant.
Section: https://sairo.app/brand#shape
## The signal dot is the point of attention.
The solid centre is the smallest shape in the mark. Its density gives it emphasis within the same ink colour as the outline. It represents the active point in a conversation: the question that needs attention, the useful detail in a page, or the next step that should not get lost.
Two pale rings soften the transition between the signal point and the surrounding form. They help the signal remain legible at different sizes without turning it into an alert. The dot is a brand signature, not a loading indicator, presence status, or notification badge.
The full wordmark contains a second dot before “app”. There it performs a literal job as domain punctuation while echoing the signal inside the mark. The two dots belong to the same visual language, but they carry different responsibilities.
Section: https://sairo.app/brand#signal
## The wordmark says exactly what the product is.
The lowercase “sairo” keeps the name direct and approachable beside the more technical geometry of the mark. The “.app” ending names the product as a digital tool rather than leaving the symbol to explain the whole brand on its own.
The lettering is drawn as vector artwork instead of depending on a browser font. Its proportions, spacing, and relationship to the mark therefore remain consistent wherever the official artwork is used. The matching punctuation connects the spoken name to the signal point without competing with it.
Section: https://sairo.app/brand#wordmark
## Motion supports the story; it does not become the story.
On public pages, the mark may respond gently to scrolling: the symbol can shift and the signal point can travel a short distance before settling back into the lockup. The movement suggests an active conversation while keeping the logo readable throughout.
Sign-in and sign-up are focused tasks, so the logo stays still there. People should be able to enter details, use an invitation link, read privacy information, and recover an account without decorative motion competing for attention. A reduced-motion preference also keeps the logo static throughout the public site.
Section: https://sairo.app/brand#motion
## Use the logo so it stays recognisable.
Use the full lockup when Sairo is being introduced for the first time. The mark can stand alone in repeated or compact places where the name is already visible, such as an app icon, navigation treatment, or small brand signoff.
Give the artwork quiet space around its outer corners and test it at the size where it will actually appear. At small sizes, use the prepared mark instead of shrinking the full lockup until the “.app” lettering becomes difficult to read.
- Keep the proportions, spacing, corner forms, and tonal signal point intact.
- Place the logo on a surface where the outline and wordmark remain clearly visible.
- Do not crop the frame, stretch the artwork, redraw the wordmark, or add another badge to the signal point.
- Keep any movement subtle, brief, and tied to an intentional public-page interaction.
Section: https://sairo.app/brand#use
## The identity should remain accessible.
A logo that appears on its own needs an accessible name. When it sits inside a link that is already named “Sairo home”, the vector artwork can be hidden from assistive technology so the same label is not announced twice.
The signal point must never be the only way to communicate a status or required action. Surrounding text and controls still need clear names, states, and sufficient contrast. Motion must respect reduced-motion settings, and the static logo must remain the complete identity.
- Give an informative standalone logo the accessible name “Sairo”.
- Hide decorative logo artwork when its surrounding link already provides the name.
- Check the final background and theme rather than assuming the original colours will work everywhere.
- Never use the signal dot alone to mean online, unread, loading, success, or error.
Section: https://sairo.app/brand#accessibility
## Common questions
### Why are there two dots in the full logo?
The dot inside the mark is the point of attention in the conversation. The dot before “app” is the punctuation in the product name. Repeating the ink colour connects the symbol and wordmark without making them mean exactly the same thing.
### Can the Sairo logo animate?
Yes, on public storytelling surfaces where a restrained movement supports the page. It should settle quickly, stay readable, respect reduced-motion preferences, and remain static on focused authentication pages.
### When should the mark appear without the wordmark?
Use the mark alone when space is constrained or the Sairo name is already clear nearby. Use the full lockup when the audience may not yet recognise the symbol.
### Is the signal dot a product status?
No. It is part of the brand artwork. Product states such as loading, availability, success, and errors need their own labelled interface patterns.
Related pages
- [About Sairo](https://sairo.app/about)
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [AI website chatbot and live chat features](https://sairo.app/features)
---
# The same assistant. A workspace that fits your team.
Canonical page: https://sairo.app/solutions
Updated: 2026-09-03
Choose the workflow around the people maintaining the website and the people following up with its visitors.
## Built around who does the work.
Sairo uses one knowledge and conversation system across direct businesses and agencies. The workspace structure changes to match your responsibilities.
- [For agencies](https://sairo.app/solutions/agencies): Manage client sites, access, and branding in one portfolio.
- [For service businesses](https://sairo.app/solutions/service-businesses): Answer service questions and offer a live specialist when needed.
- [For support teams](https://sairo.app/solutions/customer-support): Combine published help, live chat, and a shared transcript.
Section: https://sairo.app/solutions#teams
## For stores and software products.
Help visitors understand public product information and find the appropriate next step. Keep private account questions and order-specific requests with an authorised support workflow.
- [AI website assistant for ecommerce information](https://sairo.app/solutions/ecommerce): Use Sairo to answer published product and policy questions, identify missing information, and offer per-site live chat with an assigned specialist.
- [AI website chatbot for SaaS marketing and help](https://sairo.app/solutions/saas): Help SaaS website visitors understand published features and setup guidance, capture product enquiries, and identify gaps in public documentation.
Section: https://sairo.app/solutions#digital-products
Related pages
- [AI website chatbot and live chat features](https://sairo.app/features)
- [Plans and pricing](https://sairo.app/pricing)
- [Contact Sairo](https://sairo.app/contact)
---
# A better handoff between your agency and its clients.
Canonical page: https://sairo.app/solutions/agencies
Updated: 2026-09-06
Keep assistant configuration with your team while giving clients the access they need to review their own website knowledge.
## See the portfolio. Open one client at a time.
An agency workspace groups websites into client projects. Your team can move between sites while client members remain scoped to the project assigned to them.
Each site has its own sources, conversations, leads, and knowledge gaps. This separation is useful when different clients use similar terminology but have different services, prices, or policies.
Section: https://sairo.app/solutions/agencies#portfolio
## Let the right people improve answers and take chats.
Clients can be given permission to contribute knowledge without gaining the agency’s configuration or billing controls. Approved answers then become part of that site’s knowledge.
An administrator can assign eligible workspace members as live chat specialists for a particular site. Project scope still applies, keeping client conversations with the people authorised to see them.
Ask Sairo and connected AI applications follow those project boundaries. An account can review only its permitted websites. Select the intended client website before preparing a correction, and review each external application’s workspace scope during connection.
- Project-scoped invitations
- Per-site live chat specialists
- Optional client content contribution
- Agency and client branding controls
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/solutions/agencies#collaboration
## Roll out with a repeatable checklist.
Start with one client’s verified website. Review sources, configure the assistant, test important questions, and check the widget in the client’s actual theme.
If live chat is enabled, test the site with a specialist online and offline. Add more sites as you learn, choosing coverage and permissions separately for every client.
Section: https://sairo.app/solutions/agencies#rollout
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [Plans and pricing](https://sairo.app/pricing)
- [How agencies can manage client chatbots](https://sairo.app/guides/manage-client-chatbots)
---
# Help visitors understand your services before the first call.
Canonical page: https://sairo.app/solutions/service-businesses
Updated: 2026-09-06
Make published service details easier to find, then give your team enough context for the next conversation.
## Start with the questions your website can answer.
Opening hours, service areas, contact details, and published service descriptions are useful starting points. Confirm those details in the workspace and keep the source pages current.
Sairo uses the website’s content to answer. If the sources do not establish a price, policy, or availability, the assistant should say that it does not have that detail and offer a follow-up.
Section: https://sairo.app/solutions/service-businesses#questions
## Turn contact details into a lead your team can act on.
When a visitor shares an email address or phone number, the assistant can save it with the conversation. Staff can review the request, assign an owner, add notes, and track the lead’s next step.
A captured contact is an enquiry, not a guaranteed sale. Your team remains responsible for responding and confirming any quote or appointment.
Section: https://sairo.app/solutions/service-businesses#follow-up
## Let a service specialist join the same conversation.
Enable live chat for the site and assign the teammates who are authorised to answer its visitors. When someone sets themselves Available, the widget can show that a specialist is available.
The specialist sees the earlier question and assistant replies before joining. When nobody is available, the widget offers a message queue instead of implying that an immediate response is available.
Section: https://sairo.app/solutions/service-businesses#live-chat
## Use unanswered questions to improve the website.
A repeated question often points to information a visitor expected to find. Review the knowledge gaps, write an approved answer, and update the original page where appropriate.
This makes the assistant and the website more useful together, instead of turning the chat window into a second place to maintain conflicting information.
For a wrong opening-hours or service-area answer, bring the conversation to Ask Sairo and supply the confirmed business detail. Review the affected website and retest the original question after saving.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/solutions/service-businesses#improve
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
- [Plans and pricing](https://sairo.app/pricing)
---
# Make published help easier to use.
Canonical page: https://sairo.app/solutions/customer-support
Updated: 2026-09-06
Give visitors a conversational way to find your public information, with a clear route to your team when the answer needs a person.
## Keep answers tied to your published guidance.
Choose the public pages that should inform the assistant, such as service explanations, help articles, and contact instructions. Exclude obsolete or irrelevant pages.
Saved answers are useful for carefully approved wording. An exact match uses that answer directly, while other questions use the available website knowledge.
Section: https://sairo.app/solutions/customer-support#sources
## Move the same conversation to a support specialist.
Enable live chat for the site and choose the workspace members who cover it. A visitor can request a person, and an AI escalation can enter the specialist queue automatically.
The first eligible specialist to claim the chat replies in the existing widget. Other assigned specialists can see that the visitor is being helped, and an inactive owner can be taken over after the presence window expires.
Section: https://sairo.app/solutions/customer-support#live-chat
## Review the complete conversation with its context intact.
The shared inbox keeps visitor questions, assistant answers, and named specialist replies together. Internal notes help the team coordinate without exposing those notes to a client viewer.
Use the stored transcript to check what the visitor was told, whether the live exchange ended clearly, and which knowledge or follow-up work remains.
Section: https://sairo.app/solutions/customer-support#inbox
## Find the help content that is missing.
Unanswered questions become a practical content backlog. Review the phrasing visitors use and improve the source material before expanding the assistant to more pages.
Use conversation and outcome analytics as operational signals. They show what happened in the assistant; they do not establish customer satisfaction or resolution without your review.
Bring an incorrect or incomplete reply into Ask Sairo from the inbox. Review the evidence, supply approved wording and save a correction. Teams using Claude can review permitted Sairo conversations through an OAuth MCP connection.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/solutions/customer-support#gaps
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Accessibility belongs in the conversation.
Canonical page: https://sairo.app/accessibility
Updated: 2026-09-06
The widget is designed with keyboard access, focus management, and screen reader announcements in mind. Your website integration still needs its own review.
## The interaction details matter.
The chat launcher has an accessible name. Opening and closing the widget manages focus, and Escape returns the visitor to the launcher. A separate polite announcement region reads complete reply sentences while the transcript stays available to browse.
Live chat states use words such as waiting, connected, and ended, and the specialist’s name identifies the speaker. Controls use generous targets, and reduced-motion preferences are respected.
- Named controls and keyboard operation
- Clear live chat status and speaker names
- Polite transcript announcements
- Reduced-motion support
Section: https://sairo.app/accessibility#interaction
## An optional way to speak your question.
When enabled for the website and supported by the browser, dictation lets a visitor record a short question after granting microphone permission. Sairo converts the recording to text and inserts it into the composer so the visitor can check or edit it before sending.
Typing remains available. This is speech-to-text input, not a telephone service or a spoken conversation with the assistant. Availability depends on site settings, the configured transcription provider and the workspace’s dictation allowance. Test microphone permission, recording status and the typing fallback in your own website.
- [How dictation audio is processed](https://sairo.app/privacy#dictation)
Section: https://sairo.app/accessibility#dictation
## Test the widget as part of the whole page.
A widget can interact with sticky navigation, consent banners, zoom, and other fixed elements. Test the installation in your website’s actual layout, including narrow screens and enlarged text.
The widget uses Shadow DOM instead of an iframe. Its accessible relationships stay within the same component boundary; this does not remove the need to check the resulting experience with assistive technology.
Section: https://sairo.app/accessibility#integration
## Design intent is not a certification.
Sairo targets relevant WCAG 2.2 AA interaction requirements. The accessibility statement and VPAT-based draft report describe the current review and the manual validation still needed. Full conformance has not been established.
A chatbot cannot repair accessibility barriers elsewhere on your website. Include the assistant in your normal audit, document the tested browsers and assistive technologies, and report any issue through the contact form.
- [Read our accessibility statement](https://sairo.app/accessibility-statement)
- [Read the report and download the VPAT draft](https://sairo.app/accessibility-report)
- [Use the integration test guide](https://sairo.app/guides/test-chatbot-accessibility): A practical keyboard, screen reader, zoom, and motion checklist.
- [Report an accessibility issue](https://sairo.app/contact?topic=accessibility): Include the page, device, and steps needed to reproduce it.
Section: https://sairo.app/accessibility#scope
Related pages
- [AI website chatbot and live chat features](https://sairo.app/features)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Clear boundaries around your websites and workspace.
Canonical page: https://sairo.app/security
Updated: 2026-09-08
Understand the controls that are implemented, the information the assistant uses, and the checks your team should make before rollout.
## Access follows the workspace and project.
Workspaces separate organisations, while project-scoped memberships limit access within an agency. Management actions check the acting user’s permissions on the server.
Staff administration is restricted to staff accounts. Account settings let a user change their password and revoke sessions; password changes end other sessions. Passwords are stored as salted scrypt hashes.
Section: https://sairo.app/security#access
## Live chat follows site access and assignment.
A site administrator enables live chat and selects active workspace members who can access that website. Client viewers cannot configure or operate live chat, and a specialist cannot claim a conversation from an unassigned site.
The first eligible specialist claims the chat atomically. Only that specialist can reply or end it while they remain active; takeover becomes available after the owner stops reporting presence for the defined inactivity window.
Section: https://sairo.app/security#live-chat
## Reading a site has limits.
A full website crawl requires ownership verification. The fetch layer checks destinations to prevent access to private network addresses, follows robots.txt, and applies crawl and usage limits.
Source exclusions and saved answers let your team control what informs a reply. Instruction-like text in crawled content is filtered, and the response guard checks unsupported currency and percentage claims. These controls reduce risk; generated answers still need evaluation.
Section: https://sairo.app/security#sources
## Ask Sairo follows the same access boundaries.
Ask Sairo checks workspace membership, project access and website scope for each operation. Its conversation history belongs to the signed-in user; applied changes affect the shared records that user is permitted to edit. Visitor text and website content do not grant permissions.
Supported changes record the proposed value and prior state. Applying or undoing a change checks the current record and rejects a stale update. Explicit direct corrections can be saved automatically only when the dashboard setting and the request qualify; other proposals have review controls.
The tool set does not expose arbitrary database queries, billing, team administration, credentials or outbound customer messaging. Ask Sairo’s tools are fixed and are not the same thing as the actions a website can configure for its visitor assistant; those run on the visitor side, against endpoints that website’s own team registers.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
Section: https://sairo.app/security#assistant-access
## Choose and revoke external application access.
Sairo’s public MCP endpoint uses OAuth authorisation with PKCE. Sign-in lets you select the workspace, website access and whether to allow changes. Read access is the default. The service checks the connection and your current team permissions on each request.
Access tokens are short-lived and stored as hashes. Refresh tokens rotate, and the connection expires after 30 days unless you reconnect. Disconnecting, changing a password or resetting it revokes the connection. Ordinary website sign-out leaves separately authorised applications connected.
The service records prepared and applied changes, but an external application controls its own confirmation interface. Choose read-only access when it should not make updates. Disconnecting stops future access; it cannot retrieve information already shared with that application.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
- [Manage connected apps](https://sairo.app/account/connections)
Section: https://sairo.app/security#connected-apps
## Provider credentials stay on the server.
The installed widget carries a public site key, not your AI provider credential. The production service uses HTTPS, and the configured OpenRouter key is supplied to server processes through deployment settings.
Messages and relevant website excerpts may be sent to the configured AI provider to produce replies and embeddings. Review the data flow and provider terms before using the assistant for a sensitive workflow.
- [Read the data practices overview](https://sairo.app/privacy): Accounts, conversations, website content, and service providers.
Section: https://sairo.app/security#providers
## An action reaches only where you point it.
A website can let its assistant call a system you already run. Sairo accepts only HTTPS addresses that resolve to public hosts, so an action cannot be aimed at a private network or a cloud metadata service, and that check is repeated when the call is made rather than only when it is saved. A site may hold up to ten actions and the assistant may run at most two in a single reply.
What an action returns is treated as evidence, not as instruction: it enters the answer the same way a page from your website does, and the assistant still refuses to state anything the evidence does not support. Every call is recorded with the address, what was sent and what came back, for your own team to read.
- [See how evidence reaches an answer](https://sairo.app/features/website-knowledge): Indexed sources, confirmed facts and saved answers.
Section: https://sairo.app/security#actions
## Files are stored, not rendered.
A photo or PDF sent in a conversation is identified by reading its own bytes rather than trusting its name or its stated type. SVG is refused because it can carry script. Every attachment is served as a download under a restrictive content policy, so nothing a visitor uploads is ever executed or displayed as part of a page.
Uploaded reference documents become indexed knowledge and are addressed by an internal identifier rather than a web address. A citation therefore never links a visitor to a page that does not exist.
Section: https://sairo.app/security#files
## API keys are hashed and scoped.
An API key is stored as a hash with a short visible prefix, so you can recognise a key in a list but nobody, including Sairo, can read it back. Read and write access are separate scopes, a key is limited to the workspace that issued it, and revoking one takes effect immediately.
A verified custom domain serves that website’s help centre and nothing else. The workspace and the API stay on sairo.app, so a domain you point at Sairo cannot become a second entrance to an account.
- [Check the implemented capabilities](https://sairo.app/product-facts): What exists, and what to confirm before you rely on it.
Section: https://sairo.app/security#keys
## Refuse a visitor who is abusing your team.
A live chat transcript is written partly by anonymous visitors. From the live chat desk or the inbox, on the web or in the desktop app, a specialist can block that visitor and can report the conversation to Sairo. Blocking asks for a reason, ends any live chat still open with them, and takes effect on the assistant, live chat, dictation and the realtime connection.
A block records the token the widget keeps in that browser and a hash of the network address the conversation came from. Someone who clears their browser data or moves to another network can return, so treat it as a deterrent and an operator control rather than an identity check. Address blocks expire after 30 days because addresses are reassigned and shared. Active blocks are listed under a website’s live chat settings and can be lifted there.
Reporting is separate and never blocks on its own. It sends the conversation to the Sairo team for content your own team should not have to resolve. Anyone can also report abuse through the contact form.
- [Report abuse to Sairo](https://sairo.app/contact?topic=abuse): For harmful content on a website using Sairo.
Section: https://sairo.app/security#moderation
## Bring specific requirements to the review.
This page describes implemented product controls. It does not claim SOC 2 certification, a particular data-residency region, an uptime guarantee, or an independent security audit.
If your procurement process requires a security questionnaire, retention agreement, or contractual commitment, contact Sairo before sending that category of information to the service.
Section: https://sairo.app/security#review
Related pages
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [Contact Sairo](https://sairo.app/contact)
- [Sairo privacy policy](https://sairo.app/privacy)
---
# At home on your website. Connected to your work.
Canonical page: https://sairo.app/integrations
Updated: 2026-09-08
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.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
- [Follow the Claude connection guide](https://sairo.app/guides/connect-sairo-to-claude): Custom connectors, Claude Code, first requests and troubleshooting.
- [Get your connection address](https://sairo.app/connect)
Section: https://sairo.app/integrations#connected-apps
## 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.
Section: https://sairo.app/integrations#install
## 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.
Section: https://sairo.app/integrations#cms
## 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.
Section: https://sairo.app/integrations#actions
## 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.
- [Check the implemented capabilities](https://sairo.app/product-facts): What exists today, with the boundary of each.
Section: https://sairo.app/integrations#api
## 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.
Section: https://sairo.app/integrations#whatsapp
## 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.
- [Follow the installation guide](https://sairo.app/guides/add-ai-chatbot-to-website): From ownership verification to your first reviewed conversation.
- [Configure live chat](https://sairo.app/guides/set-up-live-chat): Assign specialists and test the complete handoff.
Section: https://sairo.app/integrations#verify
## Find your website platform.
Follow the custom-code route for your platform. Each guide covers prerequisites, script placement, publishing, and checks on the visitor-facing website. These are instructions for the Sairo JavaScript embed, rather than a catalogue of native plugins.
- [Add an AI chatbot to WordPress](https://sairo.app/integrations/wordpress): Add Sairo to a WordPress website with a script snippet. Check WordPress.com code restrictions, verify the website, and test the published installation.
- [Add an AI chatbot to Webflow](https://sairo.app/integrations/webflow): Install Sairo on Webflow using footer custom code. Review access, publish the snippet, and test CMS pages, navigation, and visitor conversations.
- [Add an AI chatbot to a Wix website](https://sairo.app/integrations/wix): Set up Sairo through Wix Custom Code, choose the intended pages, and test the assistant on a published Wix site with a connected domain.
- [Add a website AI chatbot to Shopify](https://sairo.app/integrations/shopify): Use Sairo on Shopify storefront pages through a maintained theme script. Review public product and policy content without implying order-system access.
- [Add an AI chatbot to Squarespace](https://sairo.app/integrations/squarespace): Install Sairo with Squarespace footer code injection, check your plan’s access, and validate the assistant on the published website.
- [Add an AI chatbot to a Framer website](https://sairo.app/integrations/framer): Set up Sairo in Framer’s Custom Code settings, select where it runs, and test the published site across navigation and responsive layouts.
Section: https://sairo.app/integrations#platform-guides
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
---
# A useful assistant starts with a careful setup.
Canonical page: https://sairo.app/guides
Updated: 2026-09-06
Practical guidance for the people maintaining the website, reviewing its answers, and checking the visitor experience.
## Start with the work in front of you.
These guides describe the current Sairo workflow and call out the checks that remain with your team.
- [Watch the video walkthroughs](https://sairo.app/guides/walkthroughs): Five narrated films, about a minute each, from first answer to weekly review.
- [Add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website): Verify ownership, review sources, install the snippet, and test.
- [Set up live chat for a website](https://sairo.app/guides/set-up-live-chat): Enable one site, assign specialists, and test handoff and offline states.
- [Prepare your website for AI answers](https://sairo.app/guides/prepare-website-for-ai): Make important information readable, current, and unambiguous.
- [Test chatbot accessibility](https://sairo.app/guides/test-chatbot-accessibility): Check keyboard access, announcements, zoom, and page interference.
Section: https://sairo.app/guides#library
## Work on the answer, wherever you are.
Review an incorrect reply inside Ask Sairo, or connect the same workspace to Claude. Start with one website and a question whose correct answer you can verify.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
- [Connect Sairo to Claude with MCP](https://sairo.app/guides/connect-sairo-to-claude): Choose access, test a read, review a change and disconnect.
Section: https://sairo.app/guides#assistant-workflows
## Improve answers and measure the result.
Use a repeatable review process to check answer quality, interpret conversation outcomes, and keep the knowledge current.
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations): Improve website chatbot answer reliability with source review, saved answers, missing-information tests, human handoff, and a practical regression set.
- [How to measure website chatbot performance](https://sairo.app/guides/measure-chatbot-performance): Build a practical chatbot measurement routine using conversation volume, captured leads, answer review, follow-up completion, and comparable date ranges.
Section: https://sairo.app/guides#quality
## Plan, launch, and maintain.
Work through capacity assumptions, domain verification, installation issues, and client responsibilities. After you create a workspace, setup saves the five launch steps. The public checklist remains a printable review aid and does not write to your account.
- [Website chatbot cost and usage planning](https://sairo.app/guides/website-chatbot-cost): Plan website chatbot capacity using pages, refresh frequency, and estimated conversations. Understand model costs, team effort, and Sairo plan allowances.
- [Troubleshoot a website chatbot installation](https://sairo.app/guides/troubleshoot-chatbot-installation): Diagnose a missing chatbot launcher, blocked scripts, origin errors, failed responses, and poor source coverage with a clear Sairo troubleshooting sequence.
- [How agencies can manage client chatbots](https://sairo.app/guides/manage-client-chatbots): Build a repeatable agency chatbot and live chat workflow with client projects, scoped invitations, per-site specialists, knowledge ownership, and handover.
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist): Use an interactive, printable checklist to review chatbot sources, installation, accessibility, lead capture, live chat staffing, and handoff before launch.
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat): Set up Sairo live chat for one website: enable the feature, assign specialists, understand presence, test AI handoff, and operate the queue.
- [Verify website ownership for a chatbot](https://sairo.app/guides/verify-website-ownership): Verify a Sairo website using its DNS TXT record or verification file. Understand the exact values, common failures, and the next indexing step.
Section: https://sairo.app/guides#operations
## Choose the right kind of help.
Compare a maintained FAQ, AI website answers, and staffed live chat. Sairo can combine AI and a specialist in one widget while keeping their responsibilities clear.
- [Compare your options](https://sairo.app/compare): Capabilities, operating effort, and boundaries.
- [Set up live chat](https://sairo.app/guides/set-up-live-chat): Configure specialists, presence, queues, and the handoff journey.
- [Website chatbot glossary](https://sairo.app/glossary): Plain-language definitions of the terms used in these guides.
- [Platform installation guides](https://sairo.app/integrations): WordPress, Webflow, Wix, Shopify, Squarespace, and Framer.
Section: https://sairo.app/guides#choose
## Know what supports the guidance.
These are first-party Sairo guides. Check the visible update date and the source references for the task, and report a step that no longer matches the product.
- [Our editorial and corrections policy](https://sairo.app/editorial-policy)
- [Product capabilities at a glance](https://sairo.app/product-facts)
Section: https://sairo.app/guides#reading-guides
Related pages
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
- [Frequently asked questions](https://sairo.app/faq)
---
# How to add an AI chatbot to your website.
Canonical page: https://sairo.app/guides/add-ai-chatbot-to-website
Published: 2026-09-03
Updated: 2026-09-06
A practical setup sequence for a site owner or the agency responsible for the site. Allow time to review the content as well as the installation.
## What is the shortest reliable setup sequence?
Verify the website, check the indexed sources, configure the assistant and install one site-specific script in the shared layout. Test a known answer, missing information, lead capture, human handoff and keyboard access on the published site.
## 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.
Section: https://sairo.app/guides/add-ai-chatbot-to-website#access
## 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.
Section: https://sairo.app/guides/add-ai-chatbot-to-website#knowledge
## 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.
Section: https://sairo.app/guides/add-ai-chatbot-to-website#configuration
## 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
Section: https://sairo.app/guides/add-ai-chatbot-to-website#test
## 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.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/guides/add-ai-chatbot-to-website#maintain
## 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.
Example embed: use the site key from your workspace
```
```
Video walkthrough 01: Get your assistant live (1:13, English narration with captions). Verify, install, and test your first website assistant. Before you start: Start with a workspace and a website already added.
Watch: https://sairo.app/media/walkthroughs/01-get-your-assistant-live.mp4
Captions: https://sairo.app/media/walkthroughs/captions/01-get-your-assistant-live.vtt
Transcript:
- 00:00 Your website. Ready to help.: Already created your workspace and added your website? Let's get your Sairo assistant live.
- 00:06 Open Get started: Open Get started in the sidebar. Your setup checklist keeps verification, indexing, installation, and testing in one place.
- 00:15 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.
- 00:25 Index your pages: Select Refresh website content. Sairo reads the verified website and prepares its knowledge. The next step appears when indexing finishes.
- 00:35 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.
- 00:46 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.
- 00:55 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.
- 01:05 Your first answer, ready for visitors.: Your assistant is ready for a first conversation. Next, keep its answers accurate with confirmed knowledge.
- [Choose your platform instructions](https://sairo.app/integrations): Use the correct location and publishing steps for your site builder.
Section: https://sairo.app/guides/add-ai-chatbot-to-website#snippet
## 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.
An example acceptance test
| 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. |
- [Use the launch checklist](https://sairo.app/guides/chatbot-launch-checklist): Check sources, installation, live chat, and accessibility.
Section: https://sairo.app/guides/add-ai-chatbot-to-website#acceptance
Related pages
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat)
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Give the assistant better information to work with.
Canonical page: https://sairo.app/guides/prepare-website-for-ai
Published: 2026-09-03
Updated: 2026-09-06
Clear source material makes answers easier to check and maintain. Start with the questions visitors need answered most often.
## What makes a website useful as chatbot knowledge?
Publish important facts in readable HTML, give policies clear conditions and dates, resolve conflicting versions and allow the relevant crawl. Map real visitor questions to source pages, then verify what the chatbot actually retrieved.
## Write down the questions that matter.
List common questions about services, eligibility, locations, hours, pricing, and next steps. For each question, identify the page that should support the answer.
If no page establishes the answer, decide whether to publish it or add a carefully approved saved answer. Do not expect the model to fill a gap in business policy.
Section: https://sairo.app/guides/prepare-website-for-ai#questions
## Remove conflicting versions of the facts.
Check the main navigation, service pages, and footer for different phone numbers, hours, or service areas. Archive expired offers and revise outdated policy pages.
Put dates and conditions next to time-sensitive information. A price without its scope or exclusions can be easy to repeat incorrectly, even when the number itself appears on the page.
Section: https://sairo.app/guides/prepare-website-for-ai#facts
## Make important information available as text.
Use descriptive headings and readable HTML for essential service information. Text that exists only inside an image, a login-only area, or a client-side interaction may not be available to a standard crawl.
Check robots.txt and the source list after indexing. If a needed page was excluded or could not be read, resolve that before judging the assistant’s answer quality.
Section: https://sairo.app/guides/prepare-website-for-ai#readability
## Review sources and test the boundary.
Exclude pages that should not inform replies. Confirm the business details extracted by Sairo and add saved answers where exact wording is necessary.
Ask both expected questions and plausible questions that the website cannot answer. Review the response and outcome, then use the gap report to decide what to improve next.
Ask Sairo can help inspect a visitor question and prepare an answer correction after you establish the correct information. Keep the website page and confirmed facts aligned with that correction.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/guides/prepare-website-for-ai#review
## Keep a source inventory your team can maintain.
Give high-impact information an owner and a review trigger. An inventory can be a short shared document; the useful part is knowing which source wins when two pages disagree.
When a policy changes, review the published page, the indexed source, confirmed business details, and any saved answers that repeat it. Refreshing a page alone does not review those separately maintained records.
Example source review record
| Information | Authoritative source | Review trigger |
| --- | --- | --- |
| Service price and scope | Current service or pricing page | A price, inclusion, or tax treatment changes. |
| Opening hours | Location or contact page | Seasonal hours, closures, or a move. |
| Eligibility or service area | Current eligibility or location page | A new region, condition, or exclusion. |
| Follow-up expectations | Contact or support page | A change in staffing, channel, or response commitment. |
### Rewrite an ambiguous source
“Packages from 200” leaves the currency, scope, and conditions unclear. A useful source states the currency, what the starting package includes, and when an individual quote is required. Use your actual approved terms rather than copying this example into a pricing policy.
- [Understand the knowledge controls](https://sairo.app/features/website-knowledge): How indexed sources, confirmed facts, and saved answers work together.
- [Build an answer-quality review](https://sairo.app/guides/reduce-chatbot-hallucinations): Test unsupported questions as well as easy answers.
Section: https://sairo.app/guides/prepare-website-for-ai#inventory
Related pages
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
- [AI website chatbot and live chat features](https://sairo.app/features)
- [How to add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website)
---
# Test the chat window as part of the website.
Canonical page: https://sairo.app/guides/test-chatbot-accessibility
Published: 2026-09-03
Updated: 2026-09-06
Use this practical integration checklist alongside your broader accessibility review. Record the browser, device, and assistive technology you use.
## How should I test a chatbot for accessibility?
Test the installed chatbot within its host page using a keyboard, screen reader, zoom, narrow layouts, increased text spacing and visual preferences. Include loading, errors, long replies and live handoff. Automated scans alone do not establish conformance.
## Start with the keyboard.
Use Tab to reach the launcher and confirm that focus is visible. Open the assistant, move through the controls, enter a question, and send it without a pointer.
Close the assistant and check where focus returns. Try Escape, and verify that opening the panel has not made important page controls impossible to reach.
- The launcher has a useful accessible name
- Focus is visible at every step
- Controls work without a mouse
- Closing the panel restores a sensible focus position
Section: https://sairo.app/guides/test-chatbot-accessibility#keyboard
## Listen to the conversation.
With a screen reader, inspect the launcher, panel, input label, and send button. Submit a question and listen for the new response. The experience should make sense without having to visually locate each new message.
Check that long replies, errors, and loading states do not create repetitive or confusing announcements. If you find a problem, include the exact browser and screen reader combination in your report.
Section: https://sairo.app/guides/test-chatbot-accessibility#screen-reader
## Check zoom, narrow screens, and other overlays.
Enlarge text and test browser zoom. Use a narrow viewport and confirm that the input and controls remain usable without the page developing unnecessary horizontal scrolling.
Inspect interactions with sticky navigation, cookie controls, other widgets, and the on-screen keyboard. A fixed launcher should not prevent a visitor from reaching the content beneath it.
If you customize the chatbot, test the saved palette in the installed widget. Include label visibility, contrast warnings, keyboard access and focus indicators.
- [Understand appearance settings and checks](https://sairo.app/features/chatbot-themes)
Section: https://sairo.app/guides/test-chatbot-accessibility#layout
## Include motion and realistic content.
Enable reduced motion and confirm that optional movement is reduced. Test short answers, long answers, an unavailable response, and a request for human attention.
This checklist supports a focused integration review. It is not a completed WCAG conformance assessment; evaluate the full website and document any remaining issues.
- [Share an accessibility issue](https://sairo.app/contact?topic=accessibility): Tell us what you expected, what happened, and how to reproduce it.
Section: https://sairo.app/guides/test-chatbot-accessibility#motion
## Record reproducible findings.
For each issue, record the page address, browser and version, assistive technology, steps, expected behaviour, and observed result. Describe the user task that was blocked rather than reporting only an automated score.
Check the widget together with cookie banners, navigation drawers, sticky contact buttons, and other content on the host page. Test keyboard focus after opening and closing those elements in different orders. An isolated widget check cannot establish the accessibility of the complete website.
If dictation is enabled, test granting and denying microphone permission, stopping a recording, editing the returned text and continuing by typing. Make sure recording and transcription status are understandable without relying on the microphone icon alone.
A practical review record
| Journey | Check | Record |
| --- | --- | --- |
| Open and close the assistant | Keyboard operation and visible focus | Where focus starts, moves, and returns. |
| Send and receive a message | Labels, status updates, and reading order | What the screen reader announces and when. |
| Read at increased zoom | Reflow, readable content, and reachable controls | Zoom level, viewport, and any overlap. |
| Recover from an error | A clear message and usable retry route | Whether the visitor understands what to do next. |
Source references
- [W3C: developing a keyboard interface](https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/)
- [W3C: preliminary accessibility checks](https://www.w3.org/WAI/test-evaluate/preliminary/)
Section: https://sairo.app/guides/test-chatbot-accessibility#record
Related pages
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# A useful website should be easier to talk to.
Canonical page: https://sairo.app/about
Updated: 2026-09-06
Sairo brings a conversational interface to the information businesses already publish, with tools for the people responsible for keeping it accurate.
## The website remains the source.
Visitors should be able to find useful information without guessing which page contains it. A website assistant can help, provided its answers stay connected to material the business has approved.
Sairo combines website indexing, saved answers, per-site live chat, conversation review, and a record of unanswered questions. The aim is a more useful website and a clear route from an AI answer to the responsible person.
Sairo also helps the people maintaining those answers. Ask Sairo provides a conversational workspace for reviewing visitor questions and making supported updates, while the MCP connection brings permitted workspace tasks into other AI applications.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/about#purpose
## The details are part of the product.
Keyboard access, focus behavior, source controls, and project permissions are not optional extras around the conversation. They shape whether the assistant is practical to install and maintain.
Useful software is easier to maintain when its behavior is clear. Source review, conversation history, and scoped access help a team understand what the assistant knows and who can change it.
Section: https://sairo.app/about#principles
## Built for the people maintaining the site.
A direct business needs a focused view of its own visitors. An agency needs a portfolio view and a reliable boundary around each client. Sairo supports both through one workspace and project model.
If you want to discuss a rollout, report an issue, or understand whether a specific requirement fits the product, use the contact form.
Section: https://sairo.app/about#teams
## Check the product and the evidence.
Sairo is an AI website chatbot and live chat platform. Our product reference brings the implemented capabilities, plan boundaries and links to supporting documentation together in one place. Sairo’s public guides are first-party product information; the editorial policy explains attribution, examples, updates and corrections.
- [Product facts and limitations](https://sairo.app/product-facts)
- [How we maintain this information](https://sairo.app/editorial-policy)
- [Accessibility review and outstanding checks](https://sairo.app/accessibility-report)
Section: https://sairo.app/about#product-reference
Related pages
- [AI website chatbot and live chat features](https://sairo.app/features)
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [Contact Sairo](https://sairo.app/contact)
---
# What Sairo processes, why, and for how long.
Canonical page: https://sairo.app/privacy
Updated: 2026-09-08
This policy covers the Sairo service, the sairo.app website, the embedded assistant, Sairo for Mac and Windows, and the Sairo mobile apps. It names the providers involved, gives the retention period for each kind of record, and explains how to request access, correction or deletion. If you chatted with Sairo on another business’s website, that business decides how it uses your conversation; this policy describes Sairo’s role as its service provider.
## The short version.
Sairo processes account details, website content, visitor conversations and workspace records to run an AI website assistant and live chat service for businesses. It sends relevant text to AI providers to generate replies, search embeddings and dictation transcripts, and it uses hosting, email, payment and backup providers to operate. Sairo does not sell personal information, does not use it for advertising, and does not place third-party analytics or tracking in its website or apps.
Records are kept for as long as the account or workspace that owns them exists, plus the fixed periods listed on this page. You can ask for access, correction or deletion at any time. A verified deletion request disables the account immediately and removes personal data within 30 days, apart from records the law requires Sairo to keep.
Section: https://sairo.app/privacy#summary
## Account and workspace information.
Sairo stores account details such as name and email address, a password hash, workspace memberships, roles, invitations and sign-in sessions. These records support access to the service and administration of a workspace. For paid plans, Sairo keeps the customer, subscription and invoice identifiers and status returned by Dodo Payments; card numbers are entered with Dodo Payments and are never stored by Sairo.
A contact form submission stores the details you enter so Sairo staff can review and respond. Do not include passwords, API keys or sensitive personal information in a general enquiry.
Section: https://sairo.app/privacy#accounts
## Website content and conversations.
The service stores indexed website content, extracted business details and saved answers. It also records visitor messages, assistant replies, live specialist replies, conversation outcomes, appointment requests and any contact details a visitor chooses to provide.
On a website whose owner has switched live chat on, the widget reports that someone is reading a page so a specialist can offer help. Sairo records the page path, its title and how long the visit has lasted, against a hash of the widget token that browser already holds. It does not record the query string, a network address or a location, and the record is removed shortly after the visitor stops reading. Websites without live chat enabled do not report this at all.
A visitor can attach a photo or a PDF to a conversation, and a specialist can send one back. Sairo stores the file with that conversation, decides its type by reading the file itself rather than trusting its name, and always serves it as a download rather than displaying it as part of a page. A workspace can also upload its own reference documents, which become indexed knowledge like any other source. Do not send information through either route that the agreed service is not meant to handle.
If a specialist blocks an abusive visitor, Sairo stores the reason, who blocked them, and hashes of that browser’s widget token and network address, so the block can be enforced and lifted. Workspace members may use conversation notes, assignments, lead follow-up records and live chat presence timestamps. Access depends on their role, project scope and site specialist assignment. The website operator decides what content to connect, who may read conversations and how its team follows up with visitors.
Section: https://sairo.app/privacy#content
## Ask Sairo history and change records.
Ask Sairo stores your requests, assistant replies, relevant tool results and proposed or completed changes. A change record includes the affected website, previous and proposed values, status and timing so you can review or undo a supported update.
History is owned by your account within the workspace. Applied updates affect shared business records, and permitted workspace activity can show those changes. Relevant conversation history and retrieved records are sent to the configured AI provider to interpret a request.
Section: https://sairo.app/privacy#workspace-assistant
## Information shared with connected AI applications.
When you approve an MCP connection, Sairo records the application, account, workspace, website scope, permissions, expiry and connection activity. It stores hashes of access and refresh tokens and records supported changes made through that connection.
An authorised application can receive permitted visitor conversations, knowledge, business information, leads and other tool results in response to its requests. Those records may include personal information a visitor or teammate provided. The application processes that information under its own terms, settings and retention practices; Sairo has no control over it once delivered.
Disconnect an application from Connected apps to stop future access through that connection. Disconnecting does not erase information already returned to the application or remove the Sairo change history. For deletion or access requests, identify both the Sairo workspace and any external service that received the information.
- [Review your connected apps](https://sairo.app/account/connections): See, limit and disconnect authorised applications.
- [Understand the connection’s available operations](https://sairo.app/integrations/mcp): Tools, scopes and read or write access.
Section: https://sairo.app/privacy#connected-apps
## Optional voice dictation.
When a visitor or workspace user chooses dictation and grants microphone permission, a short recording is sent through Sairo to the configured transcription service, OpenAI GPT-4o mini Transcribe via OpenRouter. The returned text can be reviewed in the composer before it is submitted as a message.
Sairo processes the audio for that request and records usage; it does not save the audio as a conversation attachment or keep a copy. Submitted text follows the normal conversation data flow. Dictation is optional and typing is always available.
Section: https://sairo.app/privacy#dictation
## Service providers and where information goes.
Sairo shares information with the providers below only to provide, secure and support the service, under each provider’s service and data-processing terms. Those terms require the provider to protect the information and to use it only to perform its service for Sairo. Sairo does not permit providers to use your information for their own purposes, including advertising or training their models, and Sairo does not sell personal information to anyone.
Sairo’s servers and providers are located in the United States, so information is processed and stored there regardless of where you use the service. Applications you connect yourself, and the businesses whose websites you chat on, are not Sairo providers; they are separate recipients under your or their own control.
A workspace can add recipients of its own. If it configures an assistant action, Sairo sends that action’s address the information the assistant collected for it, such as an order reference a visitor typed, and records what came back. If it issues an API key, whoever holds that key can read the conversations, leads and saved answers its scope allows. Sairo shows every action call to the website’s own team and lets a key be revoked at any time, but these recipients are chosen by the workspace and governed by its arrangements with them, not by Sairo’s.
Providers that process information for Sairo
| Provider | Purpose | Information involved |
| --- | --- | --- |
| OpenRouter (United States) | Routes AI requests to the configured model providers: Google Gemini 2.5 Flash Lite for generated replies and Ask Sairo, OpenAI text-embedding-3-small for search embeddings, and OpenAI GPT-4o mini Transcribe for optional dictation | Relevant visitor and workspace messages, website excerpts, Ask Sairo requests and short dictation recordings |
| Resend (United States) | Transactional email sent from accounts.sairo.app: invitations, password recovery, notifications and weekly recaps | Recipient email address, message subject and body |
| Dodo Payments | Checkout, subscription billing, invoices and the billing portal for paid plans | Billing contact and payment details you enter with Dodo Payments; Sairo receives customer, subscription and invoice identifiers and status |
| Hostinger (United States) | Servers and database hosting for the service | All service records described on this page |
| Google (cloud storage) | Off-site copies of database backups | Backup archives, kept for up to 60 days |
| Twilio | SMS follow-up and WhatsApp messages, only for a workspace that enables them. Neither channel is available in the current hosted service, because no Twilio account is connected to it. | Phone number and message text for that workspace |
Section: https://sairo.app/privacy#providers
## How long records are kept.
Sairo keeps records for the periods below and deletes them automatically where a fixed period applies. Deleting a record from the live service does not immediately remove it from backups, which are kept for up to 60 days and then removed; Sairo does not restore deleted records from a backup except to recover from a failure, and it re-applies deletions after such a recovery.
Retention periods by record type
| Record | Kept for |
| --- | --- |
| Account profile, memberships and workspace settings | While the account and workspace exist. Deleted within 30 days of a verified deletion request, except invoices and payment records kept for as long as tax and accounting law requires. |
| Sign-in sessions | 30 days from sign-in, or until you sign out or revoke the session in Account security. |
| Password-reset links | Valid for 30 minutes; the record is removed within one day of expiry. |
| Workspace invitations | 14 days, or until accepted or revoked. |
| Visitor conversations, leads, appointment requests, saved answers, indexed website content and Ask Sairo history | While the workspace exists, unless the workspace operator deletes or archives the record. Removed within 30 days of a verified workspace closure or deletion request. |
| Connected AI application access | A connection expires 30 days after approval unless renewed. Access tokens are short-lived and stored as hashes; expired and revoked records are removed within one day, and unused application registrations after 30 days. |
| Live chat presence and rate-limit records | Presence connections are removed after one day of inactivity; rate-limit counters are stored as hashes and removed after one day. |
| Files attached to a conversation | With that conversation, and removed when it is. A file is available only to the website’s own team and the visitor who is in that conversation. |
| Reading activity on a website | A row is kept while someone is reading and removed within thirty minutes of them stopping. It holds the page path without its query string, against a hash of the widget token. |
| Assistant action calls | The address called, what was sent and what came back are kept with the workspace so its team can audit them. Removed within 30 days of a verified workspace closure or deletion request. |
| API keys | Stored as a hash with a visible prefix, so a key can be recognised in a list but never read back. Removed when revoked. |
| Help centre articles | While the workspace exists. A published article is public, and also indexed as knowledge the assistant answers from; unpublishing removes both. |
| Operational service checks | 30 days. |
| Visitor blocks | A browser block lasts until the website operator lifts it. A network address block expires after 30 days and is then deleted automatically. |
| Dictation recordings | Not stored by Sairo. The audio is sent to the transcription provider for that request only; the returned text follows the conversation rules above. |
| Email and SMS delivery records | With the workspace records above. The delivery provider keeps its own logs under its terms. |
| Database backups | Up to 60 days, then removed automatically. |
| Desktop app local data | Recent reads for up to 24 hours and unsent drafts for 7 days, encrypted on your device; removed on sign-out or through Settings. |
| Contact form enquiries | While the enquiry is open and for reasonable follow-up; removed on request. |
Section: https://sairo.app/privacy#retention
## Access, correction, deletion and consent.
You can change your name and password, see and revoke sign-in sessions and signed-in devices, disconnect AI applications and withdraw desktop AI permission from within the product. Workspace administrators can delete or archive saved answers, remove websites and their indexed content, and revoke members.
To request a copy of your data, a correction, or deletion of your account or workspace, use the contact form with the topic Privacy question, or write from the email address on the account. Sairo verifies the request against the account, confirms receipt within five business days, disables the account on confirmation and completes deletion within 30 days. Information already sent to an AI provider, an email recipient or an application you connected cannot be recalled from that recipient; Sairo will tell you which recipients were involved where it can.
If your conversation took place on another business’s website, that business controls the record. Contact it first so it can identify the relevant workspace and record; Sairo assists it and acts directly where the law requires. Depending on where you live, you may also have the right to object to or restrict processing, to receive your data in a portable format, and to complain to a data protection authority.
Consent for AI processing in the desktop app is requested before the first AI action and can be withdrawn in Settings. Website visitors choose whether to type a question, share contact details or use dictation, and a live specialist or the visitor can end a chat at any time. Withdrawing consent does not undo processing that has already completed.
- [Contact Sairo about privacy](https://sairo.app/contact?topic=privacy): Request access, a correction or deletion.
- [Review sessions and devices](https://sairo.app/account/security): Revoke a session or change your password.
Section: https://sairo.app/privacy#rights
## Cookies, sessions and security.
Sign-in uses the HTTP-only sairo_session cookie, which expires after 30 days. The interface may store preferences such as theme, and the embedded assistant keeps a site-specific conversation reference in session storage so a visitor can reconnect after refreshing the page. Sairo sets no advertising or cross-site analytics cookies; the cookie notice lists every cookie and storage key.
Traffic between browsers, apps and the service uses HTTPS. Passwords are stored as salted scrypt hashes, and session, reset and connection tokens are stored as hashes. Every workspace action is checked on the server against the acting user’s role and scope. Operational and security records support troubleshooting and abuse prevention. Sairo does not claim an independent security certification; the security page describes the controls that exist.
- [Read the cookie notice](https://sairo.app/cookies): Every cookie and browser storage key, with its purpose and lifetime.
- [Read the security controls](https://sairo.app/security): Access boundaries, token handling and provider credentials.
Section: https://sairo.app/privacy#storage
## Sairo for Mac and Windows.
The desktop app sends your sign-in details to Sairo over HTTPS and stores session credentials using the operating system’s protected storage. It sends an app-generated installation identifier, device name and app version so you can see and revoke signed-in devices. Passwords are not saved in the desktop app.
Recent workspace reads and unsent drafts are encrypted locally. Saved reads are available for up to 24 hours and drafts expire from use after 7 days; expired data is removed during subsequent cleanup. You can clear saved reads in Settings. Signing out removes protected account data and AI permission records, while retaining the random installation identifier and local appearance preferences.
Before an AI-related action, the desktop app asks you to allow or decline sending requests and relevant workspace records to the external AI providers described in the consent dialog. Settings provides a control to withdraw that permission for the current account and workspace on that device. Withdrawing permission does not cancel an already submitted operation, delete records already processed, or change another device, a connected application or the website’s existing AI service.
Desktop notifications and continued operation after closing the window are optional and off by default. Notifications use minimal text about waiting visitors or replies. The desktop app does not request access to your camera, microphone, contacts or location, includes no advertising or cross-app tracking, and sends no crash or usage analytics to third parties. Native exports are saved only to a location you choose.
Section: https://sairo.app/privacy#desktop
## Sairo for iPhone and Android.
The mobile apps sign you in to your existing account over HTTPS and keep the session token in the device’s secure storage. They send a device name and app version so you can see and revoke signed-in devices, and they request internet access only: no camera, microphone, contacts, photos or location access, and no advertising or analytics software.
Signing out removes the stored session from the device. Workspace records shown in the app are read from the service and follow the retention rules above; they are not copied into a separate mobile store.
Section: https://sairo.app/privacy#mobile
## Children, changes and contact.
Sairo is a business tool and is not directed to children under 16. Sairo does not knowingly collect personal information from children and deletes such information when it learns of it. A business installing the assistant on a website aimed at children must not do so without its own compliance review.
Material changes to this policy are announced on this page with a new date, and account holders are notified by email or in the product where a change affects how their information is used. Questions about this policy go to the contact form under Privacy question; Sairo answers privacy questions from the address shown on the account or from the business’s registered contact.
- [Ask a privacy question](https://sairo.app/contact?topic=privacy): Send a question to the team managing this service.
Section: https://sairo.app/privacy#children
Related pages
- [Sairo service terms](https://sairo.app/terms)
- [Sairo cookie notice](https://sairo.app/cookies)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Clear terms for using Sairo.
Canonical page: https://sairo.app/terms
Updated: 2026-09-07
These terms apply when you request, buy, access or use the Sairo service, including the sairo.app website, the embedded assistant, Sairo for Mac and Windows, and the Sairo mobile apps. A signed order or separate agreement can add to or replace the relevant parts of these terms.
## Agreement, authority and eligibility.
By creating or accepting access to a workspace, using the service, installing an app or completing an order, you agree to these terms and to the privacy policy. If you use Sairo for an organisation, you confirm that you have authority to act for it. Sairo is offered to businesses and the people who work with them; you must be at least 18 years old to hold an account.
An order, checkout or written agreement identifies the customer, selected plan, price, billing arrangement and any additional commitments. If it conflicts with these general terms, the more specific written agreement controls for that customer.
Section: https://sairo.app/terms#agreement
## Accounts and workspace access.
Keep account credentials confidential and provide accurate account and billing information. Workspace owners control invitations, roles, project access, connected websites and the people authorised to review conversations or change knowledge.
Tell Sairo promptly if you believe an account or invitation link has been compromised. Sairo may revoke sessions, disable an account or restrict access when reasonably needed to protect the service, a workspace or another person.
Section: https://sairo.app/terms#accounts
## Your websites, content and conversations.
You keep ownership of the websites, source material, saved answers, branding and other content you provide. You give Sairo permission to fetch, process, store and display that material only as needed to provide, secure, support and improve the service for your workspace. Sairo does not use your content to train AI models and does not permit its providers to do so.
You must have permission to connect a website and to process the visitor, assistant and live specialist messages or contact details collected through it. You are responsible for choosing authorised specialists and giving visitors the notices your use requires. Website ownership verification, robots.txt, source exclusions and allowed origins are controls; they do not replace those responsibilities.
Section: https://sairo.app/terms#content
## Acceptable use.
Do not use Sairo to break the law, infringe rights, deceive people, distribute malware, probe systems without permission, evade usage controls, send spam, harass anyone, or make high-impact decisions about a person without appropriate authority and human review.
Do not upload secrets or sensitive information that the agreed service is not intended to handle. Do not present generated output as professional medical, legal, financial, employment, credit, housing or emergency advice. A specialist can end an abusive visitor chat, block that visitor from the website, and report the conversation to Sairo; anyone can also report abuse through the contact form. Sairo may suspend activity that creates a security, legal or service-integrity risk.
Section: https://sairo.app/terms#acceptable-use
## AI-assisted answers require review.
Sairo retrieves configured website material and uses an AI provider to prepare responses. Guardrails, saved answers, source controls and refusal behaviour reduce mistakes, but generated output can still be incomplete, delayed or incorrect.
You are responsible for reviewing the assistant before launch, maintaining the connected content, monitoring important conversations and deciding when a person must take over. Sairo does not guarantee that a generated answer is accurate, suitable for a regulated decision or a substitute for professional judgement.
Ask Sairo and authorised external applications can also prepare or apply supported workspace changes. Check the proposed information, the affected website and the access you grant. An external application has its own confirmation behaviour and data practices; read-only access is available when it should only retrieve information.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/terms#ai
## Plans, billing and cancellation.
The Free plan has no monthly charge or payment-card requirement and keeps a small Powered by Sairo mark on the installed widget. Published paid prices are monthly amounts in US dollars before applicable taxes unless an order says otherwise. Plan allowances cover websites, indexed pages, page refreshes and conversations as described on the pricing page. Sairo does not automatically charge an unlisted overage; additional capacity requires a plan or allowance change.
Payments are processed by Dodo Payments, which collects payment details, issues invoices and provides the billing portal; Sairo never stores card numbers. Subscriptions renew monthly until cancelled. A cancellation or downgrade takes effect at the end of the current billing period, and fees already charged for a period are not refunded unless the law, the checkout terms or a written order provides otherwise. Manual arrangements, custom plans, credits, taxes and payment dates follow the checkout or written order agreed with the customer. Access may be restricted for an unpaid or expired arrangement after reasonable notice where practicable.
Section: https://sairo.app/terms#fees
## Desktop and mobile apps.
Sairo for Mac, Windows, iPhone and Android are free companion apps for existing Sairo accounts. They contain no in-app purchases, do not create accounts or sell plans, and receive updates only through the store or download channel that supplied them. Features depend on your workspace, plan and assigned permissions.
An app obtained from the Apple App Store is licensed to you under Apple’s standard Licensed Application End User License Agreement, and an app from Google Play under Google Play’s terms. Those licences cover the app software; these service terms and the privacy policy govern the Sairo service you sign in to. Apple and Google are not parties to these terms and are not responsible for the service, its content or its support.
Section: https://sairo.app/terms#apps
## Personal data and privacy.
Sairo processes personal data as described in the privacy policy, which names its providers, retention periods and the way to request access, correction or deletion. For visitor conversations and other workspace records, the customer decides why and how they are processed and Sairo acts on the customer’s instructions as its service provider; the customer is responsible for its own privacy notices and lawful basis. Sairo provides a data processing agreement to a customer that needs one.
- [Read the privacy policy](https://sairo.app/privacy): Providers, retention periods and your rights.
Section: https://sairo.app/terms#privacy
## Service providers and availability.
Sairo relies on hosting, database, AI, payment, email and optional SMS providers. Their availability can affect the service. Planned maintenance, security work, provider incidents or changes to connected websites may interrupt an answer, live chat message, crawl, email or payment workflow.
Unless a separate written agreement provides a service level, the service is provided on an available basis. Sairo may change features to improve security, accessibility, reliability or product behaviour and will avoid materially reducing paid functionality without reasonable notice where practicable.
Section: https://sairo.app/terms#providers
## Warranties and liability.
The service is provided as available. Except as stated in a written order or required by law, Sairo gives no warranty of uninterrupted operation, of the accuracy of generated output, or of fitness for a particular purpose. You are responsible for backing up content you need and for the decisions you make using the service.
To the extent permitted by law, Sairo is not liable for indirect, consequential or special losses, lost profits, lost business or lost data, and Sairo’s total liability for all claims arising in any twelve-month period is limited to the fees you paid for the service in that period, or USD 100 for a workspace that paid nothing. Nothing in these terms limits liability that cannot be limited by law, including liability for fraud, or excludes rights you have as a consumer that cannot be waived.
Section: https://sairo.app/terms#liability
## Ending access and deleting data.
You may stop using the service at any time, cancel a paid subscription in the Dodo Payments billing portal, and request deletion of your account or workspace through the contact form. Deletion follows the privacy policy: the account is disabled when the request is confirmed and personal data is removed within 30 days, except records kept for legal, tax or security reasons. Sairo may suspend or end access for material breach, non-payment, unlawful use, security risk or conduct that harms the service or others, with notice where practicable.
Ending access does not remove payment obligations already incurred. Contact Sairo before cancellation if you need an export or have a contractual retention requirement; conversation transcripts and CSV exports are available in the product while the workspace exists.
- [Ask a question about these terms](https://sairo.app/contact?topic=legal): Send the agreement, billing or account detail you need clarified.
Section: https://sairo.app/terms#ending
## Changes to these terms.
Sairo may update these terms; the date shown on this page identifies the current version. Material changes to paid features, prices or your obligations are announced at least 30 days in advance by email or in the product where practicable, and continued use after the effective date is acceptance of the updated terms. If you do not agree, stop using the service and cancel any subscription before the change takes effect.
Section: https://sairo.app/terms#changes
Related pages
- [Plans and pricing](https://sairo.app/pricing)
- [Sairo privacy policy](https://sairo.app/privacy)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Small pieces of storage, used for clear reasons.
Canonical page: https://sairo.app/cookies
Updated: 2026-09-06
Sairo currently uses essential account cookies and limited local browser storage. It does not set advertising or cross-site analytics cookies on the public website.
## Essential account cookies.
The “sairo_session” cookie keeps an authenticated account signed in. It is HTTP-only, uses SameSite=Lax, is secure in production, and expires after 30 days. The server stores only a hash of the session token and lets a user revoke active sessions.
The “sairo_workspace” cookie remembers which authorised workspace to open when an account belongs to more than one. It has the same 30-day security settings and contains a workspace identifier, not a password or payment detail.
Connecting an AI application also uses the temporary “sairo_mcp_flow” cookie. It binds the OAuth approval to the browser that started the connection, is HTTP-only with SameSite=Lax, is secure in production, expires after ten minutes and is cleared after a completed approval or denial. The cookie does not give the external application your sign-in session.
Section: https://sairo.app/cookies#essential
## Local preferences.
The signed-in interface can store the “sairo-workspace-theme” preference in local storage so it can remember light, dark, or system appearance. Removing that value returns the interface to its default.
The public demo can set a first-party “sairo_demo” cookie for 24 hours so “Keep this assistant” can carry the demo into sign-up. It stores only the demo slug, uses SameSite=Lax, and is not required for browsing. The embedded widget remembers a site-specific conversation reference in session storage. This lets AI or live chat reconnect after a page refresh within the same browser session. The widget does not use a third-party advertising identifier or place a cross-site tracking cookie.
Section: https://sairo.app/cookies#preferences
## Your browser controls.
You can remove cookies and local storage through browser settings. Removing the session cookie signs the account out; removing the workspace choice or theme preference resets that convenience. Blocking essential storage can prevent account and workspace features from working correctly.
Because the current public website does not use optional advertising or analytics cookies, it does not display an optional-cookie preference banner. If that changes, Sairo must update this notice and add the consent controls required for the affected visitors before enabling those technologies.
Section: https://sairo.app/cookies#choices
## Cookies on a customer’s website.
A business that installs the Sairo widget remains responsible for the cookie and privacy notice on its own website. It should explain how visitor questions and optional contact details are used and identify any other technology that website loads.
Other services on the host website may use their own cookies. This Sairo notice does not describe the customer’s analytics, consent manager, commerce platform, or other third-party tools.
- [Read the data and privacy practices](https://sairo.app/privacy): See how accounts, website content, conversations, and service providers are handled.
Section: https://sairo.app/cookies#embedded
Related pages
- [Sairo privacy policy](https://sairo.app/privacy)
- [Sairo service terms](https://sairo.app/terms)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Give the assistant a source your team can maintain.
Canonical page: https://sairo.app/features/website-knowledge
Updated: 2026-09-08
A useful website knowledge base connects answers to approved information and gives someone responsibility for keeping that information current.
## Can Sairo answer questions from my website?
Yes. Sairo indexes permitted website pages and uses the selected knowledge alongside confirmed business facts and approved saved answers. Verify website ownership for the full crawl, exclude unsuitable pages and test important answers.
## Three kinds of knowledge, with different jobs.
Sairo uses indexed pages for the breadth of your website, site facts for recurring details such as opening hours, and saved answers for questions that need approved wording. These sources belong to a particular site; adding a second client does not create one shared pool of business information.
An exact saved question is checked first, after trimming whitespace and ignoring letter case. It can return the saved answer without a model request. Similar questions can also match a saved answer through semantic retrieval. Other questions use relevant facts and passages from the indexed website.
Choose the right place for a change
| Information | Where to maintain it |
| --- | --- |
| A published service explanation | Update the website, then refresh and review its indexed page. |
| A phone number or opening hours | Check the original page and confirm the corresponding site detail. |
| An answer that needs exact wording | Save a question and approved answer, then test relevant variations. |
| An obsolete promotion | Remove or update the original and exclude its indexed source if needed. |
Section: https://sairo.app/features/website-knowledge#sources
## Reading the site is a controlled process.
A production website must pass ownership verification before a crawl can run. The public demo has a separate, limited sampling path. Crawling follows robots.txt, checks fetch destinations, and works within the workspace allowances.
Indexed text is split into smaller passages. Sairo combines keyword matches with semantic similarity to find material relevant to a question. This retrieval step supplies context for the answer; it does not retrain the underlying model on your entire website.
Section: https://sairo.app/features/website-knowledge#indexing
## Review the evidence behind important answers.
Start with the pages visitors depend on: services, eligibility, location, contact information, pricing conditions, and policies. An attractive page can still be a poor source if its critical information is inside an image or appears only after a client-side interaction.
Test a question against its intended page. If the reply is wrong, first inspect whether the correct passage was indexed and whether another page conflicts with it. A new prompt or model cannot reliably repair missing or contradictory source material.
You can review this knowledge through Ask Sairo too. Ask about the source behind a reply, provide a confirmed correction and check the affected website before saving.
### Example: changing weekend hours
Update the public contact page, refresh the website content, and check any confirmed hours or saved answers that still contain the old schedule. Ask both “When are you open?” and “Are you open on Sunday?” before considering the change complete.
Video walkthrough 02: Teach Sairo a better answer (1:10, English narration with captions). Save confirmed information and check the next reply. Before you start: Use an account with permission to edit website knowledge.
Watch: https://sairo.app/media/walkthroughs/02-teach-sairo-a-better-answer.mp4
Captions: https://sairo.app/media/walkthroughs/captions/02-teach-sairo-a-better-answer.vtt
Transcript:
- 00:00 A better answer starts with you.: A visitor asks about Sunday inspections. Here's how to give Sairo the confirmed answer your team wants to use.
- 00:07 Open the library: Open Knowledge library, then choose Add saved answer. Select the website that this information belongs to.
- 00:15 Be specific: Enter the exact question and a clear, verified answer. Here, the business confirms that Sunday inspections are unavailable and gives the visitor a useful next step.
- 00:26 Save the answer: Select Save new answer. Wait for confirmation. Saved answers take priority when a visitor asks a matching question.
- 00:35 Check coverage: In Check your knowledge, enter the same visitor question and select Check source coverage. This checks saved knowledge; it does not generate a live reply.
- 00:45 Read the result: Look for A saved answer is ready. Read the returned wording and confirm that it answers the question completely.
- 00:53 Try the next reply: Now ask the question in the website assistant. The visitor receives the saved answer, including the next step for arranging an inspection.
- 01:02 Teach once. Help the next visitor.: Repeat this whenever a policy changes or a visitor finds a gap. Keep the wording specific and confirmed.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/features/website-knowledge#review
## Not every answer lives on a page.
A price list, a service menu or a policy is often a document rather than a web page. Upload a PDF, Word file, text, Markdown or CSV, up to 12 MB, and it is chunked, embedded and retrieved exactly like a crawled page. It appears in the library with the same source controls, and counts against your plan’s indexed-page allowance.
An uploaded document has no public web address, so a citation refers to it by name rather than linking a visitor to a page that does not exist. A scanned PDF with no text layer cannot be read; export a text-based version first.
A published help centre article is knowledge too. Writing one does both jobs at once: visitors can read the page, and the assistant can answer from it without you maintaining the same wording twice.
- [See which questions are still unanswered](https://sairo.app/features/knowledge-gaps): Then upload or write exactly what is missing.
Section: https://sairo.app/features/website-knowledge#uploads
## Assign an owner to the knowledge.
Agree who can approve service facts and who can change assistant configuration. A client who knows the business may contribute content within an assigned project, while the agency keeps broader controls.
Review unanswered questions regularly and treat recurring gaps as editorial work. Keep the public website useful in its own right: visitors should still be able to read the source without opening a chat.
- [Prepare your source content](https://sairo.app/guides/prepare-website-for-ai): A practical review of readability, consistency, and coverage.
Section: https://sairo.app/features/website-knowledge#maintenance
## Common questions
### Does adding a website train a new AI model?
Sairo indexes and retrieves the website’s content. It supplies relevant material to the configured model during a response; this workflow is different from fine-tuning model weights.
### Does excluding a page delete a confirmed fact?
Source exclusion affects retrieved page content. Explicitly confirmed facts and saved answers are separate knowledge records, so review them when a business detail changes.
Related pages
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations)
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
---
# Keep the enquiry and the reason behind it together.
Canonical page: https://sairo.app/features/lead-generation
Updated: 2026-09-06
An email address is more useful when your team can see what the person asked, what they were told, and what should happen next.
## Collect a contact when there is a useful next step.
A visitor may need a quote, an explanation that is missing from the website, or attention from someone on the team. Sairo can collect contact information during that conversation and save a lead associated with the site and conversation.
Choose the assist or capture goal in the site settings when you want the assistant to collect leads. The answer-only goal does not expose the lead-capture tool. Test the selected goal with an enquiry before publishing the workflow.
Make the invitation specific: explain why sharing an email address or phone number will help the team follow up. Avoid making a visitor submit information merely to read an answer that is already available publicly.
### Example conversation goal
A visitor asks whether a service is available for an unusual project. The assistant can explain the published scope, acknowledge the detail it cannot confirm, and ask for contact information so the team can review the request.
Section: https://sairo.app/features/lead-generation#capture
## Review context before deciding the lead’s stage.
Open the lead together with its conversation. Check whether the request fits the business, whether the contact details are usable, and whether the assistant set an expectation that needs clarification.
Lead records support stages, an assigned person, notes, and a follow-up date. These are coordination tools for your team. A captured lead does not establish that someone is qualified, has consented to marketing, or has purchased a service.
Ask Sairo can find a lead and prepare permitted changes to its stage, notes, follow-up date or assignee. Review the proposed record before applying it. The assistant does not send a message to that lead on your behalf.
Appointment requests show their requested time and status on the lead. Check your calendar and agree the time with the visitor, then mark the request confirmed or cancelled in Sairo. Opening hours, timezone and appointment length are configured per website; this does not synchronise an external calendar.
1. Read the request
Identify the visitor’s question and the information still needed to respond.
2. Assign responsibility
Give an eligible teammate ownership and choose an appropriate stage.
3. Set a next action
Record when a reply is due and the context needed by the person handling it.
4. Update after follow-up
Record the actual result after the team has contacted the visitor.
Video walkthrough 04: Turn an enquiry into a follow-up (1:18, English narration with captions). Give a captured lead an owner and a clear next action. Before you start: A visitor has shared contact details and a lead has been captured.
Watch: https://sairo.app/media/walkthroughs/04-turn-an-enquiry-into-a-follow-up.mp4
Captions: https://sairo.app/media/walkthroughs/captions/04-turn-an-enquiry-into-a-follow-up.vtt
Transcript:
- 00:00 An enquiry. A clear next step.: A visitor has shared contact details. Here's how to turn that enquiry into a follow-up your team can act on.
- 00:08 Find the enquiry: Open Conversation inbox. Search for the visitor or the subject of their enquiry, then apply the filters. Here, we're finding Jamie Parker.
- 00:18 Read before acting: Open the matching conversation. Read what Jamie asked for and the contact details they shared before deciding what should happen next.
- 00:27 Open the lead: Select Jamie under Captured leads. The lead keeps contact details, ownership, progress, and follow-up notes together.
- 00:37 Give it an owner: Choose the teammate responsible for the next action. After contacting the visitor, update the lead stage to Contacted so the team knows where it stands.
- 00:47 Set the next action: Set the next follow-up date and add a short internal note. In this example, Dave needs to confirm an inspection time with Jamie. Select Save lead.
- 00:58 Find what's due: Return to Leads and follow-ups. Select Follow-up due and apply the filters. Jamie now appears with an owner, stage, and follow-up date.
- 01:08 Every lead has a next action.: Check this list each day. Follow-up dates organise your work list; they do not send automatic reminders or messages to the visitor.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
Section: https://sairo.app/features/lead-generation#review
## Keep client information in the correct workspace.
Agency memberships can be restricted to a client project. Access to leads and related conversations follows that scope, and internal notes remain distinct from client-facing information.
Test a rollout using contact details your team controls. Confirm that the lead appears under the intended site and that the person responsible can access it. Check the same path again when a site changes project or its team changes.
Section: https://sairo.app/features/lead-generation#boundaries
## Measure the complete journey.
Sairo reports conversations that produced lead records, which helps you see whether visitors are choosing to share details. Review lead quality separately: an automated capture count is not a sales result.
Compare periods using the same site and date range. Look at a sample of both captured and uncaptured conversations before changing the greeting or asking for more information. A lower capture rate may be appropriate when more visitors find the answer immediately.
- [Read the measurement guide](https://sairo.app/guides/measure-chatbot-performance): Separate recorded outcomes from business results.
Section: https://sairo.app/features/lead-generation#measure
## Common questions
### Does Sairo send leads to a CRM automatically?
The current built-in workflow stores and manages leads in the Sairo workspace. This page does not describe a native CRM synchronisation. Confirm any external workflow separately before relying on it.
### Does a captured lead confirm an appointment?
No. Your team must confirm availability and any booking through its actual scheduling process.
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [Website chatbot for service businesses](https://sairo.app/solutions/service-businesses)
- [Plans and pricing](https://sairo.app/pricing)
---
# Move from an AI answer to a live specialist in one conversation.
Canonical page: https://sairo.app/features/live-chat
Updated: 2026-09-08
Sairo combines a website assistant with per-site live chat, so a visitor can ask for a person without repeating the question or leaving the widget.
## One conversation, two ways to help.
A site administrator can enable live chat and select the workspace members who will cover that website. The visitor can choose Talk to a person, and an assistant escalation can open the same live queue automatically.
Earlier assistant messages remain in the transcript. When a specialist joins, the widget names that person and new replies are marked as live chat in the workspace, so the change of speaker is clear.
Video walkthrough 03: Take over a live conversation (1:17, English narration with captions). Move from assistant to specialist in one conversation. Before you start: A website owner enables live chat and selects an eligible teammate.
Watch: https://sairo.app/media/walkthroughs/03-take-over-a-live-conversation.mp4
Captions: https://sairo.app/media/walkthroughs/captions/03-take-over-a-live-conversation.vtt
Transcript:
- 00:00 When a visitor needs a person.: Some questions need your team. Sairo lets a specialist join the visitor's existing conversation.
- 00:07 Choose a specialist: Open the website's Settings and installation. Enable live chat, choose an eligible teammate, and save the live chat settings.
- 00:17 Set Available: The specialist selects Go available in the workspace header. Check that the status says Available. Visitors can now see that a person is online.
- 00:27 The visitor asks: The visitor selects Talk to a person and leaves their question. Their request appears in your live queue.
- 00:34 Join the request: Open Live chat. Read the earlier messages for context, then select Join live chat. The conversation is assigned to you.
- 00:44 Reply as yourself: Write a helpful reply in Message to visitor and select Send. The visitor sees your name and your response in the same chat.
- 00:52 One conversation: There is no need for the visitor to repeat the earlier question. Your team reply stays alongside the assistant's messages.
- 01:00 Finish clearly: When you have finished helping, select End live chat. Set yourself Away when you are no longer available to take requests.
- 01:10 A human reply. All the context.: If nobody is available, Sairo lets the visitor leave a message for the team without promising an immediate reply.
Section: https://sairo.app/features/live-chat#meaning
## Availability says what is actually happening.
A specialist appears available after they set Available in the workspace, including from other pages and with browser notifications. When someone is available, the visitor sees that a specialist is available. When nobody is available, the widget offers to leave a message for the team instead of promising an immediate reply.
A queued request remains attached to its site. Specialists assigned to that site see waiting visitors first, can claim a chat, exchange messages, and end the live session when the conversation is complete.
What the visitor sees
| Team state | Visitor experience |
| --- | --- |
| Specialist online | Talk to a person, followed by a truthful waiting state until someone joins. |
| No specialist online | Leave a message for the team, with no immediate-response promise. |
| Specialist joined | The specialist’s name and live replies in the existing conversation. |
| Live session ended | A clear end state and the option to continue with the assistant or ask again. |
Section: https://sairo.app/features/live-chat#availability
## Messages are near real time and kept in the transcript.
Live chat uses a WebSocket connection between the visitor widget and the specialist desk, with database-backed HTTP updates as a fallback. A visitor normally sees a reply immediately on the open socket, or on the next refresh of about 2.5 seconds if the socket is unavailable.
Every visitor and specialist message is stored with the conversation. This keeps the live exchange available in the shared inbox, preserves the speaker’s display name, and lets the widget reconnect to the same session after a page refresh within the browser session.
The widget restores visitor, assistant and specialist messages after navigation within the same browser session. Replies are checked before display, and repeated message requests reuse a stored receipt so an interrupted connection does not repeat a captured lead or appointment request.
Section: https://sairo.app/features/live-chat#delivery
## The first specialist to join owns the chat.
Claiming is atomic, so two teammates cannot both become the active specialist. Other assigned specialists can still see that the visitor is being helped. If the owner goes offline, a teammate can take over after the presence window expires.
Site and project permissions still apply. A specialist must be an active workspace member who can access that site, and client viewers cannot operate or configure live chat.
Section: https://sairo.app/features/live-chat#ownership
## Help for the person on the desk.
Specialists keep saved replies for the wording they send most often. A reply used five times is offered for promotion into a saved answer, so wording your team already trusts becomes something the assistant can use on its own.
Joining a conversation someone else started, a specialist can ask for a summary of it, and for a first draft of the reply. A draft is written only from your website’s own material and is withheld when that material does not support it, because an unsupported draft sitting in a composer is more dangerous than no draft: sending it is one keystroke away. Nothing is sent for you.
Section: https://sairo.app/features/live-chat#desk
## A photo is often faster than a paragraph.
A visitor can attach a photo or a PDF, up to 5 MB and ten files per conversation, and a specialist can send one back. For a trade or service business this is usually the first thing a visitor tries.
Sairo identifies a file by reading its own bytes rather than trusting its name, refuses SVG because it can carry script, and always serves attachments as downloads rather than rendering them in a page.
Section: https://sairo.app/features/live-chat#files
## See who is reading, without following anyone.
On a site with live chat enabled, the desk shows which pages are being read right now, so a specialist can offer help at the moment it is useful.
It records the page path without its query string, against a hash of the widget token that browser already holds, and the row is removed within thirty minutes of the visit ending. There is no network address, no location and no identity in it. Sites without live chat enabled report nothing at all.
Section: https://sairo.app/features/live-chat#presence
## Offer help before you are asked.
Set up to five rules that show a short message on chosen pages after a delay you choose. The most specific page rule wins, so a message for the enterprise pricing page beats the general pricing one.
One prompt per visit, always dismissible, and never shown over a conversation the visitor already has open. It is an offer of help rather than a campaign tool, and the wording is capped short on purpose.
Section: https://sairo.app/features/live-chat#prompts
## Test the complete handoff before launch.
Enable live chat for a test site, assign two teammates, and set one of them Available. From the installed widget, request a person, send a message while waiting, claim the chat, reply, and end the session.
Repeat the check after setting every specialist Away. Confirm that the widget describes the offline queue honestly and that the stored transcript distinguishes assistant and specialist replies.
- [Set up live chat step by step](https://sairo.app/guides/set-up-live-chat): Configure a site, assign specialists, and test the complete visitor journey.
- [Use the launch checklist](https://sairo.app/guides/chatbot-launch-checklist): Include ownership, escalation, contact capture, and accessibility.
Section: https://sairo.app/features/live-chat#test
## Common questions
### Can a specialist reply inside the visitor’s widget?
Yes. When live chat is enabled for the site, an assigned specialist can claim the request and reply from the Live chat workspace. The visitor sees those replies in the same widget conversation.
### Does Sairo promise an immediate response?
No. Availability is based on whether an assigned specialist has set themselves Available. The widget distinguishes an available specialist from an offline message queue.
### How quickly do live chat messages appear?
The widget uses a WebSocket connection for live replies, and falls back to checking for new activity about every 2.5 seconds if that connection is unavailable.
### Is live chat enabled for every website automatically?
No. An administrator enables it separately for each site and must assign at least one eligible workspace specialist before saving the setting.
Related pages
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat)
- [Shared AI and live chat inbox for website teams](https://sairo.app/features/conversation-inbox)
- [AI chatbot vs live chat: compare and combine](https://sairo.app/compare/ai-chatbot-vs-live-chat)
---
# A shared place to understand what happened.
Canonical page: https://sairo.app/features/conversation-inbox
Updated: 2026-09-08
Bring visitor questions, assistant responses, and team follow-up into one review process across the websites you are allowed to manage.
## Start with the conversation that needs attention.
Use the inbox to search conversation content and narrow the view by the available site and workflow filters. Read the exchange before assigning work: the last message alone can leave out an important condition or an earlier answer.
A saved transcript keeps visitor messages, assistant answers, and named specialist replies together. It helps the team understand what happened, while still requiring review of any generated statement that matters.
Section: https://sairo.app/features/conversation-inbox#find
## Give the next action an owner.
Conversation assignments and status changes make follow-up visible to the rest of the team. Assign someone who can access that site and record the work that still needs to happen.
Sairo checks permissions on the server and detects stale conversation updates so one teammate does not silently overwrite a more recent change. If an update conflicts, reload the current record and review the new information before saving again.
### Example review note
“Visitor asked about a requirement missing from the services page. Confirm the answer with the service owner, then follow up using the captured email. Add the approved explanation to website knowledge.”
Video walkthrough 04: Turn an enquiry into a follow-up (1:18, English narration with captions). Give a captured lead an owner and a clear next action. Before you start: A visitor has shared contact details and a lead has been captured.
Watch: https://sairo.app/media/walkthroughs/04-turn-an-enquiry-into-a-follow-up.mp4
Captions: https://sairo.app/media/walkthroughs/captions/04-turn-an-enquiry-into-a-follow-up.vtt
Transcript:
- 00:00 An enquiry. A clear next step.: A visitor has shared contact details. Here's how to turn that enquiry into a follow-up your team can act on.
- 00:08 Find the enquiry: Open Conversation inbox. Search for the visitor or the subject of their enquiry, then apply the filters. Here, we're finding Jamie Parker.
- 00:18 Read before acting: Open the matching conversation. Read what Jamie asked for and the contact details they shared before deciding what should happen next.
- 00:27 Open the lead: Select Jamie under Captured leads. The lead keeps contact details, ownership, progress, and follow-up notes together.
- 00:37 Give it an owner: Choose the teammate responsible for the next action. After contacting the visitor, update the lead stage to Contacted so the team knows where it stands.
- 00:47 Set the next action: Set the next follow-up date and add a short internal note. In this example, Dave needs to confirm an inspection time with Jamie. Select Save lead.
- 00:58 Find what's due: Return to Leads and follow-ups. Select Follow-up due and apply the filters. Jamie now appears with an owner, stage, and follow-up date.
- 01:08 Every lead has a next action.: Check this list each day. Follow-up dates organise your work list; they do not send automatic reminders or messages to the visitor.
Section: https://sairo.app/features/conversation-inbox#ownership
## Keep internal coordination separate.
Internal notes help staff collaborate around a conversation. These notes are separate from the messages shown to the visitor, and client viewers do not receive the internal notes, including when a client has permission to contribute knowledge.
Include only the operational context needed by your team. A general conversation note is not the right place for passwords, provider keys, or unrelated personal records. Good access boundaries work best with deliberate information handling.
Section: https://sairo.app/features/conversation-inbox#notes
## Use one workflow across client projects.
Agency teams can work across the sites within their access, while a project-scoped member sees only the assigned client’s sites. The same boundaries apply when searching and opening a conversation.
Review memberships when someone changes responsibility. A clear project structure makes it easier to tell which conversations a person should be able to read, rather than relying on naming conventions alone.
Section: https://sairo.app/features/conversation-inbox#agency
## Make review a small, repeatable habit.
Begin a review session with unresolved work, requests for human attention, and recent knowledge gaps. Finish by checking whether contact follow-ups have a responsible person and whether repeated questions need a source update.
The inbox is useful alongside analytics: a metric can show a change, while the actual conversations explain it. Read a representative sample before assuming that a rising or falling count means the experience has improved.
Use “Review with Ask Sairo” on a conversation to investigate an answer with its context. You can prepare a saved answer, an internal note or a conversation status update without moving between those separate screens.
- [Set up an agency review process](https://sairo.app/guides/manage-client-chatbots): Client access, responsibilities, and a repeatable maintenance routine.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
Section: https://sairo.app/features/conversation-inbox#routine
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [Website chatbot analytics and outcomes](https://sairo.app/features/chatbot-analytics)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# See the pattern. Read the conversations behind it.
Canonical page: https://sairo.app/features/chatbot-analytics
Updated: 2026-09-08
Use chatbot analytics to decide what to review, where knowledge is missing, and which follow-up processes need attention.
## Know what the dashboard counts.
Sairo reports conversations within the chosen date range and site scope. The analytics view supports 7, 30, and 90 days and compares the selected period with the preceding period of the same length.
Daily reporting uses UTC dates. Conversations without a recorded outcome remain visible as pending, so an in-progress conversation is not silently treated as an answered one.
Read each signal in context
| Signal | What it tells you |
| --- | --- |
| Conversations | The number of conversation records that started within the selected period. |
| Leads | Conversations associated with at least one captured lead record. |
| Answered or unanswered | The recorded conversation outcome; review the transcript for quality. |
| Resolved | The team’s inbox status, which is separate from the AI outcome. |
| Daily trends | Conversation and lead counts grouped by UTC day. |
Section: https://sairo.app/features/chatbot-analytics#coverage
## Compare like with like.
Start by choosing the same site and period length for a comparison. A newly installed site, a campaign, or an interrupted crawl can change the visitor mix and the number of questions the assistant can answer.
Agency members only receive reporting for sites within their project scope. A portfolio-wide total and a single client’s total describe different populations, even if their chart shapes look similar.
Section: https://sairo.app/features/chatbot-analytics#scope
## Use outcomes as a starting point for review.
An answered outcome means the system recorded an answer, not that an independent reviewer confirmed resolution. Likewise, a captured lead is not an attributed sale and a resolved inbox status is not a customer-satisfaction score.
Select a sample of conversations from an unexpected trend. Check the supporting source, whether the reply addressed the whole question, and whether a follow-up was completed. This gives the count an operational meaning.
### Example: unanswered questions rise
If a new campaign attracts questions about a service not yet described on the site, the increase can reveal a content gap. Read the questions, add approved information, refresh the source, and compare a similar later period.
Section: https://sairo.app/features/chatbot-analytics#interpret
## Ask the visitor, and report it honestly.
After an exchange the assistant can ask whether the answer helped. An unhelpful rating opens one optional comment box. The rating is stored with the question that prompted it, so a low score points at a specific thing to fix rather than a mood.
The summary reports how many people rated and how they split. It never presents a satisfaction rate over everyone who stayed silent, because most visitors do not rate and inventing a denominator would turn a handful of responses into a statistic your team cannot defend.
Section: https://sairo.app/features/chatbot-analytics#rating
## Turn the finding into a specific change.
Choose one intervention: improve a page, clarify a saved answer, adjust a greeting, or assign ownership of handoffs. Record the change date so a later comparison has context.
Keep a separate business measurement for qualified leads, completed follow-ups, or actual sales. Sairo’s current analytics cover the assistant’s recorded activity; they do not establish a causal return on investment.
Use the pattern you find as the starting point for Ask Sairo: locate representative conversations, read their source information and prepare a correction. For reporting in Claude, a permitted MCP connection can bring workspace records into that conversation.
Email destinations can opt into a weekly recap in Settings. The worker prepares one recap for the completed Monday-to-Sunday UTC week. Delivery activity shows queued, sent and failed notifications, with a retry action for failed deliveries.
Video walkthrough 05: Review what needs attention (1:19, English narration with captions). Use visitor activity to choose the next improvement. Before you start: Conversations have started arriving in your workspace.
Watch: https://sairo.app/media/walkthroughs/05-review-what-needs-attention.mp4
Captions: https://sairo.app/media/walkthroughs/captions/05-review-what-needs-attention.vtt
Transcript:
- 00:00 See the pattern. Improve the answer.: Make a short review part of your week. Use Sairo's analytics to choose one useful improvement.
- 00:07 Set the scope: Open Analytics. Choose the website and reporting period, then apply the filters. The report uses UTC calendar days.
- 00:15 Read the signals: Compare conversations, leads and bookings, and capture rate. Look at unanswered outcomes for signs that visitors need information your assistant could not provide.
- 00:26 Keep the context: Use the activity chart and outcome breakdown to understand the pattern. These outcomes describe conversations; they are different from the list of knowledge gaps still needing attention.
- 00:38 Export if useful: Select Export daily report when you need a file for a team review. The export follows the report's selected filters.
- 00:47 Find open gaps: Open Conversation inbox, choose Unanswered, and apply the filters. This view helps you find questions that still need a verified answer.
- 00:58 Choose one fix: Open a conversation and read the actual question. Here, a visitor asked about skylight repairs. Confirm the answer with your team, then save it in Knowledge library.
- 01:10 Review. Learn. Help the next visitor.: Choose one gap, save a confirmed answer, and check it. That simple weekly habit keeps your assistant useful as your business changes.
- [Build a measurement routine](https://sairo.app/guides/measure-chatbot-performance): Sampling, definitions, and a worked review example.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/features/chatbot-analytics#actions
Related pages
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
- [Website chatbot lead capture and follow-up](https://sairo.app/features/lead-generation)
- [Website chatbot cost and usage planning](https://sairo.app/guides/website-chatbot-cost)
---
# Give each client an assistant that belongs on their website.
Canonical page: https://sairo.app/features/agency-branding
Updated: 2026-09-08
Set an agency identity once, then tailor the client-facing details where a project or website needs its own presentation.
## Branding follows the way your work is organised.
Sairo resolves branding from the platform default through the organisation, project, and site. This lets an agency maintain shared defaults while a client or individual website provides more specific values.
Available branding fields include a display name, accent, logo address, support email, and an option controlling Sairo attribution on paid plans. Free workspaces keep a small Powered by Sairo mark. The effective presentation depends on the field and the surface that uses it, so check both the customer workspace and the installed widget.
Choose the level of a branding change
| Level | Use it for |
| --- | --- |
| Organisation | An agency-wide starting identity and support contact. |
| Project | Client-specific values shared by that project’s sites. |
| Site | A website that needs a more specific presentation. |
Section: https://sairo.app/features/agency-branding#layers
## Start with a theme. Make it your own.
Pro, Agency, Growth and Scale include Pearl, Linen, Sage, Ink, Midnight and Plum themes. Choose a light or dark palette, then adjust chat and message colors, typography, text size, corners, panel width, header style and launcher position.
Workspace owners and administrators can save an organisation theme, override it for a project or website, or restore the inherited appearance. A live sample conversation uses the same styles as the installed widget. Free and Starter retain basic brand controls and the standard appearance.
Compare the six starting palettes and the accessibility review flow on the dedicated chatbot themes page.
- Six light and dark presets with checked contrast
- Eight color roles and eleven contrast-pair checks
- Editable launcher and message labels
- Layout and typography choices with minimum touch-target sizes
- [Compare theme availability](https://sairo.app/pricing): Premium themes are included from Pro upward.
- [Explore themes and customization](https://sairo.app/features/chatbot-themes)
Section: https://sairo.app/features/agency-branding#themes
## Review the actual visitor experience.
Test the business name, greeting, accent, and attribution in the installed assistant. A logo configured for a workspace should not be assumed to appear in every widget position; inspect the surface you are promising to the client.
Paid plans can hide Sairo attribution through the effective configuration. Free keeps the small mark at the bottom of the widget. Branding does not change the provider processing, service ownership, or the responsibilities described in your agreements.
Section: https://sairo.app/features/agency-branding#widget
## Choose colours that remain readable.
Use a brand accent that works with the text placed on it, and check both the launcher and interactive controls. Basic workspace branding validates its accent against white. The chatbot theme editor checks main and secondary text, visitor messages, input boundaries and keyboard focus against the backgrounds where they appear.
Low-contrast combinations and hidden visible labels produce specific warnings. Use the automatic repair option or explicitly confirm the exact changes before saving with warnings. Required screen-reader names and keyboard behavior cannot be removed.
A warning acknowledgement is not a WCAG conformance finding. Review the installed widget with your content, host page and assistive technology, including cookie controls, sticky headers and narrow layouts.
- [Review accessibility in context](https://sairo.app/guides/test-chatbot-accessibility): Check contrast, keyboard movement, zoom, and page interference.
Section: https://sairo.app/features/agency-branding#accessibility
## Make the handover specific.
Agree which person approves brand changes and which members can update knowledge. A client contributor can help maintain answers without receiving the agency’s configuration or billing access.
Keep a small launch record: project, website origin, effective brand, installed site key, approved greeting, and the person responsible for follow-up. Recheck it after a redesign or domain change.
Section: https://sairo.app/features/agency-branding#handover
## Confirm white-label requirements before selling them.
White-label requirements can include many different things: visual attribution, branded workspaces, custom domains, transactional emails, contracts, or resale rights. Confirm the exact requirement instead of treating those as one feature.
Sairo’s branding controls support the presentation described here. They do not by themselves establish a branded email delivery service or a commercial reseller agreement.
Section: https://sairo.app/features/agency-branding#scope
## Put a client’s help centre on their own domain.
Each website can publish a help centre, and that help centre can be served from a hostname the client owns, such as help.their-company.com. Articles they choose to open to search engines are then indexed under their name rather than ours.
Ownership is proved with a DNS TXT record before the domain serves anything, so a hostname nobody has verified is never answered for. The domain serves the help centre and nothing else: the workspace and the API stay on sairo.app, where the sign-in session lives.
Be precise about what this does and does not move. The widget script is still requested from sairo.app on the client’s pages, and pointing a domain also needs a certificate in place before their visitors reach it. Ask Sairo to confirm that step before you promise a date.
- [See how a help article becomes knowledge](https://sairo.app/features/website-knowledge): One article is both a public page and a source the assistant answers from.
Section: https://sairo.app/features/agency-branding#domain
Related pages
- [AI website chatbot for agencies](https://sairo.app/solutions/agencies)
- [How agencies can manage client chatbots](https://sairo.app/guides/manage-client-chatbots)
- [Contact Sairo](https://sairo.app/contact)
---
# Let visitor questions show you what is missing.
Canonical page: https://sairo.app/features/knowledge-gaps
Updated: 2026-09-08
A question the assistant cannot answer is useful feedback when your team can connect it to a concrete content change.
## Understand why an answer was missing.
An unanswered question can mean the website never covered the topic, the right page was not readable or indexed, or the available information did not establish a sufficiently supported answer. Those situations need different fixes.
Read the conversation alongside the source list. Check the exact question and any conditions introduced earlier in the exchange. Adding a generic answer can conceal a source problem without addressing the visitor’s actual need.
Section: https://sairo.app/features/knowledge-gaps#gap
## Give each gap a useful destination.
If the information should be public, update the original website. If the wording needs explicit approval, save an answer for the site and test related questions. If the request needs individual judgement, assign a person rather than publishing a rule that the business has not agreed.
Prioritise questions by relevance and consequence, then by repetition. A frequently asked low-value question may be less important than a misleading answer about an essential service condition.
A practical triage worksheet
| Finding | Next action |
| --- | --- |
| The answer is absent from the website | Ask the content owner to establish and publish it. |
| The answer exists but was not indexed | Check source exclusions, readability, verification, and crawl status. |
| Different pages give different answers | Resolve the contradiction at the original source. |
| The answer depends on an individual case | Prepare a human follow-up route. |
Video walkthrough 05: Review what needs attention (1:19, English narration with captions). Use visitor activity to choose the next improvement. Before you start: Conversations have started arriving in your workspace.
Watch: https://sairo.app/media/walkthroughs/05-review-what-needs-attention.mp4
Captions: https://sairo.app/media/walkthroughs/captions/05-review-what-needs-attention.vtt
Transcript:
- 00:00 See the pattern. Improve the answer.: Make a short review part of your week. Use Sairo's analytics to choose one useful improvement.
- 00:07 Set the scope: Open Analytics. Choose the website and reporting period, then apply the filters. The report uses UTC calendar days.
- 00:15 Read the signals: Compare conversations, leads and bookings, and capture rate. Look at unanswered outcomes for signs that visitors need information your assistant could not provide.
- 00:26 Keep the context: Use the activity chart and outcome breakdown to understand the pattern. These outcomes describe conversations; they are different from the list of knowledge gaps still needing attention.
- 00:38 Export if useful: Select Export daily report when you need a file for a team review. The export follows the report's selected filters.
- 00:47 Find open gaps: Open Conversation inbox, choose Unanswered, and apply the filters. This view helps you find questions that still need a verified answer.
- 00:58 Choose one fix: Open a conversation and read the actual question. Here, a visitor asked about skylight repairs. Confirm the answer with your team, then save it in Knowledge library.
- 01:10 Review. Learn. Help the next visitor.: Choose one gap, save a confirmed answer, and check it. That simple weekly habit keeps your assistant useful as your business changes.
Section: https://sairo.app/features/knowledge-gaps#triage
## Use saved answers deliberately.
A saved answer creates a maintained record, with someone responsible for its accuracy. Write the question in the language a visitor is likely to use and include the conditions needed to interpret the answer.
Exact matching can return approved wording directly. Semantic matching can also reuse a saved answer for a similar question, so test nearby questions that should and should not receive that response.
To work from the actual visitor exchange, open Ask Sairo and identify the question that was missed. Supply the correct answer, review the proposal and check the result. A reported error is a reason to investigate, not permission to invent a replacement policy.
An unanswered question stays in the review list even if the visitor later shares contact details or gets another answer. An active saved answer for that question closes the gap; archiving the answer makes the question available for review again.
### Example: a service-area question
A question about a nearby town may uncover that the published service area is unclear. Confirm the actual boundary with the business, update the location page, and test both an included town and an excluded one.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/features/knowledge-gaps#approve
## Let the gap propose its own answer.
Where your website already covers a question the assistant failed to answer, Sairo can draft the saved answer from that material and hand it to a person to approve. A draft appears only when retrieval clears the website’s own confidence floor, and every claim in it is checked against the supporting passages first.
When the material does not support an answer, no draft is offered and the reason is shown instead. That is the useful result: it tells you the fix is content, not wording.
Section: https://sairo.app/features/knowledge-gaps#drafts
## Ask what a change actually fixed.
Checking one typed question cannot answer the question a person really has after saving an answer or uploading a document: of the questions we already failed, which would we answer now?
Replay runs the recorded unanswered questions back through the real retrieval path at your site’s own confidence floor and sorts them into answered by a saved answer, now covered by the content, or still missing. It deliberately does not generate replies. It measures whether the evidence is there, which is the part a content change can fix.
Section: https://sairo.app/features/knowledge-gaps#replay
## Close the loop with a repeatable test.
After changing a source, refresh the relevant website content and ask the original question again. Check the answer, its evidence, and the outcome recorded in the workspace.
Keep the question in a small regression set so future model, source, or configuration changes can be checked against it. Review new conversations too; a passing test does not establish that every possible phrasing is handled.
- [Improve answer reliability](https://sairo.app/guides/reduce-chatbot-hallucinations): A workflow for source review, unsupported questions, and regression testing.
Section: https://sairo.app/features/knowledge-gaps#retest
Related pages
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge)
- [Website chatbot analytics and outcomes](https://sairo.app/features/chatbot-analytics)
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
---
# Add Sairo to your WordPress website.
Canonical page: https://sairo.app/integrations/wordpress
Updated: 2026-09-03
Use Sairo’s JavaScript embed in a location your WordPress installation permits. This guide covers a script-based setup, not a dedicated Sairo plugin.
## Identify your WordPress hosting setup.
WordPress.com limits the code available on different plans. Its documentation allows JavaScript on plugin-enabled sites with the relevant hosting features activated. A free site’s HTML support does not imply that a third-party script can run.
For a self-hosted WordPress installation, check the permissions and code-insertion method supplied by your administrator or host. A page editor that displays code for readers is different from a location that executes a script.
Source references
- [WordPress.com: adding code and JavaScript restrictions](https://wordpress.com/support/code/)
Section: https://sairo.app/integrations/wordpress#requirements
## Prepare the assistant before adding the code.
Add the published website origin to the correct Sairo workspace, verify ownership, and review the indexed sources. Prioritise service pages, contact information, and any policies a visitor is likely to ask about.
If an agency manages several WordPress sites, keep each client in the intended project. Copy the snippet from this site’s installation page so the key selects the right assistant.
Example only: replace the placeholder with the snippet from your workspace
```
```
Section: https://sairo.app/integrations/wordpress#prepare
## Use one maintained insertion point.
Choose an approved header/footer insertion tool, an appropriate shared template location, or a developer-maintained theme integration. WordPress.com documents code blocks and plugin-based approaches according to plan capability.
For Sairo, place the generated snippet near the end of the page body where your chosen method supports it. Record where you installed it. Adding the same snippet through both a theme and an insertion tool can create confusing duplicate loads.
1. Save the existing configuration
Keep the original code or revision so the change can be undone without affecting other scripts.
2. Add the site-specific snippet
Retain its source URL, public site key, and async attribute.
3. Publish and clear applicable caches
Check the visitor-facing page rather than assuming the editor view reflects the installation.
Source references
- [WordPress.com: available code insertion methods](https://wordpress.com/support/code/)
Section: https://sairo.app/integrations/wordpress#install
## Test with the theme and plugins visitors use.
Inspect a service page, a long page, and the narrow-screen layout. Confirm that the launcher does not cover a consent control, sticky call button, or form. Use a keyboard to open the panel, ask a question, and close it.
Ask a question supported by a source, one the site cannot answer, and one requesting a person. Use a contact address your team controls to test lead collection, then verify the record in the correct workspace.
Section: https://sairo.app/integrations/wordpress#test
## If the launcher is missing, check the delivered page.
Check whether the published page contains the script, whether its request succeeds, and whether a consent manager or content security policy blocks it. If a performance plugin changes script loading, test that interaction in a controlled preview before changing the visitor experience.
When changing themes or moving hosts, check the insertion point again. The knowledge belongs to the configured Sairo site, but the website still needs to load the matching snippet.
- [Use the installation troubleshooting guide](https://sairo.app/guides/troubleshoot-chatbot-installation): Separate loading, origin, connection, and knowledge problems.
Section: https://sairo.app/integrations/wordpress#troubleshoot
## Common questions
### Can I paste the script into a code-display block?
A code-display block may show the snippet as text. Use an insertion method that permits JavaScript to execute and confirm the result on the published page.
### Will changing my theme change the assistant?
It can remove a theme-specific insertion point. Check that the new theme still loads the correct Sairo snippet and that the widget works with the new layout.
Related pages
- [Verify website ownership for a chatbot](https://sairo.app/guides/verify-website-ownership)
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Connect your Webflow site to a website assistant.
Canonical page: https://sairo.app/integrations/webflow
Updated: 2026-09-03
Use Webflow’s custom-code controls to load the Sairo widget on the published pages you choose, then review it in your actual site design.
## Check custom-code access.
Webflow provides custom code at site and page level, subject to the site or workspace’s access. Check that the person making the change can use the relevant settings.
The site-level Footer code area places code before the closing body tag. Page-level code applies only to that page. Use the official instructions for the current interface and publish after saving.
Source references
- [Webflow: custom code in head and body tags](https://help.webflow.com/hc/en-us/articles/33961357265299-Custom-code-in-head-and-body-tags)
Section: https://sairo.app/integrations/webflow#requirements
## Decide where visitors should see the assistant.
A shared installation is useful when the same assistant should appear across a company’s public site. A smaller pilot can focus on one high-value service or information page before the rollout expands.
The pages displaying the widget and the pages indexed as knowledge are separate decisions. Review the source list in Sairo rather than assuming that placement on a page automatically adds all of its content to the knowledge base.
Section: https://sairo.app/integrations/webflow#scope
## Add the generated snippet.
Verify the website in Sairo and copy its installation snippet. For a site-wide setup, open Site settings, choose Custom code, and add the snippet to Footer code. Save and publish the site to the intended domain.
Keep the existing scripts intact and install Sairo once. Do not wrap the snippet in another HTML document or add a second copy at page level when it is already loaded globally.
Use your own public site key from Sairo
```
```
Source references
- [Webflow: footer code and publishing](https://help.webflow.com/hc/en-us/articles/33961357265299-Custom-code-in-head-and-body-tags)
Section: https://sairo.app/integrations/webflow#install
## Review the content, including CMS-generated pages.
Test an important collection page as well as the homepage. Confirm that the published information is readable to the crawler and that old collection items are not supplying outdated prices or conditions.
If separate client sites use the same Webflow design, they still need their own Sairo site keys and source boundaries. Duplicating a website template should not duplicate a production client’s assistant identity.
### Example pilot
An agency can start on a service page, test questions about that service, review the resulting conversations, and expand the placement after the client approves the answers and follow-up process.
Section: https://sairo.app/integrations/webflow#cms
## Check the visitor experience after publishing.
Open the public domain and navigate between the pages in your chosen scope. Check for a single launcher, correct branding, useful keyboard focus, and a working response. Inspect mobile navigation and any fixed page elements alongside the widget.
If the launcher appears but the answer is poor, check indexed knowledge before moving the script. If no launcher appears, check the deployed code, loading request, browser errors, and consent or security controls.
- [Diagnose an installation issue](https://sairo.app/guides/troubleshoot-chatbot-installation): Identify whether the problem is loading, connection, or content.
Section: https://sairo.app/integrations/webflow#validate
Related pages
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
- [How to test an embedded chatbot for accessibility](https://sairo.app/guides/test-chatbot-accessibility)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Add a website assistant to your Wix site.
Canonical page: https://sairo.app/integrations/wix
Updated: 2026-09-03
Install Sairo through Wix’s custom-code settings and validate the published site. You do not need to place the assistant inside an iframe.
## Start with the published domain.
Wix’s custom-code instructions require a published site with a connected domain. Confirm that you have access to Custom Code in the site dashboard before preparing the installation.
Wix also associates snippets with a domain. Its documentation says assigning a different domain removes those snippets, so include a code check in any domain migration.
Source references
- [Wix: custom-code prerequisites and domain changes](https://support.wix.com/en/article/wix-editor-embedding-custom-code-on-your-site)
Section: https://sairo.app/integrations/wix#requirements
## Connect that origin to the correct Sairo site.
Create or open the site in your workspace and complete ownership verification. The published origin used by visitors should match the site you are configuring. A preview URL and a custom domain may represent different origins.
Review the indexed pages before asking the assistant to represent the business. Confirm critical details and write saved answers for important questions the published site does not yet explain.
- [Verify your website ownership](https://sairo.app/guides/verify-website-ownership): Use the DNS TXT record or verification file shown in Sairo.
Section: https://sairo.app/integrations/wix#assistant
## Add one custom-code entry.
In the Wix dashboard, open Settings and then Custom Code. Add a snippet, give it a recognisable name, and select the pages where it should load. Place Sairo at Body – end and apply the change.
Choose a loading scope suited to your site and check navigation after installation. Avoid separate entries that both initialise the same assistant on the same page.
Example snippet: copy the complete generated version from Sairo
```
```
Source references
- [Wix: adding custom code and choosing page scope](https://support.wix.com/en/article/wix-editor-embedding-custom-code-on-your-site)
Section: https://sairo.app/integrations/wix#install
## Test actual journeys through the site.
Open the public website and move between several pages before starting a conversation. Check that the correct assistant remains available and that a second launcher does not appear after navigation.
Review the narrow layout alongside the Wix menu, contact buttons, and any booking or consent interface. Use a keyboard and verify that closing the panel returns focus to a sensible place.
### Example for a service website
Ask about the published service area, then ask for an exception the website does not establish. Confirm that the first answer is supported and the second leads to an honest explanation or a follow-up request.
Section: https://sairo.app/integrations/wix#test
## Diagnose the right part of the setup.
If the assistant is absent, first check that the custom-code entry applies to the current domain and page. Check whether the script loads and whether browser security or consent settings block it.
If the assistant loads but cannot answer, inspect the Sairo crawl and source list. A custom-code installation does not make hidden, login-only, or otherwise unreadable website content available to the assistant.
- [Troubleshoot the installation](https://sairo.app/guides/troubleshoot-chatbot-installation): Check the page, connection, and knowledge separately.
Section: https://sairo.app/integrations/wix#support
Related pages
- [Website chatbot for service businesses](https://sairo.app/solutions/service-businesses)
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Help shoppers find your published store information.
Canonical page: https://sairo.app/integrations/shopify
Updated: 2026-09-03
Sairo can answer from indexed public content on a Shopify storefront. This script installation does not connect the assistant to private order or inventory systems.
## Choose a useful storefront scope.
Start with questions supported by stable public material: how a service works, product care, size guidance, contact routes, or a published returns policy. Review the specific conditions, regions, and dates in those sources.
Do not rely on indexed text as live inventory or an authenticated order lookup. A shopper asking about their own purchase should be directed to your established account or support process.
- [Review the ecommerce workflow](https://sairo.app/solutions/ecommerce): Public information, policy questions, and optional live chat.
Section: https://sairo.app/integrations/shopify#fit
## Prepare a controlled theme change.
Shopify’s code editor is available through Online Store → Themes and the theme’s Edit code action. Its documentation recommends making a backup and limits editing of paid trial themes until purchase.
Have the person maintaining your theme choose the appropriate shared storefront insertion point. In a theme using the standard shared layout, that is commonly near the closing body tag in layout/theme.liquid. Preserve existing Liquid and app code.
Source references
- [Shopify: editing and backing up theme code](https://help.shopify.com/en/manual/online-store/themes/customizing-themes/edit-code/edit-theme-code)
Section: https://sairo.app/integrations/shopify#theme
## Use the assistant for this store.
Add the public store origin to Sairo, verify ownership, and review the crawl. Copy the generated site-specific installation snippet into the chosen theme location.
Keep the installation out of code-display content or product descriptions. Document the modification so a later theme replacement can deliberately retain or remove it.
Example for a shared storefront layout
```
```
Section: https://sairo.app/integrations/shopify#install
## Test policies and products carefully.
Use the published storefront to check placement on the homepage, a product page, and a policy page. Test the actual mobile layout with the cart drawer, sticky purchase controls, and consent interface.
Ask about a condition whose answer is present in the indexed source, then ask for an order-specific fact that is not available. The assistant should not invent an order status, a stock count, or an exception to a published policy.
### Example review pair
Compare “Where can I read your return conditions?” with “Has my return been approved?” The first can be grounded in public information. The second requires your actual customer-service process.
Section: https://sairo.app/integrations/shopify#validate
## Plan for content and theme changes.
Refresh and review knowledge after important policy changes. Check saved answers too: changing the public page does not automatically rewrite a separately maintained approved answer.
A script in the storefront theme should not be assumed to appear in every checkout or customer-account surface. Test only the locations where it is actually installed, and confirm any wider integration requirement before promising it.
Section: https://sairo.app/integrations/shopify#maintain
## Common questions
### Can Sairo look up a customer’s order?
The standard website embed does not authenticate customers or connect to Shopify order APIs. It uses the website knowledge configured in Sairo.
### Is there a Sairo Shopify app required for these steps?
These steps describe a theme-script installation. They do not require or claim a native Sairo app in the Shopify app store.
Related pages
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge)
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Add Sairo with Squarespace code injection.
Canonical page: https://sairo.app/integrations/squarespace
Updated: 2026-09-03
Use the published site’s code-injection controls to install the assistant, then test it alongside your navigation, forms, and mobile layout.
## Check the code-injection feature first.
Squarespace currently documents code injection for Core, Plus, Advanced, and some legacy plans. Confirm access on the actual subscription rather than assuming every site can add JavaScript.
The Footer injection field places code before the page’s closing body tag. Squarespace also notes that checkout pages do not support this code, and that scripts can be disabled in the editing preview.
Source references
- [Squarespace: code injection, plan access, and preview behavior](https://support.squarespace.com/hc/en-us/articles/205815908-Using-code-injection)
Section: https://sairo.app/integrations/squarespace#requirements
## Prepare the website’s knowledge.
Verify the published origin in Sairo and inspect the source list. For a portfolio or service business, confirm that the crawl has readable service descriptions and contact details rather than relying on image captions alone.
Decide who reviews enquiries and unanswered questions. A simple public website can still need a clear human process when a visitor asks for a custom quote or unpublished availability.
Section: https://sairo.app/integrations/squarespace#prepare
## Put the snippet in the Footer field.
Open the Code Injection panel, preserve any existing entries, and add the site’s Sairo snippet to Footer. Save the change and inspect the public website.
Use one installation point. If you are piloting only selected pages, have the site maintainer choose the correct page scope and check it explicitly rather than combining overlapping global and page entries.
Example only: replace the public site key
```
```
Source references
- [Squarespace: saving code in the injection fields](https://support.squarespace.com/hc/en-us/articles/205815908-Using-code-injection)
Section: https://sairo.app/integrations/squarespace#install
## Review the experience outside the editor.
Open the published domain as a visitor and navigate between the intended pages. If the widget is absent only in the editor, check the editor’s script setting before assuming the installation has failed.
Test the launcher beside appointment links, newsletter forms, sticky navigation, and consent controls. Ask a supported question, then an unsupported one, and inspect the conversation in Sairo.
### Example for a professional portfolio
The assistant can explain the published process and invite a visitor to share a project enquiry. It should not confirm a project start date unless the available sources actually establish it.
Section: https://sairo.app/integrations/squarespace#test
## Keep the site and assistant aligned.
Review the installation after a redesign or navigation change. A working script may still need a layout check if a new fixed button occupies the same part of the screen.
When services, contact details, or policies change, update the source website and the relevant confirmed facts or saved answers, then refresh and retest. Placement and answer accuracy are separate maintenance tasks.
- [Check keyboard and mobile behavior](https://sairo.app/guides/test-chatbot-accessibility): Review the widget in the context of your published page.
Section: https://sairo.app/integrations/squarespace#maintain
Related pages
- [Troubleshoot a website chatbot installation](https://sairo.app/guides/troubleshoot-chatbot-installation)
- [Website chatbot for service businesses](https://sairo.app/solutions/service-businesses)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Add website chat to your Framer project.
Canonical page: https://sairo.app/integrations/framer
Updated: 2026-09-03
Use Framer’s script settings to load Sairo once in the intended page scope, then verify the real published experience.
## Use the project’s script controls.
Framer’s current interface places scripts in Project Settings → Custom Code. Add a named script, choose its location and page scope, and select how often it executes.
Framer distinguishes execution once from execution on every page visit. For a persistent widget, start with a single installation and test navigation for the site’s actual behavior. Custom code added through settings is visible on the published site, not the editor preview.
Source references
- [Framer: adding custom code and choosing execution scope](https://www.framer.com/help/articles/how-to-add-custom-code/)
- [Framer: custom code and published-site testing](https://www.framer.com/help/articles/how-to-preview-your-site/)
Section: https://sairo.app/integrations/framer#settings
## Connect the domain and the assistant.
Add the public domain to Sairo, complete ownership verification, and review the indexed sources. If an agency duplicates a Framer project for another client, generate that client’s own Sairo site record and snippet.
Prepare answers to the questions your marketing site is intended to resolve. A visually rich page may need additional readable service text before the assistant has enough information to give useful answers.
Section: https://sairo.app/integrations/framer#prepare
## Add the generated script near the end of the body.
Copy the site-specific snippet from Sairo and add it to the selected custom-code entry. Choose the end-of-body location and keep the async attribute supplied by Sairo.
Publish to the domain you intend to support. Check that another component or script entry is not already loading the same assistant, and keep a record of the installation point for the next maintainer.
Use the complete snippet supplied for this Sairo site
```
```
Source references
- [Framer: custom scripts and loading considerations](https://www.framer.com/help/articles/site-optimization/)
Section: https://sairo.app/integrations/framer#install
## Test navigation, not just the first page.
Open the public homepage, start a conversation, and move through the intended page scope. Check that the launcher remains usable and that navigation does not add duplicate panels or lose important controls.
Review CMS detail pages as well as static pages if both are part of the rollout. The assistant’s indexed knowledge should reflect the published information you have approved, regardless of how Framer organised the page.
### Example for a software marketing site
A visitor can ask about a published product capability and request contact from the team. The website assistant should not claim to inspect the visitor’s private software account merely because the marketing site links to a sign-in page.
Section: https://sairo.app/integrations/framer#navigation
## Check layout and content independently.
Test narrow breakpoints with the mobile menu, sticky calls to action, and any consent interface. Follow the keyboard path from launcher to message input and back after closing the panel.
For a loading problem, inspect the published snippet and browser connection errors. For an answer problem, inspect the knowledge sources and saved answers. Keeping those checks separate makes troubleshooting much faster.
- [Follow the troubleshooting sequence](https://sairo.app/guides/troubleshoot-chatbot-installation): From a missing launcher to an unsupported answer.
Section: https://sairo.app/integrations/framer#review
Related pages
- [AI website chatbot for SaaS marketing and help](https://sairo.app/solutions/saas)
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
---
# Reduce unsupported answers with a better review process.
Canonical page: https://sairo.app/guides/reduce-chatbot-hallucinations
Published: 2026-09-03
Updated: 2026-09-06
Start with the evidence an assistant can retrieve, then test what it says when that evidence is incomplete. A confident tone is not a substitute for support.
## Check the source before changing the model.
Pick an answer that matters to the business and identify the passage that should support it. Confirm that the source is public, readable, current, and included in the site’s knowledge. Check whether other pages contradict it.
A missing exception or an outdated price can lead to a wrong answer even when the assistant accurately repeats retrieved text. Decide which page is authoritative and resolve inconsistencies there. Review confirmed facts and saved answers as well, since they can outlive an edit to the original page.
Section: https://sairo.app/guides/reduce-chatbot-hallucinations#evidence
## Understand what Sairo’s controls do.
Sairo checks saved answers and retrieves site facts and passages. Generated responses receive instructions to use that context, report missing information, and offer follow-up when needed. Instruction-like phrases in retrieved text are filtered before entering the prompt.
A response guard checks unsupported currency and percentage figures against the retrieved material. That is a targeted check, not a complete factual verifier. It does not prove that every policy, date, implication, or recommendation in an answer is correct.
- [Understand the knowledge pipeline](https://sairo.app/features/website-knowledge): Indexed pages, confirmed facts, and saved answers have different roles.
Section: https://sairo.app/guides/reduce-chatbot-hallucinations#mechanism
## Write questions with known expectations.
Build a small test set from actual visitor needs. Include direct questions, natural paraphrases, questions with an extra condition, and plausible questions whose answer is absent. Write down the expected behavior before running the test.
Test the boundary around a saved answer. A response approved for one service, location, or customer type should not be treated as a universal rule for a nearby but different question.
Example reliability test set for a service website
| Question type | Example | Expected behavior |
| --- | --- | --- |
| Known fact | What are your published opening hours? | Use the current confirmed detail or supporting page. |
| Condition | Are those hours the same on holidays? | Use explicit holiday guidance or acknowledge the gap. |
| Absent detail | Can you guarantee a visit tomorrow? | Avoid inventing availability and offer the real next step. |
| Paraphrase | When can someone take my call? | Use relevant information without confusing it with appointment availability. |
| Human request | I need to speak to a person. | Enter the site’s live chat queue when enabled, or explain the configured follow-up route. |
Section: https://sairo.app/guides/reduce-chatbot-hallucinations#test-set
## Record the failure precisely.
Save the question, the response, the source you expected, and the specific unsupported statement. Distinguish a retrieval failure from a content problem or an overbroad interpretation. Each points to a different intervention.
A response can be partly correct and still fail the test. Check conditions and scope, not just whether it includes the right phone number or a relevant citation. A linked page must actually support the claim being made.
Section: https://sairo.app/guides/reduce-chatbot-hallucinations#review
## Make one change and retest the boundary.
Improve or exclude the source, update a confirmed fact, or write an approved answer. Ask the original question again after the source refresh finishes, then test nearby questions that should produce a different result.
If you change the model, repeat the regression set rather than assuming a more expensive model is always a better fit. Keep the source, configuration, and review criteria consistent enough to understand what changed.
For a specific Sairo reply, use the inbox’s “Review with Ask Sairo” action. Supply the confirmed answer, inspect the proposed change and check the original and nearby questions. This gives the correction a reviewable record without replacing source maintenance.
### A useful review record
Question → expected source → answer received → unsupported detail → change made → retest result. Add the date and the person responsible for maintaining the underlying business information.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/guides/reduce-chatbot-hallucinations#fix
## Keep a person responsible for exceptions.
Some questions cannot be answered from a public website because they require an individual decision. Treat human handoff as a deliberate outcome: use the site’s live chat queue when enabled, or provide a usable follow-up route with a team that knows how to respond.
Continue sampling real conversations after launch. A test set provides a repeatable check for known situations; it cannot cover every future question, content change, or visitor expectation.
Section: https://sairo.app/guides/reduce-chatbot-hallucinations#ongoing
## Common questions
### Can a source-grounded chatbot still give a wrong answer?
Yes. A source may be outdated or incomplete, retrieval may find the wrong passage, or the model may interpret the material incorrectly. Grounding makes evidence available; review is still necessary.
### Should every missing answer become a saved answer?
Only after the business has established the information. Some requests should remain a human decision rather than becoming a general rule.
Related pages
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist)
---
# Measure whether the assistant is helping people.
Canonical page: https://sairo.app/guides/measure-chatbot-performance
Updated: 2026-09-08
Combine recorded activity with a review of actual conversations. Counts are useful signals, but they need a definition and a business context.
## Choose the job the assistant should do.
A service website may want visitors to understand eligibility before making an enquiry. A software marketing site may want published product questions answered accurately. An agency may need reliable client separation and a manageable follow-up process.
Write a goal that you can review directly, such as whether questions about a published service are answered with the right conditions. Avoid starting with a target percentage before you know what the current visitor mix looks like.
Section: https://sairo.app/guides/measure-chatbot-performance#goal
## Separate activity, outcomes, and quality.
Sairo’s analytics count conversations by their start time and use UTC day boundaries. The available reporting windows are 7, 30, and 90 days, with a comparison to the preceding period. Site scope follows the member’s permissions.
A conversation can have a recorded AI outcome and a separate team review status. A lead record indicates that contact details were captured. Neither automatically establishes a correct answer, a qualified prospect, or a completed sale.
A measurement worksheet
| Question | Evidence to use |
| --- | --- |
| Are people using the assistant? | Conversation volume over a consistent site scope and period. |
| Are answers supported? | A reviewed sample checked against the actual source material. |
| Are visitors sharing contact details? | Conversations with a lead record, plus the context of the request. |
| Does someone handle escalations? | Assignments, follow-up records, and the actual completed response. |
| Is the website missing information? | Unanswered questions grouped by the content change they need. |
Section: https://sairo.app/guides/measure-chatbot-performance#definitions
## Build a representative review sample.
Include answered, unanswered, escalated, and lead-producing conversations. Also inspect pending conversations instead of quietly excluding them. A sample drawn only from successful-looking answers will miss the main failure modes.
For each reviewed conversation, record whether the answer addressed the full question, matched current sources, communicated uncertainty where needed, and offered an appropriate next step. Use the same criteria across reviewers.
### Example sampling note
Review a fixed number of recent conversations from each important outcome, record why any record was excluded, and keep the same method for the next review. The sample size should fit your actual volume and the decisions you intend to make.
Section: https://sairo.app/guides/measure-chatbot-performance#sample
## State the denominator when using a rate.
If you calculate a lead-capture rate, specify whether the denominator is all conversations, a selected campaign’s conversations, or only those judged relevant to the business. These are different measurements.
For example, 12 conversations with a lead record out of 80 conversations is 15%. That arithmetic describes capture in that set. It says nothing by itself about qualification, revenue, or whether the assistant caused the visitor to contact you.
Example formula, using the same site and reporting period
```
Lead-capture rate = conversations with a lead record ÷ conversations × 100
12 ÷ 80 × 100 = 15%
```
Section: https://sairo.app/guides/measure-chatbot-performance#rates
## Control the context around a comparison.
Record changes to traffic sources, campaigns, website content, assistant settings, and team coverage. Compare periods of the same length and note whether the assistant was installed for the whole period.
A higher unanswered count after a new service launch may reveal a useful content gap. A lower conversation count may reflect lower traffic rather than poorer engagement. Read the conversations and the surrounding business context before concluding.
Section: https://sairo.app/guides/measure-chatbot-performance#comparison
## Finish each review with an owned action.
Choose a small number of improvements: fix a source, rewrite an approved answer, clarify a greeting, or assign responsibility for follow-up. Record an owner, a due date, and how the change will be checked.
Keep sales results and satisfaction measurements in the systems where they are actually recorded. Sairo’s operational analytics can inform those discussions without being presented as automatic attribution or a verified return on investment.
Video walkthrough 05: Review what needs attention (1:19, English narration with captions). Use visitor activity to choose the next improvement. Before you start: Conversations have started arriving in your workspace.
Watch: https://sairo.app/media/walkthroughs/05-review-what-needs-attention.mp4
Captions: https://sairo.app/media/walkthroughs/captions/05-review-what-needs-attention.vtt
Transcript:
- 00:00 See the pattern. Improve the answer.: Make a short review part of your week. Use Sairo's analytics to choose one useful improvement.
- 00:07 Set the scope: Open Analytics. Choose the website and reporting period, then apply the filters. The report uses UTC calendar days.
- 00:15 Read the signals: Compare conversations, leads and bookings, and capture rate. Look at unanswered outcomes for signs that visitors need information your assistant could not provide.
- 00:26 Keep the context: Use the activity chart and outcome breakdown to understand the pattern. These outcomes describe conversations; they are different from the list of knowledge gaps still needing attention.
- 00:38 Export if useful: Select Export daily report when you need a file for a team review. The export follows the report's selected filters.
- 00:47 Find open gaps: Open Conversation inbox, choose Unanswered, and apply the filters. This view helps you find questions that still need a verified answer.
- 00:58 Choose one fix: Open a conversation and read the actual question. Here, a visitor asked about skylight repairs. Confirm the answer with your team, then save it in Knowledge library.
- 01:10 Review. Learn. Help the next visitor.: Choose one gap, save a confirmed answer, and check it. That simple weekly habit keeps your assistant useful as your business changes.
Section: https://sairo.app/guides/measure-chatbot-performance#routine
Related pages
- [Website chatbot analytics and outcomes](https://sairo.app/features/chatbot-analytics)
- [Website chatbot lead capture and follow-up](https://sairo.app/features/lead-generation)
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
---
# Estimate the workload before choosing a chatbot plan.
Canonical page: https://sairo.app/guides/website-chatbot-cost
Updated: 2026-09-03
A useful budget includes the website’s content, visitor conversations, and the people maintaining the assistant. Use the planner below to explore your own assumptions.
## Start with the costs you can actually identify.
Website assistant costs can come from the service subscription, AI processing, content indexing, optional integrations, and team review. Which charges apply depends on the product and the agreement; a model’s token price alone does not describe the cost of operating a service.
Sairo’s pricing page shows the Free allowance and active paid-plan allowances. Free requires no payment card and keeps a small Powered by Sairo mark on the widget. When no paid amount is published, the page asks you to contact the team. This guide does not invent a subscription quote or a promised saving.
- [Check the current Sairo plans](https://sairo.app/pricing): Review site, page, refresh, and conversation allowances.
Section: https://sairo.app/guides/website-chatbot-cost#drivers
## Count useful pages and decide how often they change.
Count the pages the assistant needs, not every URL your CMS can generate. Archives, filters, duplicates, and obsolete offers can increase a crawl without adding useful answers. Start with the sources that support real visitor questions.
For a simple planning scenario, 100 included pages refreshed twice in a month represents 200 planned page refreshes. Initial indexing, retries, extra refreshes, and browser-rendered work can add activity. Compare the estimate with actual metering after setup.
Section: https://sairo.app/guides/website-chatbot-cost#pages
## Estimate conversation demand with explicit assumptions.
Use a website traffic figure you trust and choose a scenario for the share of visits that start a conversation. A site with 10,000 monthly visits and an assumed 2% start rate produces an estimate of 200 conversations.
That 2% is an example input, not a benchmark or a forecast for your website. Try lower and higher scenarios, then replace assumptions with observed usage after launch. Campaigns and changes in visitor intent can alter the result.
Section: https://sairo.app/guides/website-chatbot-cost#conversations
## Understand why model spend can vary.
Generated replies and embeddings are different operations. Input context, conversation length, output length, the selected model, and provider pricing can all affect processing cost. An exact saved-answer match can avoid generation for that response, but it does not make the entire service free.
Sairo staff can configure a model and maximum reply-token allowance at supported scopes. A conversation allowance is not a promise that every conversation consumes an identical number of tokens. Ask which provider costs are included in your agreement.
Questions to settle before activation
| Area | Ask about |
| --- | --- |
| Subscription | Published or quoted amount, currency, billing interval, and activation terms. |
| Allowances | Sites, pages per site, page refreshes, conversations, and any custom limits. |
| AI processing | Selected model, output allowance, and responsibility for provider charges. |
| Operations | Who reviews answers, maintains content, and completes follow-up. |
| Changes | How a higher limit or a different plan is approved. |
Section: https://sairo.app/guides/website-chatbot-cost#models
## Include the work around the widget.
Someone needs to confirm the business facts, test the installation, review knowledge gaps, and handle enquiries. An agency should agree whether that work belongs to its team or the client before quoting a rollout.
For your own planning, you can multiply expected review hours by an internal hourly cost. Keep that assumption separate from the Sairo price and avoid presenting unmeasured time savings as money already earned.
Section: https://sairo.app/guides/website-chatbot-cost#team
## Use a pilot to replace assumptions with evidence.
Choose a manageable page scope, record the initial content and conversation estimates, and review actual usage after a representative period. Check whether the assistant answered the intended questions and whether the follow-up process was sustainable.
Bring that evidence to a plan discussion. A useful quote starts with the number of sites, the included content, expected traffic, required controls, and the responsibilities around ongoing operation.
Section: https://sairo.app/guides/website-chatbot-cost#decision
## Common questions
### Does the planner calculate my Sairo bill?
No. It estimates conversation and page-refresh workload from inputs you choose. Prices, metering rules, initial indexing, extra work, and custom allowances must be confirmed separately.
### Is the example chat-start percentage an industry benchmark?
No. It is an editable scenario assumption. Replace it with your own observed data when available.
Related pages
- [Plans and pricing](https://sairo.app/pricing)
- [Website chatbot analytics and outcomes](https://sairo.app/features/chatbot-analytics)
- [Contact Sairo](https://sairo.app/contact)
---
# Find the failing step before changing the setup.
Canonical page: https://sairo.app/guides/troubleshoot-chatbot-installation
Updated: 2026-09-03
A missing launcher, a failed response, and an inaccurate answer are different problems. Start with the published page and work through the connection to the knowledge.
## Confirm the page is loading the intended snippet.
Open the public URL where visitors should see Sairo. Check that the deployed page includes one copy of the generated installation snippet and that its public site key belongs to this website.
A CMS editor may suppress custom code or show an unpublished version. Check the platform’s published-site behavior, applicable page scope, and caches before editing the assistant configuration.
Compare with the snippet generated in your workspace
```
```
Section: https://sairo.app/guides/troubleshoot-chatbot-installation#page
## Check whether the script and configuration load.
If you are comfortable using browser developer tools, inspect the request for widget.js and the widget configuration. Record the status and the page URL. If the script is absent, inspect the insertion point; if it is blocked, inspect the browser’s explanation.
A wrong public key, an inactive workspace, or an unavailable service can prevent a usable configuration. Ask the workspace administrator to verify the site record. Never paste an OpenRouter or other private provider key into a website snippet.
Match the symptom to the next check
| Symptom | Check next |
| --- | --- |
| No script request | Published code, CMS page scope, caching, and consent conditions. |
| Script blocked by the browser | The exact security-policy or extension message. |
| Configuration unavailable | The public site key, workspace status, and service health. |
| Launcher appears but replies fail | The chat request, allowed origin, usage allowance, and provider connection. |
| Replies work but contain the wrong information | Site identity, sources, confirmed facts, and saved answers. |
Section: https://sairo.app/guides/troubleshoot-chatbot-installation#network
## Read security-policy errors precisely.
Content Security Policy can control both script loading and network connections. Sairo’s script and chat requests use the sairo.app origin, while live chat uses the secure wss://sairo.app connection. Add required sources to the relevant existing directives only after your site maintainer reviews the complete policy.
The widget also creates styles inside its Shadow DOM. A strict policy can block those styles independently of the script. Record any style-policy violation and review compatibility; permitting the script alone is not a complete CSP solution.
### Useful diagnostic detail
Share the blocked request origin and directive name, such as script-src, connect-src, or style-src. Preserve the rest of your policy; disabling it entirely is not a reliable installation fix.
Source references
- [MDN: script-src](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/script-src)
- [MDN: connect-src](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy/connect-src)
Section: https://sairo.app/guides/troubleshoot-chatbot-installation#policy
## Check the host from which chat is requested.
Sairo checks the browser origin against the site’s allowed origins when present. A staging host, an alternate www address, or a new domain may not match the origin configured for the production website.
Use the approved site URL and have an authorised administrator review the configuration after a domain change. Do not work around an origin rejection by copying another customer’s key.
Section: https://sairo.app/guides/troubleshoot-chatbot-installation#origin
## Treat answer problems as a knowledge review.
If the widget is working, check which pages were indexed and whether the right content is readable. Verification, robots.txt, exclusions, an unfinished crawl, and outdated saved answers can all affect what is available.
Record one failing question and the page that should answer it. This is more useful than changing multiple settings at once. Retest after the relevant source has been corrected and refreshed.
Section: https://sairo.app/guides/troubleshoot-chatbot-installation#content
## Send a report the team can reproduce.
Include the page URL, browser, approximate time, what you expected, and the exact visible error. Say whether the problem occurs on the published site, after navigation, or only at a particular screen width.
A screenshot and the failing question are often useful. Leave passwords, API keys, recovery links, and private customer details out of the report. Use the support topic on the contact form to send the relevant information.
- [Contact Sairo support](https://sairo.app/contact?topic=support): Describe the page and the step that fails.
Section: https://sairo.app/guides/troubleshoot-chatbot-installation#report
Related pages
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations)
- [Verify website ownership for a chatbot](https://sairo.app/guides/verify-website-ownership)
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations)
---
# Make every client rollout easier to maintain.
Canonical page: https://sairo.app/guides/manage-client-chatbots
Published: 2026-09-03
Updated: 2026-09-06
A portfolio needs more than a working widget. Agree who owns the knowledge, who receives enquiries, and which people can access each client.
## Define the service you are handing over.
Document the client’s website, intended visitor questions, public information sources, and the follow-up channel. Decide whether the agency or client provides live chat coverage and who handles the offline queue.
Separate the agreed commercial service from product configuration. Removing attribution, editing an accent or serving a client’s help centre from their own domain does not establish a reseller contract or a response-time commitment. Agree those in writing.
- [Understand the branding controls](https://sairo.app/features/agency-branding): Organisation, project, and site presentation with explicit scope.
Section: https://sairo.app/guides/manage-client-chatbots#scope
## Use project boundaries from the beginning.
Create the client project within the agency workspace, then add the client’s sites to that project. Keep origins and names unambiguous so someone copying an installation snippet can identify its destination.
Invite client viewers with a specific project scope. Grant content contribution only where appropriate. Agency members who need broader operational access should receive it deliberately rather than sharing a staff login.
Decisions to record for every client
| Responsibility | Record |
| --- | --- |
| Website access | Who can publish the snippet and complete DNS or file verification. |
| Knowledge approval | Who confirms business details and approves saved answers. |
| Live chat coverage | Which eligible specialists cover the site and who checks offline requests. |
| Enquiry handling | Who reviews the inbox and completes external follow-up. |
| Configuration | Who may change branding, behavior, live chat, and installation settings. |
| Commercial administration | Who can request plan, model, or allowance changes. |
Section: https://sairo.app/guides/manage-client-chatbots#projects
## Make the business approve the facts.
Ask the client to review opening hours, service areas, contact routes, prices, and relevant conditions against its current website. Keep an explicit list of questions the assistant should leave to a person.
A shared design or similar business type does not make two clients’ information interchangeable. Test the same plausible question against each site when their policies differ, and confirm that answers come from the correct source.
Section: https://sairo.app/guides/manage-client-chatbots#knowledge
## Use a pilot and an acceptance record.
Install on the intended published site and run a repeatable test set: known information, missing information, a request for a human, and contact collection using details your team controls. When live chat is enabled, test with a specialist online and offline and confirm the queue belongs to the correct client site.
Record the result and any outstanding issues. A demo is useful for initial evaluation, but it does not replace ownership verification, full source review, or testing the client’s actual production layout.
### Example acceptance record
Client project · published origin · installed public site key · approved source set · tested questions · known limitations · responsible owner · date reviewed. Keep credentials out of this record.
Section: https://sairo.app/guides/manage-client-chatbots#rollout
## Give ongoing review a predictable place.
Set a routine for reviewing conversations, knowledge gaps, and lead follow-up. Make one person responsible for checking whether source changes require new approved wording or a retest.
Review usage before adding another site or expanding a crawl. Standard plans and custom allowances should be discussed with the administrator who manages the workspace, especially when a new client has substantially different content or traffic.
Section: https://sairo.app/guides/manage-client-chatbots#maintenance
## Recheck access when the relationship changes.
When a client contact leaves or an agency member changes responsibility, update membership and project scope. Keep an active owner responsible for the workspace instead of depending on an account nobody can maintain.
For a redesign or domain move, revisit the installation point, allowed origin, verification, and branding. Treat an ownership transfer or offboarding as an explicit administrative process; do not assume removing a script deletes the stored workspace records.
Document whether each client team will use Ask Sairo or a connected AI application. Project permissions apply to both. Start external connections with the smallest useful website scope, and reconnect when a member’s project or site access changes.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/guides/manage-client-chatbots#changes
Related pages
- [AI website chatbot for agencies](https://sairo.app/solutions/agencies)
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Check the whole journey before you call it launched.
Canonical page: https://sairo.app/guides/chatbot-launch-checklist
Published: 2026-09-03
Updated: 2026-09-06
Use this checklist with the person responsible for the website and the person handling enquiries. Record real results, including anything that needs more work.
## Agree the launch scope and owners.
Write down the published domain, pages where the assistant should appear, and information it should use. Confirm who can make website changes and who is authorised to approve business facts.
Name the person responsible for the inbox and the person who can resolve a content gap. If one person fills several roles, still record each responsibility so the handover remains clear when the team changes.
Section: https://sairo.app/guides/chatbot-launch-checklist#prepare
## Use a small test set with expected results.
Choose questions whose answers you can check against the website. Include a natural paraphrase and a question with an extra condition, such as a holiday, an exception, or a location outside the normal service area.
Add at least one plausible question the source does not answer and one explicit request for a person. Decide what the response should do before testing so a fluent answer does not hide an unsupported claim.
Capture the result of each test
| Record | What to write |
| --- | --- |
| Question | The exact wording entered by the tester. |
| Expected evidence | The source page, confirmed fact, or approved answer. |
| Actual result | The response and any record created in the workspace. |
| Decision | Accept, revise, or keep as a known issue. |
| Owner | The person who will complete and retest the change. |
Section: https://sairo.app/guides/chatbot-launch-checklist#questions
## Test the page around the assistant.
Open the published page at desktop and narrow widths. Check the widget against navigation, sticky buttons, consent controls, form fields, and page-end links. Try the page with browser zoom and reduced motion.
Use a keyboard through the complete flow and include the screen reader/browser combinations relevant to your audience. The checklist helps organise that review; marking boxes does not establish WCAG conformance for the whole website.
- [Use the detailed accessibility guide](https://sairo.app/guides/test-chatbot-accessibility): Keyboard, focus, announcements, zoom, and page interference.
Section: https://sairo.app/guides/chatbot-launch-checklist#integration
## Verify that a person receives the work.
Use test contact information your team controls and confirm the resulting lead in the correct site. If live chat is enabled, assign an eligible specialist and set them Available while testing.
Request a person from the widget, send a message while waiting, claim it from the specialist desk, reply, and end the session. Repeat with nobody online and confirm the visitor sees an honest offline queue rather than an immediate-response promise.
Agree who can correct answers through Ask Sairo and whether external AI connections are appropriate for the team. Test a correction on the intended website and review the connection’s read or write access before using it for live work.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/guides/chatbot-launch-checklist#operations
## Leave a maintainable launch record.
Record the approval date, the scope tested, the known limitations, and the location of the website snippet. Keep a way to remove or disable that snippet without disrupting unrelated website code.
Schedule review as part of your operating process after a content update, a theme change, or a change of responsibility. Reuse the original test questions so the next check has a meaningful baseline.
Section: https://sairo.app/guides/chatbot-launch-checklist#release
## Common questions
### Does this checklist save information to Sairo?
The checkboxes on this page stay in the current browser page only. They are not submitted to a workspace and reset on reload. After you create an account, the in-app setup at Get started saves add site, verify, crawl, install, and the first test answer. Use Print here if you want a paper copy of the review aid.
### Can I use this as an accessibility certificate?
No. It is a practical launch aid. A conformance assessment needs its own defined scope, testing, evidence, and findings.
Related pages
- [How to add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website)
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations)
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
---
# Set up live chat around the people who will answer.
Canonical page: https://sairo.app/guides/set-up-live-chat
Updated: 2026-09-08
Sairo adds a specialist channel to the same widget as the AI assistant. Configure it per website, make availability truthful, and test the whole handoff before visitors depend on it.
## Enable live chat for the intended website.
Open the website in the Sairo workspace, go to its assistant settings, and find Live chat. The switch belongs to that site, so enabling one client or brand does not publish live chat on every website in the workspace.
At least one eligible specialist must be selected before the feature can be enabled. Save the setting, then review the public widget on the website identified by that site’s public key.
Section: https://sairo.app/guides/set-up-live-chat#enable
## Assign specialists with the right access.
Choose active workspace members who are authorised to read and answer conversations for this site. Project access still applies in an agency workspace, and client viewers cannot configure or operate live chat.
Use individual accounts rather than a shared login. The visitor sees the replying specialist’s display name, while private account details such as the specialist’s email address are not exposed in the public response.
A practical live chat responsibility record
| Responsibility | Decision to record |
| --- | --- |
| Site coverage | Which specialists are assigned to this website. |
| Working hours | When someone is expected to set themselves Available. |
| Response authority | Which questions the specialist can answer or decide. |
| Offline requests | Who checks queued messages and how the team follows up. |
| Escalation | What happens when the specialist needs another team or private system. |
Section: https://sairo.app/guides/set-up-live-chat#specialists
## Understand what “available” means.
A specialist is shown as available after they set Available in the workspace, including from other pages. Browser notifications can alert them when a visitor is waiting. Setting Away, or never opting in, keeps the widget in the offline queue.
When nobody is available, the visitor sees Leave a message for the team. Their request still enters the site’s queue, but the wording does not promise an immediate reply. Published availability should match the way the team actually staffs the desk.
Section: https://sairo.app/guides/set-up-live-chat#presence
## Keep the AI context during handoff.
A visitor can choose the live chat control, and the assistant can also request live chat when its escalation workflow is triggered. In both cases, the existing conversation enters the specialist queue with the earlier visitor and assistant messages attached.
The visitor can continue writing while waiting. When a specialist joins, the widget shows the specialist’s name and keeps new replies in the same transcript, so the visitor does not need to open another tool or repeat the original question.
Section: https://sairo.app/guides/set-up-live-chat#handoff
## Claim, reply, take over, and end deliberately.
Open Live chat from the signed-in workspace. Waiting conversations appear for the sites assigned to that specialist. The first specialist to join claims the conversation atomically, preventing two people from becoming its active owner at the same time.
Only the active owner can reply or end the session. Other assigned specialists can see that it is being handled. If the owner stops reporting presence, an eligible teammate can take over after the inactivity window rather than leaving the visitor permanently attached to an absent operator.
1. Read the context
Review the visitor’s question, the assistant’s earlier answer, and any messages sent while waiting.
2. Join the chat
Claim the conversation when you are ready to own the reply.
3. Identify the next step
Answer within your authority or explain which follow-up route is required.
4. End the live session
Close it clearly when the live exchange is complete so the widget returns to assistant mode.
Video walkthrough 03: Take over a live conversation (1:17, English narration with captions). Move from assistant to specialist in one conversation. Before you start: A website owner enables live chat and selects an eligible teammate.
Watch: https://sairo.app/media/walkthroughs/03-take-over-a-live-conversation.mp4
Captions: https://sairo.app/media/walkthroughs/captions/03-take-over-a-live-conversation.vtt
Transcript:
- 00:00 When a visitor needs a person.: Some questions need your team. Sairo lets a specialist join the visitor's existing conversation.
- 00:07 Choose a specialist: Open the website's Settings and installation. Enable live chat, choose an eligible teammate, and save the live chat settings.
- 00:17 Set Available: The specialist selects Go available in the workspace header. Check that the status says Available. Visitors can now see that a person is online.
- 00:27 The visitor asks: The visitor selects Talk to a person and leaves their question. Their request appears in your live queue.
- 00:34 Join the request: Open Live chat. Read the earlier messages for context, then select Join live chat. The conversation is assigned to you.
- 00:44 Reply as yourself: Write a helpful reply in Message to visitor and select Send. The visitor sees your name and your response in the same chat.
- 00:52 One conversation: There is no need for the visitor to repeat the earlier question. Your team reply stays alongside the assistant's messages.
- 01:00 Finish clearly: When you have finished helping, select End live chat. Set yourself Away when you are no longer available to take requests.
- 01:10 A human reply. All the context.: If nobody is available, Sairo lets the visitor leave a message for the team without promising an immediate reply.
Section: https://sairo.app/guides/set-up-live-chat#operate
## Set expectations for near-real-time delivery.
Live chat uses a WebSocket connection between the visitor widget and the specialist desk. PostgreSQL remains the source of truth for the queue, ownership, messages, and status. If the socket is unavailable, the widget falls back to authenticated HTTP updates about every 2.5 seconds.
A short delivery delay is normal on the fallback path. The stored transcript remains the source of truth for the inbox, reconnecting the visitor’s browser session, and reviewing what happened after the live exchange.
Section: https://sairo.app/guides/set-up-live-chat#delivery
## Test every visible state before launch.
Use a site and accounts your team controls. Test a visitor request while a specialist is online, send a message while waiting, join from the desk, reply, refresh the visitor page, and end the session. Confirm speaker names, status messages, and transcript order.
Set every specialist Away and repeat the request. Confirm that the offline wording is accurate and that the request remains available when an assigned specialist returns. Include keyboard operation, screen reader announcements, zoom, narrow screens, and the host website’s other fixed controls.
- [Use the complete launch checklist](https://sairo.app/guides/chatbot-launch-checklist): Review sources, installation, live chat, lead capture, and accessibility together.
Section: https://sairo.app/guides/set-up-live-chat#test
## Common questions
### Can a visitor send messages before a specialist joins?
Yes. Messages sent while the request is waiting are stored in the same conversation and are visible to the specialist who claims it.
### Does live chat work when nobody is available?
The visitor can leave a message in the site’s queue. The widget clearly says that no specialist is available and does not promise an immediate response.
### Does Sairo live chat use WebSockets?
Yes. The widget and specialist desk use a WebSocket connection, with HTTP updates about every 2.5 seconds if that connection is unavailable.
### Can two specialists reply to the same visitor?
One specialist owns the live session at a time. Claiming is atomic, and takeover is limited to eligible teammates after the active owner’s presence expires.
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [AI chatbot vs live chat: compare and combine](https://sairo.app/compare/ai-chatbot-vs-live-chat)
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist)
---
# Prove you manage the website before indexing it.
Canonical page: https://sairo.app/guides/verify-website-ownership
Updated: 2026-09-08
Sairo provides two ownership checks so either the person with DNS access or the person who can publish a file can complete the setup.
## Get the instructions from the correct site.
Open the website’s installation page in your Sairo workspace. Check the published origin and copy the values shown for that site. Each website has its own verification token.
The public site key used by the widget, the ownership verification token, and an AI provider API key have different purposes. Use the verification value from the installation page; never substitute a provider credential.
Section: https://sairo.app/guides/verify-website-ownership#open
## Option one: publish the TXT record.
Create a TXT record at one of the DNS names shown in Sairo. The instructions offer the domain’s base name or the _sairo label under it, with a value beginning sairo-site-verification= followed by the site’s token.
DNS dashboards differ in whether the name field expects a short label or a complete hostname. Check the resulting fully qualified name so the domain is not accidentally appended twice. Add a separate record rather than replacing unrelated mail or verification records.
Illustrative DNS entry: use the actual name and token from your workspace
```
Type: TXT
Name: _sairo.example.com
Value: sairo-site-verification=YOUR_VERIFICATION_TOKEN
```
Section: https://sairo.app/guides/verify-website-ownership#dns
## Option two: publish the verification file.
Create the text file at /.well-known/sairo-verify.txt on the exact website origin shown in Sairo. Its contents should be the token supplied by the installation page. The checker expects a successful response containing that value, with surrounding whitespace ignored.
Open the file URL and inspect the response. A branded error page, a homepage rewrite, or a login screen at that path does not prove ownership, even if the browser shows a page successfully.
Illustrative file location
```
https://example.com/.well-known/sairo-verify.txt
File contents:
YOUR_VERIFICATION_TOKEN
```
Section: https://sairo.app/guides/verify-website-ownership#file
## Run the check and then request a refresh.
After publishing one of the proofs, return to the installation page and choose Check verification. Sairo checks the file and DNS methods and records the result.
Successful verification permits production crawling; it does not mean all pages have already been indexed. Request a website refresh and inspect the resulting crawl and source list. The workspace must be active and its allowances must support the work.
Video walkthrough 01: Get your assistant live (1:13, English narration with captions). Verify, install, and test your first website assistant. Before you start: Start with a workspace and a website already added.
Watch: https://sairo.app/media/walkthroughs/01-get-your-assistant-live.mp4
Captions: https://sairo.app/media/walkthroughs/captions/01-get-your-assistant-live.vtt
Transcript:
- 00:00 Your website. Ready to help.: Already created your workspace and added your website? Let's get your Sairo assistant live.
- 00:06 Open Get started: Open Get started in the sidebar. Your setup checklist keeps verification, indexing, installation, and testing in one place.
- 00:15 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.
- 00:25 Index your pages: Select Refresh website content. Sairo reads the verified website and prepares its knowledge. The next step appears when indexing finishes.
- 00:35 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.
- 00:46 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.
- 00:55 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.
- 01:05 Your first answer, ready for visitors.: Your assistant is ready for a first conversation. Next, keep its answers accurate with confirmed knowledge.
Section: https://sairo.app/guides/verify-website-ownership#check
## Match a failed check to its likely cause.
For DNS, confirm the published name, the complete token, and whether the change is visible beyond the provider’s dashboard. DNS changes can take time to become visible, so avoid repeatedly replacing a correct record.
For a file, confirm the exact path, hostname, response status, and contents. Check whether the host redirects the path or serves an HTML fallback. If an agency or host controls the website, send the exact Sairo instructions to that maintainer.
Common verification mistakes
| Mistake | Correction |
| --- | --- |
| Using the widget’s public site key | Copy the separate ownership token from the installation page. |
| Appending the DNS domain twice | Check the full published record name. |
| Publishing a token for another site | Reopen the intended website’s instructions. |
| A verification path shows the homepage | Serve the actual text file at the exact path. |
| Assuming verification completes indexing | Request a refresh and review the crawl separately. |
Section: https://sairo.app/guides/verify-website-ownership#failure
## Revisit the setup when the domain changes.
A new domain can affect website identity, the allowed browser origin, the script’s placement, and ownership verification. Ask an authorised administrator to review the complete site configuration.
Keep a record of who controls the domain and the website deployment. This makes later maintenance easier without treating access to a CMS editor as proof of every related administrative permission.
Section: https://sairo.app/guides/verify-website-ownership#changes
Related pages
- [How to add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website)
- [Troubleshoot a website chatbot installation](https://sairo.app/guides/troubleshoot-chatbot-installation)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Watch the work. Then do it yourself.
Canonical page: https://sairo.app/guides/walkthroughs
Published: 2026-09-07
Updated: 2026-09-07
Five short films follow one business from its first website answer to a useful weekly review. Each shows the real interface with English narration, captions and a written transcript, and ends with the next thing to do. The workspace, visitors and figures are fictional examples.
## 01. Get your assistant live
Verify ownership, index the website, add the installation snippet and ask a real visitor question. The film starts after a workspace and a website have been created.
Video walkthrough 01: Get your assistant live (1:13, English narration with captions). Verify, install, and test your first website assistant. Before you start: Start with a workspace and a website already added.
Watch: https://sairo.app/media/walkthroughs/01-get-your-assistant-live.mp4
Captions: https://sairo.app/media/walkthroughs/captions/01-get-your-assistant-live.vtt
Transcript:
- 00:00 Your website. Ready to help.: Already created your workspace and added your website? Let's get your Sairo assistant live.
- 00:06 Open Get started: Open Get started in the sidebar. Your setup checklist keeps verification, indexing, installation, and testing in one place.
- 00:15 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.
- 00:25 Index your pages: Select Refresh website content. Sairo reads the verified website and prepares its knowledge. The next step appears when indexing finishes.
- 00:35 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.
- 00:46 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.
- 00:55 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.
- 01:05 Your first answer, ready for visitors.: Your assistant is ready for a first conversation. Next, keep its answers accurate with confirmed knowledge.
- [Add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website): The written setup sequence, with the checks that remain with your team.
- [Verify website ownership](https://sairo.app/guides/verify-website-ownership): DNS record or verification file, and what to do when a check fails.
Section: https://sairo.app/guides/walkthroughs#get-your-assistant-live
## 02. Teach Sairo a better answer
Save a confirmed answer in the knowledge library, check source coverage and watch the next reply use it. Saved answers take priority when a visitor asks a matching question.
Video walkthrough 02: Teach Sairo a better answer (1:10, English narration with captions). Save confirmed information and check the next reply. Before you start: Use an account with permission to edit website knowledge.
Watch: https://sairo.app/media/walkthroughs/02-teach-sairo-a-better-answer.mp4
Captions: https://sairo.app/media/walkthroughs/captions/02-teach-sairo-a-better-answer.vtt
Transcript:
- 00:00 A better answer starts with you.: A visitor asks about Sunday inspections. Here's how to give Sairo the confirmed answer your team wants to use.
- 00:07 Open the library: Open Knowledge library, then choose Add saved answer. Select the website that this information belongs to.
- 00:15 Be specific: Enter the exact question and a clear, verified answer. Here, the business confirms that Sunday inspections are unavailable and gives the visitor a useful next step.
- 00:26 Save the answer: Select Save new answer. Wait for confirmation. Saved answers take priority when a visitor asks a matching question.
- 00:35 Check coverage: In Check your knowledge, enter the same visitor question and select Check source coverage. This checks saved knowledge; it does not generate a live reply.
- 00:45 Read the result: Look for A saved answer is ready. Read the returned wording and confirm that it answers the question completely.
- 00:53 Try the next reply: Now ask the question in the website assistant. The visitor receives the saved answer, including the next step for arranging an inspection.
- 01:02 Teach once. Help the next visitor.: Repeat this whenever a policy changes or a visitor finds a gap. Keep the wording specific and confirmed.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
- [Website knowledge](https://sairo.app/features/website-knowledge): Indexed pages, site facts and saved answers, and who keeps them current.
Section: https://sairo.app/guides/walkthroughs#teach-sairo-a-better-answer
## 03. Take over a live conversation
Enable live chat for a website, set a specialist available, join a waiting visitor, reply in the same conversation and end it clearly.
Video walkthrough 03: Take over a live conversation (1:17, English narration with captions). Move from assistant to specialist in one conversation. Before you start: A website owner enables live chat and selects an eligible teammate.
Watch: https://sairo.app/media/walkthroughs/03-take-over-a-live-conversation.mp4
Captions: https://sairo.app/media/walkthroughs/captions/03-take-over-a-live-conversation.vtt
Transcript:
- 00:00 When a visitor needs a person.: Some questions need your team. Sairo lets a specialist join the visitor's existing conversation.
- 00:07 Choose a specialist: Open the website's Settings and installation. Enable live chat, choose an eligible teammate, and save the live chat settings.
- 00:17 Set Available: The specialist selects Go available in the workspace header. Check that the status says Available. Visitors can now see that a person is online.
- 00:27 The visitor asks: The visitor selects Talk to a person and leaves their question. Their request appears in your live queue.
- 00:34 Join the request: Open Live chat. Read the earlier messages for context, then select Join live chat. The conversation is assigned to you.
- 00:44 Reply as yourself: Write a helpful reply in Message to visitor and select Send. The visitor sees your name and your response in the same chat.
- 00:52 One conversation: There is no need for the visitor to repeat the earlier question. Your team reply stays alongside the assistant's messages.
- 01:00 Finish clearly: When you have finished helping, select End live chat. Set yourself Away when you are no longer available to take requests.
- 01:10 A human reply. All the context.: If nobody is available, Sairo lets the visitor leave a message for the team without promising an immediate reply.
- [Set up live chat for a website](https://sairo.app/guides/set-up-live-chat): Enable one site, assign specialists, and test handoff and offline states.
- [Live chat](https://sairo.app/features/live-chat): One conversation, two ways to help, with truthful availability.
Section: https://sairo.app/guides/walkthroughs#take-over-a-live-conversation
## 04. Turn an enquiry into a follow-up
Find the conversation, read what the visitor asked, give the captured lead an owner, a stage, a follow-up date and a note, then find it again in the follow-up list.
Video walkthrough 04: Turn an enquiry into a follow-up (1:18, English narration with captions). Give a captured lead an owner and a clear next action. Before you start: A visitor has shared contact details and a lead has been captured.
Watch: https://sairo.app/media/walkthroughs/04-turn-an-enquiry-into-a-follow-up.mp4
Captions: https://sairo.app/media/walkthroughs/captions/04-turn-an-enquiry-into-a-follow-up.vtt
Transcript:
- 00:00 An enquiry. A clear next step.: A visitor has shared contact details. Here's how to turn that enquiry into a follow-up your team can act on.
- 00:08 Find the enquiry: Open Conversation inbox. Search for the visitor or the subject of their enquiry, then apply the filters. Here, we're finding Jamie Parker.
- 00:18 Read before acting: Open the matching conversation. Read what Jamie asked for and the contact details they shared before deciding what should happen next.
- 00:27 Open the lead: Select Jamie under Captured leads. The lead keeps contact details, ownership, progress, and follow-up notes together.
- 00:37 Give it an owner: Choose the teammate responsible for the next action. After contacting the visitor, update the lead stage to Contacted so the team knows where it stands.
- 00:47 Set the next action: Set the next follow-up date and add a short internal note. In this example, Dave needs to confirm an inspection time with Jamie. Select Save lead.
- 00:58 Find what's due: Return to Leads and follow-ups. Select Follow-up due and apply the filters. Jamie now appears with an owner, stage, and follow-up date.
- 01:08 Every lead has a next action.: Check this list each day. Follow-up dates organise your work list; they do not send automatic reminders or messages to the visitor.
- [Lead capture and follow-up](https://sairo.app/features/lead-generation): Collect a contact when there is a useful next step, then act on it.
- [Conversation inbox](https://sairo.app/features/conversation-inbox): Search, filter, assign and note conversations across your websites.
Section: https://sairo.app/guides/walkthroughs#turn-an-enquiry-into-a-follow-up
## 05. Review what needs attention
Set the reporting scope, read the outcome signals, export a report if useful, find unanswered questions in the inbox and choose one gap to fix in the knowledge library.
Video walkthrough 05: Review what needs attention (1:19, English narration with captions). Use visitor activity to choose the next improvement. Before you start: Conversations have started arriving in your workspace.
Watch: https://sairo.app/media/walkthroughs/05-review-what-needs-attention.mp4
Captions: https://sairo.app/media/walkthroughs/captions/05-review-what-needs-attention.vtt
Transcript:
- 00:00 See the pattern. Improve the answer.: Make a short review part of your week. Use Sairo's analytics to choose one useful improvement.
- 00:07 Set the scope: Open Analytics. Choose the website and reporting period, then apply the filters. The report uses UTC calendar days.
- 00:15 Read the signals: Compare conversations, leads and bookings, and capture rate. Look at unanswered outcomes for signs that visitors need information your assistant could not provide.
- 00:26 Keep the context: Use the activity chart and outcome breakdown to understand the pattern. These outcomes describe conversations; they are different from the list of knowledge gaps still needing attention.
- 00:38 Export if useful: Select Export daily report when you need a file for a team review. The export follows the report's selected filters.
- 00:47 Find open gaps: Open Conversation inbox, choose Unanswered, and apply the filters. This view helps you find questions that still need a verified answer.
- 00:58 Choose one fix: Open a conversation and read the actual question. Here, a visitor asked about skylight repairs. Confirm the answer with your team, then save it in Knowledge library.
- 01:10 Review. Learn. Help the next visitor.: Choose one gap, save a confirmed answer, and check it. That simple weekly habit keeps your assistant useful as your business changes.
- [Measure chatbot performance](https://sairo.app/guides/measure-chatbot-performance): Definitions, sample sizes, rates and a review routine.
- [Chatbot analytics](https://sairo.app/features/chatbot-analytics): What the dashboard counts and how to turn a finding into a change.
- [Knowledge gaps](https://sairo.app/features/knowledge-gaps): Give each unanswered question a useful destination.
Section: https://sairo.app/guides/walkthroughs#review-what-needs-attention
## Common questions
### Can I download a film or its captions?
Yes. Each film on this page has a download link for the MP4 and for its English captions in WebVTT format, and the written transcript is available under every player.
### Is the workspace in the films real?
The interface and the operations are real. The business, visitors, contacts and performance figures are fictional recording fixtures, so nothing shown is a customer result.
### Why does a film start part way through setup?
Each walkthrough opens at the point where its job begins and states what to have ready first. The first film, for example, assumes a workspace and a website already exist, which the written setup guide covers in full.
Related pages
- [AI chatbot and live chat setup guides](https://sairo.app/guides)
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist)
---
# See what your budget actually includes.
Canonical page: https://sairo.app/compare
Updated: 2026-09-06
AI answers, human support and control over your website knowledge come together in Sairo. Compare the numbers, see where Sairo offers more value, and check the details behind every difference.
- [Compare the numbers](#pricing)
- [Try your website](https://sairo.app/#try)
## Four products. The numbers beside each other.
These are entry paid plans and their billing units, not equivalent bundles. Sairo Starter includes AI and live chat in one conversation allowance. The rows below show where another subscription or usage charge applies.
USD · monthly billing · checked 6 September 2026 · taxes excluded
| Monthly price & allowance | Sairo Starter | Intercom Essential + Fin | Tidio Starter + Lyro | Chatbase Hobby |
| --- | --- | --- | --- | --- |
| Base subscription | $49 / month No per-seat charge | $39 / seat Plus Fin outcomes | $29 / month Plus recurring Lyro AI | $40 / month Message credits included |
| Recurring AI allowance or rate | 500 conversations Shared with live chat | $0.99 / outcome Standard support rate | $39 / month extra Starts at 50 AI conversations | 700 credits Model-dependent replies |
| Human support | Included Within the 500-conversation allowance | Included Paid helpdesk seats | 100 conversations Human-replied, separate from AI | Standard plan Built-in helpdesk from $150/month |
| Free AI access | 50 conversations / month On Sairo Free | 14-day trial Ongoing use is paid | 50 conversations, once Lifetime Lyro trial allowance | 50 credits / month On Chatbase Free |
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Intercom: monthly seats and plan inclusions](https://www.intercom.com/help/en/articles/9061614-fin-and-intercom-plans-explained)
- [Intercom: billable outcomes and rates](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes)
- [Tidio: pricing, AI allowances and plan inclusions (select Monthly)](https://www.tidio.com/pricing/)
- [Chatbase: monthly plans, credits and branding add-on](https://www.chatbase.co/pricing)
Section: https://sairo.app/compare#pricing
## Where Sairo gives you more from the start.
Compare the included workflow and the plan needed to use it. “Included” describes access, with the usage limits above still applying.
Documented feature and plan matrix · checked 6 September 2026
| Feature | Sairo | Intercom | Tidio | Chatbase |
| --- | --- | --- | --- | --- |
| Recurring free AI + human inbox | Included on Free 50 monthly conversations | Paid after trial Helpdesk plus Fin usage | Free inbox Recurring Lyro quota is paid | Free AI credits Built-in helpdesk on Standard |
| Paid widget attribution removal | Included from Starter $0 branding add-on | Advanced and Expert From $99/seat/month | Paid add-on $20/month where eligible | $99/month add-on Remove “Powered by Chatbase” |
| Correct answers from your own knowledge | Included Pages, facts and saved answers | Available Fin knowledge and guidance | Available Lyro knowledge and guidance | Available Sources, Q&A and instructions |
| Manage several client sites | 3 sites on Pro $149/month; project access controls | Multiple brands Plan and workspace conditions | Multiproject on Plus From $300/month plus usage | Extra agents $25/month An agent is not the same unit as a site |
| Customer account and store actions | Public website guidance No standard private order/refund connector | Connected actions Fin data and MCP connectors | Store actions Configured Lyro integrations | Connected actions Including billing integrations |
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Intercom: monthly seats and plan inclusions](https://www.intercom.com/help/en/articles/9061614-fin-and-intercom-plans-explained)
- [Intercom: attribution removal on Advanced and Expert](https://www.intercom.com/help/en/articles/15432088-your-workspace-settings)
- [Intercom: Fin MCP connectors and external actions](https://www.intercom.com/help/en/articles/11461635-add-mcp-connectors-for-popular-apps-or-custom-mcps)
- [Tidio: pricing, AI allowances and plan inclusions (select Monthly)](https://www.tidio.com/pricing/)
- [Tidio: Shopify, Calendly and other action templates](https://help.tidio.com/hc/en-us/articles/23091021128732-Lyro-Action-templates)
- [Chatbase: monthly plans, credits and branding add-on](https://www.chatbase.co/pricing)
- [Chatbase: Stripe billing actions](https://www.chatbase.co/blog/chatbase-stripe-integration-ai-agents-billing-support)
Section: https://sairo.app/compare#comparison
## See the detail for your shortlist.
Each comparison includes a numeric matrix, a feature table and the specific Sairo advantages the evidence supports.
- [Sairo vs Intercom](https://sairo.app/compare/sairo-vs-intercom): Compare included conversations with seat and outcome charges.
- [Sairo vs Tidio](https://sairo.app/compare/sairo-vs-tidio): See recurring AI allowances, live chat and monthly costs.
- [Sairo vs Chatbase](https://sairo.app/compare/sairo-vs-chatbase): Compare branding costs, credits and built-in human support.
Section: https://sairo.app/compare#alternatives
## The sources behind the numbers.
Published by Sairo. Prices and capabilities were checked on 6 September 2026 against our active plan catalogue, implemented features and the vendors’ official documentation. Prices are a dated snapshot in USD, on monthly billing, before tax. Annual discounts, negotiated contracts and third-party subscriptions are excluded. Check the linked pricing pages before purchase.
A Sairo conversation, a Fin outcome, a Tidio AI or human-service conversation and a Chatbase message credit measure different events. Examples state their assumptions and compare only the listed charges. They do not establish equivalent capacity, answer quality or total operating cost.
This is a first-party comparison, not an independent product trial. We have not established that Sairo is more accurate, faster or more accessible than these vendors. Undocumented features are unverified, not absent. Product names belong to their respective owners; no affiliation or endorsement is implied.
- [Editorial and corrections policy](https://sairo.app/editorial-policy)
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Report a comparison correction](https://sairo.app/contact?topic=support)
Section: https://sairo.app/compare#methodology
## Compare the ways you can offer support.
- [AI chatbot vs live chat](https://sairo.app/compare/ai-chatbot-vs-live-chat): Coverage, staffing and human follow-up.
- [Website chatbot vs FAQ](https://sairo.app/compare/chatbot-vs-faq): Published answers and conversational guidance.
Section: https://sairo.app/compare#approaches
Related pages
- [Plans and pricing](https://sairo.app/pricing)
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [Custom chatbot themes with accessibility checks](https://sairo.app/features/chatbot-themes)
---
# AI chatbot or live chat? Use each where it helps.
Canonical page: https://sairo.app/compare/ai-chatbot-vs-live-chat
Published: 2026-09-03
Updated: 2026-09-06
Sairo can answer routine questions from website content and let an assigned specialist join the same conversation when judgement or personal help is needed.
## What is the difference between AI chat and live chat?
AI chat can respond from maintained source information without a specialist typing each reply. Live chat depends on human availability and handles judgment or personal support. Sairo can combine both in the same visitor conversation.
## Who is answering, and what can they know?
A website assistant can retrieve published information and use it to answer a visitor’s question. In Sairo, that information comes from the site’s indexed pages, confirmed facts, and saved answers. Its usefulness depends on those sources and the response controls.
In staffed live chat, a person replies from the Sairo specialist desk. What that person can do still depends on their training, permissions, and access to business systems. The chat channel does not itself grant authority to approve a refund or inspect an account.
Section: https://sairo.app/compare/ai-chatbot-vs-live-chat#difference
## Compare responsibilities rather than labels.
The table describes both modes available in Sairo. The assistant and live specialist share one conversation, but they have different operating requirements and should set different expectations for the visitor.
AI answers and live chat in Sairo
| Question | AI website assistant | Sairo live chat |
| --- | --- | --- |
| Where does the answer come from? | Configured website knowledge and approved records. | An assigned specialist using the information and systems available to them. |
| Who handles an exception? | The assistant can acknowledge a limit and request human help. | The specialist can assess it within their actual authority. |
| What determines coverage? | Service availability, source quality, and usage allowances. | Per-site enablement, assigned specialists, presence, and queue capacity. |
| What requires maintenance? | Sources, configuration, tests, and conversation review. | Team knowledge, permissions, staffing, and queue ownership. |
| What does the visitor see? | An assistant answer with the appropriate source context. | The specialist’s name and near-real-time replies in the same widget. |
Section: https://sairo.app/compare/ai-chatbot-vs-live-chat#comparison
## Choose published answers for repeatable information.
An assistant is a useful fit when visitors repeatedly ask about public services, documentation, hours, or an established process. It can give the team a record of what was asked and reveal missing website content.
Before choosing it, test whether the important information is actually available. A website full of visual messaging but little practical detail may need content work before any source-based assistant can represent it well.
Section: https://sairo.app/compare/ai-chatbot-vs-live-chat#fit
## Choose a person for decisions and sensitive context.
A request can depend on information that is private, unpublished, or specific to one customer. The next step should reflect that dependency instead of encouraging the assistant to infer a decision from a loosely related page.
If your service needs an exchange with staff, enable live chat for that site, assign eligible specialists, and agree who will set themselves Available. Sairo shows availability from that setting and offers an offline team queue when nobody is there.
Section: https://sairo.app/compare/ai-chatbot-vs-live-chat#people
## A combined workflow needs a clear handoff.
Use AI answers for repeatable public information and live chat for questions that need judgement, clarification, or reassurance. A visitor can request a person, and an AI escalation can place the same conversation into the site’s specialist queue.
The transcript and contact context remain available to the person responding. Agree who checks the queue, who sets themselves Available, and how offline requests are owned. Enabling the button does not replace that operating process.
### Example evaluation question
“Your site explains the usual process, but my situation has an extra condition. Can someone review it?” Check whether the system explains its limits, preserves the relevant context, and leads to the actual team workflow.
Section: https://sairo.app/compare/ai-chatbot-vs-live-chat#combination
## Include the ongoing work in the decision.
Compare the full operating effort: maintaining sources, reviewing generated answers, staffing conversations, and completing follow-up. The cheapest visible subscription is not automatically the least expensive way to deliver the required service.
Use a pilot and the same review criteria to judge the experience. Record answer quality and completed follow-ups separately from the number of messages sent.
Section: https://sairo.app/compare/ai-chatbot-vs-live-chat#cost
Related pages
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat)
- [Website chatbot vs FAQ page](https://sairo.app/compare/chatbot-vs-faq)
---
# A chatbot works best with a website worth reading.
Canonical page: https://sairo.app/compare/chatbot-vs-faq
Updated: 2026-09-03
Use a clear FAQ for established information and conversation where it helps a visitor navigate that information or explain a question that remains.
## An FAQ makes the answer directly available.
A good FAQ gives a visitor an answer without requiring a conversation. Group questions around actual needs, link to the complete policy or explanation, and keep any dates and conditions next to the statement they qualify.
It is especially useful when wording must be easy to review and share. Someone should still own each answer: a static page can become stale just as easily as a saved chatbot response.
Section: https://sairo.app/compare/chatbot-vs-faq#faq
## Conversation helps with navigation and context.
A visitor may not know which FAQ category or page contains the answer. A website assistant can accept a natural-language question, retrieve relevant information, and provide a concise response connected to the source.
It can also record an unanswered question or collect contact details for follow-up when configured to do so. Those are useful additions around the content, but they do not establish facts that the business has never published or approved.
Choose the presentation that fits the information
| Need | FAQ or source page | Website assistant |
| --- | --- | --- |
| Read a complete policy | Provides stable, reviewable wording and conditions. | Can help locate or explain supported details, with source review. |
| Ask using different wording | Depends on navigation and the page’s wording. | Can retrieve relevant material for a natural-language question. |
| Share a link with someone | Directly links to the published information. | Should preserve a route back to the underlying source where available. |
| Ask an unpublished question | May provide the established contact route. | Can acknowledge the gap and record a follow-up need. |
| Maintain the facts | Requires a content owner and updates. | Requires the same source discipline plus conversation review. |
Section: https://sairo.app/compare/chatbot-vs-faq#chatbot
## Build one maintained source of truth.
For important public information, make the website useful first. Let the assistant retrieve that content rather than turning chat into the only way someone can learn a basic service condition.
Use saved answers where explicitly approved wording is useful, and record when those answers need review. Avoid maintaining a conflicting policy in the FAQ, a second version in a saved answer, and a third version in a confirmed fact.
### Example: returns conditions
Publish the complete conditions on a source page, link to it from the FAQ, and test the assistant against questions about the relevant conditions. A request for an exception should go to the business’s actual review process.
Section: https://sairo.app/compare/chatbot-vs-faq#both
## Use chat questions to improve the page.
Review recurring unanswered questions and confusing phrasing. Decide whether the website should explain the issue more directly, whether navigation makes the page hard to find, or whether the request is genuinely case-specific.
After improving the source, refresh the indexed content and retest the original question. The same change can benefit someone reading the website and someone asking the assistant.
Section: https://sairo.app/compare/chatbot-vs-faq#gaps
## Test both routes with the same visitor task.
Pick a task such as finding the service area or understanding the first step of an enquiry. Try it using the website navigation and then through the assistant. Check the accuracy, conditions, clarity, and route to more detail.
Keep an ordinary contact route available. Some visitors prefer reading or contacting the team directly, and some questions should never require a generated response.
Section: https://sairo.app/compare/chatbot-vs-faq#evaluate
Related pages
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge)
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai)
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
---
# Make store information easier for shoppers to find.
Canonical page: https://sairo.app/solutions/ecommerce
Updated: 2026-09-06
Start with the product guidance and policies you can support from public pages, and keep private order questions connected to your actual support process.
## Choose information with a reliable public source.
Product care, materials, size guidance, ordering instructions, contact routes, and published policy conditions can be useful knowledge for a storefront assistant. Include enough context for the answer to retain its meaning.
Check regions, exclusions, and dates. A short answer about shipping or returns can be misleading if it omits the condition that matters to the shopper. Link back to the source and review representative questions.
Separate public information from account-specific work
| Question | Appropriate source or next step |
| --- | --- |
| How should I care for this product? | The current published care guide for that product. |
| Where are your return conditions? | The maintained policy page and its relevant conditions. |
| Has my order shipped? | The store’s authenticated order or support process. |
| Can you make an exception for me? | A person authorised to review the request. |
Section: https://sairo.app/solutions/ecommerce#information
## Keep transactional expectations accurate.
The standard Sairo embed uses indexed website knowledge. It does not provide authenticated access to a shopper’s account, a live inventory feed, or an order-management connection.
Treat changing stock, individual order status, and discretionary decisions accordingly. A product page that mentions availability is a snapshot of indexed content, not a guarantee that inventory is current at the moment of the conversation.
Section: https://sairo.app/solutions/ecommerce#scope
## Give unresolved questions a human route.
A shopper can ask something the public website does not establish. The assistant can acknowledge that boundary, request a contact method where appropriate, or place an enabled site conversation into its live chat queue.
An assigned specialist can read the earlier transcript before replying in the same widget. Keep private order details in the store’s authenticated support process and limit the specialist’s reply to information they are authorised to handle.
Section: https://sairo.app/solutions/ecommerce#follow-up
## Test the widget beside the shopping interface.
Use an approved script location in the storefront. Check the launcher against a cart drawer, purchase controls, mobile navigation, and consent interface. Confirm that the assistant appears only on the intended surfaces.
A theme installation does not automatically extend to checkout, customer accounts, or every platform-managed page. Use the platform-specific instructions and test the published result.
- [Read the Shopify installation guide](https://sairo.app/integrations/shopify): Theme placement, public knowledge, and storefront testing.
- [Read the Squarespace installation guide](https://sairo.app/integrations/squarespace): Code injection and the published visitor experience.
Section: https://sairo.app/solutions/ecommerce#installation
## Review content changes before they become conflicting answers.
Refresh knowledge when an important policy changes and review any related confirmed facts or saved answers. Remove obsolete promotions from the approved source set instead of leaving several inconsistent versions available.
Use unanswered questions as a content backlog and captured contacts as requests to review. Measure actual support and sales results separately from raw conversation counts.
When a visitor is shown an outdated public policy, Ask Sairo can help find the conversation and prepare a confirmed answer. This works with your website knowledge; it does not grant access to private orders, payment records or a store administration API.
- [Fix an incorrect chatbot answer](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find the question, confirm the correction, save and retest.
Section: https://sairo.app/solutions/ecommerce#maintenance
Related pages
- [Website chatbot lead capture and follow-up](https://sairo.app/features/lead-generation)
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations)
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge)
---
# Help visitors understand the product before they sign in.
Canonical page: https://sairo.app/solutions/saas
Updated: 2026-09-06
Connect your public product information and help content to a conversational assistant, with a clear boundary around private accounts and unpublished commitments.
## Answer from the product information you maintain.
Visitors may ask whether a feature fits their workflow, what a setup step involves, or where to find a published plan detail. Give the assistant approved, current sources for those questions.
Separate released functionality from a roadmap or proposal. If a page discusses a future capability, make its status explicit and exclude it from the answer source where it could create a false expectation.
### Example visitor question
“Can different clients see only their own project?” The answer should reflect the product’s actual access controls and any stated plan conditions, with a route to the relevant documentation.
Section: https://sairo.app/solutions/saas#questions
## Keep the public assistant’s scope clear.
A website assistant using indexed public content does not automatically know the visitor’s subscription, account permissions, or private project data. A link to the product’s sign-in page does not grant access to those records.
Direct account-specific issues to the established authenticated support process. The assistant should explain that boundary instead of presenting a guess about someone’s plan or account state.
Section: https://sairo.app/solutions/saas#public
## Collect context for a useful product conversation.
Where the assistant’s goal enables contact collection, it can save a lead with the visitor’s request. Use that context to understand the intended use case before the team follows up.
Ask for information that helps route the enquiry, such as the problem being solved or the number of sites involved. Avoid requesting passwords, tokens, or private customer datasets in a general website chat.
- [See lead capture and follow-up](https://sairo.app/features/lead-generation): Keep the request, contact method, and team ownership connected.
Section: https://sairo.app/solutions/saas#enquiries
## Use recurring questions to improve documentation.
An unanswered question may reveal a missing setup step, ambiguous feature description, or a pricing condition that is hard to find. Review the conversation and identify the public page that should answer it.
Update that source, refresh the indexed content, and retest the original question. Keep a small set of product-critical questions for reviews after a release, plan change, or documentation reorganisation.
Use Ask Sairo to review a misunderstood feature or an outdated public answer, then provide the approved correction. A Claude MCP connection can bring permitted Sairo conversations and knowledge into your team’s AI workflow without exposing private product accounts.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/solutions/saas#documentation
## Treat the marketing site as a real integration.
Install the script in the intended page scope and check it across navigation, documentation pages, and narrow layouts. Review sticky calls to action, cookie controls, and any existing support launcher for interference.
When live chat is enabled, assign the product specialists who cover that site and test both the online and offline states. A specialist can join from the Sairo workspace and reply inside the visitor’s existing widget conversation.
- [Install on Framer](https://sairo.app/integrations/framer): Script scope and published navigation checks.
- [Install on Webflow](https://sairo.app/integrations/webflow): Footer code, CMS pages, and source review.
Section: https://sairo.app/solutions/saas#launch
Related pages
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
- [AI chatbot vs live chat: compare and combine](https://sairo.app/compare/ai-chatbot-vs-live-chat)
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist)
---
# A practical glossary for website assistants.
Canonical page: https://sairo.app/glossary
Updated: 2026-09-06
Use these definitions when planning a rollout or reading Sairo’s guides. Product-specific descriptions refer to the current Sairo workflow.
## Knowledge and answers
These terms explain how website information becomes available to the assistant. Indexing content and training a model are different operations.
### Website knowledge base
The site-specific material available for answers. In Sairo this includes indexed pages, site facts, and saved answers; it should have a clear owner and review process.
### Crawl
The process of fetching permitted website pages. A successful crawl still needs review: some URLs may be excluded, unreadable, or irrelevant to the intended questions.
### Indexing
Preparing content so it can be searched. Sairo extracts text and stores passages associated with their source pages; the indexed version can become stale after the website changes.
### Chunk or passage
A smaller piece of source text used during retrieval. A passage needs enough surrounding context to preserve conditions and meaning.
### Embedding
A numerical representation used to compare semantic similarity. An embedding is not a factuality score, and similar meaning does not guarantee that a passage answers the question.
### Retrieval
Finding relevant information for a question. Sairo uses saved-answer matching, site facts, and combined keyword and semantic search before forming a response.
### Retrieval-augmented generation
Often shortened to RAG: providing retrieved material as context for a generated response. It supplies evidence to a model without implying that its weights were fine-tuned on the website.
### Saved answer
A maintained question-and-answer record. Exact matches can return approved wording directly; semantic matches may also reuse it for a similar question, so test its boundaries.
### Confirmed fact
A business detail explicitly confirmed in the workspace. Because it is maintained separately from page text, it should be reviewed when the original business information changes.
Section: https://sairo.app/glossary#knowledge
## Answer quality and review
These terms describe evidence and behavior. None should be treated as an automatic certification of every response.
### Grounding
Connecting an answer to available supporting material. A grounded answer can still be wrong if the material is stale, incomplete, or interpreted incorrectly.
### Citation
A reference to a supporting source. Check that the cited page establishes the specific claim rather than merely mentioning the same general topic.
### Hallucination
An unsupported or fabricated model output presented as an answer. In practical reviews, record the exact unsupported detail and the evidence that should have constrained it.
### Knowledge gap
Information needed for a visitor’s question that is not adequately available to the assistant. The fix may be a source update, an indexing correction, or a human decision.
### Source exclusion
A control preventing selected page content from informing retrieval. Review related confirmed facts and saved answers separately when the underlying information should no longer be used.
### Prompt injection
Instruction-like text in untrusted input that tries to redirect the assistant’s behavior. Source content must be treated as information, not as authority over the assistant’s instructions.
### Regression test
A repeatable question with an expected result, reused after a source, model, or configuration change. It checks known behavior rather than proving every future question will work.
- [Apply these terms in an answer review](https://sairo.app/guides/reduce-chatbot-hallucinations): Build a test set and connect failures to specific improvements.
Section: https://sairo.app/glossary#quality
## Conversations, live chat, and follow-up
Sairo keeps assistant outcomes, live chat state, and the work people perform around them distinct.
### Conversation
A stored exchange containing visitor messages, assistant answers, and any live specialist replies. Reporting counts conversation records, which is different from counting individual messages or unique website visitors.
### Outcome
A recorded result associated with a conversation, such as answered, unanswered, or needing a person. It is an operational signal rather than an independent assessment of quality.
### Pending conversation
A conversation with no recorded outcome yet. Sairo includes it in relevant reporting rather than assuming that it has been answered.
### Lead capture
Saving contact information with the visitor’s request. A lead is not automatically a qualified prospect, a marketing permission, or a completed sale.
### Human handoff
Moving a conversation from the assistant to human attention while preserving its context. When live chat is enabled for a site, an assigned specialist can claim the request and reply inside the same widget.
### Live chat specialist
An active workspace member assigned to answer live chat for a particular site. Site and project access still control which conversations the person can open.
### Specialist presence
An assigned specialist’s Available or Away setting. Sairo uses it to distinguish an available specialist from an offline message queue, and can send browser, email, or SMS alerts when a visitor is waiting.
### Live chat queue
The waiting conversations for sites assigned to a specialist. Visitors can leave messages while waiting, and the first eligible specialist to claim a conversation becomes its active owner.
### Near-real-time messaging
Messages delivered over a WebSocket connection when available, with short HTTP polling as a fallback. The stored transcript remains the source of truth.
### Resolved status
A team-maintained inbox status. It indicates workflow handling and should not be confused with the system’s answer outcome or a visitor satisfaction score.
### Internal note
A team coordination record attached to work such as a conversation. It is separate from visitor-visible messages and is not exposed to client viewers in Sairo.
Section: https://sairo.app/glossary#workflow
## Installation and access
Keep public identifiers, ownership proofs, and private credentials distinct when connecting a website.
### Origin
The combination of scheme, hostname, and port, such as https://example.com. A staging host or a different www address can be a different origin for an integration.
### Public site key
The identifier in the widget snippet that selects the Sairo site. It is designed to appear in website code and is not an AI provider credential.
### Verification token
The site-specific value published in a DNS TXT record or verification file to prove control before production crawling. Use the value shown for the intended site.
### Project scope
The client project boundary assigned to a membership. It limits which sites and records a person can access within an agency workspace.
### Content Security Policy
A browser-enforced policy controlling resources such as scripts, styles, and connections. Installing a widget may require a review of the existing policy’s relevant directives.
### Shadow DOM
A component boundary used by the Sairo widget to contain its markup and styles. It is not an iframe and does not remove the need for browser and accessibility testing.
Section: https://sairo.app/glossary#installation
## Usage and capacity
Use the current plan and workspace settings to interpret allowances; do not infer a bill from terminology alone.
### Token
A unit used by a model to represent text. It is not identical to a word, character, message, or conversation, and its cost depends on the selected service and operation.
### Reply-token allowance
A configured upper allowance for a model’s response. It can constrain response length but is not a promise of identical cost for every conversation.
### Page-refresh allowance
An allowance for revisiting content under the service’s metering. A simple workload estimate multiplies included pages by planned refreshes and then accounts for additional work separately.
### Conversation allowance
A plan or custom limit on conversation usage. Check the workspace’s actual settings and usage rather than equating it with a fixed number of model tokens.
- [Plan your expected workload](https://sairo.app/guides/website-chatbot-cost): Use editable assumptions for pages, refreshes, and conversations.
Section: https://sairo.app/glossary#capacity
## Conversational workspace tools.
These terms describe how your team can work with Sairo beyond the visitor widget.
### Ask Sairo
The private workspace assistant for finding records, reviewing visitor questions and preparing supported changes through a conversation.
### MCP (Model Context Protocol)
A standard way for an AI application to discover and call another service’s tools. Sairo provides remote tools for permitted workspace operations.
### OAuth connection
A sign-in and approval flow that grants an application scoped access without sharing your Sairo password with it.
### Read and write access
Read access retrieves permitted records. Write access additionally lets a connected application call supported change tools, within your existing role.
### Change proposal
A recorded update showing the affected website and value before application. A completed change can be undone when later edits have not made that reversal stale.
- [Meet Ask Sairo](https://sairo.app/features/ai-workspace-assistant): Find the context and prepare supported updates in one conversation.
- [Connect Sairo to your AI tools](https://sairo.app/integrations/mcp): Use Claude or a compatible MCP application with the access you choose.
Section: https://sairo.app/glossary#connected-work
Related pages
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works)
- [AI chatbot and live chat setup guides](https://sairo.app/guides)
- [Sairo vs Intercom, Tidio & Chatbase: feature and price comparison](https://sairo.app/compare)
---
# A helpful assistant for the work behind the answers.
Canonical page: https://sairo.app/features/ai-workspace-assistant
Published: 2026-09-06
Updated: 2026-09-06
Tell Ask Sairo what needs attention. Find the conversation, understand what went wrong, and improve the answer from one place.
## Can I fix chatbot answers by talking to Sairo?
Ask Sairo can find a visitor question and prepare a supported correction for the selected website. Supply the correct answer, review or authorize the change, then test the visitor question again. Your existing permissions still apply.
- [Open Ask Sairo](https://sairo.app/app/assistant)
- [See a correction, step by step](https://sairo.app/guides/fix-incorrect-chatbot-answers)
## Start with the question, not a search through settings.
A visitor was given the wrong opening hours. A lead needs a follow-up. You want to see which questions your team should review. Ask Sairo brings the relevant website knowledge and workspace records into a conversation so you can work with the context in front of you.
Choose a website before making a specific correction, or review the websites you can access together. Open Ask Sairo from the workspace navigation, or use “Review with Ask Sairo” beside a visitor conversation to bring that conversation into the review.
### Example request
Find the conversation about Saturday appointments on our main website. What information did the assistant use, and which answer needs updating?
Section: https://sairo.app/features/ai-workspace-assistant#find
## Give it the right answer. Keep the wording you approve.
Describe the incorrect answer, then supply the actual business information. Ask Sairo can prepare a saved answer for that website. If the correct wording is missing, the next step is to ask you for it; a complaint alone does not establish a new policy.
Saved answers become part of the knowledge your visitor assistant uses. Exact matching prioritises the approved answer before general website content, subject to the assistant’s handoff rules. Check the original question and related wording after saving.
1. Find the original exchange
Review the visitor’s question, the reply and the relevant source information.
2. Provide the correction
Specify the correct answer and check the selected website and proposed wording.
3. Save and check
Apply the change, check the answer again and update any conflicting website page.
- [Follow the answer-correction guide](https://sairo.app/guides/fix-incorrect-chatbot-answers): A worked example, checks and recovery steps.
Section: https://sairo.app/features/ai-workspace-assistant#correct
## Bring the follow-up into the same conversation.
Ask Sairo can read conversations, saved answers, website details, leads and permitted workspace activity. It can also help prepare updates to business facts, internal notes, conversation review status, lead stages and follow-up dates.
Members with the right permissions can adjust source inclusion and refresh controls, or change an assistant’s greeting, tone and business name. Review the affected record and value before applying a proposal. Several related proposals can be reviewed together; each completed change keeps its own record.
- Find the question and its supporting information
- Correct approved answers and confirmed business facts
- Prepare lead follow-ups and internal notes
- Review recent changes and undo when needed
Section: https://sairo.app/features/ai-workspace-assistant#work
## Your team’s permissions still apply.
Ask Sairo follows your workspace, project and website access. Your conversation history is private to your account within the workspace, while applied changes update the shared records. Client viewers and contributors keep the same limits they have elsewhere in Sairo.
Proposals can be applied or dismissed. An optional automatic-corrections setting can save an explicit, unambiguous correction for one selected website. Other requests still need review. Undo checks for newer edits before restoring an earlier value, so it does not overwrite somebody else’s subsequent work.
The assistant handles supported knowledge and workspace tasks. Billing, team administration, sending messages to customers and creating websites remain in their existing workflows. Open-ended conversations need a configured AI model with tool support; Guided mode supports a smaller set of searches and direct corrections.
- [Understand assistant access and change controls](https://sairo.app/security#assistant-access)
- [Prefer to work in Claude?](https://sairo.app/integrations/mcp): Connect the same permitted workspace operations to a compatible AI application.
Section: https://sairo.app/features/ai-workspace-assistant#control
## Common questions
### Is Ask Sairo the chatbot visitors see?
Ask Sairo is for your team inside the workspace. The visitor assistant answers questions on your website. Changes you apply to saved answers and website knowledge can improve what that visitor assistant uses.
### Will it automatically invent a correction?
No. You need to supply or confirm the correct business information. A report that an answer was wrong is a starting point for review, not evidence of what the replacement should say.
### Can I use it across client websites?
You can review the websites your account can access. Select the intended website before applying a specific correction; agency project boundaries continue to apply.
Related pages
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
- [Shared AI and live chat inbox for website teams](https://sairo.app/features/conversation-inbox)
- [Sairo MCP server for Claude and AI applications](https://sairo.app/integrations/mcp)
---
# Your Sairo workspace, in the AI tools you use.
Canonical page: https://sairo.app/integrations/mcp
Published: 2026-09-06
Updated: 2026-09-06
Connect Claude or another compatible application to Sairo. Work with your website knowledge, visitor conversations and follow-ups without moving the context by hand.
## Can Claude connect to Sairo?
Compatible Claude clients can connect to Sairo’s remote MCP server through OAuth. Choose the workspace, permitted websites and read-only or supported write access. Client requirements and external subscriptions are separate from Sairo.
- [Get the connection address](https://sairo.app/connect)
- [Set up Claude](https://sairo.app/guides/connect-sairo-to-claude)
## Give your AI application useful workspace context.
MCP, the Model Context Protocol, is a way for an AI application to call tools provided by another service. Sairo’s remote MCP server exposes a defined set of workspace operations, such as finding a visitor conversation or reading an approved answer.
You sign in to Sairo during connection, choose a workspace and select the website access. The application can then request the permitted information when you ask it to help. You do not need to copy transcripts into every new conversation or give the application your Sairo password.
### A useful first request
Show the unanswered questions for my selected website. Find the relevant conversations and help me decide which answers need correcting.
Section: https://sairo.app/integrations/mcp#purpose
## Read the context. Prepare a useful next step.
Read access lets the application inspect your permitted workspace overview, conversations, knowledge, website details, leads and activity. It can check an answer against the selected website’s current knowledge.
If you also allow changes, supported tools can prepare and apply updates to saved answers, business facts, internal notes, conversation status, leads, source controls and assistant copy. Each change records what is being updated and supports dismissal or undo, subject to the current record and your permissions.
What a Sairo connection can do
| Access | Examples | What to expect |
| --- | --- | --- |
| Read | Find visitor questions, read saved answers, inspect lead follow-ups | Available within the workspace and website scope you approve. |
| Also allow changes | Correct an answer, update opening hours, prepare a follow-up date | Requires your existing editing permissions as well as write access for the connection. |
| Outside the tool set | Billing, team administration, outbound customer messages | These operations remain in their existing Sairo workflows. |
Section: https://sairo.app/integrations/mcp#capabilities
## Choose the connection’s reach.
Start with read access. During sign-in, select one website or the currently permitted websites in a workspace. Enable “Also allow changes” only when you want the application to update supported records. A connection cannot grant more access than your existing team role.
Change tools prepare a recorded proposal before applying it. Ask the application to show you the proposed change and wait for approval; the application controls its own confirmation interface. If you allow write access, it can call the permitted apply tools, so choose that access deliberately.
Connections expire and can be disconnected from Connected apps in your Sairo account. Password changes and resets revoke them too. Signing out of the website alone leaves a separately authorised connection active. Changes to your role or website access require a fresh connection.
- [Read the connection security details](https://sairo.app/security#connected-apps)
- [Understand data shared with your application](https://sairo.app/privacy#connected-apps)
Section: https://sairo.app/integrations/mcp#permissions
## Use a client that supports remote MCP and OAuth.
Sairo uses Streamable HTTP with OAuth authorisation and PKCE. Compatible clients discover the sign-in flow from the server address. Claude’s custom-connector flow and Claude Code’s HTTP MCP configuration provide two ways to start.
Client capabilities, account access and organisation policies vary. This is a custom MCP connection, not a claim of listing in an application’s connector directory. A cloud client needs a publicly reachable HTTPS Sairo address; it cannot connect to a localhost preview on your computer.
- [Connect Sairo to Claude or Claude Code](https://sairo.app/guides/connect-sairo-to-claude): Setup, first requests and connection troubleshooting.
- [Copy your Sairo server URL](https://sairo.app/connect): Use the address supplied by this Sairo installation.
Source references
- [MCP authorisation specification](https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization)
Section: https://sairo.app/integrations/mcp#clients
## Common questions
### Do I need to share an API key?
For the supported OAuth connection, sign in on Sairo and approve access. You do not paste an AI provider key or Sairo password into the connector configuration.
### Can I connect with read-only access?
Yes. Leave “Also allow changes” off. The application can then use permitted read tools, while write tools require additional connection access and the right team role.
### Does disconnecting delete information already shared?
Disconnecting prevents further access through that connection. It does not delete information the external application has already received. Its own data and conversation settings govern that copy.
Related pages
- [How to connect Sairo to Claude with MCP and OAuth](https://sairo.app/guides/connect-sairo-to-claude)
- [Ask Sairo: AI assistant for your chatbot workspace](https://sairo.app/features/ai-workspace-assistant)
- [AI chatbot and live chat security controls](https://sairo.app/security)
---
# Turn a wrong answer into a useful correction.
Canonical page: https://sairo.app/guides/fix-incorrect-chatbot-answers
Published: 2026-09-06
Updated: 2026-09-06
Use the actual visitor question, confirm what should have been said, and check the result. This guide follows the correction from the inbox to your website assistant.
## How do I correct an incorrect chatbot answer?
Find the original question, select its website, confirm the correct business information and save an approved correction through Ask Sairo or the knowledge controls. Test the original and related questions, and update any conflicting source page.
## 1. Find the original question and choose the website.
Open the conversation in the inbox and choose “Review with Ask Sairo”, or open Ask Sairo and describe the exchange you want to find. Check the transcript before changing anything: a missing detail, a stale policy and a request for a person need different responses.
Select the website the answer belongs to. If you manage several clients, include the business or website name in your request and confirm the selected site in the proposed change.
Section: https://sairo.app/guides/fix-incorrect-chatbot-answers#find
## 2. Establish the correct information.
Ask Sairo to inspect the relevant saved answer and source information. Confirm the replacement with the person responsible for that policy. “This answer is wrong” does not tell the assistant whether the hours, location or booking conditions have changed.
For this example, imagine the assistant said appointments were unavailable at weekends. The business has confirmed that Saturday consultations are available from 10am to 2pm, by appointment. Include the condition as well as the hours.
### Example correction to enter in Ask Sairo
Question: Do you offer weekend consultations? Answer: We offer Saturday consultations from 10am to 2pm, by appointment. We do not offer Sunday consultations.
Section: https://sairo.app/guides/fix-incorrect-chatbot-answers#confirm
## 3. Review and save the proposed answer.
Check the question, replacement text and website on the proposal. Apply the change when they match the approved information, or dismiss it and provide a clearer correction.
If automatic corrections are enabled, an explicit, unambiguous question-and-answer correction for one selected website can be saved directly. Turn that setting off when you want to review every correction. Either route records the completed change; a request that only reports an error should lead to clarification.
For a business fact such as a phone number or opening hours, ask for the specific fact to be updated as well when appropriate. A saved answer and a confirmed business detail are separate records, so check which record your request affects.
Video walkthrough 02: Teach Sairo a better answer (1:10, English narration with captions). Save confirmed information and check the next reply. Before you start: Use an account with permission to edit website knowledge.
Watch: https://sairo.app/media/walkthroughs/02-teach-sairo-a-better-answer.mp4
Captions: https://sairo.app/media/walkthroughs/captions/02-teach-sairo-a-better-answer.vtt
Transcript:
- 00:00 A better answer starts with you.: A visitor asks about Sunday inspections. Here's how to give Sairo the confirmed answer your team wants to use.
- 00:07 Open the library: Open Knowledge library, then choose Add saved answer. Select the website that this information belongs to.
- 00:15 Be specific: Enter the exact question and a clear, verified answer. Here, the business confirms that Sunday inspections are unavailable and gives the visitor a useful next step.
- 00:26 Save the answer: Select Save new answer. Wait for confirmation. Saved answers take priority when a visitor asks a matching question.
- 00:35 Check coverage: In Check your knowledge, enter the same visitor question and select Check source coverage. This checks saved knowledge; it does not generate a live reply.
- 00:45 Read the result: Look for A saved answer is ready. Read the returned wording and confirm that it answers the question completely.
- 00:53 Try the next reply: Now ask the question in the website assistant. The visitor receives the saved answer, including the next step for arranging an inspection.
- 01:02 Teach once. Help the next visitor.: Repeat this whenever a policy changes or a visitor finds a gap. Keep the wording specific and confirmed.
Section: https://sairo.app/guides/fix-incorrect-chatbot-answers#save
## 4. Check the original question and nearby questions.
Use the answer-check action, then test the visitor assistant with the original question. Exact saved-answer matching prioritises the approved wording, subject to handoff rules. Similar wording can use semantic retrieval, so a single passing question is not enough.
Try “Can I book a Saturday consultation?”, “Are you open on Sunday?” and a question about a weekday appointment. The Saturday correction should not invent Sunday availability or change unrelated weekday information.
A small correction test set
| Question | Expected result |
| --- | --- |
| Do you offer weekend consultations? | The approved Saturday hours and appointment condition. |
| Are Sunday consultations available? | No Sunday consultations, as confirmed in this example. |
| What does a consultation cost? | Use a separate supported source or acknowledge that the price is unavailable. |
Section: https://sairo.app/guides/fix-incorrect-chatbot-answers#test
## 5. Fix the source and keep the change reviewable.
If the website still publishes the old policy, update that page too and refresh the relevant content. Otherwise visitors reading the page and visitors using the assistant may see conflicting guidance.
Keep the original question in your review set and watch for related gaps. Use Undo on the recorded change if it should be reverted. When somebody has edited the same record since your change, review its current state and prepare a new correction instead of overwriting the newer work.
- [Build a wider answer-quality review](https://sairo.app/guides/reduce-chatbot-hallucinations): Source quality, unsupported questions and repeatable checks.
- [Explore everything Ask Sairo can help with](https://sairo.app/features/ai-workspace-assistant)
Section: https://sairo.app/guides/fix-incorrect-chatbot-answers#maintain
## When the correction does not appear.
Confirm that the proposal says it was applied, belongs to the intended website and contains the question you tested. Check whether the original exchange triggered human handoff, whether a nearby question needs different wording, or whether another source still conflicts.
If your role cannot edit answers, ask an authorised teammate to review the correction. A disconnected model, missing embedding configuration or interrupted request can leave a proposal unfinished; inspect the recorded result before retrying. Report the question, website and change status to support without sending credentials.
- [Get help with an answer correction](https://sairo.app/contact?topic=support)
Section: https://sairo.app/guides/fix-incorrect-chatbot-answers#troubleshoot
Related pages
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps)
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge)
- [How to connect Sairo to Claude with MCP and OAuth](https://sairo.app/guides/connect-sairo-to-claude)
---
# Bring your Sairo workspace into Claude.
Canonical page: https://sairo.app/guides/connect-sairo-to-claude
Published: 2026-09-06
Updated: 2026-09-06
Connect once, choose what Claude can access, and start with a question about your website. Use this guide for Claude’s custom connector or Claude Code.
## Before you connect.
You need a Sairo account with access to a workspace and at least one website. Check that you can open the website’s knowledge or conversations in Sairo first. The connection keeps your existing role and project permissions.
Your Claude account or organisation must allow custom remote connectors. Availability and settings can change, so check Claude’s current help page if the option is missing. Use the server address on Sairo’s connection page. Cloud applications need the deployed HTTPS address; a local preview address only works for a client that can reach that computer.
- [Copy the Sairo connection address](https://sairo.app/connect)
Source references
- [Claude: custom connectors and account requirements](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
Section: https://sairo.app/guides/connect-sairo-to-claude#before
## Add a custom connector in Claude.
In Claude, open Customize, then Connectors. Choose the option to add a custom connector, name it Sairo and enter the server URL. For an organisation-managed account, an owner may need to add the connector first.
Choose Connect when prompted. The browser opens Sairo’s sign-in and permission screen. Sign in there with your Sairo account, rather than entering that password into a chat message.
Section: https://sairo.app/guides/connect-sairo-to-claude#claude
## Choose the workspace, website and access.
Check the application name, choose the intended workspace and select one website or the currently permitted websites. Leave “Also allow changes” off for your first connection if you only want to search and review information.
When you want help applying corrections or other supported updates, allow changes if the option is offered and your role permits it. Approve the connection and return to Claude. If you selected the wrong workspace or website, disconnect and repeat the flow with the correct scope.
Section: https://sairo.app/guides/connect-sairo-to-claude#permissions
## Test a read before asking for a change.
Ask Claude to use Sairo to show your workspace overview, then find a conversation or saved answer you recognise. Check that the results belong to the website you approved. Empty results can mean that the selected site has no matching conversations yet.
For a correction, give the actual question and approved answer. Ask Claude to prepare the change and show the website and replacement wording before applying it. The client controls its own confirmation experience; read-only access is the option when you do not want it to write.
### Example first request
Use Sairo to show my selected website and its recent visitor questions. Read the saved answer about opening hours. Do not make any changes.
Section: https://sairo.app/guides/connect-sairo-to-claude#first-request
## Connect from Claude Code.
Add the server using Claude Code’s HTTP transport. The command below uses Sairo’s public origin; substitute the HTTPS server address shown on your connection page when using another deployment.
Inside Claude Code, run /mcp and follow the browser authentication prompt for Sairo. The same workspace and website selection applies. You do not need a static bearer token for the OAuth flow.
Add Sairo as a remote MCP server
```
claude mcp add --transport http sairo https://sairo.app/mcp
```
Source references
- [Claude Code: remote MCP and OAuth setup](https://code.claude.com/docs/en/mcp)
Section: https://sairo.app/guides/connect-sairo-to-claude#claude-code
## If connection or access fails.
A cloud client cannot reach localhost. Copy the deployed HTTPS address from the connection page and confirm that the service is reachable. Opening the MCP endpoint in a normal browser can show an authentication or method response; use the client’s connection status to test it.
If sign-in succeeds but the expected records are missing, check the selected website and your Sairo role. Reconnect after a role, project or website-access change. If reads work but changes fail, check both the connection’s write access and your team editing permission.
An expired connection or changed password requires sign-in again. For an unsupported client, confirm support for remote Streamable HTTP and OAuth with PKCE. Legacy SSE-only clients and configurations that only launch a local process are not the same connection method.
Section: https://sairo.app/guides/connect-sairo-to-claude#troubleshoot
## Manage and disconnect the application.
Open Connected apps in your Sairo account to review your connections and disconnect one. Disconnecting revokes further access through that connection. Signing out of the Sairo website alone does not revoke it.
Information already returned to Claude remains subject to Claude’s own conversation and data settings. Removing a connection does not erase that previously shared information. Review both services when you need to manage a stored conversation.
- [Manage your connected apps](https://sairo.app/account/connections)
- [Read about connected-app data](https://sairo.app/privacy#connected-apps)
Section: https://sairo.app/guides/connect-sairo-to-claude#disconnect
Related pages
- [Sairo MCP server for Claude and AI applications](https://sairo.app/integrations/mcp)
- [Ask Sairo: AI assistant for your chatbot workspace](https://sairo.app/features/ai-workspace-assistant)
- [How to fix an incorrect chatbot answer with Sairo](https://sairo.app/guides/fix-incorrect-chatbot-answers)
---
# A website that welcomes more people.
Canonical page: https://sairo.app/accessibility-statement
Updated: 2026-09-06
We want people with disabilities to be able to explore Sairo, manage their workspace, and have a useful conversation. This statement explains the support we have built, what is still being checked, and how to get help.
- [Report an accessibility issue](https://sairo.app/contact?topic=accessibility): Contact the Sairo team without signing in.
- [Read the accessibility report and VPAT draft](https://sairo.app/accessibility-report): Criterion-level evidence and the manual checks still to complete.
## Our accessibility commitment
Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We consider keyboard access, readable content, clear forms, focus, motion preferences and assistive-technology support when building the service.
Source references
- [Read WCAG 2.2 from W3C](https://www.w3.org/TR/WCAG22/)
Section: https://sairo.app/accessibility-statement#commitment
## Where the review stands
Prepared on 6 September 2026. The current review combines source inspection, automated browser checks and targeted checks of the interface. Manual testing with screen readers and other assistive technologies has not yet been completed.
Full WCAG conformance has not been established. The accompanying report is a draft with evidence and a manual test plan; it is not an accessibility certification. We will need to update its findings after manual testing and when the product changes.
- [Read the accessibility report and VPAT draft](https://sairo.app/accessibility-report): Criterion-level evidence and the manual checks still to complete.
Section: https://sairo.app/accessibility-statement#status
## What this statement covers
This statement covers the Sairo public website, sign-in and signup, account management, customer workspace, staff web administration, public demo, web-based connection approval, and the Sairo visitor chat interface.
A customer’s own website, custom branding and content, third-party checkout, connected AI applications, operating-system permission dialogs, and native desktop or mobile apps require their own assessment. Adding Sairo does not fix barriers elsewhere on a website.
Section: https://sairo.app/accessibility-statement#scope
## Using Sairo in a way that works for you
- Use a keyboard to move between links, buttons and fields. Skip links lead past repeated navigation.
- Enlarge the page using your browser. Content and tables adapt to smaller screens; long code samples and conversations can be scrolled.
- Pause the animated assistant in the homepage hero. A reduced-motion setting in your device also reduces decorative movement.
- Type instead of dictating. Microphone access is optional, and dictated text can be checked before you send it.
- Use a password manager or paste a password into account forms. Password reveal controls are available.
- Read conversation history at your own pace. Visitor reply announcements use complete sentences, while connection and handoff states also appear as text.
Section: https://sairo.app/accessibility-statement#using-sairo
## What still needs checking
Screen-reader reading order, spoken announcements, complete keyboard journeys, high zoom, forced colours and mobile assistive technology need further manual validation. Automated checks cannot establish the quality of those experiences.
Generated answers and customer content may include unfamiliar language or information that needs clarification. Site owners can explicitly acknowledge and save custom theme contrast warnings. Such a configuration is not a conformance claim. Custom colours, logos, source documents and the surrounding host page can affect the visitor experience. Check a customer installation in its real theme and context.
The core service uses HTML, CSS and JavaScript. WebGL is used for a decorative hero scene with a still-image fallback. Dictation additionally depends on browser support and microphone permission. Cross-browser assistive-technology compatibility has not yet been established.
Capabilities added after the review date have not been assessed. That currently includes attaching a file to a conversation, the rating control, proactive prompts, the hosted help centre pages, and the workspace screens for uploaded documents, actions, API keys and custom domains. They were built to the same interaction patterns as the reviewed interface, which is a design intention rather than an evaluation result. Treat them as unassessed until the next review, and report a barrier through the contact form.
Section: https://sairo.app/accessibility-statement#limitations
## Tell us when something gets in the way
Choose Accessibility issue on our contact form. Include the page address, what you were trying to do, what happened, and the browser, device or assistive technology you used. Tell us if you need the information in another format.
You do not need a Sairo account to send the form. Please leave out passwords and sensitive visitor information. If you cannot use the form, ask your workspace administrator to raise the issue through their existing support contact. For a widget on another business’s site, you can also report the barrier to that website’s operator.
- [Report an accessibility issue](https://sairo.app/contact?topic=accessibility): Contact the Sairo team without signing in.
Section: https://sairo.app/accessibility-statement#feedback
## How we are checking the service
This review uses WCAG 2.2 A and AA criteria, axe-core automated checks on the local web build, theme contrast calculations, and inspection of shared components and interactive states. The assessment record identifies its scope and remaining checks.
The next evaluation should include keyboard-only use and screen readers such as NVDA with Windows browsers, VoiceOver with Safari, and mobile assistive technology. Findings should be recorded against the same criteria and fixed before the draft report is issued as a completed conformance report.
- [Read the accessibility report and VPAT draft](https://sairo.app/accessibility-report): Criterion-level evidence and the manual checks still to complete.
- [Test a Sairo widget on your website](https://sairo.app/guides/test-chatbot-accessibility)
Section: https://sairo.app/accessibility-statement#review
Related pages
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [Sairo accessibility report and VPAT draft](https://sairo.app/accessibility-report)
- [Contact Sairo](https://sairo.app/contact)
---
# Sairo Accessibility Conformance Report
Canonical page: https://sairo.app/accessibility-report
Updated: 2026-09-06
Draft for manual validation. This report records the current web accessibility review and the evidence to carry into a complete assessment. Conformance ratings remain unassigned until the required checks are complete.
- [Download the editable VPAT draft (.docx)](https://sairo.app/documents/sairo-accessibility-conformance-report-draft.docx)
- [Accessibility statement](https://sairo.app/accessibility-statement)
## Report details
WCAG Edition, based on VPAT® Version 2.5Rev (April 2025), published by the Information Technology Industry Council (ITI). Prepared 6 September 2026 for the Sairo web application, package version 0.1.0, local development revision reviewed on that date.
Sairo provides website-grounded answers, text-based live chat, customer workspaces, administrative tools and OAuth connection approval. This draft targets WCAG 2.2 Level A and Level AA. It does not report Section 508, EN 301 549 or Level AAA conformance.
This is an evaluation working draft, not an issued procurement ACR. A blank or unassigned conformance cell means a rating still needs to be decided. “Not Evaluated” is not used as an A or AA rating. The complete report must be reviewed and approved after manual validation.
- [Report an accessibility issue](https://sairo.app/contact?topic=accessibility): Contact the Sairo team without signing in.
Source references
- [ITI VPAT® templates and guidance](https://www.itic.org/policy/accessibility/vpat)
- [W3C conformance evaluation guidance](https://www.w3.org/WAI/test-evaluate/conformance/)
Section: https://sairo.app/accessibility-report#report-details
## Scope and evaluation methods
The reviewed product includes public information pages, account flows, customer and staff web interfaces, the public demo, visitor widget and web-based OAuth approval. Customer host pages, customer-provided content and branding, external checkout, connected applications and native apps are outside this report’s conformance scope.
Methods include source inspection, axe-core 4.11.1 in the Chromium-based local browser, inspection of hydrated controls, narrow-layout and text-spacing checks, and contrast calculations for shared theme colours and image-backed forms. Sample records are used for authenticated workflows.
No screen-reader user testing, independent certification or full assistive-technology compatibility assessment is claimed. Automated passes are evidence for a review, not proof that a complete page or process conforms. Each row below gives the remaining verification task.
- HTML, CSS and JavaScript support the core web interface.
- Decorative WebGL has a still-image fallback.
- Optional microphone dictation requires browser permission.
- Customer installations must be tested as complete pages in their own environment.
Section: https://sairo.app/accessibility-report#scope
## Conformance terms for the completed report
The editable report retains the standard conformance column. Its ratings are intentionally blank during this draft stage. Use the following ITI terms only when the relevant evidence supports a conclusion.
### Supports
At least one method meets the criterion without known defects, or meets it through equivalent facilitation.
### Partially Supports
Some of the product functionality does not meet the criterion.
### Does Not Support
Most of the product functionality does not meet the criterion.
### Not Applicable
The criterion is not relevant to the product being reported.
Section: https://sairo.app/accessibility-report#terms
## WCAG 2.2 Level A
This table preserves the historical 4.1.1 row from the template. Parsing was removed from WCAG 2.2 and is excluded from its 55 current A and AA criteria.
WCAG 2.2 Level A draft assessment
| Criterion | Conformance level | Remarks and explanations |
| --- | --- | --- |
| 1.1.1 Non-text Content | Not yet assigned (draft) | Product illustrations have descriptions; purely decorative icons and the WebGL scene are hidden from assistive technology. Charts include text values. Next check: Review descriptions, charts and customer-supplied logos with a screen reader. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not yet assigned (draft) | The reviewed web routes contain no prerecorded audio-only or video-only informational media. Optional dictation is user input. Next check: Reassess when recorded media is introduced. |
| 1.2.2 Captions (Prerecorded) | Not yet assigned (draft) | No prerecorded synchronized media is included in the reviewed web interface. Live chat is text. Next check: Reassess captions when synchronized media is introduced. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not yet assigned (draft) | No prerecorded synchronized media is included in the reviewed web interface. Next check: Reassess media alternatives when synchronized media is introduced. |
| 1.3.1 Info and Relationships | Not yet assigned (draft) | Pages use headings, navigation landmarks, labelled forms, fieldsets and semantic tables. Shared field hints are connected to controls. Next check: Read complex tables, grouped settings, chart values and dialog relationships with assistive technology. |
| 1.3.2 Meaningful Sequence | Not yet assigned (draft) | Source order follows the content sequence. Responsive tables retain explicit row, cell and header roles. Next check: Check reading order at mobile widths and with styles disabled. |
| 1.3.3 Sensory Characteristics | Not yet assigned (draft) | Instructions name controls and describe actions in words; status indicators also include text. Next check: Review complete tasks for instructions that depend on position, shape or sound. |
| 1.4.1 Use of Color | Not yet assigned (draft) | Validation, availability, connection and conversation states have text labels. Active navigation also exposes aria-current. Next check: Check selected states and charts in grayscale and forced-colours mode. |
| 1.4.2 Audio Control | Not yet assigned (draft) | The reviewed pages do not start audio automatically. Dictation begins only after a user request. Next check: Reassess if autoplay media or audio notifications are added. |
| 2.1.1 Keyboard | Not yet assigned (draft) | Actions use native buttons, links and form controls. Scrollable chat transcripts and code can receive keyboard focus. Next check: Complete every primary workflow using only the keyboard, including live handoff and OAuth consent. |
| 2.1.2 No Keyboard Trap | Not yet assigned (draft) | The visitor chat is nonmodal and has Escape handling. Workspace navigation uses a native dialog with a close button. Next check: Confirm forward and reverse tabbing, Escape and focus restoration in all dialogs. |
| 2.1.4 Character Key Shortcuts | Not yet assigned (draft) | Message shortcuts are handled on the focused composer; there are no global single-character shortcuts in the reviewed web source. Next check: Check speech-input interactions and focused composer shortcuts. |
| 2.2.1 Timing Adjustable | Not yet assigned (draft) | Save confirmations remain until dismissed. Request limits and session expiry exist; long-running tasks show status and retry options. Next check: Assess expiry, recovery and preservation of unsent input through complete timed processes. |
| 2.2.2 Pause, Stop, Hide | Not yet assigned (draft) | The moving hero offers Pause motion and follows reduced-motion preferences. Other decorative effects follow the shared motion setting. Next check: Verify the pause control, all loading animations and automatic updates in a reduced-motion environment. |
| 2.3.1 Three Flashes or Below Threshold | Not yet assigned (draft) | Reviewed motion consists of slow scene movement and loading indicators; no deliberate flashing sequences are present. Next check: Inspect final rendered animations for flashes across supported devices. |
| 2.4.1 Bypass Blocks | Not yet assigned (draft) | Public, account, demo and workspace shells provide skip links and main landmarks. Next check: Activate each skip link using a keyboard and screen reader; verify its landing point. |
| 2.4.2 Page Titled | Not yet assigned (draft) | Public pages have descriptive titles. Account, workspace and staff routes have task-specific titles rather than one shared title. Next check: Check title and page-change announcements during client navigation. |
| 2.4.3 Focus Order | Not yet assigned (draft) | No positive tabindex is used. Failed form submissions move focus to feedback; dialog and chat close actions restore focus. Next check: Trace focus through validation, history, dynamic replies, navigation and removed controls. |
| 2.4.4 Link Purpose (In Context) | Not yet assigned (draft) | Links describe destinations or have their purpose provided by their containing card, table row or related text. Next check: Review repeated actions in context and the screen-reader links list. |
| 2.5.1 Pointer Gestures | Not yet assigned (draft) | Product actions use single-pointer activation. The decorative 3D scene is not required for any task. Next check: Verify no operation requires a multipoint or path-based gesture. |
| 2.5.2 Pointer Cancellation | Not yet assigned (draft) | Core actions use click or form submission, rather than completing a task on pointer-down. Next check: Test pressing, moving off a target and releasing, including touch controls. |
| 2.5.3 Label in Name | Not yet assigned (draft) | Controls generally use their visible text as their name. Icon-only controls have explicit labels. Next check: Check voice-control matching against all visible labels and state changes. |
| 2.5.4 Motion Actuation | Not yet assigned (draft) | No web task requires device movement, shaking or orientation gestures. Next check: Reassess when motion-controlled functionality is introduced. |
| 3.1.1 Language of Page | Not yet assigned (draft) | The document root declares English with lang="en". Next check: Verify the browser exposes the page language to assistive technology. |
| 3.2.1 On Focus | Not yet assigned (draft) | Focus highlights controls without submitting forms or opening destinations. Next check: Tab through complete processes and confirm there are no unexpected context changes. |
| 3.2.2 On Input | Not yet assigned (draft) | Save and submit actions have explicit controls. Filters and example selectors update content within the page. Next check: Review scope selectors and filters for clear, predictable changes. |
| 3.2.6 Consistent Help | Not yet assigned (draft) | Shared shells link to accessibility information and support in consistent locations for that group of pages. Next check: Confirm help remains discoverable throughout onboarding and error recovery. |
| 3.3.1 Error Identification | Not yet assigned (draft) | Native required and format validation is used. Server errors are written in text and shared form feedback receives focus. Next check: Test every validation branch with screen readers and check error association and recovery. |
| 3.3.2 Labels or Instructions | Not yet assigned (draft) | Inputs have labels, optional fields are identified, and password and message-length instructions are provided. Next check: Review all constraints before input and check screen-reader announcement of hints. |
| 3.3.7 Redundant Entry | Not yet assigned (draft) | Forms preserve entries when server validation fails. The demo can prefill the website when continuing to signup. Next check: Follow complete onboarding, recovery and correction processes for unnecessary repeated entry. |
| 4.1.1 Parsing | Does not apply to WCAG 2.2 | This success criterion was removed from WCAG 2.2. The retained template row is historical and is not counted in the WCAG 2.2 total. Next check: No WCAG 2.2 rating is required. |
| 4.1.2 Name, Role, Value | Not yet assigned (draft) | Controls expose names, roles and relevant states. Dropdown and dialog relationships use local element identifiers. Next check: Test names, roles and changing values across browser and assistive-technology combinations. |
Section: https://sairo.app/accessibility-report#level-a
## WCAG 2.2 Level AA
These criteria are evaluated in addition to Level A. Remarks identify implementation evidence and the manual work still needed.
WCAG 2.2 Level AA draft assessment
| Criterion | Conformance level | Remarks and explanations |
| --- | --- | --- |
| 1.2.4 Captions (Live) | Not yet assigned (draft) | The service supplies text chat and does not supply live synchronized audio/video content in the reviewed web routes. Next check: Reassess when live audiovisual media is introduced. |
| 1.2.5 Audio Description (Prerecorded) | Not yet assigned (draft) | No prerecorded synchronized video is present in the reviewed web routes. Next check: Reassess audio description when prerecorded video is introduced. |
| 1.3.4 Orientation | Not yet assigned (draft) | Layouts use responsive rules without orientation locks. Next check: Complete primary workflows in portrait and landscape, including small-height windows. |
| 1.3.5 Identify Input Purpose | Not yet assigned (draft) | Account and contact fields use applicable name, email, URL and password autocomplete tokens. Next check: Check browser and assistive-technology identification of fields about the current user. |
| 1.4.3 Contrast (Minimum) | Not yet assigned (draft) | Text and preset themes have automated contrast checks. Custom low-contrast themes require explicit acknowledgement. Image-backed account surfaces have a tested opaque colour floor. Next check: Review image and gradient contexts, all interactive states and user-supplied branding. |
| 1.4.4 Resize text | Not yet assigned (draft) | The site does not restrict browser zoom; layouts and typography use responsive sizing. Next check: Check actual 200 percent browser zoom and text-only enlargement without lost content or actions. |
| 1.4.5 Images of Text | Not yet assigned (draft) | Interface copy is rendered as text. Logos and decorative illustrations are the remaining image content. Next check: Confirm new imagery does not carry instructions that are missing from the text. |
| 1.4.10 Reflow | Not yet assigned (draft) | Responsive layouts and tables adapt to narrow containers. Main content and controls are checked at 320 CSS pixels. Next check: Complete tasks at 400 percent zoom; check overlays, diagrams and long user content. |
| 1.4.11 Non-text Contrast | Not yet assigned (draft) | Theme focus and field boundaries are checked against adjacent surfaces. Custom contrast warnings require acknowledgement. Forced colours remain available. Next check: Review icons, chart marks, selected controls and focus against adjacent colours in all states. |
| 1.4.12 Text Spacing | Not yet assigned (draft) | Containers generally grow with their content. A local testing control applies the WCAG text-spacing values. Next check: Inspect every workflow with increased line, paragraph, letter and word spacing; test text inside Shadow DOM too. |
| 1.4.13 Content on Hover or Focus | Not yet assigned (draft) | Public navigation is explicitly opened, can be dismissed, and closes when focus leaves. Browser-native tooltips are used for supplementary hints. Next check: Check all popovers with keyboard and pointer for dismissibility, persistence and hoverability. |
| 2.4.5 Multiple Ways | Not yet assigned (draft) | The public site provides primary navigation, footer links, a complete HTML sitemap and contextual links. Next check: Confirm essential pages remain reachable through more than one route. |
| 2.4.6 Headings and Labels | Not yet assigned (draft) | Pages have descriptive primary headings; fields, sections and actions use task-oriented labels. Next check: Review clarity and heading order with the screen-reader heading list, including empty states. |
| 2.4.7 Focus Visible | Not yet assigned (draft) | Shared focus-visible rules draw contrasting outlines; scoped connection styles inherit the active theme. Next check: Inspect every focused control in light, dark and forced-colours modes. |
| 2.4.11 Focus Not Obscured (Minimum) | Not yet assigned (draft) | Page focus targets have scroll margins. The floating widget yields when it overlaps a focused page control. Next check: Check sticky headers, dialogs, notices and chat at high zoom and on short screens. |
| 2.5.7 Dragging Movements | Not yet assigned (draft) | The reviewed product has no task that requires a dragging movement. Next check: Reassess if sortable, draggable or gesture-only controls are introduced. |
| 2.5.8 Target Size (Minimum) | Not yet assigned (draft) | Most standalone controls use generous targets; automated checks cover the WCAG minimum and spacing rules. Next check: Inspect all responsive states, inline-link exceptions and densely grouped controls. |
| 3.1.2 Language of Parts | Not yet assigned (draft) | The authored interface is English. Visitor messages, customer knowledge and generated text can contain other languages without reliable per-passage language metadata. Next check: Evaluate multilingual messages and announce language changes correctly before assigning a rating. |
| 3.2.3 Consistent Navigation | Not yet assigned (draft) | Shared page shells preserve navigation order within the public site, account flows and each workspace. Next check: Confirm consistent navigation across roles and responsive breakpoints. |
| 3.2.4 Consistent Identification | Not yet assigned (draft) | Shared components keep recurring actions, help links and controls consistently named. Next check: Review labels across error, empty, pending and completed states. |
| 3.3.3 Error Suggestion | Not yet assigned (draft) | Validation messages explain common corrections such as required values, format, length and password rules. Next check: Exercise server-side failures and confirm useful correction suggestions without exposing protected data. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not yet assigned (draft) | Knowledge changes can be reviewed and undone where supported. Billing uses an external checkout; workspace forms save on explicit submission. Next check: Review financial and data-changing workflows, confirmations and irreversible operations end to end. |
| 3.3.8 Accessible Authentication (Minimum) | Not yet assigned (draft) | Sign-in allows password managers and paste. Password reveal and recovery are available; no puzzle or memory task beyond supported password entry is imposed. Next check: Complete sign-in, signup, invitation acceptance, recovery and OAuth with assistive technology and a password manager. |
| 4.1.3 Status Messages | Not yet assigned (draft) | Status and error regions expose pending, completion and failure messages. Streaming visitor replies use a separate sentence announcer; the visible log is explicitly aria-live="off". Next check: Listen for lost, repeated or excessive announcements during streaming, live chat, saves and errors. |
Section: https://sairo.app/accessibility-report#level-aa
## Complete the manual validation
Record the release, browser and assistive-technology versions, tested pages and roles, test steps, result, evidence and issue reference. Test a full process, including its errors and recovery, before assigning a conformance rating.
Use the editable report to replace the open ratings with supported conclusions. Record any exceptions precisely, rerun automated checks after fixes, update the date and scope, and review the result before sharing it as a completed ACR.
1. Keyboard and focus
Complete navigation, signup, sign-in, recovery, setup, data changes, live handoff and connection approval using Tab, Shift+Tab, Enter, Space, Escape and arrow keys where appropriate.
2. Screen readers
Check headings, landmarks, forms, tables, source links, errors, streaming replies, live messages and focus changes with NVDA and VoiceOver. Include mobile screen readers.
3. Visual adaptation
Check 200 percent text enlargement, 400 percent zoom, 320 CSS pixel reflow, portrait and landscape, increased text spacing, forced colours and both workspace themes.
4. Complete processes and content
Include long content, validation failures, session expiry, saved-answer changes and undo, billing handoff, OAuth consent, customer branding and multilingual conversations.
- [Report an accessibility issue](https://sairo.app/contact?topic=accessibility): Contact the Sairo team without signing in.
- [Accessibility statement](https://sairo.app/accessibility-statement)
Section: https://sairo.app/accessibility-report#manual-validation
Related pages
- [Sairo accessibility statement](https://sairo.app/accessibility-statement)
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [How to test an embedded chatbot for accessibility](https://sairo.app/guides/test-chatbot-accessibility)
---
# What Sairo does. What to check before you choose it.
Canonical page: https://sairo.app/product-facts
Published: 2026-09-06
Updated: 2026-09-09
Sairo is an AI website chatbot and live chat platform for businesses and agencies. It answers from selected website content, lets a human join the conversation, and gives your team tools to review and improve the assistant. The table below is the reference for what is implemented today, including the boundaries of each capability and the one channel that is built but not yet available in the hosted service.
- [Compare current plans](https://sairo.app/pricing)
- [Check app availability](https://sairo.app/apps)
## What is the current product focus?
As of 9 September 2026, the existing website feature set is the baseline. New website features are paused while we complete testing, distribution and approval for the iOS, macOS, Windows and Android companion apps. Reliability, security and accessibility maintenance continues.
App availability is tracked separately from website capabilities. Internal tests and store review submissions do not establish public availability.
- [Check the status of each app](https://sairo.app/apps)
Section: https://sairo.app/product-facts#release-focus
## What is Sairo?
Sairo has three connected parts: an embedded visitor chatbot, a private team workspace, and an OAuth MCP server for compatible AI applications. The visitor assistant uses a website’s selected sources and saved answers. Ask Sairo helps the team work with permitted workspace records. The MCP connection lets an external application access supported tools within the access you grant.
### Product
Sairo, available at sairo.app.
### Category
AI website chatbot, live chat and assistant-management software.
### Who it serves
Businesses maintaining public website information, support teams and agencies managing client websites.
### Installation
A JavaScript widget installed in a website’s shared template or supported custom-code area.
- [About Sairo](https://sairo.app/about)
- [See the setup and operating workflow](https://sairo.app/how-it-works)
Section: https://sairo.app/product-facts#overview
## What can Sairo help with?
These descriptions refer to the current Sairo product. Follow the linked feature and setup pages for prerequisites and operating details.
Sairo capabilities and their boundaries
| Capability | What it does | What to know |
| --- | --- | --- |
| Website answers | Retrieves selected website content and approved saved answers for visitor questions. | Source quality and freshness affect the result. Generated answers still need review. |
| Live human handoff | An assigned specialist can join the same visitor conversation with its earlier transcript. | Enable it per site and staff the queue. An offline queue is not an immediate-response promise. |
| Leads and follow-up | Keeps contact details, conversation context, ownership and follow-up status together. | Your team handles the follow-up. An appointment request is not an external calendar reservation. |
| Ask Sairo | Finds permitted records and prepares supported updates such as corrected saved answers. | Provide the correct business information. It does not infer an unpublished company policy from a complaint. |
| MCP connection | Exposes supported workspace read and write tools through OAuth to compatible applications. | Client compatibility, team roles and selected website scope apply. External subscriptions are separate. |
| Chatbot themes | Offers six presets and controls for colors, typography, layout and labels. | Full customization requires Pro, Agency, Growth or Scale. Risky choices require acknowledgement. |
| Agency workspaces | Separates projects, websites and permitted team access in one workspace. | Available capacity depends on the active plan. |
| Uploaded documents | Indexes a PDF, Word (.docx), text, Markdown or CSV file as knowledge, up to 12 MB per file. | Each upload counts against the plan’s indexed-page allowance. A scanned PDF with no text layer cannot be read. |
| Assistant actions | Lets the assistant call a system you run and answer from what it returns. Up to ten per website, two per reply. | You build and maintain the endpoint. HTTPS and a public address are required; every call is logged for your team. |
| Answering in the visitor’s language | Replies in the language the visitor writes in, when the translation preserves every figure in the approved answer. | When a figure does not survive translation the English answer stands. This is not a claim of professional translation. |
| Attachments | A visitor can send a photo or PDF, and a specialist can send one back. Up to 5 MB and ten files per conversation. | Files are stored and served as downloads, never rendered. SVG is refused. |
| Proactive prompts | Offers help on chosen pages after a set delay. Up to five rules per website. | One prompt per visit, dismissible, and never shown over an open conversation. It is an offer of help, not a campaign tool. |
| Live visitor list | Shows which pages are being read now, on sites with live chat enabled. | The page path is recorded without its query string, against a hashed widget token, and removed shortly after the visit ends. |
| Conversation rating | Asks the visitor whether an answer helped, and keeps the question alongside the score. | Reported as a count of people who rated, never as a satisfaction rate over everyone who stayed silent. |
| Saved replies and drafts | Specialists reuse approved wording, and can request a summary or a draft grounded in the website’s own material. | A draft is withheld when the material does not support it. Nothing is sent for you; a person still edits and sends. |
| Answer gaps into drafts | Turns a recorded unanswered question into a draft answer, and replays past failures against the current knowledge. | Drafts appear only when retrieval clears the site’s confidence floor, and every one needs a person’s approval. |
| Hosted help centre | Publishes articles at a Sairo address, or your own domain, that the assistant also answers from. | Search engines are not offered an article until you ask. Article text is published as plain paragraphs, not markup. |
| Custom domain | Serves a website’s help centre from a hostname you own, after a DNS TXT record proves it. | A domain serves the help centre only. Ask Sairo before pointing a domain, so the certificate is in place first. |
| Public REST API | Reads and writes websites, conversations, leads and saved answers with a scoped bearer key. | Keys are hashed and revocable. Rate limits and plan allowances apply to API traffic as they do to the product. |
| WhatsApp | Answers messages to a business WhatsApp number with the same assistant, inside WhatsApp’s 24-hour reply window. | Built, but not available in the current hosted service: no Twilio account is connected to it. Contact Sairo before planning around it. |
- [Explore the feature details](https://sairo.app/features)
- [Understand live handoff](https://sairo.app/features/live-chat)
- [See Ask Sairo’s supported work](https://sairo.app/features/ai-workspace-assistant)
- [Review MCP access and setup](https://sairo.app/integrations/mcp)
- [Compare chatbot themes](https://sairo.app/features/chatbot-themes)
Section: https://sairo.app/product-facts#capabilities
## Which websites can use Sairo?
Sairo works through a JavaScript embed on sites that allow a custom script and the required network requests. The public catalogue includes setup guides for WordPress, Webflow, Wix, Shopify, Squarespace and Framer. These are installation instructions for the embed, not claims of native marketplace apps or certified platform partnerships.
The public demo reads a bounded sample of accessible public pages without signup. Connecting the full website requires a workspace, ownership verification and a crawl within the plan allowance. Login-only pages, blocked content and information that requires unsupported browser interactions may be unavailable.
- [Choose your platform instructions](https://sairo.app/integrations)
- [Verify your website](https://sairo.app/guides/verify-website-ownership)
- [Prepare readable source content](https://sairo.app/guides/prepare-website-for-ai)
Section: https://sairo.app/product-facts#setup
## Is Sairo free, and which features are premium?
Sairo offers Free and paid plans. The pricing page reads the active plan catalogue and is the reference for current prices, currencies and allowances. It explains websites, indexed pages, refreshes and conversations.
Pro, Agency, Growth and Scale include the full chatbot theme editor. Free and Starter retain basic branding and the standard appearance. Paid plans can hide Sairo attribution. An external AI application’s subscription is not included in a Sairo plan.
- [Read current prices and plan conditions](https://sairo.app/pricing)
- [Plan the operating cost](https://sairo.app/guides/website-chatbot-cost)
Section: https://sairo.app/product-facts#plans
## How should you evaluate privacy, security and accessibility?
Review the published data flow, role boundaries and connection controls for your proposed use. Visitor messages and relevant source material may be sent to configured AI providers. A connected external application has its own data practices.
The accessibility statement and draft conformance report describe implementation evidence and outstanding manual checks. The draft is not certification. Installing Sairo does not make the host website conformant, and accepting a low-contrast theme warning does not make that choice accessible.
- [Security controls and scope](https://sairo.app/security)
- [Data and privacy practices](https://sairo.app/privacy)
- [Accessibility statement](https://sairo.app/accessibility-statement)
- [Draft accessibility report and evidence](https://sairo.app/accessibility-report)
Section: https://sairo.app/product-facts#trust
## What should you not assume?
Sairo does not guarantee error-free AI answers, increased sales, a specific search ranking or round-the-clock human staffing. The published widget installation does not grant access to private orders, inventory or customer accounts. Optional dictation transcribes speech into editable text; it is not a telephone agent.
MCP tools do not provide arbitrary database queries, billing administration or unrestricted outbound customer messaging. Use the capability list and the selected access scope when assessing a connected workflow.
- [Evaluate answer quality](https://sairo.app/guides/reduce-chatbot-hallucinations)
- [Compare AI answers and staffed live chat](https://sairo.app/compare/ai-chatbot-vs-live-chat)
Section: https://sairo.app/product-facts#limits
## Where can you verify or correct this information?
This is a first-party product reference. Feature pages explain supported behavior, guides describe specific tasks, and pricing states current commercial allowances. A worked example is not a customer result or an independent benchmark.
To report an inaccurate claim, send the page address, the statement and the behavior you observed through Contact. A text index and a longer text reference are available for readers and tools that prefer plain text; both are generated from the public content catalogue.
- [How Sairo maintains product information](https://sairo.app/editorial-policy)
- [Report a product information issue](https://sairo.app/contact?topic=support)
- [Public content index (text)](https://sairo.app/llms.txt)
- [Public reference pages (text)](https://sairo.app/llms-full.txt)
Section: https://sairo.app/product-facts#reference
## Common questions
### Is Sairo an AI chatbot or a live chat service?
Sairo combines an AI website chatbot with per-site live chat. AI answers use selected website knowledge; an assigned specialist can join the same conversation when live chat is enabled and staffed.
### Can Sairo answer from my website without signup?
The public demo can build an assistant from a limited sample of readable public pages without signup. Connecting the full website requires an account, ownership verification and the applicable plan allowance.
### Does Sairo guarantee accurate answers or accessibility compliance?
No. Source review, answer testing and complete-page accessibility testing remain necessary. Sairo supplies controls, warnings and documented implementation evidence; those do not guarantee every generated answer or every customer configuration.
Related pages
- [AI website chatbot and live chat features](https://sairo.app/features)
- [Plans and pricing](https://sairo.app/pricing)
- [AI chatbot and live chat security controls](https://sairo.app/security)
- [How Sairo maintains guides and product information](https://sairo.app/editorial-policy)
---
# Useful guidance should be easy to verify.
Canonical page: https://sairo.app/editorial-policy
Published: 2026-09-06
Updated: 2026-09-06
Sairo publishes first-party product information for people evaluating, installing and maintaining its website assistant. This policy explains how to read the guidance, what its evidence covers and how to flag a correction.
## Who is responsible for these pages?
The Sairo product team maintains the public feature descriptions and setup guides. A Sairo byline identifies first-party product guidance, not an independent reviewer or an external certification body. Contact Sairo if you need confirmation for a procurement decision or a specific configuration.
- [About Sairo](https://sairo.app/about)
- [Contact the team](https://sairo.app/contact)
Section: https://sairo.app/editorial-policy#responsibility
## What supports a product claim?
Feature descriptions are checked against the implemented workflow and its access, configuration and plan requirements. Practical instructions identify prerequisites, expected behavior and troubleshooting steps. Platform and standards references link to the original documentation where that supports the task.
Screenshots, sample conversations and worked calculations illustrate an experience. They are not evidence of customer adoption, measured business results or universal answer accuracy. We do not present generated testimonials, invented reviews or unsupported performance statistics as evidence.
- [Read the product facts and limits](https://sairo.app/product-facts)
- [Measure results in your own workflow](https://sairo.app/guides/measure-chatbot-performance)
Section: https://sairo.app/editorial-policy#evidence
## What do the dates mean?
The Updated date marks a substantive revision to a page’s product information or instructions. A layout-only change does not establish that every referenced external service was retested. Original publication dates are preserved when a guide is revised.
Third-party interfaces and account requirements can change separately from Sairo. Check the linked official source for current restrictions, then tell us if a step no longer matches what you see.
Section: https://sairo.app/editorial-policy#dates
## Where do evaluations stop?
Sairo distinguishes implementation evidence, automated checks, manual validation and independent assessment. An automated accessibility scan is not a completed conformance evaluation. A working local integration does not establish compatibility with every external application, browser or hosting policy.
Comparison guides explain task-level differences and operating responsibilities. They do not imply that Sairo is the best option for every business. Pricing and contractual terms take precedence over illustrative cost examples.
- [Read the assessment scope](https://sairo.app/accessibility-report)
- [Check the current plan catalogue](https://sairo.app/pricing)
- [Read service terms](https://sairo.app/terms)
Section: https://sairo.app/editorial-policy#scope
## How can you report an error?
Send the page URL, the statement or step, the expected behavior and what you observed. Include the relevant date, browser or client version when it helps reproduce the issue. Avoid sending passwords, API keys or private visitor information in a public report.
Use the contact form’s Support topic for documentation and product issues, or Accessibility issue for an access barrier. The team can investigate and revise the affected guidance. No fixed response time is promised on this page.
- [Report a documentation issue](https://sairo.app/contact?topic=support)
- [Report an accessibility barrier](https://sairo.app/contact?topic=accessibility)
Section: https://sairo.app/editorial-policy#corrections
Related pages
- [Sairo product facts, capabilities and limits](https://sairo.app/product-facts)
- [About Sairo](https://sairo.app/about)
- [AI chatbot and live chat setup guides](https://sairo.app/guides)
- [Contact Sairo](https://sairo.app/contact)
---
# A chatbot that feels at home on your website.
Canonical page: https://sairo.app/features/chatbot-themes
Published: 2026-09-06
Updated: 2026-09-06
Choose Pearl, Linen, Sage, Ink, Midnight or Plum, then customize the details in a live preview. Pro, Agency, Growth and Scale include the full editor, with accessibility checks before you publish.
- [Try the themes](#theme-preview)
- [See plans with themes](https://sairo.app/pricing)
## Which chatbot themes are available?
Start with a preset, then change the supported appearance settings to suit the website. The editor and installed chatbot share the same styling.
Six Sairo chatbot starting themes
| Theme | Appearance |
| --- | --- |
| Pearl | Light stone surfaces and charcoal text. |
| Linen | Warm paper colors, serif typography and tailored corners. |
| Sage | Soft green surfaces and humanist typography. |
| Ink | A dark monochrome palette with tailored corners. |
| Midnight | Deep slate surfaces and a solid header. |
| Plum | A muted dark purple palette and humanist typography. |
Section: https://sairo.app/features/chatbot-themes#presets
## What can you customize?
Set eight color roles covering backgrounds, messages, text, buttons, borders and focus. Choose a font stack, text size, corner treatment, panel width, launcher position and header style. Edit the launcher text, message label and optional placeholder.
Apply an organisation default, then override it for a project or website. Restoring inheritance removes that layer’s override. If a workspace downgrades, premium settings are retained while the visitor chatbot uses the standard appearance.
- [Understand branding and inheritance](https://sairo.app/features/agency-branding)
Section: https://sairo.app/features/chatbot-themes#customization
## What happens if a change hurts readability?
The editor checks eleven text, border and focus color pairs. Warnings identify the affected content, the measured contrast ratio and the required minimum. Hiding a visible label also produces a discoverability warning.
A theme with warnings opens a review dialog. Keep editing, use the repair action or explicitly save with warnings. Confirmation is checked on the server against those exact settings. Required accessible names cannot be removed, and arbitrary custom CSS cannot disable the protected interaction behavior.
### An example warning
Text in assistant messages: the chosen colors do not meet the contrast target. Review the colors, use the repair action or acknowledge the specific risk before saving.
Source references
- [W3C: text contrast](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html)
- [W3C: non-text contrast](https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html)
Section: https://sairo.app/features/chatbot-themes#checks
## How does the theme work for visitors?
The chatbot uses the website’s saved appearance. Preview colors, text and labels in the editor, then test the installed chatbot with your own content.
Supported themes keep keyboard interaction, visible focus, touch targets and reduced-motion and forced-color treatment. Customer pages, logos, content, zoom behavior and assistive technology still need complete integration testing. Saving with warnings is not an accessibility conformance claim.
- [Read the accessibility statement](https://sairo.app/accessibility-statement)
- [Test the chatbot in your website](https://sairo.app/guides/test-chatbot-accessibility)
Section: https://sairo.app/features/chatbot-themes#visitor
## How do you publish a theme?
1. Choose the scope
Open Settings and select the organisation, project or website to customize. Owners and administrators can save appearance changes.
2. Preview the conversation
Choose a preset, edit the details and inspect the sample messages, controls and labels.
3. Review and save
Resolve any required-field errors. Fix or explicitly acknowledge the listed accessibility risks, then save. Newly loaded widgets use the saved appearance without changing the embed snippet.
Section: https://sairo.app/features/chatbot-themes#setup
## Common questions
### Which Sairo plans include chatbot themes?
Pro, Agency, Growth and Scale include the full theme editor. Free and Starter retain basic branding and the standard chatbot appearance.
### Can I remove the chatbot’s accessible labels?
Required accessible names cannot be removed. Hiding visible launcher or message text raises a warning while retaining the programmatic name.
### Do I need to reinstall the widget after changing its theme?
No. Newly loaded widgets use the effective saved theme from their existing site configuration. The installation snippet stays the same.
Related pages
- [Plans and pricing](https://sairo.app/pricing)
- [Agency chatbot branding and client identity](https://sairo.app/features/agency-branding)
- [Accessible chatbot design and testing](https://sairo.app/accessibility)
- [Sairo product facts, capabilities and limits](https://sairo.app/product-facts)
---
# Sairo vs Intercom.
Canonical page: https://sairo.app/compare/sairo-vs-intercom
Published: 2026-09-06
Updated: 2026-09-06
Keep website AI and human support in one monthly plan. Sairo includes a conversation allowance and team access without a per-seat charge. See how that compares with Intercom seats and Fin usage.
- [Compare the numbers](#pricing)
- [Start with Sairo Free](https://sairo.app/signup?plan=free)
## Included conversations. No per-seat fee.
Sairo Starter includes 500 new website conversations each month. Intercom Essential charges for helpdesk seats, with Fin support outcomes billed separately. This comparison uses Intercom’s own helpdesk with Fin; adding Fin to another helpdesk is a separate offer.
USD · monthly billing · checked 6 September 2026 · taxes excluded
| Price or limit | Sairo Starter | Intercom Essential + Fin |
| --- | --- | --- |
| Monthly subscription | $49 Per organisation | $39 Per full helpdesk seat |
| Included monthly AI capacity | 500 conversations Shared with human support | Usage billed separately No included outcome bundle in this seat price |
| Standard AI support charge | $0 extra Within the plan allowance | $0.99 / outcome Resolution or procedure handoff |
| Additional team member | $0 per seat Team access included | $39 / month Each additional Essential full seat |
| Try without a paid plan | 50 conversations / month Sairo Free; renews monthly | 14 days Free trial |
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Intercom: monthly seats and plan inclusions](https://www.intercom.com/help/en/articles/9061614-fin-and-intercom-plans-explained)
- [Intercom: billable outcomes and rates](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes)
Section: https://sairo.app/compare/sairo-vs-intercom#pricing
## What the listed charges look like at work.
Illustrative support workload: one website, one paid Intercom Essential seat, and 50% of new conversations producing a $0.99 Fin support outcome. That percentage is an assumption, not a measured resolution rate. Sairo uses Starter through 500 conversations and Pro for 2,000. All other Sairo allowances must also fit.
Illustrative monthly subscription + support AI usage · same assumed incoming chat volume
| New website conversations / month | Sairo | Intercom Essential + Fin |
| --- | --- | --- |
| 100 conversations | $49 Starter; 500-conversation allowance | $88.50 $39 seat + 50 × $0.99 |
| 500 conversations | $49 Starter; allowance fully used | $286.50 $39 seat + 250 × $0.99 |
| 2,000 conversations | $149 Pro; allowance fully used | $1,029 $39 seat + 1,000 × $0.99 |
### The calculation is visible; the assumptions matter.
Intercom total = $39 × full seats + $0.99 × billable support outcomes. This example excludes sales qualification outcomes ($9.99 each), voice, other add-ons, taxes and staffing. Fewer Fin outcomes reduce its charge; more seats increase it. These products do not have identical features or demonstrated equivalent answer quality.
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Intercom: monthly seats and plan inclusions](https://www.intercom.com/help/en/articles/9061614-fin-and-intercom-plans-explained)
- [Intercom: billable outcomes and rates](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes)
Section: https://sairo.app/compare/sairo-vs-intercom#cost-example
## The feature matrix.
Sairo’s advantage is an included website-support workflow with fewer separately priced components. Intercom has broader channel and connected-action capabilities.
Sairo and Intercom · capabilities and plan boundaries
| Capability | Sairo | Intercom with Fin |
| --- | --- | --- |
| Website AI answers | Included from Free Public pages, confirmed facts and saved answers | Available Configured Fin knowledge and guidance |
| Live chat and shared inbox | Included from Free A specialist can join the same chat | Included in helpdesk plans Essential from $39/seat/month |
| Remove vendor attribution | Included from Starter $49/month plan | Advanced and Expert From $99/seat/month, plus Fin usage |
| Usage at the limit | No automatic overage New activity at the limit pauses | Usage charges Fin supports configurable reminders and hard limits |
| Client website capacity | 3 sites on Pro 10 on Agency; scoped project access | Workspace and brand setup Check the required plan |
| Connect an external AI tool | OAuth MCP Supported workspace reads and writes | Remote MCP server Supported operations; US-hosted workspaces |
| Customer-facing external actions | Not in the standard widget No private order or billing connector | Available Configured data and MCP connectors |
| Support channels | Website chat Optional speech-to-text dictation | Broader channel coverage Chat, email and additional paid channels |
Source references
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Intercom: monthly seats and plan inclusions](https://www.intercom.com/help/en/articles/9061614-fin-and-intercom-plans-explained)
- [Intercom: attribution removal on Advanced and Expert](https://www.intercom.com/help/en/articles/15432088-your-workspace-settings)
- [Intercom: billable outcomes and rates](https://www.intercom.com/help/en/articles/8205718-fin-ai-agent-outcomes)
- [Intercom: remote MCP server](https://developers.intercom.com/docs/guides/mcp)
- [Intercom: Fin MCP connectors and external actions](https://www.intercom.com/help/en/articles/11461635-add-mcp-connectors-for-popular-apps-or-custom-mcps)
Section: https://sairo.app/compare/sairo-vs-intercom#comparison
## Make it yours. Keep it readable.
Sairo Pro and higher include six live-preview theme presets and 11 contrast checks, with required accessible labels protected and warnings before risky color changes are saved. These are implemented safeguards; our accessibility report remains a draft pending manual validation. We have not measured other vendors against the same checks.
- [Try all six chatbot themes](https://sairo.app/features/chatbot-themes#theme-preview)
- [Read the draft accessibility report](https://sairo.app/accessibility-report)
Section: https://sairo.app/compare/sairo-vs-intercom#appearance
## The sources behind the numbers.
Published by Sairo. Prices and capabilities were checked on 6 September 2026 against our active plan catalogue, implemented features and the vendors’ official documentation. Prices are a dated snapshot in USD, on monthly billing, before tax. Annual discounts, negotiated contracts and third-party subscriptions are excluded. Check the linked pricing pages before purchase.
A Sairo conversation, a Fin outcome, a Tidio AI or human-service conversation and a Chatbase message credit measure different events. Examples state their assumptions and compare only the listed charges. They do not establish equivalent capacity, answer quality or total operating cost.
This is a first-party comparison, not an independent product trial. We have not established that Sairo is more accurate, faster or more accessible than these vendors. Undocumented features are unverified, not absent. Product names belong to their respective owners; no affiliation or endorsement is implied.
- [Editorial and corrections policy](https://sairo.app/editorial-policy)
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Report a comparison correction](https://sairo.app/contact?topic=support)
Section: https://sairo.app/compare/sairo-vs-intercom#methodology
## Common questions
### Is Sairo cheaper than Intercom?
Sairo Starter is $49 per month including 500 conversations. Intercom Essential is $39 per full seat per month on monthly billing, plus Fin support outcomes at $0.99 each. In the displayed one-seat, 500-chat example with 250 billable support outcomes, the listed charges are $49 and $286.50 respectively. Your actual usage, channels and required features can change the comparison.
### Does every Fin conversation cost $0.99?
No. Fin charges for defined outcomes, rather than every incoming conversation. Standard support resolutions and configured procedure handoffs are $0.99; sales qualifications are $9.99. Other use cases have different terms. The worked example assumes only the $0.99 support outcomes.
### Can Sairo replace the entire Intercom platform?
Sairo covers website answers, live chat, leads and knowledge maintenance. It does not reproduce every Intercom channel, workflow or private customer-system action. Check those dependencies before migrating.
Related pages
- [Sairo vs Intercom, Tidio & Chatbase: feature and price comparison](https://sairo.app/compare)
- [Sairo vs Tidio Lyro: pricing, AI allowances and features](https://sairo.app/compare/sairo-vs-tidio)
- [Sairo vs Chatbase: pricing, branding and feature comparison](https://sairo.app/compare/sairo-vs-chatbase)
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat)
---
# Sairo vs Tidio.
Canonical page: https://sairo.app/compare/sairo-vs-tidio
Published: 2026-09-06
Updated: 2026-09-06
Get recurring AI answers and human support in one plan. Sairo Free renews its 50-conversation allowance every month, and Starter includes 500. See how Tidio’s separate service and Lyro quotas compare.
- [Compare the numbers](#pricing)
- [Start with Sairo Free](https://sairo.app/signup?plan=free)
## One allowance for the whole conversation.
Sairo counts a new website chat once, including follow-up messages and human handoff in that session. Tidio meters Lyro AI conversations and human-replied service conversations separately. Both Tidio combinations below include its smallest recurring Lyro quota.
USD · monthly billing · checked 6 September 2026 · taxes excluded
| Monthly cost & capacity | Sairo Starter | Tidio Free + Lyro | Tidio Starter + Lyro |
| --- | --- | --- | --- |
| Combined monthly price | $49 AI and human support included | $39 $0 service + $39 Lyro | $68 $29 service + $39 Lyro |
| Recurring AI capacity | 500 conversations Shared with human support | 50 AI conversations Separate Lyro quota | 50 AI conversations Separate Lyro quota |
| Human support capacity | Same 500 conversations Handoff does not use a second unit | 50 service conversations Human-replied chats / month | 100 service conversations Human-replied chats / month |
| Team access | $0 per-seat charge Included in the plan | 10 seats Included | 10 seats Included |
| Sairo / Tidio attribution | Removal included No separate branding fee | Tidio attribution Check removal eligibility | Tidio attribution Check removal eligibility |
### Tidio has a lower-priced combination, too.
Tidio Free plus the smallest Lyro add-on starts at $39/month, below Sairo Starter. Sairo Starter’s advantage is the larger shared conversation allowance and included attribution removal. The $68 Tidio Starter combination adds service capacity and features; it is not the minimum price for using Lyro. Quotas count different events, so this is not a claim of a 10× capacity advantage.
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Tidio: pricing, AI allowances and plan inclusions (select Monthly)](https://www.tidio.com/pricing/)
Section: https://sairo.app/compare/sairo-vs-tidio#pricing
## Free AI that comes back next month.
Tidio’s first 50 Lyro conversations are a one-time allowance. Sairo’s Free allowance renews each calendar month. This table assumes the first month’s allocation is used and no paid upgrade is made; unused Sairo allowance does not roll over.
Free-plan AI allowance · assuming 50 conversations used in month one
| Free AI allowance | Sairo Free | Tidio Free |
| --- | --- | --- |
| Month one | 50 conversations AI and human support share this limit | 50 Lyro conversations One-time AI allocation |
| Month two: new AI allowance | 50 conversations Monthly renewal | 0 new AI conversations Paid Lyro quota needed after initial 50 |
| Ongoing free human support | Included Within each month’s 50 conversations | Included 50 human-replied service conversations/month |
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Tidio: pricing, AI allowances and plan inclusions (select Monthly)](https://www.tidio.com/pricing/)
Section: https://sairo.app/compare/sairo-vs-tidio#free-plan
## The feature matrix.
Sairo combines website knowledge, corrections and a human queue. Tidio also provides live chat and AI handoff, with store actions and automation available through its product and add-on structure.
Sairo and Tidio · implemented workflow and published availability
| Capability | Sairo | Tidio / Lyro |
| --- | --- | --- |
| Website knowledge and corrections | Included from Free Pages, business facts and saved answers | Available Lyro knowledge and guidance |
| Recurring AI on the free plan | Included 50 new conversations each month | One-time AI allocation Recurring Lyro is paid |
| Live chat and human handoff | Included from Free Shared transcript and specialist queue | Available Lyro hands off to the live team |
| Several client projects | From Pro: $149/month 3 sites with scoped project access | Multiproject on Plus From $300/month plus usage |
| Brand appearance | Paid attribution removal Full theme editor from Pro | Basic customization Removal add-on where eligible; custom branding on Plus |
| Private store and booking actions | Not in the standard widget Guidance from public website knowledge | Available with configuration Shopify and Calendly action templates |
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Tidio: pricing, AI allowances and plan inclusions (select Monthly)](https://www.tidio.com/pricing/)
- [Tidio: Lyro knowledge and human handoff](https://help.tidio.com/hc/en-us/articles/9003475527196-Lyro-the-conversational-AI-agent)
- [Tidio: Shopify, Calendly and other action templates](https://help.tidio.com/hc/en-us/articles/23091021128732-Lyro-Action-templates)
Section: https://sairo.app/compare/sairo-vs-tidio#comparison
## Make it yours. Keep it readable.
Sairo Pro and higher include six live-preview theme presets and 11 contrast checks, with required accessible labels protected and warnings before risky color changes are saved. These are implemented safeguards; our accessibility report remains a draft pending manual validation. We have not measured other vendors against the same checks.
- [Try all six chatbot themes](https://sairo.app/features/chatbot-themes#theme-preview)
- [Read the draft accessibility report](https://sairo.app/accessibility-report)
Section: https://sairo.app/compare/sairo-vs-tidio#appearance
## The sources behind the numbers.
Published by Sairo. Prices and capabilities were checked on 6 September 2026 against our active plan catalogue, implemented features and the vendors’ official documentation. Prices are a dated snapshot in USD, on monthly billing, before tax. Annual discounts, negotiated contracts and third-party subscriptions are excluded. Check the linked pricing pages before purchase.
A Sairo conversation, a Fin outcome, a Tidio AI or human-service conversation and a Chatbase message credit measure different events. Examples state their assumptions and compare only the listed charges. They do not establish equivalent capacity, answer quality or total operating cost.
This is a first-party comparison, not an independent product trial. We have not established that Sairo is more accurate, faster or more accessible than these vendors. Undocumented features are unverified, not absent. Product names belong to their respective owners; no affiliation or endorsement is implied.
- [Editorial and corrections policy](https://sairo.app/editorial-policy)
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Report a comparison correction](https://sairo.app/contact?topic=support)
Section: https://sairo.app/compare/sairo-vs-tidio#methodology
## Common questions
### Why choose Sairo over Tidio for website AI?
Sairo provides a recurring free conversation allowance and combines AI and human support in one paid conversation quota. Starter includes 500 conversations for $49/month and removable Sairo attribution. Tidio can be a stronger fit for configured store actions, visual Flows and broader support channels.
### Is Tidio Lyro free every month?
Tidio includes an initial 50 Lyro conversations once. After those are used, a recurring paid Lyro quota is needed. Its free human-service quota is separate and monthly. Sairo Free includes 50 new conversations each month, shared by AI and human support.
### Does Tidio always cost more than Sairo?
No. Tidio Free with the smallest Lyro add-on starts at $39/month, compared with Sairo Starter at $49/month. Sairo includes a larger shared conversation allowance at that tier, but the units and features differ. Compare the full workload and plan requirements.
Related pages
- [Sairo vs Intercom, Tidio & Chatbase: feature and price comparison](https://sairo.app/compare)
- [Sairo vs Intercom Fin: pricing and feature comparison](https://sairo.app/compare/sairo-vs-intercom)
- [Sairo vs Chatbase: pricing, branding and feature comparison](https://sairo.app/compare/sairo-vs-chatbase)
- [AI website chatbot for agencies](https://sairo.app/solutions/agencies)
---
# Sairo vs Chatbase.
Canonical page: https://sairo.app/compare/sairo-vs-chatbase
Published: 2026-09-06
Updated: 2026-09-06
Put your brand on your website assistant without a separate attribution-removal subscription. Sairo includes that control on paid plans, with live chat and knowledge management available from Free.
- [Compare the numbers](#pricing)
- [Start with Sairo Free](https://sairo.app/signup?plan=free)
## Your brand, without a $99 add-on.
For an assistant without the vendor’s powered-by attribution, compare Sairo Starter with Chatbase Hobby plus its removal add-on. This is a comparison of listed subscription charges for that configuration, not identical feature sets or usage capacity.
USD · monthly billing · checked 6 September 2026 · taxes excluded
| Monthly subscription cost | Sairo Starter | Chatbase Hobby |
| --- | --- | --- |
| Base plan | $49 / month Monthly billing | $40 / month Monthly billing |
| Remove vendor attribution | $0 extra Included on paid plans | $99 / month Separate removal add-on |
| Total with attribution removed | $49 / month $49 + $0 | $139 / month $40 + $99 |
| Included usage | 500 conversations / month Follow-ups share the same conversation unit | 700 message credits / month Each AI reply consumes model-dependent credits |
| Free-plan usage | 50 conversations / month On Sairo Free | 50 message credits / month On Chatbase Free |
### $90 less per month for these attribution-free configurations.
Calculated as $139 − $49, before tax. Chatbase Hobby alone costs less than Sairo Starter ($40 vs $49) when you keep its attribution. Additional usage and features can change the total. A message credit is not a conversation: Chatbase credit consumption depends on the model and number of replies.
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Chatbase: monthly plans, credits and branding add-on](https://www.chatbase.co/pricing)
- [Chatbase: sources and model-dependent message credits](https://www.chatbase.co/docs/faq/faq)
Section: https://sairo.app/compare/sairo-vs-chatbase#pricing
## The feature matrix.
Sairo brings human follow-up into the entry workflow. Chatbase also has a helpdesk, internal assistance and connected actions; the table shows where those features sit in its current plans.
Sairo and Chatbase · feature availability and published plan requirements
| Capability | Sairo | Chatbase |
| --- | --- | --- |
| Built-in human inbox | Included from Free Live chat, specialists and offline requests | Standard plan and above Built-in helpdesk from $150/month |
| Paid attribution removal | Included from Starter No separate add-on | $99/month add-on Separate from Enterprise white-label features |
| Website knowledge and corrections | Included from Free Pages, confirmed facts and saved answers | Available Websites, files, Q&A and other sources |
| Internal AI assistance | Ask Sairo Supported operations within workspace permissions | Backstage Internal agent experience; not absent |
| Higher-tier included capacity | Pro: $149/month 3 websites; 2,000 conversations | Standard: $150/month 1 agent; 4,000 credits; 3 members |
| Usage beyond allowance | No automatic overage New activity at the limit pauses | Optional automatic recharge $40 per 1,000 credits |
| Customer billing and account actions | Not in the standard widget Public knowledge and internal workspace tools | Connected integrations Including Stripe billing workflows |
| Voice and other channels | Website chat Optional dictation produces editable text | Voice and telephony on Standard Additional channel and usage terms |
Source references
- [Sairo: current plans and allowances](https://sairo.app/pricing)
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Chatbase: monthly plans, credits and branding add-on](https://www.chatbase.co/pricing)
- [Chatbase: channels, helpdesk and Backstage](https://www.chatbase.co/)
- [Chatbase: sources and model-dependent message credits](https://www.chatbase.co/docs/faq/faq)
- [Chatbase: Stripe billing actions](https://www.chatbase.co/blog/chatbase-stripe-integration-ai-agents-billing-support)
Section: https://sairo.app/compare/sairo-vs-chatbase#comparison
## Make it yours. Keep it readable.
Sairo Pro and higher include six live-preview theme presets and 11 contrast checks, with required accessible labels protected and warnings before risky color changes are saved. These are implemented safeguards; our accessibility report remains a draft pending manual validation. We have not measured other vendors against the same checks.
- [Try all six chatbot themes](https://sairo.app/features/chatbot-themes#theme-preview)
- [Read the draft accessibility report](https://sairo.app/accessibility-report)
Section: https://sairo.app/compare/sairo-vs-chatbase#appearance
## The sources behind the numbers.
Published by Sairo. Prices and capabilities were checked on 6 September 2026 against our active plan catalogue, implemented features and the vendors’ official documentation. Prices are a dated snapshot in USD, on monthly billing, before tax. Annual discounts, negotiated contracts and third-party subscriptions are excluded. Check the linked pricing pages before purchase.
A Sairo conversation, a Fin outcome, a Tidio AI or human-service conversation and a Chatbase message credit measure different events. Examples state their assumptions and compare only the listed charges. They do not establish equivalent capacity, answer quality or total operating cost.
This is a first-party comparison, not an independent product trial. We have not established that Sairo is more accurate, faster or more accessible than these vendors. Undocumented features are unverified, not absent. Product names belong to their respective owners; no affiliation or endorsement is implied.
- [Editorial and corrections policy](https://sairo.app/editorial-policy)
- [Sairo: implemented capabilities and limits](https://sairo.app/product-facts)
- [Report a comparison correction](https://sairo.app/contact?topic=support)
Section: https://sairo.app/compare/sairo-vs-chatbase#methodology
## Common questions
### How much does it cost to remove the vendor branding?
In the checked monthly pricing, Sairo Starter is $49/month with attribution removal included. Chatbase Hobby is $40/month plus a $99/month removal add-on, or $139/month. The $90 difference applies to those listed configurations before tax; the products have different features and usage allowances.
### Are 700 Chatbase credits more than 500 Sairo conversations?
These units cannot be directly ranked. Chatbase charges credits per AI response at a model-dependent rate. Sairo counts new conversations, with follow-up messages in the same chat sharing one unit. Estimate the number and length of chats and required features before comparing capacity.
### Does Chatbase have live support and an internal assistant?
Yes. Chatbase lists a built-in helpdesk on Standard and higher plans and presents Backstage as an internal agent experience. Sairo’s advantage here is that its human inbox and live chat are available from Free, not that Chatbase lacks them.
Related pages
- [Sairo vs Intercom, Tidio & Chatbase: feature and price comparison](https://sairo.app/compare)
- [Sairo vs Intercom Fin: pricing and feature comparison](https://sairo.app/compare/sairo-vs-intercom)
- [Sairo vs Tidio Lyro: pricing, AI allowances and features](https://sairo.app/compare/sairo-vs-tidio)
- [Agency chatbot branding and client identity](https://sairo.app/features/agency-branding)
---
# Sairo on your devices.
Canonical page: https://sairo.app/apps
Published: 2026-09-09
Updated: 2026-09-09
Use Sairo in your browser today. Our companion apps for iPhone, iPad, Mac, Windows and Android are moving through testing and release preparation. Check the status below before looking for a download.
- [Open the web app](https://sairo.app/login)
- [Ask about app access](https://sairo.app/contact?topic=support)
## Our focus is getting the apps ready.
Website feature development is paused while we complete testing, distribution and store approval for the four app platforms. We continue to maintain the existing website and address reliability, security and accessibility issues.
The web app remains available. The status on this page records our release progress as of 9 September 2026; a test build or a review submission does not mean a public app is available.
- [Explore the current website features](https://sairo.app/features)
- [Read product capabilities and limits](https://sairo.app/product-facts)
Section: https://sairo.app/apps#release-focus
## iPhone and iPad: internal testing.
Sairo is in an internal TestFlight trial with invited testers. Installation checks on physical devices are still being completed. A public App Store release is not yet available.
Existing testers should use their current invitation. For everyone else, the web app is available in your browser while we complete the iOS release.
Section: https://sairo.app/apps#ios
## Mac: App Store review follow-up.
The Mac app has reached App Store review, and we are preparing the additional information needed to continue that process. Approval and public availability are still pending.
We will add a verified customer download or store link here when the release is ready. Internal Mac builds are not a public release.
Section: https://sairo.app/apps#macos
## Windows: release preparation.
Internal Windows installers have been built. We are preparing the signed customer release, installation checks and distribution channel.
A public Windows download is not yet available. This page will link to the verified customer release once it is ready.
Section: https://sairo.app/apps#windows
## Android: release preparation.
Android test builds are available to the development team. Release signing, device testing and Google Play publication are still being completed.
A public Google Play release is not yet available. Use the web app while we finish the Android release.
Section: https://sairo.app/apps#android
## One Sairo account, with access set by your team.
The companion apps use existing Sairo accounts and workspace permissions. The workflows available on each device depend on the released app version and your role; website feature availability does not imply that every native app includes the same controls.
This mobile beta includes foreground live updates. Background push notifications and native file uploads and exports are not included yet. Release notes will describe the supported scope of each public version.
- [Read the app privacy information](https://sairo.app/privacy)
- [Get help with app access](https://sairo.app/contact?topic=support)
Section: https://sairo.app/apps#using-the-apps
## Common questions
### Can I use Sairo while the apps are being prepared?
Yes. Sign in to the web app in your browser. Existing website features remain available while native app release work continues.
### Where are the App Store, Google Play and Windows download links?
Public native releases have not yet been verified. We will add usable store and download links on this page when the corresponding release is available.
### Are new website features being added during this phase?
New website features are paused. Our focus is releasing the iOS, macOS, Windows and Android apps, while continuing maintenance of the existing service.
Related pages
- [AI website chatbot and live chat features](https://sairo.app/features)
- [Sairo product facts, capabilities and limits](https://sairo.app/product-facts)
- [Sairo privacy policy](https://sairo.app/privacy)
- [Contact Sairo](https://sairo.app/contact)
---
# A clear route to what you need.
Canonical page: https://sairo.app/sitemap
Updated: 2026-09-09
Browse the complete public site by topic. Explore the current product, check app availability, find instructions for your website or connect an AI application.
## Start here.
- [Sairo home](https://sairo.app/): A website assistant with a human next step.
- [AI website chatbot and live chat features](https://sairo.app/features): Explore website AI answers, live chat, Ask Sairo, lead follow-up and the OAuth MCP connection for Claude, with knowledge and access controls for your team.
- [How Sairo AI chat and live handoff work](https://sairo.app/how-it-works): Try Sairo on your website, verify its sources, install the assistant, enable human handoff and improve answers with Ask Sairo or a connected AI application.
- [Plans and pricing](https://sairo.app/pricing)
- [Frequently asked questions](https://sairo.app/faq)
- [Contact Sairo](https://sairo.app/contact)
Section: https://sairo.app/sitemap#start
## Desktop and mobile apps.
Check release availability while iOS, macOS, Windows and Android distribution work continues.
- [All app release statuses](https://sairo.app/apps)
- [iPhone and iPad](https://sairo.app/apps#ios)
- [Mac](https://sairo.app/apps#macos)
- [Windows](https://sairo.app/apps#windows)
- [Android](https://sairo.app/apps#android)
Section: https://sairo.app/sitemap#apps
## Product features.
- [Website knowledge base for AI chat](https://sairo.app/features/website-knowledge): See how Sairo combines indexed website pages, confirmed facts, and saved answers into a controlled knowledge base for your website chatbot.
- [Website chatbot lead capture and follow-up](https://sairo.app/features/lead-generation): Capture visitor contact details with conversation context, then assign owners, track lead stages, and plan follow-up in Sairo.
- [Live chat software for AI chatbot handoff](https://sairo.app/features/live-chat): Enable live chat per website, assign specialists, move visitors from AI answers to a person, and keep one complete transcript in Sairo.
- [Shared AI and live chat inbox for website teams](https://sairo.app/features/conversation-inbox): Review AI and live chat transcripts in Sairo’s shared inbox, filter by site and outcome, assign teammates, and keep internal notes in context.
- [Website chatbot analytics and outcomes](https://sairo.app/features/chatbot-analytics): Track Sairo conversation volume, captured leads, recorded outcomes, and daily trends, with site-scoped reporting and clear metric definitions.
- [Agency chatbot branding and client identity](https://sairo.app/features/agency-branding): Understand Sairo’s agency, project, and site branding controls, including display names, accents, logos, support details, and Sairo attribution.
- [Find unanswered chatbot questions and content gaps](https://sairo.app/features/knowledge-gaps): Use Sairo’s unanswered-question workflow to find missing website information, add approved answers, and check whether the next visitor gets better help.
- [Ask Sairo: AI assistant for your chatbot workspace](https://sairo.app/features/ai-workspace-assistant): Find visitor questions, correct chatbot answers, update website knowledge and manage follow-ups in a conversation with Ask Sairo, with review and undo.
- [Custom chatbot themes with accessibility checks](https://sairo.app/features/chatbot-themes): Customize Sairo with six chatbot themes, colors, fonts, layouts and labels. Preview changes and check contrast before saving.
Section: https://sairo.app/sitemap#features
## Solutions.
- [Website chatbot solutions for teams and agencies](https://sairo.app/solutions): Find the right Sairo workflow for agencies, service businesses, and support teams, with AI answers, per-site live chat, shared inboxes, and controlled access.
- [AI website chatbot for agencies](https://sairo.app/solutions/agencies): Manage AI assistants and live chat across client websites with per-site specialists, project permissions, knowledge controls, branding, and shared reporting.
- [Website chatbot for service businesses](https://sairo.app/solutions/service-businesses): Help visitors find service information, share contact details, and move from Sairo’s AI assistant to a live specialist in the same website conversation.
- [AI website assistant for customer support](https://sairo.app/solutions/customer-support): Connect visitors with published help content, hand enabled conversations to live specialists, and review AI and human replies in one support inbox.
- [AI website assistant for ecommerce information](https://sairo.app/solutions/ecommerce): Use Sairo to answer published product and policy questions, identify missing information, and offer per-site live chat with an assigned specialist.
- [AI website chatbot for SaaS marketing and help](https://sairo.app/solutions/saas): Help SaaS website visitors understand published features and setup guidance, capture product enquiries, and identify gaps in public documentation.
Section: https://sairo.app/sitemap#solutions
## Integrations and website installation.
- [Sairo integrations: website installation, Claude and MCP](https://sairo.app/integrations): Add Sairo to your website with a script, or connect your workspace to Claude and compatible MCP applications with OAuth. Explore setup guides for both.
- [Add an AI chatbot to WordPress](https://sairo.app/integrations/wordpress): Add Sairo to a WordPress website with a script snippet. Check WordPress.com code restrictions, verify the website, and test the published installation.
- [Add an AI chatbot to Webflow](https://sairo.app/integrations/webflow): Install Sairo on Webflow using footer custom code. Review access, publish the snippet, and test CMS pages, navigation, and visitor conversations.
- [Add an AI chatbot to a Wix website](https://sairo.app/integrations/wix): Set up Sairo through Wix Custom Code, choose the intended pages, and test the assistant on a published Wix site with a connected domain.
- [Add a website AI chatbot to Shopify](https://sairo.app/integrations/shopify): Use Sairo on Shopify storefront pages through a maintained theme script. Review public product and policy content without implying order-system access.
- [Add an AI chatbot to Squarespace](https://sairo.app/integrations/squarespace): Install Sairo with Squarespace footer code injection, check your plan’s access, and validate the assistant on the published website.
- [Add an AI chatbot to a Framer website](https://sairo.app/integrations/framer): Set up Sairo in Framer’s Custom Code settings, select where it runs, and test the published site across navigation and responsive layouts.
- [Sairo MCP server for Claude and AI applications](https://sairo.app/integrations/mcp): Connect Sairo to Claude and compatible MCP clients with OAuth. Search conversations and knowledge, prepare updates, and control workspace access.
- [Connect an AI application](https://sairo.app/connect): Copy the Sairo server URL and choose the connection setup.
Section: https://sairo.app/sitemap#installation
## Practical guides.
- [AI chatbot and live chat setup guides](https://sairo.app/guides): Set up Sairo, correct chatbot answers with Ask Sairo, connect Claude through MCP, configure live chat and test your website assistant before launch.
- [How to add an AI chatbot to your website](https://sairo.app/guides/add-ai-chatbot-to-website): A step-by-step guide to adding Sairo: verify website ownership, review indexed sources, configure the assistant, install the snippet, and test replies.
- [How to prepare website content for an AI chatbot](https://sairo.app/guides/prepare-website-for-ai): Prepare useful website knowledge for an AI chatbot by fixing conflicting facts, making key pages readable, excluding stale content, and testing answers.
- [How to test an embedded chatbot for accessibility](https://sairo.app/guides/test-chatbot-accessibility): Test an embedded chatbot with a keyboard, screen reader, browser zoom, and reduced motion, including focus behavior and interference with the host page.
- [How to reduce unsupported chatbot answers](https://sairo.app/guides/reduce-chatbot-hallucinations): Improve website chatbot answer reliability with source review, saved answers, missing-information tests, human handoff, and a practical regression set.
- [How to measure website chatbot performance](https://sairo.app/guides/measure-chatbot-performance): Build a practical chatbot measurement routine using conversation volume, captured leads, answer review, follow-up completion, and comparable date ranges.
- [Website chatbot cost and usage planning](https://sairo.app/guides/website-chatbot-cost): Plan website chatbot capacity using pages, refresh frequency, and estimated conversations. Understand model costs, team effort, and Sairo plan allowances.
- [Troubleshoot a website chatbot installation](https://sairo.app/guides/troubleshoot-chatbot-installation): Diagnose a missing chatbot launcher, blocked scripts, origin errors, failed responses, and poor source coverage with a clear Sairo troubleshooting sequence.
- [How agencies can manage client chatbots](https://sairo.app/guides/manage-client-chatbots): Build a repeatable agency chatbot and live chat workflow with client projects, scoped invitations, per-site specialists, knowledge ownership, and handover.
- [Website chatbot launch checklist](https://sairo.app/guides/chatbot-launch-checklist): Use an interactive, printable checklist to review chatbot sources, installation, accessibility, lead capture, live chat staffing, and handoff before launch.
- [How to set up live chat on a website](https://sairo.app/guides/set-up-live-chat): Set up Sairo live chat for one website: enable the feature, assign specialists, understand presence, test AI handoff, and operate the queue.
- [Verify website ownership for a chatbot](https://sairo.app/guides/verify-website-ownership): Verify a Sairo website using its DNS TXT record or verification file. Understand the exact values, common failures, and the next indexing step.
- [Video walkthroughs of Sairo](https://sairo.app/guides/walkthroughs): Five narrated walkthroughs, about a minute each: get an assistant live, teach it a better answer, take over a live conversation, turn an enquiry into a follow-up, and review what needs attention.
- [How to fix an incorrect chatbot answer with Sairo](https://sairo.app/guides/fix-incorrect-chatbot-answers): Find an incorrect visitor answer, supply approved wording in Ask Sairo, save the correction, retest related questions and undo a change when needed.
- [How to connect Sairo to Claude with MCP and OAuth](https://sairo.app/guides/connect-sairo-to-claude): Connect Claude or Claude Code to Sairo with a remote MCP server URL, sign in with OAuth, choose website access, test a request and manage the connection.
Section: https://sairo.app/sitemap#guides
## Comparisons and terminology.
- [Sairo vs Intercom, Tidio & Chatbase: feature and price comparison](https://sairo.app/compare): Compare Sairo, Intercom Fin, Tidio Lyro and Chatbase in side-by-side price and feature matrices. See free allowances, AI billing, live chat and branding costs.
- [AI chatbot vs live chat: compare and combine](https://sairo.app/compare/ai-chatbot-vs-live-chat): Compare AI chatbot answers with staffed live chat across coverage, response speed, context, staffing, and cost, then see how Sairo combines both.
- [Website chatbot vs FAQ page](https://sairo.app/compare/chatbot-vs-faq): Understand when to use a website FAQ, an AI chatbot, or both, with examples of content ownership, discoverability, follow-up, and maintenance.
- [Website chatbot glossary: knowledge, usage and workflows](https://sairo.app/glossary): Understand website chatbot terms including retrieval, embeddings, saved answers, citations, handoff, origins, conversation outcomes, and usage allowances.
- [Sairo vs Intercom Fin: pricing and feature comparison](https://sairo.app/compare/sairo-vs-intercom): Compare Sairo and Intercom Fin in price and feature tables. See included conversations, per-seat fees, AI outcome charges and worked monthly cost examples.
- [Sairo vs Tidio Lyro: pricing, AI allowances and features](https://sairo.app/compare/sairo-vs-tidio): Compare Sairo and Tidio Lyro with numeric price and feature matrices. See monthly AI allowances, free-plan renewal, live chat and client-site support.
- [Sairo vs Chatbase: pricing, branding and feature comparison](https://sairo.app/compare/sairo-vs-chatbase): Compare Sairo and Chatbase in pricing and feature matrices. See $49 vs $139 monthly attribution-free configurations, message credits and human support tiers.
Section: https://sairo.app/sitemap#compare
## About the service.
- [The Sairo logo](https://sairo.app/brand): Explore the idea behind the Sairo logo: its conversation shape, tonal signal point, framing corners, lowercase wordmark, motion, and accessible use.
- [Accessible chatbot design and testing](https://sairo.app/accessibility): Review Sairo’s keyboard, focus, screen reader, and motion behavior, plus practical steps to test the chatbot within your website’s accessibility review.
- [AI chatbot and live chat security controls](https://sairo.app/security): Review Sairo’s website verification, workspace permissions, AI change controls, OAuth connections, token revocation and server-side credential handling.
- [About Sairo](https://sairo.app/about): Sairo combines accessible AI website answers, per-site live chat, controlled knowledge, and practical conversation tools for businesses and agencies.
- [Sairo privacy policy](https://sairo.app/privacy): How Sairo collects, uses, shares, keeps and deletes account, website, conversation and AI processing data, and how to request access, correction or deletion.
- [Sairo service terms](https://sairo.app/terms): Terms for Sairo accounts, workspaces, acceptable use, AI-assisted answers, plans and billing, the free desktop and mobile apps, liability and cancellation.
- [Sairo cookie notice](https://sairo.app/cookies): Understand the essential cookies and local browser storage used for Sairo sign-in, workspace selection, appearance, and embedded conversations.
- [Performance](https://sairo.app/performance): Lighthouse scores, the numbers behind them, and what keeps the site fast.
- [Sairo accessibility statement](https://sairo.app/accessibility-statement): Read Sairo’s accessibility commitment, WCAG 2.2 AA target, current assessment status, known limitations and how to report an accessibility barrier.
- [Sairo accessibility report and VPAT draft](https://sairo.app/accessibility-report): Review Sairo’s draft WCAG 2.2 AA Accessibility Conformance Report, based on VPAT 2.5Rev, with criterion-level evidence and a manual validation plan.
- [Sairo product facts, capabilities and limits](https://sairo.app/product-facts): A factual reference for Sairo: current website capabilities, app release focus, human handoff, Ask Sairo, MCP connections, pricing and product limits.
- [How Sairo maintains guides and product information](https://sairo.app/editorial-policy): How Sairo attributes product guidance, uses primary references, labels examples, records updates and receives corrections to its public documentation.
Section: https://sairo.app/sitemap#company
Related pages
- [AI chatbot and live chat setup guides](https://sairo.app/guides)
- [AI website chatbot and live chat features](https://sairo.app/features)
- [Contact Sairo](https://sairo.app/contact)