Skip to content
GullySales

Banks · Customer adoption programmes

Help an account holder start using the mobile app, not only install it.

For a bank, a customer adoption programme gets existing account holders to start using a channel or product they already have, such as the mobile app, UPI, a debit card or net banking. GullySales studies where people stop, builds the nudges and branch routines that move them forward, and reads the results against the activation figures recorded first.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

Realistic editorial illustration of banks at work in India

What customer adoption programmes means

Customer adoption programmes are planned prompts, guidance, and follow-up that keep customers using a product or service after onboarding. GullySales defines meaningful usage from your customer records, prepares messages for missed milestones, and sets up an activity view so your team knows who needs attention before the renewal conversation.

Last updated 14 Nov 2026. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.

For banks

Where it usually goes wrong, and what we would do.

  • “Registered is not the same as using”

    A bank can report thousands of app registrations while a large share of those holders never complete a transaction, or never log in after the first day. The registration count flatters the programme. Adoption has to be defined as the first meaningful use, such as a first transfer, a first bill payment or a first card tap, and each product needs its own definition.

  • “The branch is where the stuck customer shows up”

    An account holder who cannot reset a password or does not trust a first transfer walks into a branch, joins a queue and asks a cashier. That visit is the best moment to help, and the cashier's time is the scarcest resource. A programme that gives the counter a short, repeatable way to start a person on the app, instead of doing the transaction for them, changes what the visit achieves.

  • “Different customers stop at different places”

    A salaried customer in a city may never open the app because the first screen asks for an extra step. An older customer may fear a wrong tap. A customer in a smaller town may have a basic phone and a patchy connection. A single reminder message treats all of them the same. Adoption work begins by finding which group stopped where.

  • “A nudge that sounds like a sales push is ignored”

    An account holder who receives a message every time the bank wants something learns to skip it. Adoption messages must read as help with something the person already wants to do, sent through the channel they accepted for service contact. Your compliance team approves wording, and the preference record decides who may be contacted.

What we do

What we deliver for banks.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Adoption definition for each channel

    A written definition of an adopted customer for the app, UPI, net banking and the debit card, each tied to a first real use and a repeat use. Your product and finance teams agree the definitions before any number is reported, so the programme cannot redefine success midway.

    Result: Each channel has one stated meaning of adopted that the bank has accepted.

  2. Drop off map from registration to first use

    A step by step picture of where registered account holders stop, built from your app and enrolment records and from interviews with branch staff. It names the stage with the biggest loss for each group, such as first login, one time password entry or first payee set up.

    Result: The map shows, for each group, the step where the biggest loss happens.

  3. Segment list with the barrier for each

    Groups of account holders, such as salary holders, senior citizens, small business owners and holders of basic accounts, each paired with the likeliest barrier and the route best suited to reach them. Where records are thin, the sheet says the barrier is an assumption to be tested.

    Result: Each group has a named barrier and a named contact route.

  4. Branch assisted enrolment routine

    A short routine for the counter officer to start an account holder on the app without taking over the transaction: install, log in, complete one small action together, and note it. A one page card and a recorded note field keep it consistent across branches.

    Result: A branch can show how many assisted starts were recorded.

  5. Message and guide set for approval

    Short messages and step by step guides for each barrier, in the languages your account holders use, each reviewed by your compliance team. Messages go only through channels the holder has agreed to, in line with the preference record.

    Result: Every message in the set carries a compliance approval note.

  6. Adoption tracking sheet and handover

    A working sheet showing, for each group and each branch, registrations, first uses and repeat uses against the starting figures, with notes naming who updates it. It lets your team continue reading results after our support ends.

    Result: Your team can update the sheet without us.

How the result is measured

  • Customers reaching the agreed usage milestone
  • Share of customers meeting the usage benchmark
  • Customers flagged and awaiting follow-up

Recorded as a baseline before work starts, so every later report has an honest comparison.

Who it is for

This is written for these banks.

  • Private sector bank branches
  • Public sector bank branches
  • Regional rural banks
  • Cooperative banks
  • Small finance banks
  • Business correspondent networks
  • NRI-focused branches
  • MSME-focused branches

