Skip to content
GullySales

Fintech companies · Follow up systems

Reach the user who stopped at KYC and the bank that went quiet after a demo.

A follow-up system for a fintech company is a set of messages and tasks that revive unfinished applications and keep a bank pilot moving. GullySales designs them around the step where each person stopped, with consent and your compliance head's approval built in.

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

A fintech representative demonstrates a payment terminal to a shopkeeper

What follow up systems means

A follow-up system is the set routine for calling, messaging or emailing an enquiry more than once, since most buyers do not decide on the first conversation. GullySales sets the number and timing of follow-ups so an undecided buyer keeps hearing from you until they decide either way.

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 fintech companies

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

  • “The message should name the step”

    A user who stopped at the address proof does not need a general reminder. A message that says which step is waiting, and how to resume it, is read as help. A vague nudge reads as pressure.

  • “Excess reminders create complaints”

    A user who is chased across SMS, push and WhatsApp may report the app. Contact rules, a cap on messages and a clean opt-out protect the brand and the sender registration.

  • “A pilot goes quiet at a handover”

    Inside a bank, the champion is promoted or the budget moves. A follow-up record that tracks the last contact with each role lets sales reach the next person before the pilot stalls.

What we do

What we deliver for fintech companies.

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

  1. Drop-off sequences by KYC step

    Messages for each stage where users stop, with the specific document or action and a link to resume.

    Result: Each drop-off point has its own message.

  2. Contact rules

    Quiet hours, caps on reminders and a stop rule when a user declines.

    Result: Nobody is contacted outside the agreed rules.

  3. A support handoff

    A path for a user who replies with a question to reach a person, not a loop.

    Result: A reply from a user lands with a named owner.

  4. A pilot touch plan for each lender

    Planned follow-ups by role after a demo, a security review and a trial.

    Result: Every open pilot shows its next step and owner.

  5. A stalled-deal review

    A short sheet of pilots with no movement and the reason recorded.

    Result: Stalled pilots are visible in one list.

How the result is measured

  • Follow-up completion rate
  • Average number of follow-ups before close
  • Enquiries closed after repeat follow-up

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

What to capture or send

These are the moments in a user or bank journey that need a message and an owner.

A user who stopped at KYC
A message naming the step reached and what is needed to finish, sent only to users who agreed to contact, with a way to stop further messages.
A user whose application was declined by the lender
A plain note from support on what the lender allows you to share, and a route to ask. The decline is the lender's, and the message must say so.
A repayment reminder
A transactional message with the amount, the date and the route to pay, kept clear of offers so it is not read as a promotion.
A bank demo just finished
A note to every attendee the same day, with the questions raised and the answer owner for each, recorded in the account.
A pilot with no activity
A message from the pilot owner to the sponsor asking what is blocking, since a handover inside the bank is the common reason.

Who it is for

This is written for these fintech companies.

  • Digital lending apps working with an NBFC or bank partner
  • Investment and wealth apps for first-time investors
  • Insurance technology platforms selling policies online
  • Credit score and personal finance apps
  • B2B software for banks, NBFCs and cooperative lenders
  • Business accounts and neobank-style apps run with a partner bank, for startups and small businesses
  • Accounting, billing and expense tools for small businesses with a finance element
  • KYC, collections and risk technology sold to regulated lenders

Before you decide

When this may not be the right fit.

  • You have no record of where users stop in onboarding, so a reminder would not know which step to name.
  • Users have not agreed to be messaged, and reminders would feel like pressure on someone already worried about money.
  • Your team plans to chase a bank sponsor with the same message each time, which adds nothing to a stalled pilot.

Before you decide

Agree the work. Know how to judge it.

Follow-up systems for fintech companies: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

Trace recent enquiries from arrival to the last recorded action. Include a won enquiry, an unsuitable one, and one that went quiet, with personal details removed for the initial discussion.

Make the scope clear

Agree who accepts each enquiry, what makes it qualified, and how ownership changes. Include a rule for missed replies and a clear reason for closing an enquiry.

Check the work in use

Pick an enquiry at random and ask the team to find its owner, latest conversation, and next action. Check that the record agrees with what actually happened.

Know when to change course

