Skip to content
Stepwork logoStepwork logo
Marketplace
Deterministic AgentsSecurity

The Stepwork Platform

Deterministic work across the tools you already run

  • Extraction
  • Rule
  • Webhook

In product

  • ProcedureRun the process end to end
  • ExtractionPull data into the next step
  • Ask BobBuild a flow by chatting

Solutions

How Stepwork shows up for your team and industry

By team

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See all teams

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See all industries
Log inBook a Demo

Product

  • ProcedureRun the process end to end
  • ExtractionPull data into the next step
  • Ask BobBuild a flow by chatting
Marketplace

By team

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See all teams

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See all industries
Deterministic AgentsSecurity
Log inBook a Demo
  1. Home
  2. Solutions
  3. ITSM ticket automation

Automate ITSM tickets from ServiceNow and Jira Service Management

A webhook from your service desk starts a Stepwork procedure. It does the work in each admin console, with or without an API, then notes and resolves the ticket.

Book a DemoSee the procedures
  • Access request
  • Service request
  • New hire ticket
Use case
Service desk tickets run as proceduresIT
Best for
IT Manager, Service Desk Lead, ITSM Administrator
Applications used
  • ServiceNow
  • Jira Service Management
  • Freshservice
  • Microsoft Entra ID
  • Okta
Business outcome
Routine tickets resolved without waiting in the queue
  • The problem
  • Triage
  • Webhooks
  • Systems
  • Example procedures
  • Flows
  • More procedures
  • Why Stepwork
  • Related use cases
  • FAQ
  • The math

The problem

Every ticket is a trip to an admin console and back

  • Read each new ticket and decide what it is asking for
  • Look the requester up and check who has to approve
  • Open the app's admin console and make the change by hand
  • Repeat it for every app that has no API or connector
  • Go back to the ticket, write what you did, and resolve it
  • Close the notices and alerts that never needed anyone

Triage

Whatever the ticket asks for, it starts the right procedure

Tickets come from request forms, from email, and from people typing whatever comes to mind. Each service desk sends them to Stepwork the same way, and each one starts the procedure built for it.

How it arrives
  • ServiceNowCatalog requestRITM0041877 · Application access Requested for: Dana Reyes Application: License portal · Role: AdminAGoes to Access request
  • Jira Service ManagementService requestIT-2291 · New starter Monday Marcus Lee, hardware engineer. Needs the usual accounts and tools.OGoes to Onboarding bundle
  • FreshserviceTicket from emailSubject: Your certificate expires in 30 days From: no-reply@certificates.exampleTGoes to Inbox and alert triage
  • ZendeskTicketlocked out again after getting a new phone, can someone reset my authenticator?RGoes to Password and MFA reset
  • ManageEngine ServiceDesk PlusRequestRequest: USB-C dock and second monitor For: Priya Shah · Desk 4-112HGoes to Hardware request
  • ServiceNowIncident from emailINC0098214 · Budget alert Cloud spend has reached 80% of this month's budget.TGoes to Inbox and alert triage
Where it goes
  • AAccess requestFromRuns inServiceNowMicrosoft Entra IDInternal toolMicrosoft Teams
  • TInbox and alert triageFromRuns inServiceNowMicrosoft Teams
  • OOnboarding bundleFromRuns inServiceNowMicrosoft Entra IDInternal tool
  • RPassword and MFA resetFromRuns inServiceNowMicrosoft Entra IDMicrosoft Teams
  • HHardware requestFromRuns inServiceNowVendor portal

Webhooks

How a ticket becomes a run

Your service desk already knows when a ticket opens or changes status. One automation rule sends that event to Stepwork as a webhook, and the ticket's fields become the variables the procedure works from. There is nothing to install in the service desk.

  1. 1In your service desk

    A ticket opens or changes status

    An automation rule matches the ticket by category, form, or status, and sends its fields to the procedure's webhook address.
    ticket created · access request
    • Number
    • Requested for
    • Application
    • Access level
  2. 2In Stepwork

    The fields become variables

    The trigger card receives the ticket and hands each field to the cards that need it. Rules pick the path, and each step runs in the app it was recorded in.
    • Number→becomesticket_id
    • Requested for→becomesrequester_email
    • Application→becomesapp_name
    • Access level→becomesaccess_level
  3. 3Back in the ticket

    The run writes its answer

    The last card adds a note with what changed and sets the status. When a step can't finish, the run stops and the run record shows which step.
    • Work note: what changed, and in which app
    • Status: resolved
    • Assignment: a person or group, when the procedure hands off

