Service Desk App with Structured Tickets and SLAs
Global electronics manufacturer
In short
How can a team replace a shared mailbox with a simple ticketing app?
A shared mailbox is a poor ticket system. Support staff cannot tell which request is being worked on, who owns it or which matters most, so urgent and old requests wait. We built a service desk app that turns each request into a ticket with a status, an owner and a deadline.
At a glance
- One ticket per request, with a status
- Each ticket has a named owner
- Priority and SLA clock on every ticket
The client
The client is a global electronics manufacturer with many internal teams that support colleagues and partners. This use case suits a support team whose requests arrive by Outlook, outside the main IT service management tool.
What it was costing them
- Messy inbox: requests pile up in Outlook, mixed with other mail.
- No ownership: nobody can see who is working on which request.
- No priority: urgent requests look the same as routine ones.
- No SLA: nobody notices a missed deadline until the requester complains.
What we built
We built a service desk app started from an out-of-the-box Power Apps template and adapted to the team.
- One ticket per request: emails to the support mailbox create a ticket through Power Automate, with requester, category and priority.
- Clear ownership: every ticket has an agent, and the team sees who is on what.
- Visible priority: urgent tickets sit at the top and are colour coded.
- An SLA clock: target response and resolution times by priority, with a warning before a breach.
- Real statuses: new, in progress, waiting for requester, resolved and closed.
- Requesters kept informed: replies and status changes go back by email.
Results
- Result: structured tickets, clear statuses, named owners and a clear SLA.
- Result: fewer requests lost or answered late, as every ticket has an owner and a deadline.
- Result: less time spent asking who is handling what, as ownership is on screen.
The risk most teams miss
Two places for requests. By month three some people still email a colleague directly, and tickets exist for only part of the work. We routed every request through one shared mailbox, auto-replied with the ticket number and reported only on tickets. SLA targets were agreed with the business before go-live.
What we would add today
Improvements we would add on top of what is live.
- Use AI Builder to categorise and prioritise incoming emails, with the agent confirming the suggestion.
- Add a Copilot Studio agent grounded on a knowledge base to answer common requests before a ticket is raised.
- Move to Dynamics 365 Customer Service if the team needs queues, entitlements and omnichannel support.
- Show tickets and SLA warnings in Teams with adaptive cards.
Technology
Power Apps (out-of-the-box template), Dataverse, Power Automate, Outlook, Power BI.
Tell us how requests reach your support team today, and we will tell you how to give each one an owner and a deadline.
Products and capabilities
- Power Apps
- Power Automate
- Dataverse
- service desk
- ticket management
- SLA tracking
The service behind this work
Power Platform developmentMore on this industry
Manufacturing and distribution
Related use cases
IT and platform teamsDataverse Housekeeping and Storage Advice
Dataverse capacity costs money, and it fills quietly. Import logs, system jobs and old workflow records grow in the background until an environment runs short. The client asked how to housekeep its environments. We put in place a short routine of checks and clean-ups that frees storage without touching business data.
SharePoint Online and Power Platform Deep-Dive Session
Sites that grow without a plan end up with mixed branding, unclear permissions and guests who can reach more than intended. Copilot adds a new question: what will it find, and who can ask it? We ran a deep-dive session for the client covering both.
Power Platform Governance Kickstarter and Handbook
The client held more than 2,000 per-user Power Platform licences, yet had no agreed way to open an environment, approve a connector or hand an app to IT. Each request was decided from scratch. We ran five governance workshops and wrote the strategy and handbook that make those decisions repeatable.
- c. 180
- handbook pages
- 2,000+
- per-user licences
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.