Sales associate

Sales lead

How We Helped Bank Sales Teams Keep Context Through SME Onboarding

How We Helped Bank Sales Teams Keep Context Through SME Onboarding

Shared notes that keep every detail in the journey.

Role

Role

Product Designer

Team

Team

Product manager, Lead designer

Sales team, Developers

Tools

Tools

Figma, Claude-Code, Jira

Duration

Duration

Jul 2026 - Sep 2026

about the company

What is Pollinate?

Pollinate is a fintech platform serving tier 1 banks and financial institutions. It provides a suite of configurable mini apps and merchant acquiring tools that enable banks to deliver seamless financial experiences to their merchants. Beyond customer-facing solutions, Pollinate also builds internal tools like assisted onboarding, announcements, onboarding reporting and status tracking systems to help banks manage and support their merchant networks more effectively.

about the company

What is Pollinate?

Pollinate is a fintech platform serving tier 1 banks and financial institutions. It provides a suite of configurable mini apps and merchant acquiring tools that enable banks to deliver seamless financial experiences to their merchants. Beyond customer-facing solutions, Pollinate also builds internal tools like assisted onboarding, announcements, onboarding reporting and status tracking systems to help banks manage and support their merchant networks more effectively.

about the company

What is Pollinate?

Pollinate is a fintech platform serving tier 1 banks and financial institutions. It provides a suite of configurable mini apps and merchant acquiring tools that enable banks to deliver seamless financial experiences to their merchants. Beyond customer-facing solutions, Pollinate also builds internal tools like assisted onboarding, announcements, onboarding reporting and status tracking systems to help banks manage and support their merchant networks more effectively.

About the problem

Overview

We have an SME onboarding product that works in two ways: self-service, where the merchant completes the process on their own, and assisted, where a sales associate completes it on the merchant’s behalf, in person or over a call, using an internal system we built for them. These journeys are long and rarely finish in one sitting. The merchant may need to upload documents, get other owners to sign, or take time to think about pricing. When that happens, the associate gives the merchant time and moves on to another case. When the merchant returns, a different associate often picks the case up. They need to know what has been discussed so far, but there was no way to pass that context on. That created the need for a feature to capture it.

About the problem

Overview

We have an SME onboarding product that works in two ways: self-service, where the merchant completes the process on their own, and assisted, where a sales associate completes it on the merchant’s behalf, in person or over a call, using an internal system we built for them. These journeys are long and rarely finish in one sitting. The merchant may need to upload documents, get other owners to sign, or take time to think about pricing. When that happens, the associate gives the merchant time and moves on to another case. When the merchant returns, a different associate often picks the case up. They need to know what has been discussed so far, but there was no way to pass that context on. That created the need for a feature to capture it.

About the problem

Overview

We have an SME onboarding product that works in two ways: self-service, where the merchant completes the process on their own, and assisted, where a sales associate completes it on the merchant’s behalf, in person or over a call, using an internal system we built for them. These journeys are long and rarely finish in one sitting. The merchant may need to upload documents, get other owners to sign, or take time to think about pricing. When that happens, the associate gives the merchant time and moves on to another case. When the merchant returns, a different associate often picks the case up. They need to know what has been discussed so far, but there was no way to pass that context on. That created the need for a feature to capture it.

The challenge

Understanding the problem

The requirement came from the banks, raised through their sales teams. Roughly 75 to 80 percent of assisted cases changed hands before completion, yet the system only recorded what had been filled in, not what had been said. Associates kept manual notes of their own or relied on instinct. Those notes stayed with the person who wrote them, so the next associate had no view of why the merchant paused, what they were unsure about, or what had been agreed. Context mattered for custom quotes too. An associate could offer a merchant better pricing based on long-term profitability, but that quote needed approval from a lead salesperson. Without the reasoning attached to the case, the lead had to approve with only the numbers in front of them.

The challenge

Understanding the problem

The requirement came from the banks, raised through their sales teams. Roughly 75 to 80 percent of assisted cases changed hands before completion, yet the system only recorded what had been filled in, not what had been said. Associates kept manual notes of their own or relied on instinct. Those notes stayed with the person who wrote them, so the next associate had no view of why the merchant paused, what they were unsure about, or what had been agreed. Context mattered for custom quotes too. An associate could offer a merchant better pricing based on long-term profitability, but that quote needed approval from a lead salesperson. Without the reasoning attached to the case, the lead had to approve with only the numbers in front of them.

