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