All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

IT Service + Asset + Knowledge · Available now

Keep service work tied to its records.

IT Service + Asset + Knowledge brings service interruptions, requests, changes, assets, problems and articles into linked working records. An incident can identify the affected service and asset, its assigned person, priority, acknowledgment and resolution times.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen incident queue
IT Service + Asset + Knowledge · Incidents

Open incident queue

Incidents in one list

New incident
Incidents in view
6
Low
2
Medium
2
High
1
Low2
Restore west office connectivityCustomer support portal
21 Oct
Expand backup storage poolFinance reporting
12 Oct
Add
Medium2
Finance reports fail during exportEmployee identity and access
01 Nov
Support portal mail queue delayedFinance reporting
02 Nov
Add
High1
Apply firewall firmware updateEndpoint management
15 Oct
Add
Critical1
Warehouse scanners cannot sign inFinance reporting
27 Oct
Add
Restore west office connectivityIncidents · INC-65900
Low
Opened at21 Oct
StatusOpen
ServiceCustomer support portal
AssetConference room display
Assigned toJamal Ellis
Approve service requestINC-65900 · Restore west office connectivity

Service Manager decides whether the submitted request is approved or rejected.

Waiting for Service Manager
ApproveReturn
Example screen with sample data
Tables, ready to use
12
Saved views
13
Roles with set permissions
6
Reports and dashboards
9
Features

Service work in context

Every feature works on the same records. Pick one to see the screen your team works in.

Incidents

Record an interruption, acknowledge it, investigate and close it with its service context.

  • Intake
  • Response
  • Closure
  • Incidents
  • Incident updates
  • Services
  • Assets
  • People
Explore incidents
OverviewIncident update history
IT Service + Asset + Knowledge · Incidents

Incident update history

Incident updates

New
NameOccurred atUpdate textIncidentAuthor
Network team investigating uplink03 NovUplink errors continue; carrier ticket opened.West office internet intermittentNora Ibrahim
Finance service restored24 OctReport export recovered after pool restart.Endpoint enrollment stalledAlina Petrova
Scanner login workaround shared22 OctWorkaround shared with warehouse supervisors.Backup job missed overnight windowAlina Petrova
Vendor engaged for backup fault27 OctBackup vendor reviewing storage errors.Endpoint enrollment stalledAlina Petrova
Wireless controller restarted16 OctWireless controller restart completed.West office internet intermittentRohan Desai
6 of 6 records
Network team investigating uplinkIncident updates · IU-52823
Occurred at03 Nov
Update textUplink errors continue; carrier ticket opened.
IncidentWest office internet intermittent
AuthorNora Ibrahim
Example screen with sample data
Process

From request to completion

Request fulfillment ships ready to use. One step needs a named approval before the work moves on: Approve service request (Service Manager).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Submit service request

    Record the requester, service and due date.

    Restore west office connectivityINC-65900 · Service Desk Agent
    Submit service requestBy Service Desk Agent
  2. Approve service request

    The Service Manager decides whether the work is authorized.

    Restore west office connectivityINC-65900 · Service Manager
    Approve service requestBy Service Manager
    ApprovalService Manager decides whether the submitted request is approved or rejected.
  3. Begin fulfillment

    An agent starts approved work.

    Restore west office connectivityINC-65900 · Service Desk Agent
    Begin fulfillmentBy Service Desk Agent
  4. Complete service request

    Record the actual completion time.

    Restore west office connectivityINC-65900 · Service Desk Agent
    Complete service requestBy Service Desk Agent
  5. Review request completion

    The manager checks the result against the request.

    Restore west office connectivityINC-65900 · Service Manager
    Review request completionBy Service Manager
Inside a record

Service records stay linked

Open any incident to see its incident updates, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Opened at, Status, Service and Asset.

  2. 2
    Incident updates

    Each line is linked to this incident.

  3. 3
    Who works on it

    Service Manager, Service Desk Agent and Change Approver, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Approve service request, with who decides.

Open incident queueRestore west office connectivity
IT Service + Asset + Knowledge · Incidents

Restore west office connectivity

Customer support portal · Low

Log activity
1
Record details
Opened at21 Oct
StatusOpen
ServiceCustomer support portal
AssetConference room display
2
Incident updates

Restore west office connectivity

NameOccurred atUpdate text
Network team investigating uplink03 NovUplink errors continue; carrier ticket opened.
Finance service restored24 OctReport export recovered after pool restart.
Scanner login workaround shared22 OctWorkaround shared with warehouse supervisors.
Incident updates
6
3

Who works on it

  • Service ManagerManage Services, Incidents, Problems
  • Service Desk AgentManage Incidents, incident updates, service requests
  • Change ApproverView Changes, Services, Assets, Incidents
5

Approvals

  • Approve service requestService Manager
    Approved
Example screen with sample data
Approvals

Decisions with an owner

OverviewApprovals
IT Service + Asset + Knowledge · Overview

Approvals

Signed in as Service Manager

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SR-46035Grant access to finance reports
    Access requestRequested by Caleb Wright
    Submitted1dActions
  • SR-78141Set up laptop for new analyst
    Hardware replacementRequested by Meera Venkatesh
    Submitted3dActions
  • SR-21157Add warehouse scanner user
    Software installationRequested by Meera Venkatesh
    Submitted3dActions
  • SR-68039Restore shared folder access
    New starter setupRequested by Sofia Haddad
    Submitted4dActions

Who approves what

DecisionApprover
Approve service requestThe Service Manager decides whether the work is authorized.Service Manager
Approve service requests, ChangesService Manager
Approve ChangesChange Approver
3 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens IT Service + Asset + Knowledge to the work that is theirs. Pick a role to see what it starts with.

Service Manager

