Unwrapped

Teardown · decagon

DECAGON

DECAGON

CategoryCustomer Support AIValuation · $4.5B · 2026Site ↗
  • Andreessen Horowitz
  • Accel
  • Coatue
  • Index Ventures

Customer support tickets + transcripts + LLM API + voice/chat/email workflow.

01

Public data / API layer

Zendesk Support API
Zendesk Support APIAPI
Salesforce Service Cloud API
Salesforce Service Cloud APIAPI
Intercom API
Intercom APIAPI
CS
Customer Support Tickets & TranscriptsYours
Customer Knowledge Bases & Help Docs
Customer Knowledge Bases & Help DocsYours

Internal replication score

Easy
0.72

Feasibility of a useful internal substitute built with Claude (or similar), the same data access, and light agent logic — not rebuilding the whole product.

IRS = 0.30·D + 0.25·L + 0.20·O + 0.15·R + 0.10·Sthis record · 72%
  • D

    Data accessibility

    weight 0.300.85
    • 1.0mostly customer-owned / public / standard third-party sources
    • 0.5mixed accessibility
    • 0.0hard-to-access or proprietary source layer
  • L

    LLM substitutability

    weight 0.250.75
    • 1.0mostly retrieve / prompt / cite / summarize / classify / compare
    • 0.5mixed standard + custom behavior
    • 0.0strongly custom model behavior (fine-tunes on proprietary data, etc.)
  • O

    Output simplicity

    weight 0.200.80
    • 1.0straightforward internal work product (memo, list, reply, SQL query)
    • 0.5moderately specialized
    • 0.0highly specialized (e.g. FDA-graded clinical text)
  • R

    Review / risk tolerance

    weight 0.150.60
    • 1.0internal use with human review is acceptable
    • 0.5moderate risk
    • 0.0very low tolerance for error (e.g. external legal filings)
  • S

    Surface complexity

    weight 0.10inverse — higher means less surface dependence0.30
    • 1.0a simple internal shell is enough
    • 0.5polished workflow matters somewhat
    • 0.0product surface / rollout / trust posture is central to value
LabelsEasy ≥ 0.67Medium ≥ 0.34Hard < 0.34

Missing factor rows use heuristics from wrapper scores. Editorial heuristic, not investment advice.

Build it yourself

Recreate the workflow inside your org.

Internal build

Build it yourself

Same support data + frontier LLM API + thin retrieval agent — no brand trust, rollout surface, or voice polish.

Internal use only. Replacing them in-market is a different bar than replaying the useful workflow inside your org.

01 · Connectors & flow

Zendesk Support API
Zendesk Support API
Salesforce Service Cloud API
Salesforce Service Cloud API
Intercom API
Intercom API
CS
Customer Support Tickets & Transcripts
Customer Knowledge Bases & Help Docs
Customer Knowledge Bases & Help Docs

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
cite
permissions
voice synthesis
orchestrate channels
not custom weights

Outputs

Internal search
Answer
Citations

02 · Claude / agent prompt

Paste as the system or developer message in Claude (or your agent runtime). Scroll to read; Copy grabs the full text.

Claude / agent prompt

// Customer support agent for internal use You are a customer support agent working inside [YOUR_COMPANY]. You help support team members answer customer inquiries using ONLY materials in connected systems: Zendesk tickets, internal knowledge base articles, CRM customer records, order history, and policy documentation. ## What you must do 1. Retrieve first: Search connected systems for relevant context before answering 2. Cite rigorously: Every factual claim must reference a specific source document or ticket 3. Surface conflicts: If policy docs contradict each other or information is outdated, flag it explicitly 4. Scope: Only answer questions grounded in retrievable data — no speculation or assumptions ## What you are not Not a replacement for human judgment on escalations, refunds, or policy exceptions — always route sensitive cases to a human agent. Internal tool only. ## Refusal Refuse when: (1) no relevant data exists in connected systems, (2) question requires accessing customer PII without proper authentication, (3) answer would require policy interpretation beyond documented guidelines. ## Safety Internal use with human review required for all customer-facing responses. Assume operator has appropriate access permissions.

03 · Result

Customer asks why their order was delayed and when it will arrive
Order tracking system + shipping policy KB

Order #12345 delayed due to warehouse backlog. Shipped today via FedEx, arrives Feb 3.