From f03d4b10ecd589e8cd72515e3e12d3df48e6e6da Mon Sep 17 00:00:00 2001 From: tristantelleb Date: Tue, 4 Aug 2026 10:16:14 +0200 Subject: [PATCH 1/2] docs: open the Intercom messenger from in-docs "Chat with us" links Steer docs readers to the support chat instead of the Ask AI deflection email. Mintlify boots Intercom itself from `integrations.intercom`, so it owns `window.intercomSettings` and Intercom `custom_launcher_selector` is unavailable; a click delegate on links ending in #chat calls the global Intercom() API instead. Mirrors the #manage-cookies handling already in cookie-consent.js. - intercom-chat.js: capture-phase delegate for a[href$="#chat"], retries for up to 5s while the snippet boots, no-ops if the widget is blocked - docs.json: "Chat with us" navbar link - v3/general/support.mdx: Live Chat said the chat was dashboard-only; it runs on every docs page too `mint broken-links` unchanged at 172 in 50 files. Co-Authored-By: Claude Opus 5 --- docs.json | 4 +++ intercom-chat.js | 59 ++++++++++++++++++++++++++++++++++++++++++ v3/general/support.mdx | 6 +++-- 3 files changed, 67 insertions(+), 2 deletions(-) create mode 100644 intercom-chat.js diff --git a/docs.json b/docs.json index 7dee118..ece93dd 100644 --- a/docs.json +++ b/docs.json @@ -346,6 +346,10 @@ }, "navbar": { "links": [ + { + "label": "Chat with us", + "href": "#chat" + }, { "label": "Website", "href": "https://edenai.co/" diff --git a/intercom-chat.js b/intercom-chat.js new file mode 100644 index 0000000..5465a6a --- /dev/null +++ b/intercom-chat.js @@ -0,0 +1,59 @@ +/** + * "Chat with us" launcher for the Eden AI docs (Mintlify). + * + * How it works: + * Mintlify boots the Intercom messenger itself from `integrations.intercom` + * in docs.json, which means it owns `window.intercomSettings` — so Intercom's + * usual `custom_launcher_selector` option is not available to us. Instead we + * delegate clicks: any link ending in #chat opens the messenger through the + * global `Intercom()` API. Same pattern as the #manage-cookies link handled in + * cookie-consent.js. + * + * Used by the "Chat with us" navbar link (docs.json) and the Live Chat section + * of v3/general/support.mdx. + * + * Intercom is not consent-gated (see cookie-consent.js), so the messenger is + * available on first load. It can still be missing when a privacy extension + * blocks the widget or the snippet is mid-boot, so we poll briefly and then + * give up quietly rather than leaving a dead click that throws. + */ +(function () { + var SELECTOR = 'a[href$="#chat"]'; + var BOOT_TIMEOUT_MS = 5000; + var POLL_INTERVAL_MS = 150; + + // Mintlify is a SPA; guard against re-registering the listener on + // client-side navigation. + if (window.__edenaiChatLauncherLoaded) return; + window.__edenaiChatLauncherLoaded = true; + + function show() { + if (typeof window.Intercom !== "function") return false; + window.Intercom("show"); + return true; + } + + // The click can land before Mintlify's Intercom snippet has finished booting, + // so retry until it does or the deadline passes. + function showWhenReady(deadline) { + if (show()) return; + if (Date.now() > deadline) return; + setTimeout(function () { + showWhenReady(deadline); + }, POLL_INTERVAL_MS); + } + + // Capture phase so this wins over Mintlify's own anchor handling, which would + // otherwise treat #chat as an on-page heading link. + document.addEventListener( + "click", + function (e) { + var trigger = e.target.closest && e.target.closest(SELECTOR); + if (!trigger) return; + e.preventDefault(); + e.stopPropagation(); + showWhenReady(Date.now() + BOOT_TIMEOUT_MS); + }, + true + ); +})(); diff --git a/v3/general/support.mdx b/v3/general/support.mdx index c4be1ed..6fd89e0 100644 --- a/v3/general/support.mdx +++ b/v3/general/support.mdx @@ -15,14 +15,16 @@ import { TechArticleSchema } from "/snippets/TechArticleSchema.mdx"; proficiencyLevel="Intermediate" keywords={["Eden AI", "AI API", "rate limits", "billing", "monitoring"]} datePublished="2026-05-06T00:00:00Z" - dateModified="2026-05-07T00:00:00Z" + dateModified="2026-08-04T00:00:00Z" /> Eden AI offers several support channels depending on the nature of your question and your plan. ## Live Chat -A direct support chat is available in the [Eden AI dashboard](https://app.edenai.run/). Send your question and our team will respond as soon as possible. +The fastest way to reach us is the support chat, available on every page of this documentation and in the [Eden AI dashboard](https://app.edenai.run/). + +**[Chat with us](#chat)** or use the chat bubble in the bottom-right corner. Send your question and our team will respond as soon as possible. ## Status Page From 54117a4ee7a3f7ba580cf3e31fe8655ae43fd13b Mon Sep 17 00:00:00 2001 From: tristantelleb Date: Tue, 4 Aug 2026 10:21:19 +0200 Subject: [PATCH 2/2] docs(assistant): escalate to the docs support chat instead of email The assistant's Scope section pointed billing and account questions at edenai.co or "the in-app Intercom chat", so unanswered questions ended up in the Ask AI deflection contact form and reached us as Mintlify emails rather than as Intercom conversations. Replace it with an explicit Escalation section naming the chat available on the docs page itself. Note this steers what the assistant says; the deflection contact form is platform behaviour driven by the support/sales addresses in the Mintlify dashboard and has to be cleared there too. Co-Authored-By: Claude Opus 5 --- .mintlify/Assistant.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.mintlify/Assistant.md b/.mintlify/Assistant.md index da0e0ea..a63b7d3 100644 --- a/.mintlify/Assistant.md +++ b/.mintlify/Assistant.md @@ -39,6 +39,13 @@ OpenAI Python/TypeScript SDK (drop-in), LangChain, Claude Code, Continue.dev, Li ## Scope - Answer questions about Eden AI's API, features, SDKs, integrations, and documentation. -- For billing or account issues, direct users to [Eden AI Support](https://www.edenai.co/) or the in-app Intercom chat. - Eden AI is an API gateway, not a model training or fine-tuning platform. - If unsure, say so and refer to the API reference rather than guessing. + +## Escalation + +When a question is outside the documentation, send the user to the live support chat that runs on this page, not to email. + +This covers billing and invoicing, payment methods, quotas and limit increases, account, contract and plan questions, suspected outages, and anything else you cannot answer from the docs. + +Tell them to open it with the **Chat with us** link in the navbar or the chat bubble in the bottom-right corner, and mention that the team answers there. Link to [Support](/v3/general/support) when they want the full list of channels, including the status page and dedicated SLA support. Do not offer an email address as the escalation path.