ITSMJune 27, 2026
IT Service Desk Starter
A simple service desk for a small IT team. Log incidents when something breaks, take service requests from a catalog or by free text, and move each ticket from new to resolved to closed without a heavyweight tool. Turn on a knowledge base so common answers get written once and reused, a request catalog so people ask for the right things, and SLA clocks so nothing sits too long, each when you are ready. Start with just tickets and grow into the rest as your team and your process mature. Built for IT teams that want ticketing and self-service without standing up a full enterprise service-management suite.
Use the IT Service Desk Starter semantic blueprint
/semantius-admin use the architect, analyst and modeler skills to update the semantius platform with the model specified in https://www.semantius.com/blueprints/itsm-starter-semantic-blueprint.mdEntity summary
| Name | data_object | Description |
|---|---|---|
| Incidents | service_incidents |
Unplanned service interruptions or quality reductions, with severity, priority, category, assignee, and affected components. |
| Knowledge Articles | knowledge_articles |
Knowledge-base articles backing self-service portals and agent-assist tools, moving through draft, review, published, and retired. |
| Service Catalog Items | service_catalog_items |
Definitions of what can be requested: the request form, fulfillment workflow, approvals, service level, and charge-back rules. |
| Service Requests | service_requests |
Planned, catalog-driven requests for access, hardware, software, or information, distinct from reactive incidents. |
| SLAs | service_slas |
Service-level agreements setting response, resolution, and availability targets by priority, category, or customer tier. |
| Users | users |
Platform users referenced as assignees, authors, approvers, and creators across records. |
flowchart TD classDef embedded_master fill:#fff4cc,stroke:#c79100,color:#5b4500; classDef consumer fill:#e8def8,stroke:#7b1fa2,color:#3a155d; service_incidents["Incidents"] service_requests["Service Requests"] service_catalog_items["Service Catalog Items"] knowledge_articles["Knowledge Articles"] service_slas["SLAs"] users["Users"] users -->|"authored"| knowledge_articles users -->|"approved"| knowledge_articles service_catalog_items -->|"spawns"| service_requests users -->|"authors"| knowledge_articles users -->|"requests"| service_requests users -->|"fulfills"| service_requests service_requests -->|"routes_to"| service_incidents service_requests -->|"triggers"| service_incidents service_slas -->|"governs incident"| service_incidents service_slas -->|"governs request"| service_requests service_incidents -->|"resolved_with"| knowledge_articles users -->|"assigned incidents"| service_incidents users -->|"reported incidents"| service_incidents users -->|"assigned requests"| service_requests users -->|"submitted requests"| service_requests users -->|"authored articles"| knowledge_articles users -->|"owned catalog items"| service_catalog_items users -->|"owned SLAs"| service_slas class service_incidents embedded_master; class service_requests embedded_master; class service_catalog_items embedded_master; class knowledge_articles embedded_master; class service_slas embedded_master; class users consumer; style service_catalog_items stroke-dasharray:5 5; style knowledge_articles stroke-dasharray:5 5; style service_slas stroke-dasharray:5 5;