Can the “reason” field for Zoom Marketplace app requests be made mandatory, and what intake information do others collect?
Hi everyone, I’m exploring governance and intake processes for Zoom Marketplace app requests in an enterprise university environment.
At present, when a user clicks Request to Add for a Marketplace app, the request email we receive only contains very limited information such as:
-
requestor name
-
requestor email
-
app name
There is also an optional reason field in the Zoom request pop-up, but in practice this is often skipped, and we are also finding that it may not reliably carry through into our downstream ticketing workflow.
I wanted to ask whether anyone in the Zoom Community has dealt with similar issues and, if so, how you approached them.
I would like to know:
- Can the “reason” field on a Zoom Marketplace app request be made mandatory?
- Has anyone successfully passed that field into ServiceNow or another ticketing system?
- What minimum fields do you collect before deciding whether to review an app request?
- Do you use a second intake form or triage form to gather purpose, users, cost, accessibility, privacy, and security details?
Any advice or examples from higher education or enterprise settings would be appreciated.
Thanks.