Before you decide

Agree the work. Know how to judge it.

Customer adoption programmes for banks: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Map what the customer has been promised and what happens after the order. Gather the questions that repeatedly delay the start of delivery or use.

Make the scope clear

Agree the sales-to-delivery handover, customer responsibilities, and the point at which onboarding is complete. Name the owner of each unresolved dependency.

Check the work in use

Follow a recent customer from order confirmation to their first useful outcome. Check that they received the right instructions and know where to ask for help.

Know when to change course

If the sale includes a promise delivery cannot fulfil, correct the promise and handover. An automated welcome message will not resolve that gap.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from banks. Anything missing is noted in the written scope, with who will supply it.

Enrolment and usage records by channel
Registrations, logins and first transactions by channel, branch and period, drawn by your technology team. Without usage records we can only describe registrations, and the programme would reward a count that says nothing about use.
Time with branch officers and agents
A few counter officers and call centre agents willing to describe the questions and problems they meet. They know where an account holder gets stuck. Without them, the drop off map shows where people stop but not the reason.
Decision on who may be contacted
A confirmation, from compliance or the preference record, of which account holders have agreed to which channels. Adoption messages sent to people who refused contact break the bank's own rules and damage the trust the programme depends on.
Screens and journeys of the app
Access to the current app, the enrolment screens and the help pages, with a test account. We follow the same journey an account holder does and note each step that might confuse. A missing test account leaves the guides written from description.
A named owner for the programme
One person in retail or digital banking who owns the adoption figures after we leave. When nobody does, the branch routine fades, the sheet goes unread and the figures drift back to where they started.

How it works

How the customer adoption programmes work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Fixing the starting figures

    We take registrations, first uses and repeat uses by channel and by branch from your records, and note the starting position of each. Your product team confirms the definitions. These baseline figures are what every later result is read against, so we settle them first.

  2. 2

    Finding where account holders stop

    We study the enrolment and usage records, then speak with branch officers and call centre agents about what they are asked. The drop off map shows the stage where people stall, and the staff interviews explain why, which the records alone do not.

  3. 3

    Grouping holders by barrier

    Account holders are grouped by what holds them back: trust, skill, device, connection, or a missing reason to use the channel. We test our reading of each group with a small branch sample, and we label unsupported guesses as assumptions.

  4. 4

    Writing branch and message materials

    We prepare the counter routine, the step guides and the messages. Your compliance team reviews wording, and your marketing lead checks language and tone. Nothing goes to an account holder before it carries written approval.

  5. 5

    Trial in selected branches

    The routine and messages run first in a few branches chosen with you, including at least one with a different customer mix. Officers give feedback on what they could and could not do at the counter, and we change the material before wider use.

  6. 6

    Reading the result against the baseline

    We compare first and repeat use in the trial branches with the starting figures and with branches not yet changed. We report what moved, what did not and what we cannot yet tell, and agree with you whether to extend, adjust or stop.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2 · you are here

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

What counts as adoption for a bank?
Your product and finance teams decide, and we record it before any figure is reported. A common choice is a first real transaction followed by a repeat use. A registration or an install alone is a poor measure, because it records intent and not use.
Will you contact our account holders directly?
Only through the bank's own approved channels and only to those who have agreed to receive such messages. Your compliance team approves the wording first. GullySales prepares the material and the routine, and the bank sends the messages.
What about older customers who distrust the app?
They are treated as their own group with their own barrier, which is trust and fear of a wrong tap. The branch assisted routine suits them better than a message. Some will always prefer the counter, and the programme does not push them out of it.
Can the programme promise higher app usage?
No. We set starting figures, run the programme and report what changed, including when nothing did. Usage depends on the app, the branch effort and the customer mix, and none of those are fully in our control.
Does this involve changing the app itself?
Not as part of this work. We find where the app loses people and report it to your digital team, who decide whether to change it. Our materials work with the app as it is, and we say so when the barrier lies in the product.
How do you avoid overloading branch staff?
The counter routine is short, uses a printed card and one note field, and is trialled in a few branches first. Staff tell us what takes too long, and we cut it. A routine that officers drop within days has no value, so we design it for them.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.