Owns service decisions and reviews work across incidents, requests and changes.

This is the first screen this role sees.

OverviewChange schedule

Change schedule

Changes · Service Manager

SummaryRiskScheduled startScheduled endStatusService
Restore west office connectivityLow24 Oct01 NovApprovedFile storage and sharing
Finance reports fail during exportMedium25 Oct30 OctImplementingFile storage and sharing
Apply firewall firmware updateHigh26 Oct29 OctApprovedEmail and collaboration
Warehouse scanners cannot sign inLow29 Oct01 NovImplementingFile storage and sharing
Expand backup storage poolMedium29 Oct05 NovApprovedEmail and collaboration
6 of 6 records
Example screen with sample data
Reports

Questions you can answer

Review service response, request completion, change outcomes and record health.

Overview
IT Service + Asset + Knowledge · Overview

IT Service + Asset + Knowledge dashboard

This quarter

Changes in view
6
Low
2
Medium
2
High
2

Incidents by status

How far records got this quarter

StageReachedStep
Open38
Acknowledged821%
Investigating338%
Resolved133%

Number of incidents by status

Sample counts per stage

200
-20Open
0Acknowledged
-40Investigating
-60Resolved
20Closed
Example screen with sample data
  1. 01Incident priority and status

    Group incidents by Priority and Status to see current work.

  2. 02Acknowledgment timing

    Compare opened at and acknowledged at for acknowledged incidents.

  3. 03Resolution timing by service

    Group incidents by Service and compare opened at with resolved at.

  4. 04Request completion by service

    Group service requests by Service and Status, with requested at and completed at.

  5. 05Change risk and outcome

    Group Changes by Risk and Status to review outcomes.

  6. 06Assets by service and condition

    Group Assets by Service and Status and inspect Location.

  7. 07Problems by service

    Group Problems by Service and Status with Owner and root cause.

  8. 08Knowledge publication

    Group knowledge articles by Service and Status with published at.

  9. 09Integration processing outcomes

    Group integration receipts by Provider and Status with received at.

Controls

Trace the work

Each stage of request fulfillment names the role that acts and the status it records, so a change is never anonymous.

OverviewRequest fulfillment
IT Service + Asset + Knowledge · Process

Request fulfillment

Each stage, the role that acts and the status it records

Process stages
12
Approval steps
1
Roles involved
3
Tables touched
3
Acknowledge incident
Service Desk Agent
StatusOpen → Acknowledged
RecordsServices
Investigate incident
Service Desk Agent
StatusAcknowledged → Investigating
RecordsServices
Resolve incident
Service Desk Agent
StatusInvestigating → Resolved
RecordsServices
Request fulfillment
  1. Start
    Acknowledge incidentOpen → Acknowledged
    Services
  2. Step
    Investigate incidentAcknowledged → Investigating
    Services
  3. Step
    Resolve incidentInvestigating → Resolved
    Services
  4. Approval
    Approve service requestSubmitted → Approved
    Services
  5. Step
    Begin fulfillmentApproved → in progress
    Services
Example screen with sample data
AI agent

A useful assistant

Use Proto to inspect linked service records and prepare the next action.

It can

  • Service Desk Agent: Show Open incident queue with priority, affected service, asset and assigned person, then prepare an update for the agent to check.
  • Service Manager: Summarize Submitted requests and the information needed for a decision.
  • Change Approver: Present a change in Review with its risk, window and rollback plan.
  • Asset Manager: Compare an asset's condition with its named service dependency and verification date.

Stays with a person

  • A person decides whether a request or change is authorized and checks whether an article is ready to publish.
  • The agent can gather records and prepare an action, while the named owner verifies the facts and makes the decision.
  • Confirm that timestamps describe events that actually occurred before recording them.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • IT Service + Asset + Knowledge
  • Event source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 12 tables
12tables
  • Incidents5
  • Requests3
  • Changes2
  • Assets4
  • Problems5
  • Knowledge5
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Name services and owners

    Add the services the team supports, their criticality and the people responsible for them.

  2. Load operating context

    Add assets, locations and verified service dependencies, then establish the initial people records.

  3. Configure decisions

    Assign responsibility for incident intake, request approval, change authorization and article review.

  4. Rehearse cases

    Run an interruption, a submitted request, a planned change and a knowledge publication with the people who will own them.

  5. Connect event sources

    Agree how external identifiers map to the working records and how Failed receipts are investigated.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for IT Service + Asset + Knowledge.

All questions
How do I get started?

Click Get started, then use Proto to configure IT Service + Asset + Knowledge for your business. Begin with a few active services, named owners and assets your agents can identify, then rehearse an incident and a submitted request.

Who owns an incident?

The incident names an assigned person. The Service Desk Agent uses that assignment with the affected service and asset to continue the response.

Can I see when an incident was acknowledged?

Yes. Record the actual acknowledgment time on the incident. The opening and resolution times are kept on the same case.

How does a request receive approval?

A submitted service request goes to the Service Manager for a decision. Approved work enters fulfillment; rejected work keeps its rejection outcome.

What does a change review include?

The Change Approver checks the affected service, risk, scheduled start and end, and rollback plan before recording a decision.

How are assets tied to services?

Each asset references a service. A named asset service link can also record the dependency type and when it was verified.

Where does a recurring issue go?

Use a problem record with a statement, service, owner and root cause. Its status shows whether investigation is open, a known error or resolved.

How does an article become current guidance?

The Knowledge Editor drafts it for a service, reviews its content and records the publication time when it moves to Published.

What can I learn from integration receipts?

A receipt records provider, external event identifier, receipt time, payload hash and processing outcome. The team can inspect Failed and Rejected outcomes for follow-up.

Set up IT Service + Asset + Knowledge your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appIT Service + Asset + Knowledge

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.