The ‘Request for Someone Else’ checkbox doesn’t show up until after the requester hits Place Request. This is incredibly inconvenient and often missed. Is there a way to get this to be the FIRST FIELD on all Service Requests instead of have it hidden after clicking Place Request? We have had to result to adding another field for ‘who are you requesting this for’ because it’s too confusing for end users.
New Idea
"Request for someone else" should be First in Service Request, not after hitting Place Request
Thank you for bringing this to our attention. We understand the inconvenience caused by the current placement of the 'Request for Someone Else' checkbox. We'll prioritize exploring ways to make it the first field on all service requests for improved clarity. Your feedback is appreciated as we work towards enhancing the user experience. Check my new startup here Menu prices.
+5- Top Contributor ⭐
I strongly support this suggestion as it is a major pain point.
It’s useless building workflows based on the ‘Requested For’ field when it’s so easy for a requester to leave this blank, in such a way that a request that should be raised for someone else appears for ‘self’.
What workaround do you suggest ?
In addition to making this a standard option on all forms, I believe there should be an option to make the checkbox mandatory based on field selection within the form. This way it will re-enforce to the end users that they need to enter in the the Requeted For user’s name or email address.
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.