Solutions Requests
Request intake
Intake that captures what is needed first time, and tells the requester where it is.
01 / What it looks like running
Start to finish, and where a person still comes in.
- 01 / TriggerSomeone asks for something
- 02 / AutomatedQuestions asked until complete
- 03 / AutomatedRouted to the right team
- 04 / AutomatedStatus published back
- 05 / Needs a personDoing the thing that was asked for
Automated Needs a person 3 of 5 run without anyone
02 / What stops happening
7 steps become 1.
The struck lines are the ones nobody performs after this is live.
- Request arrives however the requester felt like sending it
- Half the information is missing
- Someone emails back to ask for the rest
- It waits
- The requester emails to ask where it is
- Someone looks it up and replies
- The request itself, done once, with everything needed
03 / Built on
In your tenant, under your licences.
- Copilot Studio
- Power Automate
- Power Apps
Yours may differ. What a process runs on is decided by what it touches, not by what we prefer building with.
Does yours run like this?
It probably runs nearly like this, with two steps that are entirely your own. Those two are the interesting part.