Getting the best results

How to phrase requests so the assistant produces accurate, useful HaloPSA reports first time.

ElegantInsights is an expert at writing SQL queries for Halo. It already knows your Halo database schema and the SQL patterns the reporting engine accepts, so you don't need to know SQL. You just need to describe the report you want clearly.

What the output looks like

Ask in plain English and the assistant returns a ready-to-run HaloPSA query, exactly as it appears in the chat. Pick a question to see how the phrasing maps to SQL:

Pick a question:

List open tickets this month with customer and status

Assistant

sql

SELECT    f.FaultID AS [Ticket ID],    f.Symptom AS [Subject],    a.aareadesc AS [Customer],    ts.TStatusDesc AS [Status],    f.DateOccured AS [Date Opened]FROM Faults fJOIN Area a ON a.AArea = f.AreaIntJOIN TStatus ts ON ts.TStatus = f.StatusWHERE f.FDeleted = 0    AND f.Status <> 9    AND f.DateOccured >= @startdate    AND f.DateOccured < @enddate

SELECT    f.FaultID AS [Ticket ID],    f.Symptom AS [Subject],    a.aareadesc AS [Customer],    ts.TStatusDesc AS [Status],    f.DateOccured AS [Date Opened]FROM Faults fJOIN Area a ON a.AArea = f.AreaIntJOIN TStatus ts ON ts.TStatus = f.StatusWHERE f.FDeleted = 0    AND f.Status <> 9    AND f.DateOccured >= @startdate    AND f.DateOccured < @enddate

Say what you want, specifically

The assistant does best when your request names the entity, the columns, and the date filter you care about.

Show me open tickets

The assistant has to guess which tickets, which fields, and over what period, so the report may not match what you had in mind.

List all tickets by date closed, grouped by agent, with the count and average time to resolution.

Names the entity (tickets), the date filter (date closed), the grouping (agent), and the metrics (count, average resolution time). You choose the actual period when you run the report.

Tips that consistently help

Name the date filter

Say which date to filter by (created, closed, logged) rather than a fixed period. Reports use Halo's runtime date range, so you pick the actual dates each time you run the report.

Name the columns you need

Ask for the specific fields you want rather than 'everything', it's clearer and uses fewer tokens.

State the grouping & metrics

Say how to group (by agent, client, priority) and what to measure (counts, averages, sums).

Iterate in follow-ups

Refine in the same chat: 'now only include priority 1' or 'add the client name'. The assistant keeps context.

Let your settings do the repetitive work

If you always want the same style, set it once in AI settings instead of repeating it every prompt:

Prefer terse output? Set SQL Column Detail to Concise and turn off Brief Explanations / Report Summary.
Need formal language for client-facing reports? Turn on Professional Mode.
Have a standing rule? Put it in Custom Instructions (e.g. "Always exclude cancelled tickets").

AI settings: every formatting and output option explained.
Use fewer tokens: tighter prompts leave room for more turns.