Skip to content
iRon King Automated IT Book 30 min WhatsApp
Menu

Process automation

The process runs itself as far as it can, and stops where it needs a person

Purchasing, onboarding, access release, discount approval. The flow executes, stops at the gate, the manager approves from their phone, and who approved what is on record.

Book 30 min about Process Automation Chat on WhatsApp

Illustration.
Illustration.

The problem

The process exists on paper and happens in a spreadsheet, an email thread and a chat group. When the auditor asks who approved the March purchase, the answer takes three days to assemble, when it is found at all.

In action

See it happen

  1. Request flow
  2. Approval by phone
  3. Execution
  4. Who approved
The flow is a replay, in the editor, of the real runs of this approval, with the data they produced. The messages are real, with the wait shortened; the tap on Yes was made by phone and is shown on screen.

What it does

What your team stops doing

  • Executes

    The flow does the repeatable part: it takes the request, checks the systems you already have and moves on, from purchasing to access release.

  • Asks for approval

    When the decision belongs to a person, the flow stops and the question reaches the phone of whoever holds the authority for it.

  • Chases the deadline

    Deadline, reminder and a rule for when nobody answers. The request does not sit waiting for someone to remember.

  • Records

    Every step is recorded, with who approved what, in the format the auditor asks for.

In practice

In production at Grupo NTK

Process Automation runs today at Grupo NTK, alongside the other six solutions. What seven years of modernization changed is in the case.

42% fewer IT tickets Grupo NTK See the case

What you get

What ends up running in your environment

  • A survey of the process as it actually happens, in spreadsheets and email
  • A workflow orchestrator deployed on your server, integrated with the systems you already have
  • Approval with verified identity: only someone with authority for that item can approve
  • Deadline, reminder, and what happens when nobody answers
  • A record of every step, in the format the auditor asks for
  • Monthly follow-up of the flows, with an alert when one stops working

How it works

From request to record, step by step

  1. We map the process

    As it really happens: in spreadsheets, email and chat groups.

  2. The flow executes

    On your server, integrated with the systems you already have.

  3. Whoever has the authority approves

    From their phone. With no answer, the deadline and reminder rule applies.

  4. It records, we follow up

    Everything is recorded, and every month we check that no flow has stopped working.

The flow runs on its own up to the point where someone has to decide. And who decided is on record.

Tell us what is holding your IT back