Halo's form builder lets you add, reorder, and customise every field on every ticket type — no developer, no database knowledge required. Your forms adapt to your process, not the other way around.
Form Building
Halo includes nine field types out of the box. Mix and match them on any form, in any order, for any ticket type — entirely through the admin interface.
Single-line input for names, references, short answers, and identifiers.
Multi-line text area for detailed descriptions, instructions, and longer notes.
Dropdown for choosing one option from a defined list — static or dynamically populated.
Dropdown that allows multiple values to be selected — useful for tagging, categories, or affected services.
Date pickers and time entry fields for go-live dates, deadlines, and scheduled maintenance windows.
Yes/no toggles for confirmations, compliance acknowledgements, and binary decisions.
Let users add multiple structured entries — line items for orders, equipment lists, or approval recipients.
Full editor with images, screenshots, links, and formatting — for detailed notes or instructions that need structure.
Pull live data from Halo or external systems — HR platforms, asset databases, third-party tools — without storing a copy inside Halo.
Smart Visibility
Fields appear and disappear based on what the user selects. The form doesn't hide fields behind blank space — it collapses and reflows. Set visibility rules in the admin interface without writing a line of code.
Show or hide any field based on the value of another. "If Department = HR, show Job Band." Rules are set per field, per audience.
When a field is hidden, the form reflows — blank gaps don't appear. The mobile experience is clean and compact regardless of how many conditional fields are in play.
Every field value is available to Halo's routing rules, SLA profiles, and workflow automations. The data you capture on the form becomes the trigger for what happens next.
New Starter Request — Self-Service Portal
GitHub Username only appears when Engineering is selected — not visible to other departments.
Role-Based Rules
The same form can behave differently depending on who is raising the ticket. End users see a streamlined experience. Agents see the full detail they need to process and close it.
Show only what the person raising the ticket needs to fill in. Technical fields like Category, Priority, and Assignment Group stay hidden — they don't know the answer, and you don't need them to.
Required fields for agents ensure the data quality that drives automation. Before an agent closes or reassigns a ticket, the form enforces the fields that matter for reporting, SLA, and routing.
Mandatory fields at each workflow stage mean tickets can't progress without the right data. Agents aren't chased for information after the fact — Halo enforces it at the right moment.
3 fields. Clean, fast, no confusion.
5 fields. Full data for reporting, SLA, and routing.
Dynamic Lookups
Single-select and multi-select fields don't have to use lists you maintain manually. Connect them to any system with an API and let Halo pull the options in real time — without storing a copy of the data inside Halo.
How a dynamic lookup works
Configure a Custom Integration in Halo — set the base URL and authentication method for your external system.
Define a Method — the specific API endpoint to call, with the output mapped to an ID and a display value.
Attach the Method to a single-select or multi-select field — the dropdown is populated live when the form loads.
The selected value is stored against the ticket — the source data stays in the external system, always current.
FAQ
Allied ESM configures Halo forms as part of every implementation — designing the right fields, visibility rules, and role settings for your processes from day one.