IT Managed Services Operations

Business Problem

Managed service providers operate across tickets, incidents, changes, patch cycles, backups, asset assignments, vendor escalations, invoicing, and renewals. A dedicated operating model is essential for reliable service delivery.

Four-Step Application

This scenario works best as a four-step, human-in-the-loop application. The required object model already gives this scenario a strong delivery backbone for a four-step operating experience.

• Mission metric focus: lower time-to-resolution, higher retention, and better support productivity.
• Human + AI pattern: Each step combines structured workflow data with chat assistance, background generation, document understanding, and accessible interaction patterns when they improve the experience.

Step 1. Capture demand and context

• Goal: Make it easy for the user to start the IT Managed Services Operations journey with complete, trusted context.
• Required data: ClientAccount (client account), Site (client site), ServiceContract (service contract), Asset (managed asset), and User (end user).
• AI support: Use chat to guide intake, generate clearer prompts, create accessible summaries, and assist with voice or vision-led capture when a form alone is not the best experience. EAI can support structured intake, chat workflows, and document-centred capture today; richer native multimodal capture may still need workflow extensions or connected services.
• Business impact: Improve completion rate, reduce first-touch effort, and raise customer or staff confidence in the UX from the very first interaction.
• EAI delivery: Model the intake as tenant-isolated object types and resources, then use actions, chat workflows, and document indexing or classification to keep the initial record complete and usable.

Step 2. Prepare the decision

• Goal: Turn the captured context into the next best action for IT Managed Services Operations without forcing the human reviewer to assemble the case manually.
• Required data: Ticket (support ticket), Incident (major incident), ProblemRecord (problem record), ChangeRequest (change request), and MaintenanceWindow (maintenance window).
• AI support: Run background summarisation, extraction, classification, recommendation drafting, and answer generation so a reviewer sees a prepared case instead of raw fragments. EAI delivers the structured records and AI workflow hooks for this today; specialised scoring engines, external rules, or advanced reasoning controls may still need integration work.
• Business impact: Reduce cycle time, improve quality and consistency, and protect the mission-critical metric before the case moves into execution.
• EAI delivery: Link records across the scenario, persist decision state as resources, and use workflow actions plus chat assistance to keep humans in control while AI prepares the work.

Step 3. Execute and collaborate

• Goal: Coordinate the actual work, handoffs, approvals, and user updates needed to deliver the service or outcome.
• Required data: KnowledgeArticle (knowledge article), MonitoringAlert (monitoring alert), PatchCycle (patch cycle), BackupJob (backup job), and LicenseAssignment (license assignment).
• AI support: Draft replies, produce work packets, monitor exceptions in the background, and surface the next action for each operator. EAI can orchestrate tenant-isolated records, actions, chats, and document workflows today; deeper system-to-system automation may require additional connectors or workflow capability.
• Business impact: Increase operator productivity, reduce rework across handoffs, and improve service consistency across the application journey.
• EAI delivery: Use linked object types, actions, resource updates, and workflow-triggered AI assistance so the team can execute in one model instead of splitting work across disconnected tools.

Step 4. Resolve, explain, and improve

• Goal: Close the loop with a clear outcome, an understandable explanation, and feedback that improves the next case.
• Required data: SLAReport (SLA report), OnCallRoster (on-call roster), RootCauseReview (root cause review), Invoice (service invoice), and QBRDeck (quarterly review deck).
• AI support: Generate outcome summaries, customer-friendly answers, compliance-ready notes, management insights, and accessible follow-up content. EAI can store outcome records and support answer generation today, while richer proactive agents, advanced analytics, or channel-specific accessibility features may need additional product capability.
• Business impact: Increase trust, quality, and measurable business value through lower time-to-resolution, higher retention, and better support productivity.
• EAI delivery: Keep the full audit trail in structured resources, use AI workflows to explain outcomes, and feed the resulting signals into future product, service, and operational improvement work.

EAI Platform Support By Step

EAI provides the safe service boundary for IT Managed Services Operations through Object Types, tenant-scoped resources, document processing, chat workflows, and CLI verification. For this scenario, the main records are ClientAccount, Site, ServiceContract, Asset, User, and 17 more Object Types.

