Create your first stack
Pick a template that's close to what you do, rename a few things, and you're ready for tickets in minutes.
A stack is where one kind of work lives. The fastest way to start is a template: it comes with fields, steps and even emails already set up, and you change what doesn't fit.
Start from a template
- Go to Stacks and click + New stack. (Your very first time, the button says + Create stack, next to the cactus.) (Only company Admins see this button. If you don't, ask an Admin to change your role.)
- Browse the templates, grouped by Operations, Sales, Finance, People and more: Customer orders, Facility requests, IT help, Purchase requests, Time off requests, Vehicle maintenance and others. Each card shows how many steps and fields it has.
- Pick the closest one. Don't worry about a perfect match; everything can be changed.
- Give the stack a name and a short ticket ID prefix (like FR for facility requests). Ticket numbers will look like FR-1, FR-2.
Prefer a blank slate? Choose Start from scratch and build it your way.
Make it yours
The editor walks you through seven short steps, one job each. You'll find a full tour in The stack editor:
- Name: the name, description, color and an optional icon.
- Fields: what you need to know about each request. See Ticket fields.
- Getting in: how requests reach you: the app, a web form or QR code, email, schedules or other tools.
- Stages: the stages a ticket goes through, like To do → Doing → Done. See Statuses and steps.
- Rules: what has to be filled in before a ticket moves on. See Step rules.
- Automations: optional work the stack does for you, like emailing the requester. Skip for now is fine.
- Sharing: who can see it and what they can do. See Who can see a stack.
Click Save stack when it looks right. Your stack appears on the Stacks page, ready for tickets.
Good first changes
- Rename fields to the words your team already uses.
- Mark the details you can't work without as Required.
- Turn on the web form so requests come straight in.
Next: Invite your team.
Related
- The stack editorA quick tour of the seven steps, plus how drafts and publishing keep your team's work safe while you make changes.
- Ticket fieldsEvery field type, when to use each, and how Required, help text and requester visibility make better tickets.
- Statuses and stepsStatuses are the big picture (New, In progress, Done); steps are the real stages inside them. Here's how to set both up.
- Web formsGive a stack a public request form, so customers and coworkers can ask without an account and every request lands as a ticket.
🧭 See it in a how-to guide
- Take repair requests with a QR code · 20 minutes
- Track customer orders and keep customers posted · 30 minutes
- Set up a simple IT help desk · 20 minutes
Still stuck? Email hello@ticketstacker.com. A real person reads every message.
