Hello @Fabian Teves - greetings from Brazil!
If I understood correctly, you already have the dropdown populated with destination numbers, and now you want to start a conference to the selected number (instead of doing a blind transfer).
Here's the key point: in Genesys Cloud Scripts, the native "telephony actions" exposed by Scripter are Blind Transfer and Consult Transfer (to a number, queue, or user). There isn't a native "Conference" script action in the standard list of available script actions.
But, you can performe a consult transfer from the script:
-
Use your dropdown value as the target for Scripter.Consult Transfer.
-
After the consult leg is established, the agent can then use the client UI controls to convert to a conference (depending on the client experience and permissions).
-
This keeps the script "native" and avoids custom API orchestration.
If you were hoping for a "conference transfer" action directly in the script (similar to blind/consult), that capability doesn't appear in the official script actions list today. If you share which client your agents use (Agent Workspace vs embedded client / integration), I can suggest the cleanest approach for that specific UI (some experiences make the "consult → conference" step clearer than others).
Available script actions View summary - Genesys Cloud Resource Center
------------------------------
Fernando Sotto dos Santos
Consultor Grupo Casas Bahia
------------------------------