Process step	What EAI provides	Calling pattern
Step 1. Capture demand and context	Tenant-scoped intake resources for ClientAccount (client account), Site (client site), ServiceContract (service contract), Asset (managed asset), and User (end user). Object Type validation, starter forms, optional document intake, and chat-guided capture keep the first record complete.	Define fields in src/eai.config/object-types.ts, run eai types validate and eai types seed, create initial ClientAccount records with useResources('ClientAccount') or eai resources create ClientAccount, and keep browser calls behind /api/eai/....
Step 2. Prepare the decision	Linked resource queries over Ticket (support ticket), Incident (major incident), ProblemRecord (problem record), ChangeRequest (change request), and MaintenanceWindow (maintenance window). Search, schema checks, document classification or RAG indexing, and chat summaries turn raw context into a prepared decision.	Use useResources('ClientAccount') list/query/search patterns, verify shape with eai resources schema, use useDocuments().upload/classify/ragIndex, eai docs upload, eai docs classify, and eai docs index where supporting material exists, and send decision-support prompts through useChat(workflowId, 'chat') or eai chat send.
Step 3. Execute and collaborate	Resource updates and actions for KnowledgeArticle (knowledge article), MonitoringAlert (monitoring alert), PatchCycle (patch cycle), BackupJob (backup job), and LicenseAssignment (license assignment). Status changes, assignments, notes, generated work packets, and chat support keep humans in control during execution.	Model actions in the Object Type code, call client.resources.executeAction(type, id, action) or the app hook equivalent, update records through the app service layer, and verify with eai resources get/list/query.
Step 4. Resolve, explain, and improve	Outcome resources for SLAReport (SLA report), OnCallRoster (on-call roster), RootCauseReview (root cause review), Invoice (service invoice), and QBRDeck (quarterly review deck). Audit-friendly links, indexed final documents, reporting snapshots, and answer generation make the result explainable and reusable.	Persist outcomes as resources, index final material with eai docs index or useDocuments().ragIndex, send explanation prompts with useChat or eai chat stream, and use eai resources aggregate/search for reporting checks.

Prompt, Code, And Service Pattern Mapping

When this scenario is turned into code, eai-gofer should generate Object Type definitions and app calls from the process model instead of inventing direct backend calls.

Use this prompt shape when asking eai-gofer or another coding agent to implement the scenario:

Use the EAI App Template. Model IT Managed Services Operations with Object Types for ClientAccount, Site, ServiceContract, Asset, User. Use useResources for records and actions, useDocuments for uploads/classification/RAG where documents appear, useChat for workflow assistance, and verify with eai types/resources/docs/chat commands. Use eai publicapi only when no named command covers the required platform call.

Scenario artifact	How it maps to EAI service calls
Four-step process	Step 1 becomes resource creation, Step 2 becomes resource query/search plus optional document or chat preparation, Step 3 becomes resource update/action calls, and Step 4 becomes outcome persistence plus explanation/reporting calls.
Object Type definitions	eai types validate, eai types seed, and eai resources schema make the model available and checkable before UI work starts.
Properties and indexes	Fields become useResources payloads, filters, list views, and eai resources create/list/query/search checks. Indexed fields should support lookup and triage, not duplicate canonical records.
Links between Object Types	Relationships become linked-resource UI, timeline context, and audit trails that app code loads through resource queries rather than separate bespoke stores.
Actions and status fields	Workflow buttons and operator transitions call resource action/update helpers, then verify state with eai resources get/list/query.
Document and chat prompts	Prompts should call the platform documents and chat patterns: useDocuments().upload/classify/ragIndex, eai docs upload, eai docs classify, and eai docs index for documents, and useChat, eai chat send, or eai chat stream for conversational assistance.

Required Object Model (22 object types)

This scenario needs more than 20 object types because it spans intake, delivery, exceptions, governance, and reporting.

Client and Service Context

• ClientAccount — client account
• Site — client site
• ServiceContract — service contract
• Asset — managed asset
• User — end user
• Ticket — support ticket
• Incident — major incident
• ProblemRecord — problem record

Service Execution

• ChangeRequest — change request
• MaintenanceWindow — maintenance window
• KnowledgeArticle — knowledge article
• MonitoringAlert — monitoring alert
• PatchCycle — patch cycle
• BackupJob — backup job
• LicenseAssignment — license assignment
• VendorCase — vendor escalation

Governance and Growth

• SLAReport — SLA report
• OnCallRoster — on-call roster
• RootCauseReview — root cause review
• Invoice — service invoice
• QBRDeck — quarterly review deck
• RenewalTask — renewal task

Delivery Workflow

1. Authenticate and choose the tenant you want to work in.

   eai login
   eai tenant select

2. Pull environment values, validate the type definitions, and seed the model.

   eai env pull --include-secrets
   eai types validate
   eai types seed

3. Verify that the full model is available for the active tenant before building UI and workflows.

   eai resources schema --format json
   eai verify calls --format json

4. Load pilot data and exercise the operational workflows for the scenario.

AI and Document Opportunities

• Classify incoming tickets and monitoring alerts into the right service, asset, and urgency levels.
• Summarise incident histories and root-cause reviews before QBRs and renewal discussions.
• Generate proactive service tasks from patching, backups, knowledge gaps, and SLA trends.

Why This Scenario Is High-Value

MSPs need one operational view across support, preventative work, governance, and commercial follow-up. This scenario creates that shared model.