mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-08-21 14:34:03 +00:00
434c86e2c3
Keep docs asset URLs repo-root-relative and pass images as literal MDX children so Mintlify can compile them through OptimizedImage under the /docs mount. Mintlify's official guidance says: “Image paths are root-relative from your docs repository.” It also says relative paths such as `./screenshot.png` are unsupported. See [Image embeds](https://www.mintlify.com/docs/create/image-embeds). The existing `/images/...` paths were correct. The failure came from passing them through custom-component string props, which kept Mintlify from seeing those images during its MDX transform. - fix hero, building-block, and Slack avatar images - preserve Slack avatar clipping - normalize Hermes and Company Brain icon sizing Tested with Mintlify validation, broken-link checks, and browser checks across every changed route.
39 lines
1.9 KiB
Text
39 lines
1.9 KiB
Text
---
|
|
title: "Automatic Support"
|
|
sidebarTitle: "Support"
|
|
description: "Company Brain chimes in on customer questions with answers from docs and tickets"
|
|
icon: "headset"
|
|
---
|
|
|
|
import { SlackThread, SlackMessage } from "/snippets/slack-message.mdx";
|
|
|
|
## The scenario
|
|
|
|
A customer question lands in `#support`. Nobody has to @mention the bot — it already has the answer from past tickets and the help docs.
|
|
|
|
## What happens
|
|
|
|
<SlackThread channel="#support" members={24}>
|
|
<SlackMessage name="Maya" color="#2BAC76" time="2:14 PM">
|
|
customer on the Pro plan is asking if they can export their full memory graph as CSV — do we support that?
|
|
</SlackMessage>
|
|
<SlackMessage bot hasAvatar time="2:14 PM">
|
|
<img src="/images/company-brain/supermemory-slack-icon.png" alt="" />
|
|
Yes — **Settings → Export → Full graph (CSV)**. Available on Pro and above. Same answer went out on ticket PLN-1842 last week if you want the exact wording.
|
|
</SlackMessage>
|
|
</SlackThread>
|
|
|
|
## What's really going on
|
|
|
|
This is [proactiveness (chime-in)](/company-brain/automations) plus a connected support tool (Plain) and public channel memory. The bot is already a member of `#support` (an admin invited it — it never joins on its own). It decided the answer was clear enough to speak without being asked, pulled the export path from docs in public channel memory, and cited a recent ticket from Plain.
|
|
|
|
Same channel scope rules apply: a public support channel writes durable learnings back to public channel memory; a private support channel keeps them scoped to that room's own memory. See [Permissions](/company-brain/permissions).
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Automations & proactiveness" icon="wand-magic-sparkles" href="/company-brain/automations">
|
|
How chime-in decides when to speak.
|
|
</Card>
|
|
<Card title="Connectors" icon="plug" href="/company-brain/connectors">
|
|
Wire up Plain and your help docs.
|
|
</Card>
|
|
</CardGroup>
|