Work intake is how requests reach your team. For most teams the answer is "every way at once": email, chat, a comment in a meeting. Requests are lost, the same question is asked three times, and nobody can say how much is being asked of the team. A request form fixes that with one front door.
One front door
Pick one place where requests are made and say so plainly. The form does not need to be the only way to talk to your team. It needs to be the only way work gets onto the list.
When a request arrives some other way, answer with the link. It feels unhelpful for a week and then it is simply how things are done.
Ask for what you need to start
Every extra question lowers the number of people who finish the form. Ask for what you need to begin and no more: what is wanted, why, by when, and who to go back to.
Make the common answers a choice rather than a text box. A list of request types is quicker to fill in and far easier to sort later.
Decide where requests land
A form is only half of intake. The other half is what happens next. Send every response to one place, a "new requests" group, and agree who looks at it and how often.
Triage is a small, regular job: accept, ask a question, or decline with a reason. A request that sits unanswered teaches people to go back to chat.
Close the loop
People stop chasing when they can see their request has been seen. Tell them when it is accepted and when it is done. Those two messages are the easiest things in the whole process to automate.
Doing this in TaskNow
In TaskNow you build a public form with your own branding, map each question to a column and choose the group its answers land in. Every response becomes a real task, and any file attached stays private to the board. The person filling it in needs no account and sees nothing of the board.