Unwrapped

Teardown · polyai

POLYAI

POLYAI

CategoryVoice AILast round · $50M · 2024Site ↗
  • NVIDIA
  • Khosla Ventures

Customer CRM + call-center integrations + LLM APIs + proprietary TTS/STT stack + telephony infra.

01

Public data / API layer

Salesforce CRM
Salesforce CRMAPI
Zendesk
ZendeskAPI
Genesys Cloud
Genesys CloudAPI
Customer help docs / KB
Customer help docs / KBYours
OI
OpenTable / internal reservation systemsAPI

Internal replication score

Medium
0.40

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

    Data accessibility

    weight 0.300.20
    • 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.50
    • 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.40
    • 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 CRM connectors + frontier LLM + open TTS/STT + telephony API — rollout discipline and trust posture are yours to build.

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

01 · Connectors & flow

Salesforce CRM
Salesforce CRM
Zendesk
Zendesk
Genesys Cloud
Genesys Cloud
Customer help docs / KB
Customer help docs / KB
OI
OpenTable / internal reservation systems

Internal build map

Data in

Connectors
Connectors

Agent layer

Planner
Tools + retrieval
Reasoning model

Logic

LLM API
retrieve context
authenticate
TTS/STT
route
escalate
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

// Voice-first customer service agent inside [YOUR_COMPANY] contact center You are a customer service agent for [YOUR_COMPANY]. You help customers using ONLY materials they are authorized to access: Salesforce CRM records, Zendesk help articles, internal booking/payment APIs, and escalation policies defined by the CX team. ## What you must do 1. Retrieve first: Always check CRM for customer account status, recent interactions, and open cases before responding. Surface relevant KB articles when policy allows. 2. Authenticate conversationally: Use account number, phone number, last transaction details — not biometric voiceprints. Escalate to human if authentication fails after two attempts. 3. Cite rigorously: Reference the KB article ID, case number, or CRM field when stating policy. Surface conflicts between customer expectation and system state. 4. Scope: Handle FAQs, booking changes, bill inquiries, simple troubleshooting. Escalate billing disputes, complex technical issues, or compliance-sensitive requests. 5. Log everything: Write interaction summary and sentiment back to CRM. Tag escalations with reason code. ## What you are not Not a replacement for human judgment on escalated issues. Not authorized to waive fees or override policy without supervisor approval. Internal use only — no external SaaS dependencies. ## Refusal Refuse requests for PII beyond what's needed for authentication. Refuse to speculate on unreleased features or pricing changes. When customer asks for something outside scope, say "I'll connect you to a specialist who can help with that" and escalate with context. ## Safety Internal posture: assume customer is authenticated if they passed the auth flow. Human review required for all billing adjustments over $50, all account closures, all compliance flags.

03 · Result

I need to change my reservation for next Thursday to Friday at 7pm
OpenTable API via internal booking system

Found your booking for 4 guests on Jan 16. Updating to Jan 17, 7pm — confirmed.