Where the webhook comes from in each service desk

  • ServiceNowBusiness rule or Flow DesignerSends an outbound REST message when a record is created or updated.
  • Jira Service ManagementAutomation ruleUses the Send web request action when an issue is created or transitioned.
  • FreshserviceWorkflow AutomatorUses the Trigger webhook action on a ticket event.
  • ZendeskTrigger with a webhookNotifies an active webhook when a ticket meets the trigger's conditions.
  • ManageEngine ServiceDesk PlusCustom triggerCalls a webhook when a request matches the trigger's criteria.

Systems

The service desk stays. The work happens in these.

Tickets keep arriving where they do today. Stepwork does the work in the systems each ticket is about: your identity provider, the apps people ask for, and the consoles and portals that have no API or connector. It works through their screens with a login your team grants.

  • Service desks: ServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, Zendesk
  • Identity and devices: Microsoft Entra ID, Active Directory, Okta, JumpCloud, Microsoft Intune, Jamf
  • Apps people ask for: Microsoft 365, Google Workspace, GitHub, Salesforce, Figma, Zoom, Adobe Creative Cloud
  • Consoles and portals with no API: Internal tool, On-prem app, Vendor portal
  • Where approvals happen: Microsoft Teams, Slack
  • Jira Service Management
  • Freshservice
  • ManageEngine ServiceDesk Plus
  • Microsoft Entra ID
  • Active Directory
  • Jira Service Management
  • Freshservice
  • ManageEngine ServiceDesk Plus
  • Microsoft Entra ID
  • Active Directory
  • Jira Service Management
  • Freshservice
  • ManageEngine ServiceDesk Plus
  • Microsoft Entra ID
  • Active Directory
  • Jira Service Management
  • Freshservice
  • ManageEngine ServiceDesk Plus
  • Microsoft Entra ID
  • Active Directory
  • Jira Service Management
  • Freshservice
  • ManageEngine ServiceDesk Plus
  • Microsoft Entra ID
  • Active Directory
  • Jira Service Management
  • Freshservice
  • ManageEngine ServiceDesk Plus
  • Microsoft Entra ID
  • Active Directory
  • JumpCloud
  • Microsoft Intune
  • Jamf
  • JumpCloud
  • Microsoft Intune
  • Jamf
  • JumpCloud
  • Microsoft Intune
  • Jamf
  • JumpCloud
  • Microsoft Intune
  • Jamf
  • JumpCloud
  • Microsoft Intune
  • Jamf
  • JumpCloud
  • Microsoft Intune
  • Jamf
  • Zoom
  • Adobe Creative Cloud
  • Internal tool
  • On-prem app
  • Vendor portal
  • Microsoft Teams
  • Zoom
  • Adobe Creative Cloud
  • Internal tool
  • On-prem app
  • Vendor portal
  • Microsoft Teams
  • Zoom
  • Adobe Creative Cloud
  • Internal tool
  • On-prem app
  • Vendor portal
  • Microsoft Teams
  • Zoom
  • Adobe Creative Cloud
  • Internal tool
  • On-prem app
  • Vendor portal
  • Microsoft Teams
  • Zoom
  • Adobe Creative Cloud
  • Internal tool
  • On-prem app
  • Vendor portal
  • Microsoft Teams
  • Zoom
  • Adobe Creative Cloud
  • Internal tool
  • On-prem app
  • Vendor portal
  • Microsoft Teams

Example procedures

Five ticket procedures, card by card

Each one starts from a service desk webhook, takes the path its rule picks, and writes the result back to the ticket. Swap in Jira Service Management, Freshservice, or Okta above each one and the steps stay the same.

Grant access in an app with no API, from a ServiceNow ticket

An access ticket in ServiceNow starts the run by webhook. Admin access waits for the manager; standard access goes straight through. Either way the user is added in the app's own admin console, and the ticket gets the result.
  • ServiceNow
  • Microsoft Entra ID
  • Internal tool
  • Microsoft Teams
Swap in your systemsThe steps stay the same. Only the screens change.
Service desk
Identity provider
Team chat
Grant access in an app with no API, from a ServiceNow ticket
Webhook
ServiceNow

