slug: gorgias
provider: Gorgias
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 4
edges:
- tag: Surveys
  spec_file: gorgias-surveys-api-openapi.yml
  capability_id: BC-430.50
  capability_id_l1: BC-430
  capability_name: Customer Feedback Management
  confidence: 0.85
  evidence: GET /api/satisfaction-surveys  listSatisfactionSurveys  List satisfaction surveys
  reason: Operations create and list customer satisfaction surveys, which is squarely voice-of-customer
    / feedback capture attached to support interactions.
- tag: Tickets
  spec_file: gorgias-tickets-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.85
  evidence: 'POST /api/tickets  createTicket  Create ticket; schemas: Ticket, Customer, Meta'
  reason: Ticket lifecycle CRUD in an ecommerce helpdesk is the capture, routing and resolution of inbound
    customer contacts — customer inquiry management.
- tag: Messages
  spec_file: gorgias-messages-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.8
  evidence: POST /api/tickets/{id}/messages  createTicketMessage  Create a message on a ticket
  reason: Reading and posting messages on support tickets is the handling of inbound customer contacts
    and agent responses — customer inquiry management in a helpdesk.
- tag: Customers
  spec_file: gorgias-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.78
  evidence: 'POST /api/customers  createCustomer  Create customer; schemas: Customer, Meta'
  reason: Full CRUD over customer records in the support platform, which is the customer master used to
    associate conversations — customer data management. Not lifecycle or segmentation, as there is no
    campaign or segment semantics.