Olá @Nadir Isaacs, saudações do Brasil!
Based on your requirements, there are two viable architectural approaches, depending on whether you want a true agent-driven click-to-call experience or a campaign-driven outbound model.
Option 1: Embeddable Agent Workspace
For scenarios where the outbound call must be:
-
initiated by the user,
-
handled by the same user,
-
fully tracked in Genesys Cloud,
-
and controlled directly from the web application,
the cleanest approach is to embed the Genesys Agent Workspace (or outbound script) using the Embeddable Framework.
In this model, your third-party application passes context (such as the MSISDN) to the embedded agent experience, while Genesys Cloud natively handles call control, media, routing, and interaction history. This avoids the complexity of managing call state via APIs and aligns with standard agent-assisted outbound patterns.
Option 2: Outbound Campaign–driven model
Another possible approach is to drive the call via Outbound Campaigns:
-
The third-party application injects a contact into an Outbound Contact List via API.
-
The contact record includes the Genesys userId of the intended agent (for example, targetAgentId), and all other data that you want.
-
The campaign dials the contact.
-
In the outbound flow, you read targetAgentId from the contact data, using the apis, and apply routing logic to deliver the call to that specific agent, while the Agent Workspace is embedded in the third-party application.
This approach works well if you want to leverage outbound capabilities such as pacing, retry rules, compliance controls, and reporting. However, it introduces a campaign-driven behavior, which may not feel like an immediate click-to-call depending on the dial mode and campaign configuration.
-
If the goal is direct, immediate, agent-initiated outbound, embedding the Agent Workspace is usually the simplest and most robust solution.
-
If the use case benefits from Outbound Campaign governance and controls, injecting contacts into a campaign and targeting the agent via contact data is a viable alternative, with some trade-offs in timing and behavior.
Both approaches keep interaction history and traceability fully within Genesys Cloud; the choice depends mainly on the desired user experience and operational model.
------------------------------
Fernando Sotto dos Santos
Consultor Grupo Casas Bahia
------------------------------
Original Message:
Sent: 01-12-2026 04:46
From: Nadir Isaacs
Subject: Initiate outbound call from 3rd party web application
Hi Genesys Community
Requirement: initiate an outbound call via web application
we are in the process of unpacking a requirement to allow a user on a 3rd party application to initiate an outbound call, when the user starts the outbound conversation, we would like the interaction history to be stored within Genesys cloud for traceability.
User Stories:
- The outbound call must be handled by the user who initiated the call
- The interaction must connect the MSISDN that is on the web application
- The web application contains the MSISDN of a customer where their sales orders need to be confirmed
- The user must be able to end the conversation on the web application
(Possible) solutions
- Platform API and using PKCE as the authorization Type
- Chrome and Edge Genesys cloud extension
- Storing sales orders within a calling list and having the campaign dial out in power dialing modePlease kindly advise what is the cleanest solution or if there is a cleaner way we can initiate an outbound call via a web application.
regards
nadir Isaacs
#Integrations
#PlatformAPI
------------------------------
Nadir Isaacs
Specialist
------------------------------