Operations, IT, finance, and HR teams
Internal request forms your team can actually run
Internal requests arrive as chat messages until someone builds the form. The form only sticks if it asks the right questions per request type — and if the team can run it without you.
The reason internal requests keep arriving as messages is that the form asked for everything and so answered nothing. An expense claim and an access request have almost no fields in common; a form that unions them is longer than either and worse than both.
One request type per branch fixes it. A single "what do you need" question at the top, then conditional rules reveal only the fields that request actually requires. The requester sees a short form; you receive a complete one.
The other half is who runs it. Team invites bring colleagues in by email link with roles — owner, admin, editor, viewer — so the person who owns the process can edit the form and the people who only need to read responses get exactly that. Per-request PDF export gives finance or an approver the single document they asked for, and webhooks put the request into the ticketing system where it will actually be worked.
What carries this in FormXen
One form, many request types
Multi-condition rules reveal the fields a request type needs and hide the rest, so a single form serves processes that share almost no questions.
Roles for the people who run it
Invite teammates by email link as owner, admin, editor, or viewer, so maintaining the form and reading responses are separate permissions.
A document per request
Download any single submission as a PDF — the format approvals and finance tend to ask for — without exporting everything.
Into the queue it belongs in
Webhooks post each request to your ticketing or ops system on submit, and email notifications reach the team meanwhile.
How it is set up
- Start from the bug report, expense claim, or onboarding template, or describe the process to Create with AI.
- Open with one question that identifies the request type.
- Add conditional rules so each type reveals only its own fields.
- Invite the team with roles — editors to maintain the form, viewers to read responses.
- Export a PDF per request for approvals, or send a webhook into your ticketing tool.
Start from a template
Questions teams ask
Can one form handle several kinds of request?
Yes, and it is usually the right shape. Ask the request type first, then use conditional rules so each type reveals only its own fields. The requester sees a short form and you receive a complete one.
Can teammates read responses without being able to edit the form?
Yes. Roles are owner, admin, editor, and viewer, so reading submissions and changing the form are separate permissions. Teammates join by email invite link.
Can approvals get a document rather than a spreadsheet row?
Yes. Any individual submission can be downloaded as a PDF, which is generally what an approver or a finance team is asking for.
Can requests be pushed into our ticketing system?
Yes. A webhook posts each submission to your endpoint as it arrives, so the request lands in the queue where it will be worked rather than in an inbox.