Forms
Forms are Submitt's lightweight information-collection feature. A member presses a Form button in Discord, answers the configured questions, and Submitt creates a private response channel for that submission under the configured category.
A completed Form creates a private response channel with priority controls, a staff close action, and a stored transcript when closed. Forms still do not use Ticket claim ownership, support-hours schedules, SLAs, satisfaction surveys, or the broader Ticket automation lifecycle.
What you configure
Use Copy to Server in the Form editor to duplicate the title, description, button text, confirmation message and questions to another licensed server. The destination Form starts disabled with no launcher channel, response category, approved roles or published Discord message, so you can map the new server safely before publishing.
Use Duplicate to clone the Form channel, response category, approved roles, questions, confirmation message and other settings in the current server. The duplicate starts disabled and unpublished and does not copy submissions or response-channel history.
Questions
A Form can contain up to 25 questions. Supported answer types are Short answer, Long answer, Single choice and Multiple choice. Questions can be required or optional.
Discord limits one modal to five components. Submitt automatically splits longer Forms across multiple pages and retains the member's draft between pages for up to 24 hours.
Response workflow
After submission, Submitt creates a private response channel. Approved staff can change the response priority between Low, Normal, High and Urgent. Closing the Form locks the conversation, records the closing staff member and reason, and generates a transcript from the complete Discord conversation.
The submitter and approved staff can access the stored transcript from the closed response workflow. If a transcript archive channel is configured, Submitt also posts a transcript link there.
Combined Form Panels
Two to twenty-five Forms can be grouped into one public Discord Multi-Panel. Choose Buttons or a Dropdown. Selecting a Form from the grouped launcher starts that Form normally; each Form still keeps its own questions, response category, approved roles, priority/close controls and transcripts.
Normal workflow
Forms vs Tickets
You need structured intake followed by a private response channel with priority, closing and transcript history.
You need the broader support lifecycle: claims, member management, support hours, SLA tracking, automations, satisfaction surveys and advanced operational controls.
Older Submitt Tickets may still have a reusable ticket-intake template attached. Those existing Tickets remain compatible, but new standalone Forms are managed separately under Forms and are not attached to Tickets.