Ticket / Workflow Creation App

Enables bankers and advisors to conveniently assist their clients by creating service tickets on the go, streamlining the support process.

The Opportunity

Redesigned the existing application to improve usability and successfully scale the experience to mobile—empowering users to initiate workflows from anywhere.

The Goal

These enhancements boost accuracy and first-time request completion, enabling advisors to efficiently support clients on the go—delivering faster, more reliable service anytime, anywhere.

Ideation

HMW streamline workflow initiation for Front Office users on the go, minimizing delays and improving efficiency?

Familiar experience

When we can’t predict what users will select, our goal is to keep things simple—making it really easy for them to search and navigate without getting stuck or overwhelmed.

  • Enable users to search with relevant terms that resonate with them

  • Use plain, familiar language to provide clear context and instructions

  • Offer only the most relevant choices to avoid overwhelming the user

  • Ensure the experience feels intuitive and similar to the apps users interact with daily

Anticipate the user's need

Leveraged user insights and behavior data to proactively surface relevant options, reducing the need for manual search or browsing and streamlining the overall experience.

  • Recent Client

  • Recent Workflows

  • Commonly used workflows (by role)

  • Commonly used workflows (by role)

  • Date & Time of day

Gets better with each use

Analyze user behavior to deliver personalized, real-time suggestions based on their preferences and actions

  • Ensure users never have to search for the same item twice by providing intuitive navigation and easy access to previously viewed content.

  • Continuously refine the data model with each use, leveraging user interactions to improve accuracy and relevance over time

What problems are we solving?

Learnings from the user interview

01

I use the same path every time!

Users often follow the same path when creating workflows.

02

I didn't even know we could do that

Participants heavily rely on training and knowledge sharing, yet key features often go unnoticed.

03

I want to do more than 1 thing

Users want to do multiple things at once, so we need to make multitasking easier.

04

I want to upload related documents

Many users have suggested that the ability to add documents directly to requests would make the workflow much smoother and more efficient.

How can we help users to overcome these challenges?

Purposed solutions

01

Bulk Initiation

Imagine a scenario where multiple tickets follow one another. Streamlining this process would be a game-changer, saving a ton of time and reducing unnecessary clicks.

02

Guided Journey

Added a onboarding flow to show users the most important features. This way, they can easily find out how to use the app better and get more out of it.

03

Single Click Launch Points

Offers users a quick way to access frequently used request types, like a ‘favorites’ section, making things easier and more convenient.

04

Attach documents

Big improvement to how we attach documents to requests. Now, processors will have all the info they need to handle requests quickly and accurately.

05

Estimated time completion

Give users the ability to see how tickets are progressing and when they’ll be finished, so they know what to expect.

06

Recommendation

Give users suggested workflows that are often started together, making their process smoother and boosting their productivity

Feature Prioritization

Feature prioritization

Features for MVP

Based on the findings from interviews and usability testing, we decided on these 4 features as starting points.

01

Bulk Initiation

02

Recommendation

03

Single Click Launch Points

04

Attach documents

User Journey

Meet our client, Amanda

Meet our client, Amanda

Amanda had just got married! She is moving on to the new chapter of her life!

While Amanda is excited about plans for the future, she is also worried about her finance at the same time.

Reaching out to advisors

She wants to talk to her advisor about her plans for the future, like having kids and buying a house.

She sends her advisor Chris an Email and schedules a phone call for tomorrow.

Amanda reaching out to advisors
Amanda asking her advisor for help

Hey Chris.. I need some advices

At 10:32 AM, Amanda receives the call from Chris, and she tells Chris that she had just got married, her partner and her want to buy a house together.

Meet our user, Chris

At 10:32 Am, as soon as the morning meeting is over, Chris commutes back to the office. While on the way, he calls Amanda ..

From the conversation, Chris understands her concerns and offers her the option to open the joint account for the mortgage.

He also notices that a few information on her account needs to be updated, like her legal name and marriage status.

Meet our user, Chris
Christ won't be able to start a workflow at current state

Current State

In current state, Chris has to jot down notes and use the desktop back in the office in order to launch the workflows for Amanda.

Future State

With the integration into Mobile app, Chris can quickly launch the workflows as soon as the conversation is over.

Chris will be able to do more in the future

Mobile First Design

Start with hand sketch

Mobile hand sketch

Mid-Fi Wireframe

After completing the mid-fi screens, we conducted user testing to gather feedback on potential usability issues, ensuring a solid foundation before advancing to the high-fidelity prototype

wireframe

Hi-Fi Portotype

After finalizing the mid-fi screens, we tested the concepts with users to identify potential usability issues, ensuring we addressed concerns before moving on to the high-fidelity prototype

01.Bulk Initiation

The majority of users praised the ability to initiate multiple workflows for an account simultaneously, appreciating the increased efficiency and time savings

Bulk icon

Do more at once

Let users launch multiple workflows in one go, not one at a time. Users instantly recognized this as a time-saver. It turned a repetitive 3-minute task into a 30-second one.
"I would love this. If I need to knick off multiple workflows, it would be so nice if I can just do it at
once. It would save a lot of time"

02.Recommendation

We used behavioral data to suggest frequently launched workflows based on past usage and account types—similar to a “smart favorites” system. It felt tailored without being intrusive.

Heart Icon

Peanut & Butter logic

Why don't we make them a couple if they are always paired together? This will save our users time and clicks.
"I love this feature, which will be super beneficial when we start the same workflows every time. This reminds me of Amazon's recommendation when I add products to my cart; it will prompt me with items that go well together."

