AI-powered Halo ITSM configuration

Just describe what you need.
Halo configures itself.

Stop clicking through the admin UI. halo-cli lets AI agents configure your entire Halo ITSM instance from plain English — workflows, approvals, SLAs, custom fields, email templates, dashboards. What used to take a configurator a full day now takes a single prompt.

AI coding agent + halo-cli
Requirements

"Build an employee onboarding workflow for Meridian Health. Multi-step approval — manager, then IT, then HR. Custom fields for department, start date, and equipment needs. 3-day SLA with escalation. Email notifications at each stage."

Agent

I'll create the ticket type, custom fields, approval workflow, SLA, email templates, and a monitoring view.

$ halo api post /api/TicketType --data '[{"name":"Employee Onboarding"}]'
$ halo api post /api/FieldInfo --data '[{"name":"Department","type":"dropdown"}]'
$ halo api post /api/FieldInfo --data '[{"name":"Start Date","type":"date"}]'
$ halo workflow create --name "Onboarding Approval" --data @workflow.json
$ halo sla create --name "Onboarding SLA" --data @sla.json
$ halo email-template create --title "Onboarding: Pending Approval" ...
$ halo email-template create --title "Onboarding: Approved" ...
$ halo view create --name "Active Onboarding Requests" ...
 Created ticket type Employee Onboarding with 3 custom fields
 Built 3-step approval workflow (Manager → IT → HR)
 Set 3-day SLA with escalation to service manager
 Created 4 email templates for workflow stages
 Added dashboard view Active Onboarding Requests
40 Command Groups
818 Database Tables
Full SQL Read Access
MIT Licensed

Halo ITSM is powerful. Configuring it should be effortless.

Every Halo implementation is the same grind — ticket types, custom fields, workflows, approval chains, SLAs, email templates, views, dashboards. Detailed work, done manually, one click at a time. halo-cli changes that. Give your AI agent the requirements brief, and it configures everything for you. The entire admin surface, automated.

Describe the outcome. The agent handles the rest.

"Build an employee onboarding process with multi-step approval, asset provisioning, and automated notifications"

Onboarding Workflows

Creates the ticket type, custom fields, a multi-stage approval workflow, SLA with escalation, email templates for each stage, and a dashboard view for HR to monitor active requests.

ticket-type custom-field workflow approval sla email-template view
"Set up an SLA framework — P1 through P4 with escalation rules, breach notifications, and a real-time monitoring dashboard"

SLA Frameworks

Defines SLA tiers with response and resolution targets, creates escalation automations for each priority level, builds email templates for breach alerts, and configures a dashboard with SLA compliance widgets.

sla automation email-template dashboard webhook
"Build a service catalog with hardware requests, software access, and facilities — each with their own approval flow and fulfilment teams"

Service Catalog Design

Creates service categories, defines request types with category-specific custom fields, sets up approval processes per service, assigns fulfilment teams, and builds the end-user portal views.

service ticket-type custom-field workflow team view
"Restructure our ticket categories — merge duplicates, create new hierarchy, migrate existing tickets, and update all views and automations"

Configuration Migration

Audits existing categories via SQL, builds the new hierarchy, bulk-updates tickets to the new structure, updates views and filters, and adjusts automation rules — all without manual re-mapping.

sql category ticket view automation
"Create a change management process — CAB approval, risk assessment fields, rollback plans, and post-implementation review tracking"

Change Management

Builds the full ITIL change process: ticket type with risk and impact fields, CAB approval workflow, rollback plan templates, PIR scheduling via automation, and a change calendar dashboard.

ticket-type custom-field cab workflow automation dashboard
"Set up automated reporting — weekly ticket volume by team, SLA compliance trends, and asset warranty expiry alerts sent to stakeholders"

Reporting & Analytics

Writes complex SQL queries across FAULTS, AGENTS, and DEVICE tables. Builds scheduled automations, configures webhook integrations for delivery, and creates dashboard widgets for live metrics.

sql automation webhook dashboard email-template

Your agent already knows Halo. Just add the skill file.

