Email is the main way requests come in, but a request form lets a customer submit one through a structured form instead: useful when you want specific details up front (an account name, a category, a priority) rather than whatever they happen to type. Forms and email feed the same Inbox.
Forms live in Settings → Service Desk → Request Forms, the same forms used for ordinary item requests. A form has a title, a destination (the workstream or item submissions are filed under), the work type it creates, and a list of components you arrange in order: headings for section labels and instructions, item fields such as title and description, and custom fields from the work type's collection. Each field can be labeled, given a default, and marked required or hidden.
To make a form feed Service Desk:
In the forms list, forms that create tickets carry a Ticket badge and listed ones a Portal badge, so you can tell at a glance which forms feed the Inbox. Forms can be grouped for easier management.
Each form row has a drag handle beside its title. Drag a form up or down within its group; the order is saved as you drop it. New forms go to the end of their group.
Groups have an order too. Each group header has a grip; drag a group up or down (or focus the grip and use the arrow keys) and the groups are saved in that order. Other, the forms in no group, always stays last. A new group goes to the end until you move it.
Customers see both orders on the portal's Submit a request page: your groups as section headings, in your group order, with each group's forms in your form order underneath, and any ungrouped forms under Other. A portal whose forms are all ungrouped shows one plain list.

A submission creates a ticket at the form's destination, as the form's work type, with the submitted values on the item. The submitter becomes a requester and the ticket's channel is Portal. The ticket also remembers which form it came through, so customers can group My requests by request form; tickets from email, the API or before 25 October 2026 have no form and group under Other requests.
A required rich-text field, such as the description, must contain real content; an empty paragraph doesn't count.
If your organization receives more than 100 form submissions from people who are not signed in within one hour, each further new submitter that hour is asked to confirm their email first. Their request waits (nothing is refused or lost) and shows the requester as Pending verification. They are verified as soon as they prove the address in any way: clicking the link, signing in to the portal, or emailing your desk from that address. Signed-in customers are never asked.
Attach a form to a channel address as its Default request form so new tickets from that address, by email or opened by your team for a client, are filed through the form: its location, its work type and its field set. See where a ticket actually lands.
Switch on List in customer portal to show the form on the portal's Submit a request page, under its group and in the order you set in the forms list. Only groups that hold at least one listed form appear on the portal, so a group of internal-only forms stays out of sight. Listing is per form and off by default:
What customers see. Customers are never shown Relationships or user / item reference fields. If such a field is hidden and carries a default (a default reviewer, say), the default still applies; if the work type or form requires a reference field, you must give it a default before the form can be saved as public or listed. Hidden fields keep their defaults. A default saved through the API in a shape the ticket can't take is skipped and the submission still goes through.
Required fields are enforced on submit, on the portal, the public link, and the API alike. A required checkbox left unticked counts as "no", a required calculated field is worked out once the ticket exists, and explicit No and 0 answers are kept as entered.
The Item Request Submitted automation trigger fires for every form submission, ticket or not, so you can route or notify from there. See Setting Up Basic Automations.
Managing forms, and reordering them, needs the Manage Service Desk Settings permission.
Working a Ticket
Triage from the Inbox, open a ticket for a client, reply to the customer by email, copy other people on the conversation, keep internal notes separate, fix the requester, merge duplicates, and understand what the customer sees as the ticket moves through your statuses.
Held for Review and Rejected Mail
Some inbound mail is held back instead of becoming a ticket or an article reply. Review what was held and why on the Held for review tab, recover real messages, and use Rejected mail to answer 'did this email reach us?'