Form fields: show, pre-fill, hide
Pre-fill a field, hide it with a fixed value, or fill it from the link, so one stack can serve every store, machine or campaign.
Your stack's fields are the form's questions. But you don't always want to ask every one. In the editor's Getting in step, click Set up the form →. Under Form fields, each field can be:
| Setting | What happens | Great for |
|---|---|---|
| Show | Asked as usual | Most fields |
| Show, filled in from the link | Asked, but the link pre-fills it | A best guess people can change |
| Hide, always this value | Not asked; every ticket gets the value you set | "Source: Website" |
| Hide, value from the link | Not asked; the link decides the value | One link per store or machine |
Make a link
Click Make a link, pick the values (like Location: South Lamar), and copy the Link with values or download its QR code. Print a different one for each store, room or piece of equipment, and every ticket arrives already knowing where it came from. Nobody has to type it, and nobody gets it wrong.
Why this matters
Fewer questions means more people finish the form. And values you set yourself are exactly right every time, so your reports by location or source are trustworthy.
Walkthrough: Take repair requests with a QR code.
Related
- QR codes and website embedsDownload a QR code for flyers and counters, or paste the form into your own website with one line of code.
- Web formsGive a stack a public request form, so customers and coworkers can ask without an account and every request lands as a ticket.
- Ticket fieldsEvery field type, when to use each, and how Required, help text and requester visibility make better tickets.
- LocationsAdd your stores, offices or sites with a shared email and a manager, then route tickets and emails to them.
🧭 See it in a how-to guide
- Take repair requests with a QR code · 20 minutes
- Run requests across several stores · 45 minutes
Still stuck? Email hello@ticketstacker.com. A real person reads every message.