Receive
A form creates a request. An employee enters phone and email cases in the app.
My own Power Platform project
Request intake and follow-up
Form submissions and cases entered after a phone call or email go into one register. The team can see who owns each case and what should happen next.
Power AppsPower AutomateSharePointMicrosoft FormsTeams
Request intake
Starting point
One queue. An owner, a deadline and a next step.
When cases are scattered across inboxes and spreadsheets, it is difficult to see who should reply or whether a deadline has passed.
The workflow
How it works
One problem, clear steps and a visible result.
Organise
Each case receives a number, owner, priority and status.
Follow up
Next-contact dates, reminders and escalation help the team keep track of open cases.
Close
The team closes or reopens the case while retaining earlier activity records.
What the working solution shows
The working app shows the queue, details and a new-request form on desktop and mobile. Flows handle numbering, form intake, deadlines and closure. AI classification is optional.
What connects this project
Tools and their roles
- Power Apps
- Queue, detail and new-request screens, including the phone layout.
- Power Automate
- Numbering, form intake, deadline checks and case closure.
- SharePoint
- Request records and the data used to allocate request numbers.
- Microsoft Forms
- The form used to submit a new request.
- Microsoft Teams
- Access to the app as a tab in Teams.
- Office 365 Users
- Looking up a user when selecting the case owner.
Optional AI classification uses an AI Builder prompt and a Dataverse connection. It is a separate option with its own licensing and cost checks. The core workflow operates without it.
Fit
When a similar process may help
- Requests arrive through several channels.
- There is no clear owner or next-contact date.
- The team needs a shared queue with visible statuses.
Scope and requirements
What we agree before deployment
This is my own portfolio project. A client deployment requires mapped SharePoint lists and connections, agreed roles, statuses and deadlines, and testing. AI classification needs separate configuration and a licensing and cost review.
Let's discuss your task
Have a specific task
or a process to improve?
Tell me how your team works today and what you want to change. You do not need a ready specification or technical knowledge.
We briefly check the fit. Detailed investigation, building or repair is agreed as paid work.
Write to Maciejkontakt@klimekautomation.plPrefer a form?
Use a general description without confidential customer data. Privacy policy.