Access request opens in ServiceNow

ticket created · access request

Output variables

  • ticket_id
  • requester_email
  • app_name
  • access_level
Extraction
Microsoft Entra ID

Find the requester and manager in Microsoft Entra ID

Input variables

  • requester_email

Extracted variables

  • user_account
  • manager_email
Rule logic

Does this access need approval?

Input variables

  • access_level

Paths

  1. If access_level is adminThen: Ask the manager to approve in Microsoft Teams
  2. OtherwiseThen: Add the user in the app's admin console
Execution
If admin access
Microsoft Teams

Ask the manager to approve in Microsoft Teams

Input variables

  • manager_email
  • app_name
Execution
Internal tool

Add the user in the app's admin console

Input variables

  • user_account
  • access_level

Output

  • access_result
Execution
ServiceNow

Add a work note and resolve the ticket

Input variables

  • ticket_id
  • access_result

Drag to explore · pinch to zoom

Step by step

  1. 1
    The ticket starts the run
    Someone asks for access to an app through ServiceNow. The service desk sends the ticket to Stepwork as a webhook, with who asked, which app, and which level of access.
  2. 2
    Stepwork finds the person
    It looks the requester up in Microsoft Entra ID and reads back their account and their manager. If no account matches, the run stops instead of guessing.
  3. 3
    The rule checks the level
    Admin access takes the approval path. Standard access skips it and goes straight to the change.
    • If admin accessAsk the manager to approve in Microsoft Teams
    • If standard accessAdd the user in the app's admin console
  4. 4
    The manager approves
    On the admin path only, Stepwork asks the manager in Microsoft Teams and waits for the answer before anything changes.
    Only on this path: If admin access
  5. 5
    The user is added in the app
    Both paths meet here. The recorded flow signs in to the app's admin console and adds the user at the level asked for. It works in the app's own screens, so the app does not need an API.
  6. 6
    The ticket gets the answer
    Stepwork adds a work note with what was granted and resolves the ticket in ServiceNow, so the requester sees it where they asked.

Field map

FromTo
ServiceNowTicket: requested forMicrosoft Entra IDUser search: email
Microsoft Entra IDProfile: managerMicrosoft TeamsApproval message: toOnly for admin access
ServiceNowTicket: access levelInternal toolUsers: role
Internal toolResult of the changeServiceNowTicket: work note and statusResolved when the change succeeds

Sort the tickets that vendor emails and alerts create

Vendor emails, budget alerts, and certificate reminders all land in ServiceNow as tickets. This run reads each one, closes the notices nobody has to act on, and gives the rest an owner and a due date.
  • ServiceNow
  • Microsoft Teams
Swap in your systemsThe steps stay the same. Only the screens change.
Service desk
Team chat

Step by step

  1. 1
    An email becomes a ticket
    A vendor notice or an alert is sent to the IT address and ServiceNow opens a ticket for it. That ticket starts the run with its subject and body.
  2. 2
    Stepwork reads it
    An AI card reads the subject and body and names what it is: a receipt, a renewal, an expiring certificate, a budget alert. If the email has a deadline, the card reads the date.
  3. 3
    The rule decides
    The category decides the path, the same way every time. Receipts, newsletters, and status notices take the top path. Everything else needs someone.
    • If a noticeClose the ticket with its category
    • If it needs actionSet the category, due date, and owner
  4. 4
    Notices are closed
    On the notice path, Stepwork sets the category and closes the ticket in ServiceNow. It stays in your reports and leaves the queue.
    Only on this path: If a notice
  5. 5
    The rest get an owner
    On the other path, Stepwork sets the category and the due date on the ticket and assigns it to the group that owns that kind of work.
    Only on this path: If it needs action
  6. 6
    The owner hears about it
    Stepwork posts the ticket and its due date to the owner in Microsoft Teams, so a certificate that expires in 30 days is seen on day one.
    Only on this path: If it needs action

Field map

FromTo
ServiceNowTicket: subject and descriptionServiceNowTicket: categoryRead by the AI card
ServiceNowDate named in the emailServiceNowTicket: due date
ServiceNowTicket: assignment groupMicrosoft TeamsMessage to the owner

Set up a new hire's accounts from one ServiceNow ticket

