This page presents the main steps for setting up the Salesforce Alcmeon connector, from the initial scoping to the checks to be carried out before production deployment.

Step-by-step implementation guide

Define your target operating method

Where will your advisors respond?

• From Alcmeon
• From Salesforce
• In hybrid mode

What data do you want to upload to Salesforce?

• Only conversations
• Conversations with Case Logic
• Conversations with routing or Omni-Channel
• Integrate Case , Routing , or Omni-Channel logic

Prerequisites

• Salesforce Alcmeon package installed
• Salesforce organization connected to Alcmeon
• Salesforce rights and configuration required

Package installation and authorization

Implementation steps

The connector setup follows three phases:

Phase 1 — Scoping: organize a kick-off meeting with your team and your Salesforce integrator to define the target operating method and present the technical documentation.

Phase 2 — Technical implementation: package installation, connection and configuration of a test Salesforce organization, then end-to-end testing. For detailed technical steps, see the implementation guide.

Phase 3 — Go-live: reproduce the validated test configuration on the production Salesforce organization, then run final checks.

Choose the synchronization mode to configure

Once your target operation is defined, activate the corresponding synchronization mode in Alcmeon.

• If your organization relies on an advisor response in Alcmeon, verify that linking to the correct Salesforce contact is part of the process.
• If your organization relies on routing conversations to Salesforce, verify that the mapping between Alcmeon teams and Salesforce queues is correctly configured.

The choice of synchronization method therefore depends less on a theoretical principle than on your operational organization and the processing circuit chosen.

Learn more about supported workflows

Pre-production checks

• Send a test message
• Check its arrival in Alcmeon
• Verify that the correct synchronization trigger is applied
• Check that the conversation has arrived in Salesforce
• Check the expected behavior in the queue or in Omni-Channel if necessary.

For step-by-step verification before production deployment, see the configuration validation procedure.

Omni-Channel

Use Omni-Channel with the Salesforce connector

If you use Salesforce as your primary processing interface, you can integrate the Alcmeon connector with Salesforce Omni-Channel to automatically distribute conversations to available agents . This compatibility applies to workflows where agents respond from Salesforce, or in a hybrid Alcmeon + Salesforce model where conversations are sent to Salesforce via team routing from Alcmeon.

To learn more about how this works, see the Omni-Channel configuration in Salesforce

What is Omni-Channel used for?

Omni-Channel allows for the automatic assignment of items to be processed by advisors in Salesforce, based on their availability. Within the Alcmeon connector, this means that when a conversation is synchronized in Salesforce, it can then be distributed to the appropriate advisors via standard Salesforce routing mechanisms.

How does this work with Alcmeon?

The important point to understand is that the Alcmeon package does not itself directly route conversations into Omni-Channel. It creates and updates objects in Salesforce.

It is then your Salesforce implementation that must create the work items and let Omni-Channel distribute them to the advisors.