Salesforce Service Cloud Voice with Amazon Connect: Setup Guide 2026

Amazon Connect Bundled with Salesforce vs Partner Telephony from Amazon Connect

Before you start, decide which of the two Amazon Connect models you are setting up, because the steps, ownership, and billing differ. In Salesforce’s documentation they are called Salesforce Voice with Amazon Connect (the bundled model) and Salesforce Voice with Partner Telephony from Amazon Connect (also known as Bring Your Own Amazon, or BYOA).

Which should you choose? If you do not already run Amazon Connect and want the simplest start, the bundled model means Salesforce provisions the AWS side for you. If you already have an Amazon Connect instance, or want to manage your own AWS account, partner telephony is the route to review. See Salesforce’s setup guides for Voice with Amazon Connect and Voice with Partner Telephony from Amazon Connect before you commit, since licensing terms and menu names change between releases.

1. Salesforce Service Cloud Voice with Amazon Connect: Prerequisites

Before starting the Salesforce Service Cloud Voice setup, confirm that your Salesforce environment, AWS account, and user permissions are ready. Missing permissions or incomplete identity configuration can delay implementation and make troubleshooting more difficult.

• Salesforce edition and licensing: Confirm that your Salesforce org and purchased licenses support the Service Cloud Voice configuration you intend to deploy. Enterprise, Unlimited, and Developer editions may be relevant depending on the setup, but verify current eligibility and licensing with Salesforce.
• AWS account: Ensure you have administrative access or the necessary permissions to create, configure, or manage an Amazon Connect instance.
• Salesforce administrator access: Use an administrator account with the appropriate Contact Center Admin permissions and access to the relevant setup pages.
• Agent and supervisor permissions: Identify the users who need voice access and confirm their assigned licenses, permission sets, and presence-status access.
• Contact center requirements: Plan your phone numbers, operating hours, queues, routing profiles, and contact flows before configuring production call handling.

2. Salesforce Service Cloud Voice with Amazon Connect: Identity Setup

Identity configuration helps establish the authentication foundation for the integration. Complete the required domain and identity-provider steps before proceeding to contact center configuration.

Step 1: Enable My Domain in Salesforce

1. Open Setup in Salesforce.
2. Search for My Domain.
3. Register your organization’s Salesforce domain if it has not already been configured.
4. Deploy the domain and verify that administrators and users can access Salesforce through the configured URL.

My Domain supports Salesforce authentication and application configuration. Completing this step early helps avoid domain-related issues later in the setup process.

Step 2: Enable the Identity Provider

1. In Salesforce Setup, search for Identity Provider.
2. Enable the Identity Provider if required by your selected integration architecture.
3. Review the authentication configuration and save the settings.
4. Follow the integration-specific instructions for establishing the required authentication relationship with AWS.

Do not assume that enabling the Identity Provider alone completes single sign-on. The corresponding AWS and Salesforce configuration must also be completed according to the supported integration instructions.

3. Salesforce Service Cloud Voice with Amazon Connect: Enable Voice

Once the prerequisites and identity settings are ready, enable the voice functionality and configure the connection between Salesforce and Amazon Connect.

Step 3: Enable Service Cloud Voice

1. Open Salesforce Setup.
2. Search for Service Cloud Voice Settings or the relevant Amazon Setup page available in your org.
3. Enable Service Cloud Voice and follow the configuration wizard, where available.
4. Review any required terms, licensing details, and permission assignments.

The exact setup page and available options may vary by product version and implementation type. Follow the configuration flow presented for your Salesforce org rather than assuming every environment uses identical menu names.

Step 4: Create or Connect an Amazon Connect Contact Center

1. In Salesforce Setup, open Amazon Setup or the relevant Amazon Contact Centers section.
2. Select Create Contact Center if your configuration supports provisioning through Salesforce.
3. Enter the requested details and assign the appropriate administrator.
4. Complete the required AWS permissions and role configuration, following the instructions shown in the setup flow.
5. If using an existing Amazon Connect instance, verify that it meets the integration requirements before connecting it.

Depending on the deployment path, the setup may provision an Amazon Connect instance and configure the required AWS roles, or connect to an existing instance. Confirm that the correct AWS account, region, and contact center are being used.

Step 5: Configure Telephony Provider Settings

Open the contact center record in Salesforce and select Telephony Provider Settings when available. Use the guided configuration to establish the connection between Salesforce and Amazon Connect.

Next, review the Amazon Connect configuration. Check that the following elements are correctly configured:

• Hours of operation and business availability.
• Queues and routing profiles.
• Inbound and outbound contact flows, where applicable.
• Phone numbers and the associated routing configuration.
• Permissions required by agents and supervisors.

