slug: trengo
provider: Trengo
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Telecommunications
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: 3
edges:
- tag: Tickets
  spec_file: trengo-tickets-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.85
  evidence: GET /tickets listTickets; PATCH /tickets/{ticket_id}/assign assignTicket; PATCH /tickets/{ticket_id}/close
    closeTicket; schemas Ticket, Contact, Channel
  reason: Tickets here are customer conversations captured across channels and routed/assigned/closed
    by agents — squarely inbound customer contact routing and resolution.
- tag: Messages
  spec_file: trengo-messages-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.78
  evidence: POST /tickets/{ticket_id}/messages  sendMessage  Send a ticket message; "Manage tickets (conversations),
    contacts and profiles, messages ... across email, WhatsApp, live chat, voice, SMS, and social channels"
  reason: Operations read and post messages inside support tickets on an omnichannel shared-inbox platform
    — the inbound/outbound contact handling of customer service inquiry management, not marketing or telecom
    messaging infrastructure.
- tag: Contacts
  spec_file: trengo-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /contacts "List contacts"; POST /contacts "Create a contact"; PUT /contacts/{contact_id}
    "Update a contact"; schemas Contact, ContactList
  reason: Full CRUD over customer contact records in the engagement platform — maintenance of the customer/contact
    master record. Mapped to Customer Data Management; confidence moderate because contacts here also
    serve as conversation participants rather than a governed golden record.