Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Amelia says with 21 agents and 3 humans, inbound emails, outbound from four tools, renewals, and support were falling through cracks. They built Prospector as one queue so an agent can filter, route, and follow up until each item reaches its goal, preventing handoffs from silently dropping.

Related Insights

Jason explains their four outbound platforms each send autonomously, but Prospector pulls replies through APIs into one queue and starts a timer. It is not unifying initial sends; it unifies responses. The agent drafts follow-ups and reminds them when to ping again or try another contact.

Jean-Denis describes a Town internal CRM where an agent finds a colleague connected to a target customer by querying other employees’ agents. Instead of Slack’s slow human routing, users get immediate answers, with AI trusted to mediate privacy and security for that request.

Instead of one monolithic agent, build a multi-agent system. Start with a simple classifier agent to determine user intent (e.g., sales vs. support). Then, route the request to a different, specialized agent trained for that specific task. This architecture improves accuracy, efficiency, and simplifies development.

Instead of manually responding to every message, build a custom app using an AI like Claude. This system can create a unified inbox for comments and DMs, sort them by urgency, and draft replies based on your past communications, leaving you to simply approve, edit, or skip.

For processes that span multiple departments, like customer onboarding, a 'bridge agent' can maintain the complete picture. It prevents context loss and broken handoffs that occur when each team's individual agent operates in a silo, solving for work that 'sits between' teams.

While consolidating tools seems efficient, using specialized, best-in-class AI agents for each GTM function (one for outbound, one for inbound) yields superior results. The depth and focus of specialized tools enable more powerful and nuanced use cases, justifying the management overhead of multiple systems.

To eliminate delays from reps chasing approvals from Deal Desk, Legal, and RevOps, Anthropic centralized all support requests into Slack. An AI agent then triages these tickets, either resolving them based on company policy or escalating them with full context to the right human. This shifts the burden from reps navigating systems to systems coming to the reps.

Designate a single "manager" bot to receive all incoming tasks. This bot then delegates the work to specialized bots, simplifying the user's workflow by removing the need to choose the right agent for every single task. It acts as a central router.

Don't fear deploying a specialized, multi-agent customer experience. Even if a customer interacts with several different AI agents, it's superior to being bounced between human agents who lose context. Each AI agent can retain the full conversation history, providing a more coherent and efficient experience.

The GTM process is fundamentally broken for buyers due to constant handoffs from chatbot to SDR to AE to SE. This creates a disjointed experience where context is lost and customers are forced to repeat themselves.