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.
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.
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.
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.
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.