One onboarding ticket usually turns into a dozen small ones. Here it stays one ticket: Stepwork creates the account in Microsoft Entra ID, works through each app the role needs, and writes the summary back.
  • ServiceNow
  • Microsoft Entra ID
  • Internal tool
Swap in your systemsThe steps stay the same. Only the screens change.
Service desk
Identity provider

Step by step

  1. 1
    The onboarding ticket opens
    HR or a manager files a new-hire ticket in ServiceNow with the person's email and their role. That ticket starts the run.
  2. 2
    The account is created
    The recorded flow creates the account in Microsoft Entra ID with the groups the role starts with.
  3. 3
    Stepwork reads the app list
    It reads which apps that role is assigned in Microsoft Entra ID. Each app it finds becomes one pass through the loop.
  4. 4
    The loop sets up each app
    Inside the dashed frame, a recorded flow runs once per app, in that app's admin console. If one app fails, it is marked and the rest still get set up.
    Repeats: For each app the role needs · 8 apps
  5. 5
    The results come together
    After the last app, the Summary card runs once and lists what was set up and anything that needs a person.
  6. 6
    The ticket gets the summary
    Stepwork adds the summary as a note and resolves the ticket in ServiceNow, so the manager can see what is ready before day one.

Field map

FromTo
ServiceNowTicket: new hire's emailMicrosoft Entra IDNew user: sign-in name
ServiceNowTicket: roleMicrosoft Entra IDGroups and apps for that role
Microsoft Entra IDApp assigned to the roleInternal toolNew user in that appOnce per app
Internal toolResult for each appServiceNowTicket: summary note

Reset a password or MFA from a ticket, after an identity check

A reset is a common way into someone else's account, so this run checks before it changes anything. The manager confirms in Microsoft Teams; only then does Stepwork reset the password or MFA in Microsoft Entra ID.
  • ServiceNow
  • Microsoft Entra ID
  • Microsoft Teams
Swap in your systemsThe steps stay the same. Only the screens change.
Service desk
Identity provider
Team chat

Step by step

  1. 1
    The reset ticket opens
    Someone locked out files a ticket in ServiceNow, or the service desk files it for them. The ticket starts the run with who it is for and which reset they need.
  2. 2
    Stepwork finds the account
    It looks the person up in Microsoft Entra ID and reads back their account and their manager.
  3. 3
    The manager is asked
    Stepwork messages the manager in Microsoft Teams and waits for a yes or a no.
  4. 4
    The rule reads the answer
    A no, or no answer, takes the top path. A yes goes on to the reset.
    • If not confirmedHand the ticket to security with a note
    • If confirmedReset the password or MFA in Microsoft Entra ID
  5. 5
    Unconfirmed requests go to security
    On the top path nothing is reset. Stepwork adds a note to the ticket and reassigns it to the security group in ServiceNow.
    Only on this path: If not confirmed
  6. 6
    The reset runs
    On the confirmed path, the recorded flow resets the password with a forced change, or clears the MFA factors so the person enrolls again.
    Only on this path: If confirmed
  7. 7
    The ticket is resolved
    Stepwork notes which reset ran and who confirmed it, then resolves the ticket in ServiceNow.
    Only on this path: If confirmed

Field map

FromTo
ServiceNowTicket: requested forMicrosoft Entra IDUser search: sign-in name
Microsoft Entra IDProfile: managerMicrosoft TeamsConfirmation message: to
Microsoft TeamsManager's answerServiceNowTicket: work noteKept with the ticket either way

Fill a hardware request from stock, or order it

A request for a dock, a monitor, or a headset is checked against what is already on the shelf. Stock is assigned; anything else is ordered in the vendor's portal, and the ticket says which.
  • ServiceNow
  • Vendor portal
Swap in your systemsThe steps stay the same. Only the screens change.
Service desk

Step by step

  1. 1
    The hardware ticket opens
    Someone asks for a piece of equipment in ServiceNow. The ticket starts the run with who asked and what they need.
  2. 2
    Stepwork checks the shelf
    It searches the asset list in ServiceNow for that item and reads how many are unassigned, with the tag of the first one.
  3. 3
    The rule decides
    With none in stock, the request takes the order path. With one on the shelf, it goes to the assignment.
    • If out of stockOrder it in the vendor's portal
    • If in stockAssign the asset to the requester
  4. 4
    Out of stock: it is ordered
    On the order path, the recorded flow signs in to the vendor's portal, orders the item for the requester, and reads back the order number.
    Only on this path: If out of stock
  5. 5
    In stock: it is assigned
    On the other path, Stepwork assigns the asset to the requester in ServiceNow, so the asset list is right before anyone picks it up.
    Only on this path: If in stock
  6. 6
    The ticket says what happened
    Both paths end here. The ticket gets the order number, or the asset tag and where to collect it.

