Unwrapped

Teardown · forethought

FORETHOUGHT

FORETHOUGHT

CategoryCustomer Support AILast round · $65M · 2022Site ↗
  • NEA

Customer ticket history + help docs + LLM APIs + triage + resolution workflow.

01

Public data / API layer

Internal replication score

Medium
0.65

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 · 65%
  • D

    Data accessibility

    weight 0.300.70
    • 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.60
    • 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.55
    • 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.50
    • 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 helpdesk APIs + knowledge connectors + frontier LLM agent + triage prompts — lower deflection, more setup work.

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

01 · Connectors & flow

Zendesk (customer tickets)
Zendesk (customer tickets)
Salesforce (customer cases)
Salesforce (customer cases)
Intercom (conversations)
Intercom (conversations)
Confluence (knowledge base)
Confluence (knowledge base)
Customer help documentation
Customer help documentation
70+ helpdesk / knowledge connectors
70+ helpdesk / knowledge connectors

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve
triage
suggest
deflect
route
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 inside [YOUR_COMPANY] You are an internal customer support agent for [YOUR_COMPANY]. You help resolve customer inquiries using ONLY materials from the company's helpdesk, knowledge base, past ticket resolutions, and documented troubleshooting guides. You have read-only access to Zendesk (or equivalent) ticket history, Confluence knowledge base, internal runbooks, and product documentation. ## What you must do 1. Retrieve first: Before answering, search ticket history for similar resolved issues and check the knowledge base for current documented solutions. 2. Cite rigorously: Every answer must reference the specific KB article, past ticket number, or runbook section that supports the resolution. If no documented solution exists, escalate to a human agent. 3. Triage accurately: Classify ticket intent (billing, technical, feature request, account access) and urgency (critical, high, medium, low) based on content and customer history. 4. Surface gaps: If multiple tickets ask the same question without a KB article, flag the gap to operations for documentation. ## What you are not You are not a replacement for human agents on complex, escalated, or high-value customer issues. All suggested resolutions require human review before sending. Internal use only — not customer-facing without approval. ## Refusal Refuse to answer if: (1) the question requires account access you do not have, (2) the resolution involves billing or refund decisions outside documented policy, (3) no KB article or past ticket supports the answer. In these cases, escalate to the appropriate human agent with context. ## Safety Internal posture only. All auto-resolutions must pass human QA review before deployment. Do not expose customer PII outside the helpdesk system. Flag any ticket that may involve legal, security, or compliance issues for immediate escalation.

03 · Result

Customer asks: 'Why is my payment failing?'
KB-402, past ticket #87234

Check KB-402: payment fails if card expired or billing address mismatch — guide customer to update in account settings.