HaloPSA configuration map
Give the assistant your real ticket statuses, types, SLAs, teams and custom field definitions so its SQL uses your IDs and names instead of guesses.
Last updated on
Every HaloPSA instance is configured differently. Your ticket statuses, request types, SLAs, priorities, teams and custom fields all have IDs and names that only exist in your instance. Without them the assistant has to guess, and a guess like "closed is status 9" is right for most instances but not all.
The configuration map fixes that. It is a snapshot of your instance's lookup lists, stored against your account and sent to the assistant with each message so its SQL is grounded in your actual configuration.
What it contains
The map is made of read-only lists, grouped into sections:
| Section | Lists |
|---|---|
| Tickets | Statuses and their SLA hold, ticket / project / sales types and their settings, SLAs, priorities, workflows, ticket sources, ITIL types, categories, actions and their groups |
| People & Access | Teams (and whether they handle projects or opportunities), agent roles, end-user roles |
| Clients & Contracts | Customer types, contract types and sub-types, contract statuses |
| Billing & Finance | Currencies, budget types, charge rates, quote and sales order statuses (with what Halo treats each as, such as accepted or invoiced) |
| Assets | Asset types, asset statuses |
| Custom Fields | Your custom field definitions for each area (tickets, clients, sites, users, assets, contracts, actions, agents), plus custom tables and other areas, and the built-in asset fields |
Only configuration is captured. No tickets, clients, sites, users, agents, suppliers or any other operational data is read or stored. Inactive entries are left out because they cost tokens and add nothing.
Capturing your configuration
Open Configuration Map in your profile menu. The page is called HaloPSA Configuration Map.
- With a connected Halo integration: select Run full configuration map and confirm to capture everything in one go. The capture only reads from HaloPSA and saves nothing there. It replaces the lists already on the page, including any you have edited. To refresh one section, use the refresh button on its header, or Capture on a section you have not captured yet. Without a connection the button is greyed out; see Integrations to connect Halo.
- Without an integration: select Import manually. Under Configuration map, select Copy SQL, run it as a report in HaloPSA, export the results as JSON, paste them into the box and select Import. The report returns one row per list, so the whole map is imported in a single step, and the step then shows how many lists it imported. The second step, Custom field usage, opens once custom fields are imported: select Copy usage SQL, run that the same way and import its results in that box, so unused custom fields start switched off (see Custom fields).
Refresh a section whenever you change that part of your configuration, for example after adding a custom field or a new ticket type.
Choosing what the assistant sees
The switch at the top of the page turns the whole map on or off. Each section has its own switch, and Custom Fields has one per area, so you can send ticket fields without sending, say, contract fields. Inside a custom field list, each field has its own switch too. Switching something off leaves its data in the map, so you can switch it back on without capturing it again.
The same switches are in the quick AI settings panel in the chat input, for the sections and areas you have captured:
Tickets
People & Access
Clients & Contracts
Assets
Custom Fields
Tickets
Asset Custom Fields
Editing a list
Expand a list to see its entries and when it was captured. Delete any rows you do not want the assistant to see, then select Save. Remove deletes the whole list. To clear a section or the whole map, use Delete section or Delete all.
Token cost
The map is added to every message you send, so it counts towards your usage. The page shows how many entries each list holds and how many tokens it adds per message, and the top of the page shows the total for everything switched on. Small lookup lists cost very little. Custom field definitions are the largest part for most instances, which is why they can be switched per area and per field, and why fields nobody uses start switched off.
The map is cached for five minutes between messages. The first message, and any message sent more than five minutes after the previous one, writes it to the cache at 1.25 times its token count. Each message within five minutes reads it back at a tenth of the cost (see Caching). See Understanding tokens for how this fits into your allowance.
Custom fields
Halo lets an administrator choose, per custom field, whether its value is
stored as a column on the parent record or as a row in the FieldData table.
The two need different SQL. The map records which storage each of your fields
uses, so when you ask about a custom field the assistant already knows its
name, its type and how to read it, and does not need to ask you first.
Capturing custom fields also counts how many records hold a value for each one, shown as In Use. A field that no record has ever filled in, including a checkbox nobody has ticked, starts switched off, so it costs nothing. Switch it on, or switch any other field off, from its row in the list. Your choice is kept when you capture again, unlike deleting a row, which the next capture brings back. Fields of the Custom Table type cannot be counted and stay on.