Field map

FromTo
ServiceNowTicket: item requestedServiceNowAssets: search
ServiceNowTicket: item requestedVendor portalOrder: productOnly when none is in stock
Vendor portalOrder numberServiceNowTicket: work note

Flows

The flows these ticket procedures are built from

Each flow is one recorded job in one app. Procedures connect them, and any of them can also run on its own from a ticket.

  • ServiceNow
    ServiceNow

    Create standard change request

    Files a standard change request from a template with schedule and implementation details.

    Execution · Slack request
  • ServiceNow
    ServiceNow

    Close resolved incidents older than 7 days

    Bulk-closes incidents that have sat resolved past the confirmation window.

    Execution · Scheduled
  • ServiceNow
    ServiceNow

    Extract open incidents by assignment group

    Extracts open incidents grouped by assignment group with age and priority into a table.

    Extraction · Scheduled
  • ServiceNow
    ServiceNow

    Extract incidents breaching SLA

    Extracts incidents at or past SLA thresholds with owners and elapsed time.

    Extraction · Scheduled
  • Jira
    Jira

    Create standard intake ticket

    Creates a Jira ticket in the intake project with the standard fields, labels, and priority from the request details.

    Execution · Slack request
  • Freshservice
    Freshservice

    Create onboarding ticket set for new hire

    Creates the standard set of onboarding tickets (accounts, hardware, access) for a new hire from a template.

    Execution · Slack request
  • Freshservice
    Freshservice

    Close resolved tickets past confirmation window

    Closes tickets sitting in resolved state past the confirmation window in bulk.

    Execution · Scheduled
  • Microsoft Entra ID
    Microsoft Entra ID

    Add user to security groups

    Adds a user to specified Entra security groups that gate app and resource access.

    Execution · Slack request
  • Okta
    Okta

    Add user to group

    Opens the target Okta group and adds the specified user, granting the app assignments tied to that group.

    Execution · Slack request
  • Microsoft Entra ID
    Microsoft Entra ID

    Reset password with forced change

    Resets a user's password in Entra and requires a change at next sign-in.

    Execution · Slack request
  • Okta
    Okta

    Reset MFA factors for user

    Finds the user in Okta admin, resets all enrolled MFA factors, and triggers re-enrollment at next sign-in.

    Execution · Slack request
  • Internal tool
    Internal tool

    Add a user in an internal admin page

    Signs in to the internal admin page, creates the user with the role the ticket asks for, and saves the user list afterwards as a timestamped screenshot.

    Recorded on your screens
  • Vendor portal
    Vendor portal

    Order a peripheral for an employee

    Signs in to the vendor's ordering portal, adds the item to the cart for the requester, places the order, and reads back the order number.

    Recorded on your screens
See every helpdesk & requests flow in the Marketplace

More procedures

More service desk procedures in the Marketplace

Ready-made procedures for queue hygiene, SLA escalation, intake, and access requests.

  • FreshserviceServiceNow
    Freshservice · ServiceNow

    Weekly ticket queue hygiene

    Closes resolved Freshservice tickets past the confirmation window and resolved ServiceNow incidents older than seven days each week, posting the closure counts and any tickets that bounced back.
  • ZendeskSlack
    Zendesk · Slack

    SLA breach real-time escalation

    Hourly during business hours, extracts tickets breaching or within an hour of SLA from Zendesk, pings the assigned agent, and escalates unacknowledged breaches to the shift lead with account context.
  • TypeformJiraAsana1 more
    Typeform · Jira · Asana + 1 more

    Intake form to tracked work pipeline

    Every few hours, extracts new intake submissions from Typeform, applies routing rules by request type, creates the Jira ticket or Asana task with the mapped fields, and confirms to the requester with the tracking link.
  • SlackOktaGitHub1 more
    Slack · Okta · GitHub + 1 more

    App access request with manager approval

    Takes an access request from Slack, routes an approval to the requester's manager, and on approval branches by app to add the Okta group, GitHub team, or Google group that grants it, confirming back in the thread.

