Some processes require multiple forms to be filled by different people in different stages. When translating this to a workflow, it always results in suboptimal solution that requires too much manual work from the agent.
Instead, after a step, the workflow can send a task to a person to fill a form, result of which can be added as a child ticket to the initial ticket that triggers the workflow automation.
Also, having invisible service request forms that can only be accessed by their URLs would be really good. This way, only the person, who needs to fill the form at a certain stage, can see and access it through a certain link.
New Idea
Service Request Form Calls from Workflows
+2
+14- Top Contributor ⭐
Some processes require multiple forms to be filled by different people in different stages. When translating this to a workflow, it always results in suboptimal solution that requires too much manual work from the agent.
Instead, after a step, the workflow can send a task to a person to fill a form, result of which can be added as a child ticket to the initial ticket that triggers the workflow automation.
Also, having invisible service request forms that can only be accessed by their URLs would be really good. This way, only the person, who needs to fill the form at a certain stage, can see and access it through a certain link.
No good solution for this. Can be done in Journey with extra form.
Downside there are no good way to assign static stakeholders for it.
You could make workaround. Have a normal service item that trigger a journey using API. In that way you can set the stakeholders your self and then take the advantage of the form functions in Journey.
Join the Community
Already have an account? Login
Welcome back to Freshworks 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.