Platform Capabilities

What Gene builds. And what it won't.

Most ServiceNow AI tools sell a fantasy: type a story, get production code. The reality is messier. Some artifacts the agents handle end-to-end. Some need a human in the middle. Some we won't touch at all. Here's the honest map — so you can plan around it instead of finding out at deployment.

01The honest capability matrix

Three tiers. One straight answer per artifact type.

Every ServiceNow artifact maps to one of three tiers based on real delivery data. HIGH means the agents handle it end-to-end with high accuracy. MEDIUM means the agents draft it and a human reviews. LOWER means the agents help, but a senior engineer runs the work. The classifications are what we'd put on a contract.

High Fit
90–100% · End-to-end automation
Fully autonomous. The agent team builds, tests, evidences, and packages without a human in the middle.
Service Catalog items — variables, sets, fulfillment, approval gates
Notifications & templates — content, conditions, recipients
Client Scripts — onLoad, onChange, onSubmit, mandatory logic
UI Policies — show/hide, mandatory, read-only conditions
Knowledge Articles — KB seeding, structuring, refresh
System Properties — config flags, defaults
Scheduled Jobs — schedules, scripts, recurrence
User / Group / Role admin — onboarding, role assignment, deactivation

Reviewer effort: spot-check. The agents have a clean track record on these artifact types — review is a sanity pass.

Medium Fit
65–85% · Draft + human review
Agents produce a working draft. A senior engineer reviews logic, edge cases, and integration boundaries before merge.
Business Rules — async, before, after, query
Script Includes — server-side reusable logic
UI Actions — server & client-side execution paths
Outbound REST & Inbound Scripted REST APIs
Transform Maps — field mapping, transform scripts, coalesce logic
Service Portal Widgets — HTML, server, client controllers
Reports & Dashboards — list reports, bar/pie/trend charts
ATF Tests & Fix Scripts — generate, parameterize, run
Inbound Email Actions — parsing rules, action scripts
Scoped App scaffolding — table design, navigation, basics

Reviewer effort: meaningful. Architect reads the diff, runs the ATF, signs off. Same review as a junior dev's PR.

Lower Fit
40–65% · Assist, don't autopilot
Agents help — pattern lookup, scaffolding, code review — but a senior engineer drives the work end-to-end.
Multi-component orchestrations — workflows spanning many tables, integrations, and gates
Performance Analytics indicators — formula design, scoring, breakdowns
Service Portal full-page builds — multi-widget composition, custom theming
Mobile Studio builds — native apps, screen flows, push config

Reviewer effort: the agent is a junior pair-programmer. The architect designs and owns the work — the agent accelerates the mechanical parts.

02What we won't touch · 12 hard exclusions

Twelve areas where autonomous AI is the wrong tool.

ACL design

Security boundaries are a human-architect call. Agents don't design ACLs.

Flow Designer action graphs

Visual orchestrations remain in human hands.

CMDB Identification & Reconciliation Engine

IRE rules drive your single system of record. Don't let an agent guess.

Service Mapping & Relationship discovery

Agents don't author dependency topology.

Performance Analytics collectors

Frequency, rollup, and snapshot logic stay with the analyst.

UI Builder / Workspace experiences

Component composition is hand-crafted.

Discovery & Service Mapping configuration

Patterns, credentials, schedules — human-owned.

NLU / Virtual Agent corpus

Intent design and utterance curation is a domain task.

SSO / SAML / IdP configuration

Identity is a security boundary, not an automation target.

MID Server lifecycle

Provisioning, certificates, network paths — infra team's domain.

Production deployments

The CAB calendar exists for a reason. Promotion is human-driven.

Domain-separated configurations

Cross-domain logic is a senior architect call.

If you're being told an AI tool can do all of this end to end, ask for proof. We don't claim it because it isn't true.

03How it knows ServiceNow

Trained on everything. It learns from its mistakes.

The agents didn't start cold. They were trained across the entire ServiceNow knowledge surface — backed by an embeddings store — and a self-healing loop plus lessons-learned files mean they get more reliable the longer they run on your instance.

Trained on
ServiceNow product documentationUpgrade & release notesProduct fixes & known errorsServiceNow YouTube transcriptsCommunity notes & forumsPartner-portal methodologiesSupport documentationGeneWorks delivery IP
Self-healing

When a build or test fails on a known pattern, the agents repair and re-run it automatically — the same one-click Fix ATF / Fix FT you see in the Verify stage.

Lessons learned

Every mistake is written to a lessons-learned file the agents read before they act — so the platform stops repeating errors and gets sharper on your specific instance.

Embeddings store

A database layer with embeddings lets the agents retrieve exactly the right ServiceNow knowledge for the task in front of them — not generic answers.

04Module coverage

Where the loop runs today.

The continuous loop is live across ITSM and ITOM with full agent support. CSM, HRSD, FinOps, and SecOps follow on the published roadmap. Below is what's available now — and what each workspace handles end-to-end.

ITSM Workspace · Live

Incident, Problem, Change, SLM, Knowledge

End-to-end ITSM delivery in the continuous loop — catalog item creation, business rule modifications, SLA reconfiguration, knowledge article authoring, change management workflow updates. Full ATF coverage on every build, every story, every release.

IncidentProblemChangeSLMKnowledgeService Catalog
ITOM Workspace · Live

Discovery, Service Mapping, Event Management, AIOps

The ITOM agent handles event rule generation, alert correlation logic, threshold tuning, and CMDB CI class extensions. Service Mapping pattern configuration sits in the medium-fit tier; the underlying topology and dependency authoring stays human-owned.

Event MgmtAlert correlationCMDB CI extensionAIOps thresholds
CSM Workspace · Q3 2026

Customer Service Management

Case management, omni-channel routing, account hierarchy, customer portal builds. Same continuous loop, same two human gates, same ATF coverage. Cross-workspace dependency awareness flags conflicts with ITSM routing automatically.

Case mgmtOmni-channelCustomer Portal
HRSD Workspace · Q3 2026

HR Service Delivery

Employee lifecycle workflows, onboarding orchestration, HR case management, employee document templates. Bidirectional dependency tracking with ITSM (provisioning), CSM (employee-as-customer flows), and downstream identity systems.

Employee onboardingHR casesDocument templates
Integrations · Live

REST, Spokes, Inbound & Outbound

The Integration agents handle Outbound REST messages, Scripted REST APIs (inbound), IntegrationHub spoke configuration, and transform maps. Authentication flow design, secret management, and gateway sizing remain human-driven.

Outbound RESTScripted REST APIIntegrationHub spokesTransform maps
Custom Apps · Live

Scoped Application Engineering

Scoped app scaffolding, table design, business rules, client scripts, integration patterns, basic Service Portal widgets, full ATF coverage. The agent team delivers the build with documentation and tests included — not bolted on after.

Scoped appsTable designServer / client logicATF coverage

Want to see the loop in motion? Walk through the six stages, the two human gates, and the agent roster.

See How It Works →