Genesys Cloud - Developer Community!

Has anyone successfully used the params attribute on the Salesforce LWC lightning-click-to-dial component to pass through to the Voice Call record?

Salesforce documentation suggests we can pass a comma-separated list of parameters through to the third party phone system.

<lightning-click-to-dial value="14155555553" record-id="5003000000D8cuI" params="accountSid=xxx, sourceId=xxx, apiVersion=123">

I was expecting these to come through as participant attributes that I could then map to the Salesforce Voicecall custom fields. 

Unfortunately, no luck so far. Are params supported?

Hi Andy,

From what I've seen, this behavior depends heavily on which Salesforce integration model you are using.

With the older Genesys Cloud for Salesforce connector, custom attributes/interaction data were much more exposed through screen pop, participant data, and custom mappings, so some customers managed to pass additional metadata using custom integration logic.

However, with CX Cloud from Genesys and Salesforce, the architecture is different because Salesforce owns part of the telephony orchestration and VoiceCall object lifecycle.

From my understanding, the params attribute in lightning-click-to-dial is primarily intended for the third-party telephony adapter invocation itself, but Genesys Cloud does not automatically convert those params into participant attributes or VoiceCall field mappings natively.

So even though Salesforce passes:

params="accountSid=xxx,sourceId=xxx"

those values do not automatically appear in:

• participant data
• conversation attributes
• VoiceCall mappings
• Architect flow variables

at least not out-of-the-box in CX Cloud.

I believe this is why you are not seeing them available for VoiceCall custom field mapping.

In practice, the more reliable approaches I've seen are:

• using custom participant data injection through Architect/Data Actions
• custom screen pop parameters
• Salesforce-side custom logic/LWC handling
• or middleware APIs to enrich the VoiceCall after creation

especially in CX Cloud environments.

One important distinction:
the older Genesys Cloud for Salesforce package offered much more customization freedom inside the embedded client model, while CX Cloud is more standardized around the Service Cloud Voice framework and therefore exposes fewer low-level interaction customization points.

So I do not believe params are currently natively mapped into Genesys participant attributes automatically in either integration model.