slug: helpscout
provider: Help Scout
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: 3
edges:
- tag: Conversations
  spec_file: helpscout-conversations-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.88
  evidence: GET /conversations listConversations, POST /conversations createConversation on an "email-first
    help desk platform with shared inboxes, live chat"
  reason: Conversations are the support tickets/contacts of a help desk; creating, listing and updating
    them is inbound customer contact capture and resolution, i.e. Customer Inquiry Management.
- tag: Threads
  spec_file: helpscout-threads-api-openapi.yml
  capability_id: BC-430.10
  capability_id_l1: BC-430
  capability_name: Customer Inquiry Management
  confidence: 0.8
  evidence: POST /conversations/{id}/threads createThread, schema Thread
  reason: Adding a thread to a help desk conversation is recording a reply/note in the handling of an
    inbound customer contact, which falls under Customer Inquiry Management.
- tag: Customers
  spec_file: helpscout-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.72
  evidence: POST /customers createCustomer, GET /customers/{id} getCustomer, schema Customer
  reason: CRUD over customer records in the help desk maintains the customer master used for support context,
    which is Customer Data Management. Some chance it is better read as support-contact administration,
    hence moderate confidence.