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

# Customers

> Planned customer identity and profile categories for the Woes public API.

Customer APIs will help teams connect Woes support data to the users and accounts in their product.

## Planned resources

<CardGroup cols={2}>
  <Card title="Profiles" icon="user">
    Customer display name, email, and stable profile details.
  </Card>

  <Card title="External IDs" icon="fingerprint">
    IDs from your product, CRM, or data systems.
  </Card>

  <Card title="Traits" icon="list">
    Plan, environment, version, region, or other support-relevant metadata.
  </Card>

  <Card title="Channel identities" icon="combine">
    Live chat, Discord, and future channel identity mappings.
  </Card>
</CardGroup>

## Common use cases

| Use case                          | Result                                                           |
| --------------------------------- | ---------------------------------------------------------------- |
| Identify a customer from your app | Operators see who is asking for help.                            |
| Attach account context            | Support can route and prioritize with better information.        |
| Sync CRM traits                   | Woes stays aligned with the systems your team already uses.      |
| Connect channel identities        | Live chat and Discord activity can point to one support profile. |

## Privacy expectations

Only send customer data that helps support the conversation.

Avoid:

* Secrets.
* Full payment details.
* Unnecessary personal data.
* Data from unrelated accounts.
* Internal-only risk or scoring fields unless operators need them.

<Note>
  Customer identity is separate from widget conversation history authorization. Verified identity should not replace a per-conversation history secret.
</Note>