These settings determine how calls enter the contact center and reach the right agents. A working connection alone does not guarantee that calls will route correctly.

4. Salesforce Service Cloud Voice with Amazon Connect: Omni-Channel Setup

Omni-Channel helps manage agent availability and work distribution across supported service channels. Configuring it correctly is essential when voice interactions need to fit into existing service workflows. For a deeper look at queues, routing configurations, and skills-based routing, see our Salesforce Omni-Channel routing implementation guide.

Step 6: Create Presence Statuses

1. Navigate to Setup → Presence Statuses.
2. Create a status such as Available for Calls.
3. Configure the appropriate availability and supported channel options.
4. Save the status and confirm that it matches your routing requirements.

Step 7: Assign Presence Status Access

Make sure the relevant agent and supervisor users can access the required presence statuses. Review profile and permission-set assignments based on your Salesforce security model. Agents must be able to select the appropriate availability status for voice work to be routed to them as intended.

Step 8: Enable Omni-Channel

1. Search for Omni-Channel Settings in Salesforce Setup.
2. Enable Omni-Channel if it is not already active.
3. Review the routing configuration and confirm that the required voice and digital-channel settings are in place.
4. Save your changes and test agent availability.

Menu names and routing capabilities can vary depending on the Service Cloud Voice implementation. Check the current Salesforce configuration instructions for your org before making production changes.

5. Salesforce Service Cloud Voice with Amazon Connect: Configure the Console

The Service Console brings the agent’s core service tools together. Adding the relevant utility components gives agents a consistent place to manage supported voice interactions while viewing customer information.

Step 9: Update the Service Console App

1. Open Setup → App Manager.
2. Locate your Service Console application, or the appropriate console app used by your organization.
3. Select Edit and open the utility-item configuration.
4. Add the Omni-Channel utility component where supported.
5. Save and activate the application changes, as required.

After configuration, agents can use the available console tools to manage their work. Depending on the specific Service Cloud Voice setup and enabled features, the interface may support embedded call controls, call information, transcription, and customer context. Verify the features enabled in your org instead of assuming they are all available by default.

6. Salesforce Service Cloud Voice with Amazon Connect: Testing Checklist

Before deploying the integration to your entire service team, test it in a controlled environment. Validate the complete call journey rather than checking only whether the contact center connects successfully.

• Agent access: Confirm that each test user has the required licenses, permissions, and presence-status access.
• Inbound calls: Verify that calls reach the correct queue and are routed to available agents.
• Outbound calls: Test outbound calling if it is part of your implementation.
• Customer context: Confirm that the expected customer or case information is accessible to agents.
• Audio and browser behavior: Test microphone permissions, supported browsers, and behavior after reconnecting or refreshing the console.
• Routing and availability: Confirm that changes in agent presence and queue configuration produce the expected routing behavior.
• Supervisor access: Verify that supervisors can access the monitoring and management capabilities assigned to their roles.

Document any errors and test again after changes. For production readiness, also review your support process, escalation path, and monitoring requirements, and use our Salesforce Service Cloud implementation checklist to cover the rest of the rollout.

7. Benefits of Salesforce Service Cloud Voice with Amazon Connect

When implemented correctly, the integration can deliver several operational benefits:

• A unified agent workspace: Agents can handle supported voice interactions within Salesforce instead of continually switching between separate systems.
• Better customer context: Access to relevant CRM records can help agents understand the customer’s history during service interactions.
• More structured call routing: Queues, routing profiles, and agent availability help direct calls according to configured rules.
• AI-assisted service workflows: Supported transcription and AI features can help agents capture information and work with call insights.
• Improved operational visibility: Configured reporting and monitoring capabilities can help service leaders review performance and identify opportunities for improvement.

Actual results depend on licensing, configuration, call volume, data quality, agent training, and the features enabled in your environment. Define measurable service goals before rollout so you can evaluate whether the integration is meeting business needs.

How Service Cloud Voice with Amazon Connect Is Billed

Service Cloud Voice with Amazon Connect is billed on a per-user basis, with telephony usage handled differently depending on the model you choose. This section summarizes what Salesforce publishes. We deliberately do not quote prices here, because they vary by region, edition, and contract. Check Salesforce’s Voice pricing page and your order form for current figures.

• Per-user licensing: Salesforce prices Voice per user per month. Its pricing page lists Salesforce Voice for Partner Telephony, and Salesforce Voice with Amazon Connect in bundled platform-minute tiers of 750, 2,000, and 5,000 minutes.
• Bundled Amazon Connect usage: Salesforce’s help documentation has a dedicated billing section covering IVR utterances, Salesforce Voice minutes, and telephony minutes, along with reports for checking Amazon Connect usage and cost.
• Partner telephony: With a partner provider, Salesforce’s pricing page describes connecting telephony and services from your preferred partner, and notes that voice-to-text transcription is licensed from the telephony partner.
• Additional AWS services: For the bundled model, Salesforce offers an Additional AWS Services add-on license that removes some contractual limits on which AWS services you can use.

