Build Voice Agents That Act Across Sales Tools

Summary

Pixel shares a DEV Community guide to building voice agents that take action across sales and marketing tools. It explores updating a CRM, scheduling follow-ups, finding contacts, and drafting email, while addressing authentication, response speed, misheard commands, and user visibility.

DEV Community

Give Your Voice Agent Hands: Let It Act Across Sales and Marketing

The call ends. The admin starts. Maya is an account executive. She just finished a good call with Priya at Larkspur Freight. They agreed on pricing in principle, Priya wants a recap in writing, there's a follow-up on Tuesday, and Larkspur's CMO should hear about the enterprise plan. Now Maya has fifteen minutes before her next call, and four tools to update: HubSpot: log the call, move the deal to negotiation. Apollo: find the CMO, add her as a contact, put her in the enterprise sequence. Google Calendar: book Tuesday. Gmail: write the pricing recap. Her team already has a voice agent. It's good at talking. It can summarize the call and suggest next steps. But it can't touch any of those four tools, so Maya does all of it by hand, again. The obvious fix is to give the agent access to those apps. With voice, that's harder than it sounds: There's no screen mid-call. If HubSpot's connection expired, the agent can't pop up an OAuth consent page while Maya is talking to it. Every tool slows the reply. Each tool schema goes into the model's context on every turn. In a chat app, a second of extra thinking is fine. In a voice call, it's an awkward silence. Voice gets misheard. "Draft Priya the recap" can become "send Priya the recap." One wrong word and a half-finished email reaches a prospect. Maya can't see what changed. In a chat UI she'd see the tool calls scroll by. On a call, she only knows what the agent tells her. This article builds a voice agent that handles that whole list for one rep, with her own access, and tells her what it did. The job: one sentence, five actions Here's the job, in Maya's words: When I hang up with a prospect, I want to say what happened and have the CRM, follow-up and outreach updated before my next call. So after the call she says one thing: "Log the Larkspur Freight call, move the deal to negotiation, book a follow-up for Tuesday, draft Priya the pricing recap, and add their CMO to the enterprise sequence." That sentence turns into five actions, each backed by a tool from the connector's docs: What Maya asked App Tools Log the call, move the deal HubSpot hubspot_deals_search, hubspot_call_log, hubspot_deal_update Find the CMO and add her to the sequence Apollo apollo_enrich_contact, apollo_create_contact, apollo_add_contacts_to_sequence Book Tuesday's follow-up Google Calendar googlecalendar_create_event Draft the pricing recap Gmail gmail_create_draft Tell her what changed (the agent) none, it reads back what the tools returned Two choices here are deliberate. The recap is saved as a draft, not sent. gmail_create_draft exists next to gmail_send_message, and for a voice agent the draft is the right default. If a word was misheard, it sits in Maya's drafts folder instead of Priya's inbox. And the agent reads back what it did: "Logged the call, moved Larkspur to Negotiation, booked Tuesday at 10, saved the recap as a draft, and added Dana Okafor to the enterprise sequence." On a voice call, that read-back is the only audit trail Maya sees. Building it yourself You can wire this up directly. Here's what that takes for a team of 30 reps. Three OAuth apps, four tools. HubSpot, Apollo and Google each need an OAuth app, a consent flow, scopes, an encrypted token store per rep, and refresh logic. Google Calendar and Gmail can share one Google app, but their scopes still need to be right. Token handling that works mid-call. A rep's HubSpot token expires at 2 p.m. The voice agent tries to log a call at 2:05 and fails. Your code needs to refresh before the call, and if refresh isn't possible, say so out loud and get a link to the rep somewhere other than the call. A tool list small enough to talk with. The four connectors together expose hundreds of tools. HubSpot's connector alone has 457 in Scalekit's catalog, 80 of them destructive. You'll hand-pick eight, write their schemas, and keep them in sync as the APIs change. Guardrails against mishearing. You'll need to make sure no delete, archive or send too...
Build Voice Agents That Act Across Sales Tools
Powered by Readybot.io

The latest from Pixel

Incident Response: Look Beyond the Red Alert

Pixel’s DEV Community announcement explores how teams can fixate on one failing service while overlooking the real cause of an outage, such as a full …

Sach: AI Fact-Checks WhatsApp Forwards in India

Pixel’s announcement introduces Sach, a tool that checks forwarded messages in English, Hindi, Telugu, and 14 other Indian languages against official sources. It gives cited …

Java 25 Removes SecurityManager: What to Fix

Pixel’s announcement explains how Java 24’s JEP 486 permanently disabled the SecurityManager, breaking test workarounds that intercept System.exit. It recommends returning exit codes or throwing …