Salesforce business context is planned to surface inside Amazon Quick while AWS agents come to Slack. AWS and Salesforce announced a group of integrations intended to move CRM context and agent actions into the tools employees already use. The work spans Amazon Quick, Slack, Amazon Bedrock, Data 360 and contact-centre voice rather than introducing one standalone product.
AWS and Salesforce: verified facts
| Announced | September 15, 2026 | AWS; Salesforce |
|---|---|---|
| Productivity surface | Salesforce context in Amazon Quick | AWS; Salesforce |
| Collaboration | AWS agents coming to Slack | AWS; SiliconANGLE |
| Voice | A2A support between Agentforce Voice and Amazon Connect Customer | AWS; Salesforce |
What the announcement changes
AWS and Salesforce announced a group of integrations intended to move CRM context and agent actions into the tools employees already use. The work spans Amazon Quick, Slack, Amazon Bedrock, Data 360 and contact-centre voice rather than introducing one standalone product.
Amazon Quick is planned to surface Salesforce business context so a team can prepare work without first opening the CRM. AWS frontier agents are also coming to Slack. Administrators still need to verify which records and actions each user can reach; a convenient interface should not broaden underlying permissions.
The data layer expands Salesforce Zero Copy support to additional AWS services. The promise is access without bulk migration, reducing duplicated stores and stale copies. Zero copy does not mean zero governance: organisations still need lineage, policy enforcement, query controls and cost monitoring across both platforms.
Agentforce customers will gain broader access to models through Amazon Bedrock. Model choice can help teams match cost, latency and capability, but it complicates evaluation. A workflow should be tested whenever its model changes, especially where structured actions or regulated records are involved.
The voice integration uses Agent2Agent support for bidirectional communication between Agentforce Voice and Amazon Connect Customer. That could reduce handoff friction in service operations. Buyers should confirm regional availability, latency, recording rules and how a human agent takes control when the systems disagree.
Several announced capabilities are forward-looking or rolling out over time. The companies describe what will be possible, not a guarantee that every account can enable every connection today. Implementation plans should list exact editions, regions, preview status and dependency dates before promising an operational deadline.
The commercial logic is interoperability: Salesforce wants its data and rules to retain value outside the Salesforce interface, while AWS wants cloud agents and models to work with CRM context. Customers gain flexibility only if identity, audit and exit paths remain portable rather than creating a larger coupled stack.
A sensible rollout begins with one read-heavy workflow, maps permissions end to end and measures whether users complete work faster without creating new data copies or policy exceptions. The AWS Salesforce AI integration is broad; its value will be proven one governed workflow at a time.
Related Lapaas Voice coverage
Read our coverage of Cohere encrypted inference and NVIDIA CUDA-Q logical quantum codesign for adjacent context.
Frequently asked questions
What is AWS and Salesforce?
Salesforce business context is planned to surface inside Amazon Quick while AWS agents come to Slack.
What changed?
Zero Copy expands across more AWS data services, reducing the need to move duplicated data.
What should organisations verify?
Agentforce Voice and Amazon Connect Customer add planned real-time A2A interoperability.
Sources
- AWS — 2026-09-15
- Salesforce — 2026-09-15
- SiliconANGLE — 2026-09-15
- TechTimes — 2026-09-16
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