03.AI-Powered Suggestions

Give users the chance to kick things off with their most-used workflows, based on what they’ve been doing lately. Think about workflows they use often and account types that work best for them. These suggestions are powered by AI, analyzing their usage patterns and giving them personalized, data-driven recommendations.

Speed up icon

Save clicks & time

We used behavioral data to suggest frequently launched workflows based on past usage and account types—similar to a “smart favorites” system. It felt tailored without being intrusive.
" I'd use this feature because I help my clients with similar tasks every day! So.. does it launch directly from an account with that information pre-filled?"

04. Attach documents

Users showed strong interest in this capability, recognizing that directly attaching documents would significantly streamline the process and enhance overall efficiency

attach doc icon

Documents will speed up the process

Users are required to attach documents to each workflow, often needing to follow up post-launch to add them—resulting in extra time and clicks for a single request.
"“I would love to be able to add documents here, rather than finding the ticket # and pulling it
up again. Just being able to be done with it and move on to the next thing”

Impact and KPI

01

Reduced 10 clicks

Users frequently follow the same path when creating workflows. Requiring them to repeat these selections for each request increases the number of clicks and adds unnecessary friction to the process.

02

Abandon rate

Dropped from 8.1 % to 5.2%

03

I want to do more than 1 thing

The majority of users expressed a strong desire to initiate multiple workflows simultaneously, highlighting the need for greater efficiency and time-saving

04

I want to upload related docs

Many users suggested that the ability to add documents directly to requests would be a significant benefit, streamlining the process and improving efficiency.

Usability Testing

Home landing Screen

Participants responded well to the overall simplicity and look/feel of the new landing screen
Recommended Requests:
•For some participants, they initially assumed that these were system generated generic cards (rather than frequently used)
Recommendation to adjust title language to be more intuitive
•Once the theory was explained participants commented that this was very useful functionality.
•Participants liked that they can also add their own request card in..especially for one off/coverage scenarios •While the number varied, participants felt 6-9 cards might not be enough, most participants recommended keeping it within the 12-15 card range for their daily requests.
•this was a very useful functionality•However —participants found the information to be very useful •Superdots; all participants assumed this was an action menu (edit, launch, remove) — being that it is very similar in WH today•
•One participant commented it would be beneficial to show the owning/processing team here as well
account ttile
I would change the title “Recommended Requests” to favorite requests. Recommended is just generic. If you don’t know that its based on your own usage, its confusing. ” - Operations Participant

Search for aLL 

While participants liked the idea of having the capability to start with a request; majority agreed that they are still likely to start with the Account/ECI first, with the possibility of requests for one off scenariosFew participant commented that new comers might be more likely to utilize the request search as they get adjusted to the language and terminology — especially with the keyword search (especially FO users with high turnover)
Client & Accounts/Requests Buttons:This was partially confusing for some participants, initially users assumed the search bar would be a true global search and show all results relatedParticipants assumed the buttons were to help filter the search posts after entering a searchFew participants commented that it’s adding an unnecessary extra click and feels backwards to have to select “request” in order to search for a request
account ttile
I like how different how different it is from todays IR, normally you need to select what type of search you are doing from the drop down. Plus now you can search for a request which is a plus ”

Party Account Search

Participants responded well to smart search
• Liked the history of recent searches for quick access if needed
• Sole ownership; participants liked this feature, especially for larger accounts with long account lists
• Folks who start their search with account # found it less relevant, but still a nice to have feature.

In-Flight Ticket
• Participants commented on the benefit of transparency to view open tickets and useful to help avoid duplicate tickets
• Saves time & clicks from having to go into Work to check for status/other tickets
• Two participants commented that they would like to see who the initiator was - incase they need to reach out

account ttile
I see where this is going, in IR now when you input an account number it shows beneficiaries which is silly, we can’t do anything with that. I don’t know a single request where we would use a beneficiary, so why show it as an option? And some of these accounts have like 6/7 of them and we can’t use them. So 13 this is really helpful.

Change Client Selection

Participants were able to easily identify how to change the clientFew participants tried to re-search within the request selection but quickly realized the correct path Participants liked the simple flow to change the client, no need to cancel and start over — saving additional time and clicks
account ttile
I would change the title “Recommended Requests” to favorite requests. Recommended is just generic. If you don’t know that its based on your own usage, its confusing. ” - Operations Participant

Home landing Screen

Participants responded well to the overall simplicity and look/feel of the new landing screen
Recommended Requests:
•For some participants, they initially assumed that these were system generated generic cards (rather than frequently used)
Recommendation to adjust title language to be more intuitive
•Once the theory was explained participants commented that this was very useful functionality.
•Participants liked that they can also add their own request card in..especially for one off/coverage scenarios •While the number varied, participants felt 6-9 cards might not be enough, most participants recommended keeping it within the 12-15 card range for their daily requests.
•this was a very useful functionality•However —participants found the information to be very useful •Superdots; all participants assumed this was an action menu (edit, launch, remove) — being that it is very similar in WH today•
•One participant commented it would be beneficial to show the owning/processing team here as well
account ttile
I would change the title “Recommended Requests” to favorite requests. Recommended is just generic. If you don’t know that its based on your own usage, its confusing. ” - Operations Participant

Next steps

1. Conduct usability testing and gather feedbacks
2. Set tasks & scenarios to test the new user flows
3. Analyze feedback and work my way towards a more refined result.

Next steps

  1. Add workflow templates for power users
  2. Test deeper automation triggers based on behavior patterns
  3. Build a metrics dashboard to quantify how these changes reduce time-on-task and support tickets