Why Stepwork

The ticket is the record. The run is the proof.

Stepwork is a deterministic agent platform: it runs the steps you recorded in each admin console, in the same order, for every ticket. It works in an app's own screens, so a request does not wait for an API or a connector. Rules decide which path a ticket takes, so admin access always gets its approval and a reset always gets its check. Credentials stay in your vault, and every run records which ticket started it, which path it took, and what changed.

Deterministic agentsProceduresCredentials
Book a Demo

Related use cases

More use cases

  • IT helpdesk automationStepwork runs the requests your helpdesk repeats, from password and MFA resets to licenses and mailbox access, from a Teams message or a ticket, the same way every time.Learn more
  • Employee onboarding automationStepwork reads new hires from your HR system, creates their accounts, sets up every app in their bundle, including ones without SCIM, and tells the manager what's ready.Learn more
  • User access review automationStepwork pulls accounts from every app, including ones without SCIM, matches them to HR, carries out reviewer decisions, and files the evidence in Vanta.Learn more
See all teams

FAQ

Common questions

  • No. People keep filing tickets where they do today, and your queues, SLAs, and reports stay in the service desk. Stepwork does the work between the ticket opening and the ticket closing, then writes the result back.
  • With a webhook. You add one automation rule in the service desk, such as a ServiceNow business rule, a Jira automation rule, or a Freshservice Workflow Automator step, that sends the ticket to the procedure when it is created or changes status. The ticket's fields arrive as variables.
  • Stepwork works in the app's own screens, the way an admin would, so it does not need one. That covers internal admin pages, on-prem consoles, vendor portals, and SaaS plans that keep user management out of the API.
  • Yes. The last card of a procedure adds a work note with what changed and sets the status. A procedure can also reassign a ticket, for example to security when a reset request is not confirmed.
  • Beside it. An AI service desk resolves requests through the APIs of the apps it connects to and hands the rest to a person. Stepwork takes the repeatable ones from that pile, because it works in the app's screens and does not need an API.
  • Send us a ticket export and we will run a free IT ticket analysis. It sorts every ticket into a use case, shows which ones a procedure can run, and estimates the hours that come back over a year.
    Free IT ticket analysis

The math

What these tickets cost a service desk by hand

Example volumes for a company of about 500 people with a service desk of three. Swap in yours.

Illustrative estimate, not a quote. These are example volumes and typical hand times, not a customer's results. Your numbers will differ, and we can work them out with you.
The manual taskTimes a weekMinutes eachHours a week
Grant access in an app's admin console20124
Sort and close a ticket created from email3042
Set up a new hire's accounts2903
Reset a password or MFA after a check1582
Fill or order a hardware request8152
Hours a week
13
Hours a year
650
Of one full-time person
33%
Example volumes, not a customer's numbers. Minutes are the typical time to do each ticket by hand, including opening the ticket and writing the note. Hours a year assume 50 working weeks.

See it run on a process you already repeat

Bring one. We will show you what it looks like as a flow and what each run records.

Book a Demo
Stepwork

Deterministic agents for work that must run the same way every time.

Product

  • Procedure
  • Extractions
  • Marketplace

Solutions

By team
  • IT
  • Security & Compliance
  • Finance & Accounting
  • Sales & RevOps
  • Operations
  • HR & People
By industry
  • Healthcare
  • 3PL and warehousing
  • Freight and trucking
  • Fuel and convenience stores
  • Construction
  • Manufacturing and distribution
  • Accounting firms
  • Field services and trades
  • MSPs

Capabilities

  • Deterministic Agents
  • Stepwork MCP
  • Containers
  • Ask Bob

Company

  • Security
  • FAQ

Resources

  • AngelList Case Study
  • Claude Co-Work Alternative
  • Free IT Ticket Analysis
  • Stack check
  • For AI tools (llms.txt)

Legal

  • Terms and Conditions
  • Privacy Policy
  • Data Processing Agreement
  • Subprocessors

Ask your AI about this page

  • ChatGPT
  • Claude
  • Perplexity

2261 Market Street #4481, San Francisco, CA 94114, USA

Loot Discount inc dba Stepwork

© 2026 Stepwork. All rights reserved.