halo-cli ships with a skill file that gives any AI coding agent deep knowledge of Halo ITSM — the full API surface, 818 database tables, legacy naming conventions, and multi-step chaining patterns. Drop it into Claude Code, Codex, or any agent. It just works.

SLA framework — end-to-end from requirements
Requirements

"Configure P1-P4 SLAs for NovaTech. P1: 15-min response, 2-hour fix. P4: 8-hour response, 5-day fix. Escalate breaches to the account manager. Add a compliance dashboard."

Agent

I'll create four SLA definitions, set up escalation automations, configure breach notification emails, and build the dashboard.

$ halo sla create --name "NovaTech P1" --data @p1-sla.json
$ halo sla create --name "NovaTech P2" --data @p2-sla.json
$ halo sla create --name "NovaTech P3" --data @p3-sla.json
$ halo sla create --name "NovaTech P4" --data @p4-sla.json
$ halo automation create --name "P1 Breach Escalation" ...
$ halo email-template create --title "SLA Breach: Immediate Attention" ...
$ halo dashboard create --name "NovaTech SLA Compliance" ...
 Created 4 SLA tiers (P1: 15m/2h through P4: 8h/5d)
 Built escalation automations for each priority
 Configured breach notification to account manager
 Published NovaTech SLA Compliance dashboard

818 database tables. Zero SQL required from you.

Need to audit ticket volumes before restructuring? Want to validate SLA compliance after a configuration change? Just ask. The agent writes the SQL, runs it across the full Halo database, and gives you the answer.

Natural language to SQL
You

"Before we restructure the ticket types, show me what we're working with — volume by type and how many categories each one uses."

Agent

I'll join FAULTS against REQUESTTYPE to get ticket volumes and category distribution per type.

$ halo sql query "SELECT r.RName as ticket_type, COUNT(*) as total, COUNT(DISTINCT f.Category1) as categories FROM FAULTS f JOIN REQUESTTYPE r ON f.RequestTypeID = r.RID GROUP BY r.RName ORDER BY total DESC"
 ticket_type         total  categories
────────────────────┼───────┼───────────
 Incident             1,847  23
 Service Request        931  14
 Change Request         289  8
 Problem                 74  6
You

"Now check SLA compliance over the last quarter — are the current targets realistic?"

$ halo sql query "SELECT f.Priority, COUNT(*) as total, AVG(DATEDIFF(minute, f.DateOccured, f.ResponseDate)) as avg_response_min, SUM(CASE WHEN f.SLAResponseActual > f.SLAResponseTarget THEN 1 ELSE 0 END) as breaches FROM FAULTS f WHERE f.DateOccured >= DATEADD(month, -3, GETDATE()) GROUP BY f.Priority"
 Priority  total  avg_response_min  breaches
──────────┼───────┼──────────────────┼──────────
 P1            42                12         3
 P2           187                48        11
 P3           534               186        27
 P4           891               412        15
 P1 and P2 targets look healthy (7% and 6% breach rate)
 P3 has a 5% breach rate — within tolerance
! P4 avg response is 412 min vs likely 480 min target — tight but holding

40 command groups. Every configurable entity in Halo.

Tickets, workflows, approvals, SLAs, services, automations, webhooks, dashboards, email templates — the complete Halo ITSM admin surface, programmable with halo <noun> <verb>.

ticket action sql user agent client site asset asset-type kb status category team contract ticket-type custom-field attachment report item invoice supplier workflow workflow-step approval ticket-approval sla dashboard view service project automation webhook email-template email-rule release custom-table lookup role cab api

What's next for AI-powered Halo configuration

Open source is the start. We're building the ecosystem to make AI-driven Halo ITSM implementations the new standard.

Launching Soon

Open Source on GitHub

MIT-licensed. Install with pip install halo-cli, point it at your instance, and start building. The AI skill file is included — drop it into any agent and it's ready.

In Development

Implementation Courses

Step-by-step courses on AI-driven Halo implementations. Workflow design, SLA frameworks, service catalog builds, change management — from requirements brief to production configuration.

In Development

Configuration Recipe Library

Battle-tested implementation patterns. Employee onboarding, incident management, change advisory, asset lifecycle, compliance reporting — each a complete, copy-paste configuration.