Business Systems
Internal Requests
HR and IT requests stop bouncing around in chat.
Asked inChat or ticketWhere people already work
If allowedIt gets doneNo extra process
If notA personThey still approve
Before and after
A laptop request should not need five messages.
SituationBefore
Work lives in threads nobody owns
A simple ask turns into a thread, then a ticket, then a chase.
- HR and IT asks start in chat and may never become a ticket.
- The next step depends on who is online.
- Simple repeats sit in the same pile as one-off policy questions.
ResultAfter
Known requests get done. The rest go to a person.
Repeat requests get done. Special ones go to the right person.
- The request is understood where it was asked.
- Allowed actions run in the tools you already use.
- Anything outside the rules goes to a person — with the request already written up.
The steps
How it works
Chat or ticket
Someone asks
The request is captured where the team already talks. No parallel process.
How we change the work
What changes, what people still do, and which tools.
What we change
The process, not a chatbot demo
Someone asks in chat or a ticket. If it is a known request, the system does it. If not, it goes to a person with the details already filled in.
Where people stay
People still decide the hard bits
People still approve exceptions and anything that needs a policy call.
Tools involved