The challenge

Understanding the problem

The requirement came from the banks, raised through their sales teams. Roughly 75 to 80 percent of assisted cases changed hands before completion, yet the system only recorded what had been filled in, not what had been said. Associates kept manual notes of their own or relied on instinct. Those notes stayed with the person who wrote them, so the next associate had no view of why the merchant paused, what they were unsure about, or what had been agreed. Context mattered for custom quotes too. An associate could offer a merchant better pricing based on long-term profitability, but that quote needed approval from a lead salesperson. Without the reasoning attached to the case, the lead had to approve with only the numbers in front of them.

Leads approved pricing without the reasoning

Associates offered better pricing for long-term profitability, but the rationale was not attached

Context lived in personal notes or instinct

Notes stayed with whoever wrote them, so the next associate could not see them.

75% to 80%

of assisted cases change hands before they are completed.

competitive analysis

Learning from other tools

Before designing anything, I looked at how tools that people already use every day handle notes. Jira attaches comments directly to a ticket, so the discussion always sits next to the work it refers to. Google Keep keeps a note to a heading and a body, which makes it quick to write and easy to scan later. CRM tools such as Salesforce and HubSpot log notes against a customer record, so anyone opening that record sees the history. Three patterns repeated across all of them: a short title, free text, and clear authorship. These became the starting point for supporting notes, because associates would recognise them without any training.

competitive analysis

Learning from other tools

Before designing anything, I looked at how tools that people already use every day handle notes. Jira attaches comments directly to a ticket, so the discussion always sits next to the work it refers to. Google Keep keeps a note to a heading and a body, which makes it quick to write and easy to scan later. CRM tools such as Salesforce and HubSpot log notes against a customer record, so anyone opening that record sees the history. Three patterns repeated across all of them: a short title, free text, and clear authorship. These became the starting point for supporting notes, because associates would recognise them without any training.

competitive analysis

Learning from other tools

Before designing anything, I looked at how tools that people already use every day handle notes. Jira attaches comments directly to a ticket, so the discussion always sits next to the work it refers to. Google Keep keeps a note to a heading and a body, which makes it quick to write and easy to scan later. CRM tools such as Salesforce and HubSpot log notes against a customer record, so anyone opening that record sees the history. Three patterns repeated across all of them: a short title, free text, and clear authorship. These became the starting point for supporting notes, because associates would recognise them without any training.

Exploring visualisation approaches

A side panel, not a new pattern

Notes open in a side panel that slides in from the right side of the screen. We already use this panel in many places across the onboarding journey, so reusing it kept the experience consistent and meant associates did not have to learn a new interaction. The panel also suits how notes are used. An associate is usually in the middle of a case when something worth recording comes up, so the case stays in place behind the panel and they can return to where they were as soon as they close it.

Exploring visualisation approaches

A side panel, not a new pattern

Notes open in a side panel that slides in from the right side of the screen. We already use this panel in many places across the onboarding journey, so reusing it kept the experience consistent and meant associates did not have to learn a new interaction. The panel also suits how notes are used. An associate is usually in the middle of a case when something worth recording comes up, so the case stays in place behind the panel and they can return to where they were as soon as they close it.

Exploring visualisation approaches

A side panel, not a new pattern

Notes open in a side panel that slides in from the right side of the screen. We already use this panel in many places across the onboarding journey, so reusing it kept the experience consistent and meant associates did not have to learn a new interaction. The panel also suits how notes are used. An associate is usually in the middle of a case when something worth recording comes up, so the case stays in place behind the panel and they can return to where they were as soon as they close it.

Two simple fields

Adding a note takes two plain text inputs: a title and the note content. The title is optional and limited to 70 characters, so an associate can label a note when it helps but is never slowed down by it. The content is plain text with a 400 character limit, which keeps notes short and to the point. The save button stays disabled until there is content to save, and a confirmation message appears once the note is added. When a case already has notes, the form opens above the existing list, so the associate can see what has been written before adding to it.

Two simple fields

