Salesforce
7 min read

Scaling Sales Agents: Engineering Next-Gen AI for the Enterprise Era

Read Full Article

Summary

The article outlines the engineering advancements made in scaling the Engagement Agent, a generative AI system designed for automating personalized sales outreach. It describes the transition from a single-agent MVP to a multi-agent architecture capable of handling over 1 million outreach actions monthly. Key improvements include the implementation of a dispatcher-mediated execution model, a persistent queue to manage workloads, and fairness algorithms to ensure equitable resource allocation among agents. The article emphasizes the importance of observability in diagnosing performance issues and maintaining consistent throughput during peak usage periods.

Key Learnings

  • 1The transition from a single-agent to a multi-agent architecture significantly improved scalability and reliability for high-volume sales outreach.
  • 2Implementing a persistent queue allows for better management of workload surges, preventing bottlenecks and ensuring timely processing of tasks.
  • 3Fairness algorithms, such as Round-Robin, are crucial in balancing resource usage among multiple agents, preventing monopolization of system resources.
  • 4A dispatcher-mediated execution model enhances the system's ability to prioritize urgent tasks while adhering to organizational constraints.
  • 5Improved observability through clear separation of intake and processing functions allows for rapid diagnosis of performance issues across the system.

Who Should Read This

Senior Software Engineers specializing in AI frameworks and architecture, focusing on scaling generative AI systems for enterprise applications.

Test Your Knowledge

?

What are the trade-offs of using a dispatcher-mediated execution model compared to a direct task assignment approach?

?

How does the implementation of a persistent queue impact system performance during unexpected workload surges?

?

What design decisions were made to ensure fairness in resource allocation among multiple Engagement Agents?

?

In what ways did the initial MVP architecture limit the system's scalability and reliability?

?

How do channel-aware quotas influence the throughput of the Engagement Agent across different email providers?

Topics

Read Full Article at Salesforce

More from Salesforce Engineering

View Salesforce engineering blogs →
Salesforce
6m

Engineering Platform Trust: Cutting Customer Case Volume 20x with Petabyte-Scale Health Signals

The article details the development of a Technical Health Score system at Salesforce, aimed at quantifying platform trust through analytics pipelines that handle petabytes of telemetry data. By...

Salesforce
5m

How Data 360 Optimized Kubernetes Scheduling Architecture, Delivering 13% Cost Savings

The article discusses how the Data 360 Compute Fabric team at Salesforce optimized Kubernetes scheduling to enhance resource efficiency and reduce costs. By evolving the default kube-scheduler...

Salesforce
6m

Delivering Accurate, Low-Latency Voice-to-Form AI in Real-World Field Conditions

The article explores the development of a hybrid architecture for a voice-to-form AI system used in field service applications. It highlights the integration of on-device speech-to-text capabilities...

Salesforce
7m

Hyperforce Migration at Scale: How Deterministic Automation Replaced Manual Spreadsheets Across 95,000 Organizations

The article outlines the development of the Migration Intake and Processing Service (MIPS) at Salesforce, which automates the migration of over 95,000 organizations to Hyperforce. It highlights the...

Salesforce
5m

Building an AI-Accelerated Compliance Automation Platform for 24x Faster Audits

The article outlines the development of FastTrack, a compliance automation platform by Salesforce, which significantly reduces audit execution time through AI-assisted development and API-based...