> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tasksmind.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Customer Support, Without the Leak

> How tasksmind splits a customer-reported bug into a plain-language update in your support channel and full technical detail in a separate dev channel.

The same underlying incident, told two ways: a plain-language update for the customer, and
progress detail for the engineers fixing it.

## The scenario

A customer posts in the Slack channel your team connects to a support project. tasksmind turns
that report into an incident, and the customer only ever sees a friendly status update in return,
never code, logs, or a stack trace.

## Two channel types, never both

An org owner or admin marks a channel as one or the other, from Slack or the dashboard. A channel
can't be both. Designating one refuses if the channel is already the other type.

```
@tasksmind connect support your-org/your-repo
```

The repo needs an on-call project set up in your dashboard already. Reports posted here become
incidents and fix PRs automatically. The difference is only in what gets said back into the
channel.

<CardGroup cols={2}>
  <Card title="Support channel" icon="message-circle">
    Friendly, plain-language status only. No code, no logs, no stack traces, no file paths.
  </Card>

  <Card title="Dev channel" icon="code">
    Root cause, file paths, and the PR link. Set with `@tasksmind set dev channel here` or from
    Settings in the dashboard.
  </Card>
</CardGroup>

## What it looks like

**In the customer-facing support channel**

**#support**

**Jordan (customer)** · 2:10 PM
hey, my export keeps failing and just says "something went wrong." anyone know what's up?

**tasksmind** <Icon icon="bot" size={14} /> · 2:11 PM
Thanks for flagging this. I've found the issue and I'm already working on a fix. I'll update this
thread as soon as it's resolved.

<br />

**In the connected dev channel**

**#eng**

**tasksmind** <Icon icon="bot" size={14} /> · 2:11 PM
New incident from `#support`: export failure reported by a customer. Root cause: the CSV export
job times out on accounts with more than \~50k rows, in `jobs/export.ts`.

**tasksmind** <Icon icon="bot" size={14} /> · 2:14 PM
Tests passed in the sandbox. Draft PR ready: **Approve** / **Request Changes** / **Stop** /
**Escalate** below.

<Note>
  `connect support` and `set dev channel here` are gated to org owners and admins. No one else
  can point tasksmind at a repo or open up the technical-detail channel.
</Note>

<CardGroup cols={2}>
  <Card title="From customer report to pull request" icon="git-pull-request" href="/use-cases/report-to-pr">
    The full investigate-to-PR pipeline this feeds into.
  </Card>

  <Card title="See everything tasksmind can do" icon="sparkles" href="/use-cases/overview">
    Back to the full use-case index.
  </Card>
</CardGroup>