Practical tip: Review platform licensing and telephony usage together each month. The per-user fee and the call minutes are separate cost drivers, so a forecast based on seats alone will miss real usage.

Common Setup Errors and Fixes

Most problems with Service Cloud Voice and Amazon Connect trace back to a handful of configuration gaps. Use this table to diagnose them before escalating.

Frequently Asked Questions About Salesforce Service Cloud Voice with Amazon Connect

1. How does Service Cloud Voice work with Amazon Connect?

Amazon Connect runs the phone numbers, IVR, queues, and contact flows, while Salesforce provides the agent workspace. When a call arrives, the contact flow creates a Voice Call record in Salesforce, and Omni-Channel routes the call to an available agent in the Service Console. The agent sees call controls, customer context, and real-time transcription in one place.

2. What is the difference between Amazon Connect bundled with Salesforce and Partner Telephony from Amazon Connect?

With the bundled model, Salesforce creates the AWS account and the Amazon Connect instance for you. With Partner Telephony from Amazon Connect, you integrate your own Amazon Connect instance and manage your own AWS account. Ownership, billing, and who handles service quota increases differ between the two.

3. Can I use my existing Amazon Connect instance with Salesforce?

Yes. Salesforce Voice with Partner Telephony from Amazon Connect lets you integrate an existing Amazon Connect instance, using an IAM role you configure for Salesforce. Salesforce recommends a new instance for the best end-to-end experience and the latest Voice features, so weigh that against reusing your current setup.

4. How is Service Cloud Voice with Amazon Connect billed?

Salesforce prices Voice per user per month. Its pricing page lists bundled Amazon Connect tiers of 750, 2,000, and 5,000 platform minutes, plus a separate licence for partner telephony. Salesforce also provides usage and billing reports. Confirm current pricing and contract terms with Salesforce, since they vary by region and agreement.

5. Does Service Cloud Voice support live transcription and AI agents?

Yes for live transcription: Salesforce supports real-time transcription through Amazon Transcribe, Contact Lens for Amazon Connect, or a partner telephony provider. Amazon Transcribe covers only the first 15 minutes of a call, so use Contact Lens for longer calls. For AI voice agents, see our Agentforce voice agent setup guide, and confirm licensing for your org.

6. How long does Service Cloud Voice with Amazon Connect take to set up?

Salesforce does not publish a standard setup time. Turning on Voice and creating the contact center is the quick part. Timelines are driven by contact flows, phone numbers, queues, routing, permissions, and testing, so plan the work in phases and test with a pilot group before a full rollout.

7. What are the prerequisites for Salesforce Service Cloud Voice with Amazon Connect?

You generally need a supported Salesforce org and appropriate licenses, AWS access, administrator permissions, and the required contact center configuration. My Domain, identity settings, and Omni-Channel may also be necessary. Confirm the current requirements for your specific integration before beginning implementation.

8. Why is Omni-Channel important for Salesforce Service Cloud Voice with Amazon Connect?

Omni-Channel helps coordinate agent availability and work routing across supported service channels. When configured with the appropriate presence statuses and routing settings, it helps ensure that voice interactions are directed according to your contact center’s rules and agent availability.

9. How can I test Salesforce Service Cloud Voice with Amazon Connect before launch?

Test inbound and outbound calls where applicable, agent permissions, presence statuses, queue routing, customer context, audio behavior, and supervisor access. Run tests with representative users and document any issues before production deployment. Recheck the integration after configuration changes or updates.

Conclusion: Implement Salesforce Service Cloud Voice with Amazon Connect Successfully

Salesforce Service Cloud Voice with Amazon Connect can help organizations bring telephony and customer context into a more unified service environment. A successful implementation starts with the right prerequisites and continues through identity configuration, contact center setup, telephony settings, Omni-Channel, and console customization.

Before launch, test the full customer call journey, confirm that agents have the correct access, and verify that routing and audio behave as expected. A well-planned rollout can help your team make better use of Salesforce and cloud contact center capabilities while creating a more consistent support experience.

Planning Your Salesforce Integration?

Get expert guidance on Salesforce integration, service workflows, and implementation planning with Kizzy Consulting.

Request a consultation below.

Please enable JavaScript in your browser to complete this form.

Name *

Name Email Message

Email *

Message *

Submit