HRPulsarAI or Human?
All processes

Can AI do support request from intake to closure?

An expert breakdown of a typical process from public sources, worked out by the same rules as your own check.

3 of 12 steps go to an agent

Goes to an agent (3)

An agent does these steps on its own.

  1. Receive the request through the contact channel and sort it: incident or service request

    An agent can do this step alone: everything it takes is a strong suit of AI.

    • Rule-based classification and routing
    • Scripted or regulated dialogue with an external party
  2. Categorise by the predefined reference of categories and subcategories

    An agent can do this step alone: everything it takes is a strong suit of AI.

    • Rule-based classification and routing
  3. First line: diagnostics by the known error database and scripts, resolution at first contact

    An agent can do this step alone: everything it takes is a strong suit of AI.

    • Checking against a reference and finding discrepancies
    • Scripted or regulated dialogue with an external party

AI drafts, a person checks (7)

AI prepares the work; a person reviews and confirms it.

  1. Log the request — user, description, affected service and configuration item

    A person confirms it: the step changes something outside the company.

  2. Functional escalation to the second line with transfer of ownership and notification of the user

    A person signs off: the step needs a formal approval.

  3. Second-line investigation: timeline, full scope, search through past incidents and logs

    AI drafts it and a person checks: AI only drafts part of what it takes.

    • Investigating a cause across heterogeneous sources
  4. Apply the resolution and restore the service, including through the user's actions under dictation

    A person signs off: the step needs a formal approval.

  5. Record the resolution: closing notes, closure code, status 'resolved', notification of the user

    A person confirms it: the step changes something outside the company.

  6. Confirmation by the user and closure of the request; on disagreement — reopening

    A person signs off: the step needs a formal approval.

  7. Satisfaction survey on the closed request

    A person confirms it: the step changes something outside the company.

Stays with people (2)

These steps need a person's judgement or presence.

  1. Prioritise by the impact and urgency matrix, override with a rationale

    Stays with people: it takes judgement that depends on your business context.

    • Judging risk or priority in a business context
  2. Hierarchical escalation: VIP, risk of an SLA breach, sensitive topic

    Stays with people: it takes judgement that depends on your business context.

    • Judging risk or priority in a business context

Sources

What about your own process?

Describe it in your own words and get the same breakdown in about a minute.

Check your own process