Adding a note takes two plain text inputs: a title and the note content. The title is optional and limited to 70 characters, so an associate can label a note when it helps but is never slowed down by it. The content is plain text with a 400 character limit, which keeps notes short and to the point. The save button stays disabled until there is content to save, and a confirmation message appears once the note is added. When a case already has notes, the form opens above the existing list, so the associate can see what has been written before adding to it.

Two simple fields

Adding a note takes two plain text inputs: a title and the note content. The title is optional and limited to 70 characters, so an associate can label a note when it helps but is never slowed down by it. The content is plain text with a 400 character limit, which keeps notes short and to the point. The save button stays disabled until there is content to save, and a confirmation message appears once the note is added. When a case already has notes, the form opens above the existing list, so the associate can see what has been written before adding to it.

Exploring notes and documents in one panel

Alongside notes, there was an early need for associates to upload supporting documents. I proposed combining the two in a single panel, with a toggle at the top to switch between adding a note and uploading a document. The thinking was that both are supporting material for a case, so one entry point would be simpler than two. As we worked through it, document upload turned out to be the more complex of the two, and the journey already asks for documents at a later step. Combining them would have duplicated that step and made a simple notes feature heavier. We removed documents from the panel and kept them separate, so notes stayed quick and focused.

Exploring notes and documents in one panel

Alongside notes, there was an early need for associates to upload supporting documents. I proposed combining the two in a single panel, with a toggle at the top to switch between adding a note and uploading a document. The thinking was that both are supporting material for a case, so one entry point would be simpler than two. As we worked through it, document upload turned out to be the more complex of the two, and the journey already asks for documents at a later step. Combining them would have duplicated that step and made a simple notes feature heavier. We removed documents from the panel and kept them separate, so notes stayed quick and focused.

Exploring replies, and why we dropped them

Comment threads in tools like Jira inspired an early version that let associates reply to each other’s notes. It seemed natural, because a second associate could answer a question or add to what the first had written, and the whole exchange would stay in one place. When I reviewed it with the wider stakeholders, we saw the risk: replies would turn notes into a chat between associates. Conversations would bury the facts the next person needed, and the feature would start competing with the communication tools the bank already uses. The problem we set out to solve was passing on context, not helping associates talk to each other. We removed replies so that every note stands on its own as a clear record of the case.

Exploring replies, and why we dropped them

Comment threads in tools like Jira inspired an early version that let associates reply to each other’s notes. It seemed natural, because a second associate could answer a question or add to what the first had written, and the whole exchange would stay in one place. When I reviewed it with the wider stakeholders, we saw the risk: replies would turn notes into a chat between associates. Conversations would bury the facts the next person needed, and the feature would start competing with the communication tools the bank already uses. The problem we set out to solve was passing on context, not helping associates talk to each other. We removed replies so that every note stands on its own as a clear record of the case.

Edit and delete, based on role

Notes are a shared record, so who can change them matters. A sales associate can edit their own notes but cannot delete any, because a deleted note takes its context with it, which is the very thing the feature exists to protect. A sales lead can edit or delete any note on the case. The interface only shows the actions a user is allowed to take. An associate sees a single edit icon on their own note, while a lead sees edit and delete on every note. When a note is changed, its timestamp switches to “Edited on” with the new date and time, so everyone can tell it is not the original. Deleting is permanent, so a lead has to confirm it first. The dialog states that the note will be removed from the case and cannot be recovered.

Edit and delete, based on role

Notes are a shared record, so who can change them matters. A sales associate can edit their own notes but cannot delete any, because a deleted note takes its context with it, which is the very thing the feature exists to protect. A sales lead can edit or delete any note on the case. The interface only shows the actions a user is allowed to take. An associate sees a single edit icon on their own note, while a lead sees edit and delete on every note. When a note is changed, its timestamp switches to “Edited on” with the new date and time, so everyone can tell it is not the original. Deleting is permanent, so a lead has to confirm it first. The dialog states that the note will be removed from the case and cannot be recovered.

Edit and delete, based on role

