Portfolio · Recreated Mockup · BNY Confidential Data Not Shown

Level 1 Support & Ticketing System

An end-to-end intake, routing, and knowledge system for a 1,200-person internal user base — designed, built, and shipped on Microsoft's Power Platform.

Case study by Danita Walton · Senior Specialist, Business Technology Liaison, BNY Wealth Service Delivery
What you're looking at: the real project shipped and is in daily use at BNY — but the actual screens, data, and users are confidential and can't be shown publicly. Everything below is a faithful recreation built from scratch to demonstrate the interface, data structure, and automation logic, using entirely fictional sample tickets and names. No real BNY system, data, or users are shown anywhere on this page.

The approach

From messy, undocumented support requests to a system people actually trust.

01

Research before building

Led an Agile-based user-research initiative across roughly 1,200 internal Wealth application users — survey framework, user stories, and a scoring model to evaluate pain points across applications, workflows, and support before writing a single requirement.

02

Define the structure

Defined objectives, scope boundaries, success criteria, data structures, workstreams, and milestones — then migrated legacy Microsoft Access data into a modernized SharePoint Lists backend.

03

Build the front end

Designed a Power App interface for search, filter, assignment, status updates, and communication — giving the support team a clearer framework for ownership and escalation.

04

Automate and validate

Built Power Automate flows for ticket routing, notifications, and audit/export activity, then performed release-night validation on the shipped solution, confirming functionality and logging proof of expected behavior.

1,200Wealth users covered by the research
4Power Platform tools combined
1Legacy Access system migrated to SharePoint

What's recreated below

Three connected pieces of the same system.

Front end

Ticket queue & detail

The Power App support agents use to search, filter, assign, and update tickets. Fully interactive — click into a ticket below.

Data layer

SharePoint List

The backing list every ticket, status, and priority actually lives in — the structure the app and the automations both read from.

Automation

Power Automate flow

The routing logic behind the scenes: notifications, escalation branching, and the audit trail that feeds compliance reporting.


1. Ticket queue & detail panel

Try it — click a row, change status/priority/assignee, add an update
wealthservicedelivery.powerapps.com/level1-tickets — recreated mockup

2. SharePoint List — the data behind it

Same fictional sample tickets, shown as the underlying list
bny.sharepoint.com/sites/wealthservicedelivery/lists/level1tickets — recreated mockup

3. Power Automate — the routing logic

Trigger → condition → notify → update → audit
make.powerautomate.com/flows/level1-ticket-routing — recreated mockup
Microsoft Power Apps Power Automate SharePoint Lists Microsoft Forms Requirements Gathering User Research Change Management Release Validation