# Freshdesk

Attify reads Freshdesk through its API, read-only, with an API token, for customer support. It is the customer's own system, so what Attify reads there is connected data: the strongest provenance, and what a vendor verification rests on.

## As a help desk, for customer support

| Stored            | Freshdesk                                                                   |
|-------------------|-----------------------------------------------------------------------------|
| id                | ticket `id`                                                                 |
| started_at        | ticket `created_at`                                                         |
| updated_at        | ticket `updated_at`, the sync cursor                                        |
| customer          | ticket `requester_id`                                                       |
| channel           | ticket `source` as its name (1 email, 2 portal, 3 phone, 7 chat, ...)       |
| claim             | none: Freshdesk records no AI resolution field in its REST API (Freddy AI   |
|                   | Agent's outcomes are automation events only), so the claim is reconstructed |
| messages          | the ticket's description (`description_text`, the opening), then public     |
|                   | conversations oldest first (`body_text`). Private notes are left out        |
| messages[].role   | the opening and any `incoming` conversation or one by the requester: the    |
|                   | customer (an outbound email's opening is support's); anyone else: support   |
| messages[].author | "ai" only when Freshdesk lists the replying user as an agent of an AI or    |
|                   | bot type; any other reply is a person's. Freshdesk does not document how    |
|                   | Freddy AI Agent's replies are stored, so until that is seen live a reply    |
|                   | Freshdesk does not label as an AI agent's counts as a person's, and a       |
|                   | person's work never lands in the AI-only subject                            |
| reopens           | `stats.reopened_at` when Freshdesk sends it (its latest reopen; not in the  |
|                   | API reference); every other reopen is inferred from the conversation        |
| merged_into       | on a merged (secondary) ticket, the ticket its private merge note names     |
|                   | ("merged into ... #<id>", English only)                                     |
| merged_from       | tickets the primary's private merge note names, and conversations whose own |
|                   | `ticket_id` is another ticket's (Freshdesk moves a secondary's              |
|                   | conversations into the primary): those become a stored item of their own,   |
|                   | `merged_into` the primary, so they are a contact, never part of it          |
| rating            | the latest satisfaction rating's `ratings.default_question`: -103 to 103    |
|                   | (or 3 to 1 on a classic survey); Freshdesk's happy answers (101 to 103, or  |
|                   | 1) are satisfied. Customer satisfaction is its own signal: the question asks|
|                   | how satisfied the customer was, so it never confirms a resolution           |
