Connect LabAmazon Connect study

Integrations

Salesforce starts as a CCP embed in a sandbox

Learn it in 5 minutes

HTML

About five minutes of reading

The admin guide's Salesforce page is a Contact Control Panel inside Salesforce, installed in a sandbox first.

That page says the CTI Adapter's core job is a WebRTC Contact Control Panel within Salesforce. It says the integration has two components. It says to install the package in a Salesforce sandbox first, then configure the Salesforce Call Center.

The public repository amazon-connect-salesforce-cti is the documentation home named for that adapter. This room stops at those two pages.

  • The softphone in the embed is the Connect CCP.
  • Sandbox first. Production is a later copy of a configuration you have already tried.
  • The page points at separate installation guides for Lightning and for Classic.
  • This room does not invent screen-pop fields. Read the adapter guide before you promise a pop.

Number on this page: First install Sandbox. Then configure the Call Center

Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.

Visual

HTML
Salesforce starts as a CCP embed in a sandbox

Picture from this room.

Worked example

HTML
  1. Sandbox. Install there first.
  2. Package. The managed CTI adapter.
  3. Call Center. Salesforce configuration.
  4. CCP. WebRTC panel inside Salesforce.

What usually goes wrong: Installing the package in the production org on the first try.

Quiz

HTML

Question 1

Which term matches this description? Salesforce Contact Center with Amazon Connect. Voice stays on Connect. Messaging can be Connect or Salesforce.

Show the cited answer

Salesforce Contact Center with Amazon Connect. Voice stays on Connect. Messaging can be Connect or Salesforce. The term is SCC-AC.

Salesforce Contact Center with Amazon Connect: Streamlining omnichannel customer engagement | AWS Contact Center AWS docs. last checked 2026-10

Question 3

Which term matches this description? CUCM or Webex keeps enterprise extensions. Connect keeps the public contact center number. They meet by transfer, not by a shared dial plan.

Show the cited answer

CUCM or Webex keeps enterprise extensions. Connect keeps the public contact center number. They meet by transfer, not by a shared dial plan. The term is Side-by-side.

Flow block in Connect Customer: Transfer to phone number - Amazon Connect Customer AWS docs. last checked 2026-10

Sources

HTML

Embed the Connect Customer Contact Control Panel (CCP) into Salesforce - Amazon Connect Customer AWS docs. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Ecosystem

HTML

Glossary

  • Salesforce CTI Adapter A managed package plus a serverless app that embeds the CCP in Salesforce.
  • SCC-AC Salesforce Contact Center with Amazon Connect. Voice stays on Connect. Messaging can be Connect or Salesforce.
  • ServiceNow Voice The ServiceNow integration that imports flows, maps queues to Advanced Work Assignment, and can attach AI voice agents.
  • Teams chat bridge A published pattern: a Teams app, Azure Bot Service, API Gateway, Lambda, and StartChatContact. It is chat, not a phone trunk.

Mind map

Open the Integrations mind map

Sister technologies

The CRM, the PBX, and the chat client each own a different seam. Mixing them up builds a transfer that pops the wrong record.

Config and troubleshooting

Installing the package in the production org on the first try.

Salesforce and ServiceNow do not receive contact attributes unless you write them and call out. The association is what lets the flow invoke the function that sets the customer id.

IntegrationAssociation Lambda functions

CloudFormation study snippet
Resources:
  PopAssociation:
    Type: AWS::Connect::IntegrationAssociation
    Properties:
      InstanceId: !GetAtt CampusInstance.Id
      IntegrationType: LAMBDA_FUNCTION
      IntegrationArn: !GetAtt ScreenPop.Arn

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Open the mapping room

Future hooks

Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.

Sources and go deeper

sources.json