Gorgias

Attify reads Gorgias through its API, read-only, with OAuth or 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

StoredGorgias
idticket id
started_atticket created_datetime
updated_atticket updated_datetime, the sync cursor
customerticket customer.id
channelticket channel
claimAI Agent's own tags, read as it sets them, when it took part (any ai_
outcome tag, or a message from it): ai_close ("closed without human
involvement") without ai_handover claims a resolution; ai_handover, or
a final outcome without ai_close, claims none; ai_processing or
ai_snooze alone is no outcome yet (no claim). No AI Agent: no vendor
claim, so the reconstructed claim applies
messagespublic messages, oldest first: stripped_text, else body_text. Internal
notes, failed or deleted messages, and replies sent by a rule (rule_id)
or a self-service flow (via self_service) are left out: nobody's reply
messages[].rolefrom_agent false: the customer; true: support
messages[].author"ai" when the sender is a user whose role is bot (AI Agent appears in the
help desk as a user of its own, "AI Agent Bot" by default and renameable,
so it is matched by id and role, never by name); "human" otherwise
reopensticket-reopened events, at their created_datetime
merged_fromtickets a ticket-merged event names, and messages in the ticket whose own
ticket_id is another ticket's (Gorgias deletes a merged ticket and moves
its messages into the survivor): those messages become a stored item of
their own, merged_into the survivor, so they are a contact, never part of
the survivor's conversation
ratingthe satisfaction survey's score (1 to 5) at scored_datetime; 4 or 5 is
satisfied. Customer satisfaction is its own signal: the merchant's question
asks about satisfaction, so it never confirms a resolution