Notes are a shared record, so who can change them matters. A sales associate can edit their own notes but cannot delete any, because a deleted note takes its context with it, which is the very thing the feature exists to protect. A sales lead can edit or delete any note on the case. The interface only shows the actions a user is allowed to take. An associate sees a single edit icon on their own note, while a lead sees edit and delete on every note. When a note is changed, its timestamp switches to “Edited on” with the new date and time, so everyone can tell it is not the original. Deleting is permanent, so a lead has to confirm it first. The dialog states that the note will be removed from the case and cannot be recovered.

Prioritising what user need to see first

The overview screen is the first thing the user sees when they open a case, so I added a supporting notes card there. It shows the latest note in full, with its heading, author, date, and time, along with a count of how many notes the case has. An associate picking up a case gets the most recent context straight away, without opening anything. From the card, “All notes” opens the side panel with the full list. When a case has no notes yet, the same card shows an empty state with an “Add a note” action, so it works as a starting point as well as a summary.

Prioritising what user need to see first

The overview screen is the first thing the user sees when they open a case, so I added a supporting notes card there. It shows the latest note in full, with its heading, author, date, and time, along with a count of how many notes the case has. An associate picking up a case gets the most recent context straight away, without opening anything. From the card, “All notes” opens the side panel with the full list. When a case has no notes yet, the same card shows an empty state with an “Add a note” action, so it works as a starting point as well as a summary.

Access from anywhere in the journey

An associate can need to add context at any stage, for example during a pricing conversation, while waiting on documents, or before a signature. So notes are available on every stage of the journey through the more actions button at the top right of the case. Selecting “Supporting notes” opens the side panel, where the associate can read all previous notes or add a new one without leaving the step they’re on. I explored three placements. A dedicated notes icon at the top right was the most visible, but it added another button to a header that’s already busy. A floating button in the bottom right corner was always within reach, but it could cover content on longer pages such as the quote. The more actions menu was already on every stage and associates already used it for case actions, so putting notes there made them available everywhere without adding anything new to the screen.

Access from anywhere in the journey

An associate can need to add context at any stage, for example during a pricing conversation, while waiting on documents, or before a signature. So notes are available on every stage of the journey through the more actions button at the top right of the case. Selecting “Supporting notes” opens the side panel, where the associate can read all previous notes or add a new one without leaving the step they’re on. I explored three placements. A dedicated notes icon at the top right was the most visible, but it added another button to a header that’s already busy. A floating button in the bottom right corner was always within reach, but it could cover content on longer pages such as the quote. The more actions menu was already on every stage and associates already used it for case actions, so putting notes there made them available everywhere without adding anything new to the screen.

Edge cases

Error scenarios

Notes are often written in the middle of a call, so errors needed to be clear without getting in the way. If a title goes over 70 characters or the content goes over 400, the field turns red, the limit below it is highlighted, and the save button is disabled until the text is shortened. The associate sees which field is the problem and what the limit is, at the point where they are typing. If the note fails to save for a reason outside their control, a message at the bottom of the panel tells them something went wrong and asks them to try again. The text they typed stays in the form, so nothing has to be written twice.

Edge cases

Error scenarios

Notes are often written in the middle of a call, so errors needed to be clear without getting in the way. If a title goes over 70 characters or the content goes over 400, the field turns red, the limit below it is highlighted, and the save button is disabled until the text is shortened. The associate sees which field is the problem and what the limit is, at the point where they are typing. If the note fails to save for a reason outside their control, a message at the bottom of the panel tells them something went wrong and asks them to try again. The text they typed stays in the form, so nothing has to be written twice.

Impact

Here is what we achieved

Impact

Here is what we achieved

75–80% of assisted cases change hands, and every one of them now has its context on the case.

Zero repeated questions: merchants don’t have to explain themselves again to a new associate.

One place to approve: leads see the pricing rationale right next to the quote.

Increased business revenue

One place to approve: leads see the pricing rationale right next to the quote.

Created a reusable widget pattern that scales to other reporting contexts across the platform

  • Visual Designer

  • Product Designer

  • UX/UI Designer

  • Framer Developer

Do you have a great idea 🧠

I'm up for awesome chats, meet-ups, a game of table tennis, and any exciting work opportunities

  • Visual Designer

  • Product Designer

  • UX/UI Designer

  • Framer Developer

Do you have a great idea 🧠

I'm up for awesome chats, meet-ups, a game of table tennis, and any exciting work opportunities

Enter the password

Enter the password