Skip to content
GullySales

Payment service providers · Follow up systems

Chase the stalled merchant with a reason, not a reminder.

A follow-up system for a payment service provider is the set of messages, calls and tasks that move a merchant from a signed form to a first live payment. GullySales writes the sequence for each stage and sets it up so nobody is left waiting without a reason.

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 payment service providers

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

  • “The silence after signup is where merchants are lost”

    Once the form is signed, the field executive moves on and the activation team waits for documents. The merchant hears nothing and concludes that the provider is not serious.

  • “A reminder that repeats itself is ignored”

    A message asking for pending documents sent in the same words again and again is read once. A follow-up that names the exact missing document and how to send it is acted on.

  • “The right channel depends on the merchant”

    A shop owner answers a call or a chat message, while a developer answers an email with a clear technical step. A single channel for every merchant leaves half of them unreached.

  • “A merchant who has not transacted needs a nudge after go-live”

    An active account with no payments is still a lost merchant. The follow-up has to continue after activation until the first payment is made.

What we do

What we deliver for payment service providers.

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

  1. Stage-by-stage follow-up sequence

    Messages and call prompts for each stage from documents to first payment, each naming the next step.

    Result: Each stage has a ready follow-up with a clear ask.

  2. Missing-document messages

    Short messages that name the exact document needed and show how to send it.

    Result: A merchant knows precisely what is pending.

  3. Developer follow-up track

    Emails with sandbox steps and common errors for merchants waiting on integration.

    Result: A developer receives help at the point of difficulty.

  4. First-payment nudge

    A message and a call prompt for activated merchants who have not yet taken a payment.

    Result: Activated merchants without payments are contacted.

  5. Owner and reminder rules

    A rule for who follows up, when a task is raised and when it moves to a manager.

    Result: Every waiting merchant has an owner and a reminder.

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

The moments in a merchant's journey where a message or call moves it forward.

Missing document at review
Name the exact paper that is missing, such as the bank proof page. A general request for documents goes unanswered.
Signed up, not integrated
A message for the developer with the documentation link and a contact. Offer a call only if they ask.
Approved, no first payment
A short note with the steps to take a test payment. Record the date so the executive can call.
Rejected at review
Tell the merchant why, to the extent policy allows, and what to correct. Record the reason for later.
Settlement query open
Send a status on the ticket. A merchant waiting for money who hears nothing starts complaining in public.
Merchant with falling volume
Note the drop in the record and have a person call. Do not send a promotional message to someone with a problem.

Who it is for

This is written for these payment service providers.

  • Payment aggregators and gateways for online sellers and platforms
  • UPI QR, soundbox and card machine providers for shops and restaurants
  • Payment link and invoice collection providers for small sellers
  • Merchant acquiring resellers and sales partners
  • Payout and vendor payment platforms for marketplaces and businesses
  • Bill payment and recurring collection providers for fees and subscriptions
  • Cross-border payment providers for exporters and freelancers
  • Providers that serve a single sector, such as schools, clinics or logistics

Before you decide

When this may not be the right fit.

  • Your onboarding team cannot answer the replies a follow-up would produce.
  • Merchants have not agreed to messages on the channel you would use.
  • You do not know where merchants stall, so you would chase everyone with the same reminder.

Before you decide

Agree the work. Know how to judge it.

Follow-up systems for payment service providers: 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 payment service providers. Anything missing is noted in the written scope, with who will supply it.

The documents list for every merchant type
Missing-document messages must name the right paper for a proprietorship, a company or a trust. Your onboarding checklist is acceptable in any state. If it differs by person, we write to the strictest version and flag the conflict. If documents differ by state or by the bank you settle with, tell us which rule applies where, so a merchant is not asked for a paper that is not needed.
Merchant contact consent records
Reminders need permission to contact a number on the channel used. Tell us what the signup form says and who holds the record. When consent is unclear, messages go only to those who reached out themselves.
A named owner for developer support
Stalled integrations need an engineer or support person who can answer technical questions. Name one. Without that person, developer follow-up becomes the same reminder repeated and the track is left out. This person should also know which integration errors repeat, so the developer messages mention the actual error and not a generic prompt.
Your rule for rejected applications
Only you can decide what a rejected merchant hears, and whether they may reapply. A short written line is enough. If it is missing, rejected merchants receive no message or the wrong one, and your executives answer angry calls.
Access to the current reminder tool
If reminders are sent from a tool today, we need to see what is configured. A screen-share is fine. Without it, new sequences may duplicate old messages and a merchant receives two reminders for the same paper. Include the screen where reminders are paused or stopped, because a merchant who has already replied must not receive another request.

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

    Read what happens after each signup

    We take a sample of signups from your register and trace what each received afterwards: a call, a message, nothing. You tell us which stage of the merchant's journey goes quietest. What exists after this is a plain list of the quiet gaps.

  2. 2

    Decide who follows up at each stage

    A missing document is chased by onboarding, a stalled integration by the developer-support person, a merchant who never transacted by the field executive. We write these owners into the register. You approve each owner, because a message with no owner is ignored. For merchants who are live but silent, the field executive who signed them is the natural owner, and we write that in rather than leaving it to the shared inbox.

  3. 3

    Write the reason-based messages

    Each message names what the merchant is waiting for: the cancelled cheque, the shop licence, the API key. We write them in the language your merchants use, with your onboarding staff checking for errors. A message that only says please respond is not written. We keep each message to one request, and where the merchant needs a form we give the link in the same message so no second search is needed.

  4. 4

    Set closing rules for the unreachable

    You decide when a merchant is moved to closed, and what the final message says. We write the rule down, including what happens if a rejected merchant asks to reapply. The register then holds a reason for every closure, not a silent drop. We also write what a field executive says on the phone when a merchant has gone quiet after go-live, so the call and the message do not contradict each other.

  5. 5

    Test the tasks with live staff

    We run several real merchants through the tasks and watch whether staff see them, act on them and record the outcome. Wrong owners and duplicate reminders are corrected before the full team is handed the system. We note any message that arrives out of order, so the register shows the merchant's real stage.

  6. 6

    Compare silent merchants against first payments

    We read the stage-by-stage figures against the starting ones: documents received, integrations passed, first payments made. You decide which messages to rewrite and which stages need a person to call instead.

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.

Should follow-up be automated?
Reminders and task creation can be automated. The conversation with a stuck merchant should be human, because the reason is specific. We set up the first and train for the second.
What if a merchant is rejected at review?
The follow-up changes. The merchant is told the outcome in plain words and, where your rules allow, what could be corrected. Your risk and compliance teams decide what is said.
Do you set the timing of messages?
We recommend a rhythm and you confirm it. The gaps depend on your onboarding process and your merchants, so we record what works rather than promise a schedule.
What if a merchant ignores every reminder?
Stop after the sequence you set and mark the stall reason. Repeating the same message trains the merchant to ignore you. Send a different note only when something changes, such as a new integration or a changed document requirement.
Can we automate all merchant follow-up?
No. Missing-document and first-payment reminders can be automated safely, because they follow a clear trigger. A merchant who is hesitating about charges, or whose integration is failing, needs a person. We mark which tasks are automatic and which create a task for a named staff member. You decide the line. The register records every message sent, so a field executive can see what the merchant already received before calling.
Who decides how often a merchant is reminded?
You do. We recommend the order of messages and the trigger for each, but the spacing is set in your tool after you have talked with onboarding and field staff. We do not fix a schedule on this page, because merchants differ and your team knows when they are reachable. The rule we do insist on is that every reminder names a specific missing item and has an owner.
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.