In our use case, agents perform key activities—for example, the IT team creating a user’s email address or the HR team creating an employee ID. While there is an option to add a stakeholder, the dropdown consistently shows “No options available.” Is this expected behavior, or could this be a bug?
Solved
Journeys – Stakeholders: We should be allowed to select agents as Stakeholder in a Journey as they perform certain activities.
Best answer by asduhj312
Hey
I also wish FS would add the feature to create a ticket and then assign tasks to the ticket from within the Journey instead of doing Workflow Automation tasks. They’re already doing this for Service ITs, generating Child Activities, why don’t they translate that to Ticket creation as well? 🤷♂️
- Edit your journey
- Select the “Request For” field in the Initiator Configuration section of the Journey
- Make sure people who submit the Journey cant see the field, so “not visible to initiator”.
-
- Set the Data Source to “All Agents”
- Make sure the “Request For” is updated in Stakeholders
-
For me, this works pretty well.
Hey
I also wish FS would add the feature to create a ticket and then assign tasks to the ticket from within the Journey instead of doing Workflow Automation tasks. They’re already doing this for Service ITs, generating Child Activities, why don’t they translate that to Ticket creation as well? 🤷♂️
- Edit your journey
- Select the “Request For” field in the Initiator Configuration section of the Journey
- Make sure people who submit the Journey cant see the field, so “not visible to initiator”.
-
- Set the Data Source to “All Agents”
- Make sure the “Request For” is updated in Stakeholders
-
For me, this works pretty well.
Join the Community
Already have an account? Login.
Sign in to the Community
No account yet? Create an account.
Social Login
Login for Freshworks Employees Login with LinkedInor sign up below
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.