Seu agent conversa (mas não fala como humano)
Your agent = text-based (slow, awkward). Dessa: Full-duplex speech agents (real conversations, interruptions, natural flow). Voice agents = next frontier.
Equipe OpenClaw · Time de Engenharia & Produto
A Equipe OpenClaw é formada por engenheiros, designers e especialistas em IA dedicados a construir a melhor plataforma de agentes conversacionais para negócios brasileiros. Combinamos expertise…
Seu agent conversa (mas não fala como humano)
What just happened (October 2026):
Block released Dessa full-duplex speech model:
"Technology: Full-duplex speech AI (two-way conversation simultaneously)."
"Capability: Agents can interrupt, listen, respond naturally (like real humans)."
"Problem solved: Previous agents = single-turn (you talk, agent listens, agent responds, waits). Robotic."
"New: Agent and human talk simultaneously (like real conversation)."
"Authenticity: Most natural agent speech ever (Dessa claim)."
"Implication: Voice agents = finally viable (not just text-based)."
What this means for your company:
Current situation (your SaaS agent):
Setup (typical agent on WhatsApp): Your agent: Customer support chatbot Interface: Text-based (WhatsApp messages) User experience: 1. Customer types: "Hi, I have a problem" 2. Agent responds: "What's your issue?" 3. Customer types: "My order hasn't arrived" 4. Agent responds: "Let me check your order" 5. Customer waits... (agent is "thinking") 6. Agent responds: "Order #123 shipped on X date"
Problem: - Slow (waiting between turns) - Awkward (doesn't feel conversational) - Limited (text is formal, stiff) - Unnatural (no interruptions, no real conversation flow) - Poor UX (customer feels they're talking to machine)
Customer sentiment: "This is clearly a bot" "Why can't it just understand?" "I have to type everything" "This is slow compared to calling"
Reality check: Your agent: Technically works Customer experience: Feels robotic Satisfaction: Lower than human agent Retention impact: Negative (customers prefer human)
Alternative situation (if voice agent existed):
Setup (voice agent on phone/WhatsApp Audio): Your agent: Customer support voice agent Interface: Voice (WhatsApp call or phone) User experience: 1. Customer calls: "Hi, I have a problem" 2. Agent responds (interrupting, natural): "What's your issue? I'm—" 3. Customer interrupts naturally: "My order—" 4. Agent understands real-time: "—hasn't arrived, got it" 5. Agent seamlessly: "Let me check immediately" 6. Agent responds in real-time (no awkward silence) 7. Conversation feels natural (like talking to person)
Benefit: - Fast (immediate responses) - Natural (conversation flows, interruptions ok) - Rich (tone, emotion, urgency conveyed) - Human-like (doesn't feel like machine) - Better UX (more satisfying)
Customer sentiment: "That was surprisingly natural" "Felt like talking to a real person" "Got my issue resolved fast" "Way better than typing"
Reality check: Your agent: Actually feels human Customer experience: Positive Satisfaction: Matches human agent Retention impact: Positive (customers satisfied)
The problem: Text agents are limited (why agents feel robotic)
Why text-based agents fail at natural conversation
Text = slow, formal, unnatural
Text agent limitations:
Limitation 1: Turn-by-turn (not simultaneous) Reality: Humans interrupt each other Text agent: Waits for full message Result: Conversation feels stiff
Example:
Human: "I have a problem with—"
Agent: (waits for full message)
Human: "—my order"
Agent: "What's your problem?"
Real conversation:
Human: "I have a problem with—"
Agent: "—your order? Let me check"
(interrupts naturally)
Limitation 2: No emotional tone Text: "Your order is delayed" Missing: Urgency, sympathy, understanding Result: Feels robotic
Voice: "Your order is delayed..." (concerned tone)
Conveys: Agent understands your frustration
Result: Feels human
Limitation 3: Latency (waiting for response) Text: Type → send → wait 2-3 seconds → response Feels: Slow, mechanical
Voice: Speak → response (real-time)
Feels: Natural, immediate
Limitation 4: Clarity issues Text: Typos, abbreviations, unclear intent Agent: Struggles to understand Result: Misunderstandings, poor UX
Voice: Natural speech, tone, context
Agent: Understands intent immediately
Result: Smooth conversation
Limitation 5: Not how humans communicate Text: Formal, complete thoughts Reality: Humans talk in fragments, interrupt, overlap Result: Agent doesn't match how humans naturally talk
Voice: Natural cadence, interruptions ok
Reality: Matches how humans actually talk
Result: Comfortable, familiar interaction
Why agents suck at phone calls (before Dessa)
Previous voice agents = single-turn hell
Old phone agent call (before full-duplex):
Customer: "Hi, I need to report a—" Agent: (interrupts, didn't catch whole thing) "What can I help with?" Customer: "—fraudulent charge" Agent: (already moved on) "Let me transfer you" Result: Frustrating, slow, feels broken
Problem: Agent couldn't listen while responding Technical term: Half-duplex (one direction at a time) User experience: Terrible (like old walkie-talkies)
What customers wanted:
Customer: "Hi, I need to report a—" Agent: (listening + understanding) "—fraudulent charge? I've got that" Customer: "Yeah, on my—" Agent: "—credit card? Let me pull that up right now" Result: Natural, fast, feels human
What this requires: Full-duplex Technical term: Both can talk at same time Technology: Complex (but now possible with Dessa) User experience: Natural
The breakthrough: Full-duplex speech agents (Dessa changes the game)
What full-duplex means (and why it matters)
Two-way conversation (like real people)
Full-duplex technical definition:
Half-duplex (old): Agent: Listens OR speaks (one at a time) User: Has to wait for agent to finish Result: Unnatural (like walkie-talkie)
Full-duplex (new): Agent: Listens AND speaks (simultaneously) User: Can interrupt naturally Result: Natural (like real conversation)
Practical example:
Half-duplex agent call: You: "My internet is down and I need—" Agent: "I'm sorry to hear that. What can I help with?" You: (repeat yourself) "My internet is down" Agent: "Let me check your account" You: Wait... (awkward silence)
Full-duplex agent call (Dessa): You: "My internet is down and I need—" Agent: "—help getting back online? I'll fix that now" You: "Can you check if—" Agent: "—it's a modem issue? Already on it" You: Feel like talking to real person Agent: Understands + responds + doesn't wait
Why it matters:
Before: Agent couldn't interrupt or respond in real-time After: Agent is responsive, dynamic, human-like Impact: Customer experience goes from "this is a bot" to "this is natural" Business impact: Better satisfaction, fewer escalations, happier customers
Dessa's innovation (most authentic voice agent ever)
Block's Dessa = game changer for voice agents
Dessa capabilities:
Feature 1: Full-duplex speech (simultaneous conversation) Meaning: Agent and human can talk at same time Result: Natural conversation flow Feeling: Talking to real person
Feature 2: Authenticity (most natural-sounding) Claim: "Most authentic full-duplex speech model ever built" Meaning: Voice sounds human, responses feel genuine Result: Customers don't realize it's AI (initially) Impact: No uncanny valley (creepy robot voice)
Feature 3: Real-time understanding Meaning: Agent understands while you're still talking Result: No delays, interrupts naturally Feeling: Agent is actually listening
Feature 4: Emotional awareness Meaning: Agent detects frustration, urgency, emotion Result: Responds appropriately (empathy, urgency) Feeling: Agent actually cares
Feature 5: Context retention Meaning: Agent remembers what you said before Result: No "can you repeat that?" Feeling: Agent is following the conversation
Practical application:
Use case 1: Customer support calls Before: Text agent (slow, robotic) After: Voice agent (natural, fast, satisfying) Customer impact: "This actually worked"
Use case 2: Sales calls Before: Text agent (can't build rapport) After: Voice agent (builds trust, closes deals) Sales impact: Higher conversion rate
Use case 3: Appointment booking Before: Text agent (back-and-forth messages) After: Voice agent (real conversation, confirms in real-time) Time saved: 5 minutes → 30 seconds
Use case 4: Complaint resolution Before: Text agent (customer gets frustrated) After: Voice agent (agent empathy + resolution) Satisfaction: +40%
Why this matters for your business (voice agents are the future)
The shift from text to voice (inevitable)
Voice = how humans naturally communicate
Market reality:
2024-2025: Text agents (early stage, limited) Adoption: Experimental Satisfaction: Low (people don't like texting with bots) Use case: Basic FAQ, not complex conversations
2026+: Voice agents (Dessa era) Adoption: Mainstream (because they work now) Satisfaction: High (feels human) Use case: Everything (support, sales, appointments)
Why the shift? Voice is natural: How humans talk Voice is fast: No typing, immediate Voice is rich: Tone, emotion, urgency Voice is inclusive: Elderly, disabled, lazy people (prefer not to type)
Competitive advantage: Company with text agent: "Please contact support via chat" Company with voice agent: "Call our agent (instant support)" Customer choice: Voice agent (obvious)
Business implications:
If you stay text-only: Your agent: Feels robotic Customer experience: Poor Competitors: Offer voice (better UX) Your disadvantage: Obvious
If you move to voice (Dessa-powered): Your agent: Feels human Customer experience: Great Competitors: Still using text Your advantage: Clear
Voice agent ROI (why you should care)
Voice agents = better business outcomes
Metrics improvement (voice vs text):
Customer satisfaction: Text agent: 60% CSAT Voice agent: 85%+ CSAT Difference: +25 points
Resolution time: Text agent: 5-10 minutes Voice agent: 1-2 minutes Difference: 5-8x faster
Escalation rate: Text agent: 30% escalate to human Voice agent: 10% escalate Difference: -67% escalations (massive)
Customer retention: Text agent: Poor UX → churn Voice agent: Great UX → retention Difference: 15-20% higher retention
Cost per interaction: Text agent: R$2.50 (slow, requires human escalation) Voice agent: R$0.50 (fast, self-resolved) Difference: -80% cost
Financial impact (example company):
Setup: Daily interactions: 1000 Current: Text agents (60% CSAT) New: Voice agents (85% CSAT)
Cost savings: 1000 interactions × R$0.50 = R$500/day R$500 × 30 days = R$15,000/month R$15,000 × 12 = R$180,000/year
Satisfaction improvement: +25 CSAT points = higher retention Conservatively: 5% fewer churn ACV R$10,000, lifetime: R$100,000 5% of 1000 daily customers × 30 = 150 saved customers/month 150 customers × R$100,000 = R$15M value (per month!)
Total ROI: Cost savings: R$180k/year Retention value: R$15M+ per month Combined: Massive (voice agent is obvious financial win)
How to prepare (voice agents are coming)
Roadmap for voice agent adoption
Plan your transition (text → voice)
Phase 1: Now (evaluate)
Actions: - Monitor Dessa + similar models (what's possible) - Calculate current text agent costs (baseline) - Measure text agent satisfaction (benchmark) - Identify use cases where voice would help most
Timeline: 1 month Effort: Low (research only)
Phase 2: Q1 2027 (test)
Actions: - Get Dessa API access (when available) - Build voice agent POC (one use case) - Compare text vs voice (side-by-side) - Measure customer preference - Calculate ROI (voice vs text)
Timeline: 2-3 months Effort: Medium (engineering required) Expectation: Voice wins on all metrics
Phase 3: Q2 2027 (scale)
Actions: - Move primary support to voice agent - Keep text as fallback (for typed notes) - Monitor metrics (satisfaction, cost, resolution time) - Expand to sales, appointments, other use cases - Train team (how to oversee voice agents)
Timeline: Ongoing Effort: Medium (operational) Expectation: 2-3x improvement in key metrics
Phase 4: 2028+ (optimize)
Actions: - Full voice-first strategy - Text available only if customer prefers - Use voice data to improve agent (feedback loop) - Expand to new languages, regions - Integrate with other systems (CRM, billing, etc)
Timeline: Ongoing Effort: Low (maintaining competitive advantage) Expectation: Industry-leading customer experience
Technical preparation (what you need)
Infrastructure for voice agents
Requirements:
-
Voice infrastructure - Phone system (VOIP, SIP, or API-based) - Audio codec (opus or similar) - Real-time audio processing (low latency)
-
LLM integration - Voice-to-text (speech recognition) - LLM reasoning (Dessa or similar) - Text-to-speech (voice synthesis) - Full-duplex orchestration (complex)
-
Data infrastructure - Audio storage (encrypted) - Transcription logs (compliance) - Metrics collection (satisfaction, cost, time) - Analytics dashboard (monitor agent health)
-
Security - GDPR compliance (audio data sensitive) - Encryption (in transit + at rest) - Access controls (who can listen to calls) - Audit logs (compliance, accountability)
Recommendation: Don't build from scratch (too complex) Use existing platforms: AWS Connect, Vercel Agents, Block Dessa Focus on integration, not infrastructure
The bottom line: Voice agents are inevitable (Dessa just made them real)
Text agents are the training wheels. Voice agents are the bicycle. Dessa = brakes that work.
Why Dessa matters:
Before: Voice agents were possible but creepy/robotic After: Voice agents are natural and authentic Impact: Voice agents become actually good
Why you should care:
Customer experience: Massive improvement Business metrics: Cost down, satisfaction up, churn down Competitive advantage: Clear (voice > text) Timeline: 2027 is inflection point
What to do NOW:
- Start monitoring voice agent space
- Plan voice pilot project
- Evaluate Dessa + competitors
- Calculate ROI (voice vs your current solution)
- Build business case (for leadership buy-in)
- Don't wait (first-mover advantage exists)
Why not wait:
Reason 1: Dessa proves it's viable now (not in 2 years) Reason 2: Competitors will adopt (you'll be behind) Reason 3: Customer expectations rising (voice is new normal) Reason 4: ROI is massive (voice pays for itself) Reason 5: Technology mature enough (ready for production)
Final truth:
Your text agent: Works technically Your customer: Dislikes it (slow, awkward, robotic) Better alternative: Voice (natural, fast, human) Technology: Available now (Dessa) Decision: Adopt voice or lose to competitors Timeline: Start now, launch in 2027
Your agent converses in text (slow, robotic). Voice agents exist now (natural, human). Dessa makes them real. Plan your transition. 🎤🤖💬✅
Publicado em 24 de outubro de 2026