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

# Start by role

Dovetail is used by whole organizations, not just research teams — and where you should start depends on the job you're doing.

Pick your role below for a short path: what you'll get out of Dovetail, the first three things to do, and one agent worth stealing before you build your own.

<CardGroup cols={3}>
  <Card title="Product management" href="#product-management">
    Decide what to build next.
  </Card>

  <Card title="Product design" href="#product-design">
    Ground design decisions in evidence.
  </Card>

  <Card title="User research" href="#user-research">
    Analyze faster, share wider.
  </Card>

  <Card title="Customer experience and support" href="#customer-experience-and-support">
    See what's actually breaking.
  </Card>

  <Card title="Sales and customer success" href="#sales-and-customer-success">
    Walk into every call informed.
  </Card>

  <Card title="Marketing" href="#marketing">
    Use your customers' own words.
  </Card>
</CardGroup>

<Info>
  Agents are not available on free plans. Everything else on this page works on any plan.
</Info>

***

## Product management

**What you'll get:** a ranked view of what's worth doing next, with the evidence and the revenue behind each item — instead of a backlog built from whoever asked loudest.

**Your first three things**

1. Create a [channel](/help/channels/channels-beta) over your support tickets, reviews, and survey responses. Channels 2.0 groups incoming feedback into **Ideas**, ranked by severity, frequency, how many accounts are affected, and ARR.
2. Open an idea and check the **Evidence** behind it before you commit — the original tickets and quotes are one click away. Send the idea straight to Jira or Linear when you're convinced.
3. Ask [Chat](/help/chat) the questions you'd normally assign to someone: *"What have customers actually said about \[feature]? Show me the quotes."*

**Steal this agent first:** [Feature request ARR calculator](/help/agents-use-cases/product-and-research) — when a request passes a mention threshold, it sums the ARR behind it and opens a ticket with the top quotes.

***

## Product design

**What you'll get:** the evidence behind a design decision, and a customer you can ask questions of before the first round of usability testing.

**Your first three things**

1. Create a [project](/help/projects) for your usability sessions and interviews. Recordings are transcribed and summarized automatically.
2. Mark the moments that matter as [highlights](/help/projects/highlights) — each one becomes a shareable video or audio clip you can drop into a critique or a [doc](/help/docs/getting-started-with-docs).
3. Build a [digital twin](/help/agents/digital-twins) of the segment you're designing for, then attach a mockup in [Chat](/help/chat) and ask it what it thinks. Every answer traces back to a real interview or ticket.

**Steal this agent first:** [Power user persona twin](/help/agents-use-cases/digital-twins-experts) — a twin that pushes back when a concept misses what long-time users actually care about.

***

## User research

**What you'll get:** the analysis busywork handled, and findings your stakeholders can self-serve instead of queuing for.

**Your first three things**

1. [Import your data](/help/projects/import-data-to-projects) into a project — interviews, usability sessions, survey responses. Set the project's **Context** so Dovetail's AI knows what you're investigating.
2. Work through [highlights](/help/projects/highlights) and [tags](/help/projects/project-tags) to build your evidence layer, then write up findings in a [doc](/help/docs/getting-started-with-docs) with a [highlight reel](/help/projects/highlight-reels) so people hear the customer, not your summary of them.
3. Point stakeholders at [Chat](/help/chat) — including [in Slack and Teams](/help/chat/chat-in-slack-and-teams) — so repeat questions stop landing in your inbox.

**Steal this agent first:** [Weekly research digest](/help/agents-use-cases/product-and-research) — pulls the week's findings, groups them by theme, and posts a summary to your product channel.

***

## Customer experience and support

**What you'll get:** the patterns underneath your ticket volume, and a way to tell customers when the thing they complained about is fixed.

**Your first three things**

1. Create a [channel](/help/channels/channels-beta) from your helpdesk — Zendesk, Intercom, Freshdesk, Front, and more connect directly, or import a CSV.
2. Use **Evidence** to check whether a spike is real, and the activity-over-time view to see exactly when it started.
3. Track CSAT, NPS, and sentiment over time on a [dashboard](/help/dashboards), then drill into the feedback driving a change.

When an idea moves to **Resolved**, use **Notify customers** to draft a personalized update to everyone whose feedback contributed to it.

**Steal this agent first:** [Known issues expert](/help/agents-use-cases/support-risk-quality) — @mention it mid-ticket with a bug description and it returns whether it's known, the ticket status, and any workaround.

***

## Sales and customer success

**What you'll get:** everything an account has ever told you, available before the call rather than buried in someone else's notes.

**Your first three things**

1. Connect your CRM so [contacts](/help/contacts/index) carry through to feedback — Dovetail enriches from Salesforce or HubSpot, so you can see company, plan tier, and ARR alongside what was said.
2. Ask [Chat](/help/chat) about an account or a segment: *"What are churned accounts saying about pricing compared to customers who expanded?"* Every answer is cited.
3. Connect Salesforce, Slack, or Gmail in Chat, so you can act on what you find — update a record or draft the follow-up — without leaving the conversation.

**Steal this agent first:** [Closed won CS handoff](/help/agents-use-cases/sales) — on close, it compiles stated goals, promises made, and concerns raised into a handoff doc and tags the CSM.

***

## Marketing

**What you'll get:** the exact language customers use about their problems, and proof for the stories you want to tell.

**Your first three things**

1. Create a [channel](/help/channels/channels-beta) across reviews, surveys, and NPS responses to see what customers say when nobody from your team is in the room.
2. Ask [Chat](/help/chat) with web search on to set customer language against what competitors are shipping and how the market is moving.
3. Track keyword frequency and sentiment over time on a [dashboard](/help/dashboards) to catch vocabulary shifting before a campaign goes out on the old words.

**Steal this agent first:** [Weekly customer language digest](/help/agents-use-cases/marketing-and-growth) — the phrases customers used this week, grouped by theme, each with a real quote.

***

## Where to go next

* [What is Dovetail?](/help/what-is-dovetail/index) for how Projects, Channels, Chat, and Agents fit together.
* [Agent use cases library](/help/agents-use-cases/index) for prompts organized by team, well beyond the one suggested for your role.
* [Dovetail terminology](/help/dovetail-terminology/index) if a word on this page is new to you.