Enable Chatlas

Chatlas brings your Atlas content to a website widget so visitors can chat with it in real time. Use the app toggle to activate or pause the experience and tailor the widget to your brand.

🧪 Test in staging first

Add staging domains to the allowlist and embed Chatlas in a non-production site before you go live. Once flows look good, add the public domain and redeploy.

Activate Chatlas

1. Open the Atlas you want to deploy via chat.
2. Navigate to the App tab and select Chatlas.
3. Toggle the app to Active.
4. (Optional) Adjust the widget messages, avatar, title, and colors to match your brand.
5. Switch to the Integration tab and add the domain(s) where the widget will be embedded.
6. Copy the embed code using the clipboard icon and paste it into your website before the closing </body> tag.
   • Optional: To embed in a Jupyter Notebook, paste the code into a cell and run it.
7. Select Save to confirm.

Deactivate Chatlas

1. Return to the same Chatlas integration panel.
2. Toggle the app back to Inactive.
3. Save your changes.

The app list shows a blue icon for active chatbots and a crossed-out red icon for inactive ones. Use it to confirm the current status at a glance.

Why enterprises use Chatlas

Chatlas is an Atlas-powered AI concierge that sits on top of your curated knowledge base and answers questions in natural language directly inside the widget. It ingests your published Atlas content, monitors updates automatically, and uses retrieval-augmented generation to return grounded, citation-rich responses while masking sensitive sources that you mark as private. Because it runs on the same governance stack as Atlas, security, data residency, and audit logging remain consistent with enterprise requirements.

Value pillars

• Always-on expertise: Deliver instant answers 24/7 without waiting for a live agent, reducing mean time-to-resolution and lowering contact center volume.
• Personalized context: Pass session metadata, CRM IDs, or entitlement tiers through the embed code so Chatlas tailors answers and escalation routes for each visitor.
• Actionable analytics: Conversation transcripts and intent dashboards show what customers struggle with, guiding new Atlas articles and product improvements.
• Safe handoffs: Built-in escalation rules let you route complex cases to Slack, Teams, or ticketing queues with the chat history attached so agents pick up midstream.

Ways to deploy Chatlas

1. Customer support: A SaaS company embedded Chatlas in its support portal and deflected 48% of “how-to” tickets by surfacing step-by-step Atlas guides instantly.
2. Customer success: An enterprise hardware manufacturer shares onboarding Atlases through Chatlas inside a gated partner site, helping field engineers troubleshoot equipment at the edge without downloading manuals.
3. Sales enablement: A financial services firm deployed Chatlas on product pages so prospects can ask compliance questions; qualified leads hand off to reps with complete context, shortening the sales cycle by two weeks.
4. Employee help desk: Internal Atlases that cover HR policies, IT setup, and procurement flow through Chatlas in the corporate portal, cutting repetitive chat volume for internal service desks by 35%.

When rolling out Chatlas, pilot in one region or business line, tune prompts and tone with local stakeholders, and monitor transcript tags to identify new automation opportunities. Pair success metrics (CSAT, resolution time, ticket deflection, ARR influenced) with qualitative win stories so leadership sees the compounded impact on customer engagement, support efficiency, and satisfaction.

🔐 Why domain allowlisting matters

Restrict Chatlas to trusted domains so malicious sites cannot impersonate your support team or hijack customer conversations. Allowlisting ensures visitor traffic, auth tokens, and analytics only flow through approved origins, which preserves your brand voice and keeps data in the right hands. Add both staging and production domains up front, review the list whenever a site changes, and coordinate updates with your security/IT team to prevent outages when new subdomains launch.

SEO and crawling safeguards

Chatlas generates conversational content that is great for humans but rarely useful for search engines. Wrap the widget container in a <div> marked with data-nosnippet and add rel="nofollow" to any links rendered inside the widget so crawlers ignore the dynamic replies. If the chat lives on a stand-alone landing page that you do not want indexed, set the page-level meta tag to <meta name="robots" content="noindex, nofollow"> and confirm the rule in your sitemap to keep the URL out of SERPs.

When embedding the widget on production pages, leave the core page content untouched and load Chatlas asynchronously so bots still see the original copy first. This avoids duplicate-content penalties and retains the ranking signals tied to your existing text, schema, and backlinks. If you reuse the same Atlas across multiple domains, vary the surrounding copy or use canonical tags to point search engines to the primary source. Review Search Console regularly: if impression or crawl stats dip after enabling Chatlas, tighten your robots rules or move the widget below the main body content. These guardrails keep the chat experience invisible to crawlers while preserving your hard-earned rankings.