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

# Product

> Capture feedback, link it to features, and close the loop with users.

Product teams use Custral to keep customer feedback tightly linked to the features and accounts it came from, and to notify the right people the moment something ships.

## What product runs on

<CardGroup cols={2}>
  <Card title="Feedback as an object" icon="cube" href="/data/objects/overview">
    Model feedback as a first-class object with [relations](/data/properties/select/relation) to accounts and features, and a [conversation property](/data/properties/select/conversation) linking each note to the thread it came from.
  </Card>

  <Card title="AI summarize & classify" icon="wand-magic-sparkles" href="/ai/property-agents/overview">
    A Summarize agent condenses each note; a Classify agent tags it by theme and urgency into a closed set.
  </Card>

  <Card title="A scoped product agent" icon="comments" href="/ai/chat-agents/overview">
    A chat agent scoped to your feedback and product objects answers "what are people asking for?" in the right voice.
  </Card>

  <Card title="Workflows" icon="bolt" href="/automation/workflows/overview">
    Auto-tag incoming feedback, route it to the product owner, and notify the reporter when the linked feature ships.
  </Card>

  <Card title="Reporting" icon="chart-line" href="/bi/reporting/overview">
    Rank requests by frequency and weight them by the revenue on the accounts they're linked to.
  </Card>

  <Card title="Tasks" icon="check-circle" href="/team/tasks/overview">
    Turn a request into trackable work with an owner and a due date, linked back to the feedback record.
  </Card>
</CardGroup>

## Set it up like this

<Steps>
  <Step title="Model feedback">
    Create a Feedback [object](/data/objects/overview) with relations to Contacts and Features and a [conversation](/data/properties/select/conversation) link.
  </Step>

  <Step title="Enrich automatically">
    Attach a [Summarize and a Classify agent](/ai/property-agents/overview) so every new note is condensed and tagged by theme and urgency.
  </Step>

  <Step title="Route and close the loop">
    A [workflow](/automation/workflows/overview) routes by tag to the owner and notifies reporters when the linked feature ships.
  </Step>

  <Step title="Prioritize with data">
    Build a [dashboard](/surfaces/views/types/dashboard) that ranks requests by frequency and revenue weight; drill any bar to the underlying records.
  </Step>
</Steps>

## Related

* [Objects & records](/data/objects/overview) · [Relation](/data/properties/select/relation) & [conversation](/data/properties/select/conversation) properties
* [Property auto-fill agents](/ai/property-agents/overview) · [Chat agents](/ai/chat-agents/overview)
* [Workflows](/automation/workflows/overview) · [Reporting](/bi/reporting/overview)


## Related topics

- [Product Updates](/product/overview.md)
- [Learn the Product](/start/onboarding/learn.md)
- [Getting Started](/dev/getting-started.md)
- [Stripe](/integrations/stripe.md)
- [Chat Agents](/ai/chat-agents/overview.md)