If no one has capacity to respond, assign that responsibility before buying more leads. Automation can support the owner, but it cannot replace an unresolved handover.

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 fintech companies. Anything missing is noted in the written scope, with who will supply it.

A list of stopped applications by step
An export of users who did not finish, with the step at which each stopped and the date. A rough export is acceptable. Without it, we write one general reminder, and a general reminder does not tell a person that their only missing item is the selfie.
The consent record for each contact
For users, the record of what they agreed to receive and through which channel; for institutions, the contacts you may write to. Partial records are acceptable. Without them, messages go only to people whose consent is certain, and the rest wait for your compliance head.
Notes on stalled bank pilots
A short note on each lender that went quiet: the last contact, the last question and who on your side knew them. A few lines each are acceptable. Without them, the touch plan sends a generic note to a committee that asked something specific.
A support person for reply handling
One member of support who will see the replies and answer questions about the app. A part-time role is acceptable. If nobody is named, replies pile up in a shared inbox, and a user who answered a reminder meets silence, which is worse than no reminder.
Your compliance head's contact limits
The limits your compliance head sets on how many messages a person may receive, at what times and through which channels, in writing. Existing policy is acceptable. Without them, we set cautious limits that you may find too tight, and the sequence is then trimmed.

How it works

How the follow up systems 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

    Find where the stopped applications sit

    We ask for the list of applications that stopped, split by the KYC or onboarding step, and the list of bank conversations that went quiet after a demo or a pilot start. You tell us which records hold consent to be contacted and which do not. This gives us the groups to write for and the groups to leave alone.

  2. 2

    Decide what counts as closed

    With sales and support we settle when a stopped user is treated as lost, when a bank is treated as paused and who may mark either. We write these rules before any message, so a user who has asked to stop is never contacted and a bank is not chased by three people.

  3. 3

    Write the messages that name the step

    For each stopping point, such as the selfie check, the bank link or the mandate, we write a message that says where the person stopped and what comes next in plain words, with the name of the app screen they will see. For a lender, we write notes that bring a fresh point, such as an answer to a question raised in the demo. Your compliance head reads every wording.

  4. 4

    Build the tasks and test them with staff

    We set up the reminders and tasks in your CRM or tool, so a caller sees the step, the last message and the lender's role. Your team sends test messages to colleagues and a test user goes through the whole path. You decide who owns each task and who covers when that person is away, and we adjust the sequence of messages where a staff member says a message would never be sent in that form, or that a lender would find it pushy.

  5. 5

    Hand over to support and the partnership team

    Support learns which user questions to answer and which to pass to the compliance head. The partnership team learns which stalled pilots need a call from a senior person. We write a short sheet of replies to the questions that arise, and you confirm who is on duty for the handover days.

  6. 6

    Compare the revived against the baseline

    We read the sequences against the counts recorded at the start: how many stopped users returned to finish, how many asked to stop and how many banks resumed a pilot. We look at which message got replies and which got complaints. You decide which messages to rewrite, which to retire and whether the contact rules need a tighter limit.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales process design, at stage 2, qualification. 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.

Is it acceptable to message users who have not finished?
Where the user has agreed to be contacted and the platform's current rules allow it. We build consent and opt-out into every sequence.
How many reminders is right?
Few enough that nobody complains. We set the cap with your team and read the unsubscribe and complaint signals.
What do we send a bank after a demo?
A short note that answers what each role asked, with the relevant document attached. Do not resend what was already shared.
What should we send a bank that has gone quiet after a pilot started?
Write to the sponsor and one other contact with a specific question, such as which team holds the test data. A general check-in is easy to ignore. Naming a blocker lets the sponsor pass it on, and the record shows who was asked.
Should the follow-up come from a person or from the system?
Use the system for the first reminders that name the step, and a person for anything about money, a rejection or a complaint. A user who was refused a loan should hear from a trained member of staff, not a template. For banks, every message after the first should be signed by a named person on your side, because committees answer people.
What do we do when a stopped user asks why they were refused?
Pass it to the person your compliance head names, with the reason the partner lender allows you to share. Do not improvise a reason from the system. We write a plain holding reply that says a person will respond, and we keep the question in the record, so the next message from marketing does not ignore it.
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.