A payment reminder can help your customer remember a GPS service renewal and find a way to act on it. In Plaspy’s My customers, you can connect that communication to a subscription and its Paid until date. Making it useful requires accurate information and a prepared message. Whether the customer pays on time remains an outcome to check, rather than an assured consequence of saving a name and a date.
Think about deciding to organize your renewals. You know the customers, but their dates are scattered across files, and you would like to stop writing every notice from scratch. There is also a reasonable question: is it worth starting before you have organized every detail?
You can begin with a manageable part of your customer base. What matters is distinguishing between creating a record, preparing a useful reminder and evaluating what happened afterwards. Those are different stages. Keeping them clear lets you start simply while giving the automation a realistic purpose.
A renewal reminder opens a conversation
For one customer, a notice may bring an outstanding service renewal back to mind. For another, it may raise a question about the amount or who handles payments within their company. The same communication can meet different circumstances. Assuming everyone had forgotten makes it harder to hear what each person needs.
Give the reminder a concrete purpose: identify the renewal and make the next action understandable. The person might pay, request clarification or tell you about a payment already made. Each response provides information for continuing the business relationship. A useful conversation does not have to be described as a payment the message produced.
Your team can also gain a shared reference for which service needed renewing. When dates exist only in the salesperson’s memory, covering their work becomes difficult. Bringing the relevant information together helps prepare communication more consistently. Better organization has value before you can attribute an improvement in payment timeliness to it.
This sets a different expectation for the first use. Rather than hoping a message will resolve every overdue account, ask whether the customer recognizes the renewal and can understand how to continue. A disagreement about the service, difficulty paying and an incorrect contact address call for different responses. Sending more notices without understanding the case may leave the actual obstacle untouched.
A late reply does not, by itself, establish a lack of interest. It offers a chance to clarify this particular service. The conversation might confirm the date, reveal an incorrect record or identify a condition requiring review. The reminder can open that contact, while someone on your team remains responsible for responding.
Research supports a possibility, rather than a universal promise
There are reasons to investigate reminders, but it is useful to read what was actually studied. In Remembering to Pay?, by Ximena Cadena and Antoinette Schoar , a field experiment with a microfinance lender in Uganda found improvements in payment behavior through SMS reminders. The experiment compared that treatment with financial incentives and a control group. Its setting was loan repayment, with particular participants and conditions.
A contrasting result matters too. An EfD working paper about water service payments in Nairobi , published in 2024, reports that SMS reminders did not improve payments on average. Its abstract describes a randomized trial involving 50,000 residential customers. That finding encourages attention to context rather than treating any message as a sufficient solution.
Together, these papers describe different outcomes in different sectors. They do not allow a GPS tracking reseller to assign the Ugandan result to their own customer base. Nor does the Nairobi result establish that reminders never help. Neither paper independently explains why each of your customers pays late.
For a reseller, the useful conclusion is closer to everyday work: prepare a reasonable communication and examine its outcome. You can use the idea of reminding someone about a date without importing another sector’s commercial promise. This preserves the research’s value while avoiding an advertised success rate that your business has not established.
It also helps frame questions when the result is disappointing. Did the customer understand the service? Was there a question about the agreement? Was the message directed to the intended contact? Those questions can guide a review without assuming any one of them explains an entire customer base. Research informs judgment; your records and conversations establish the circumstances of the actual case.
Starting with fewer details still means understanding each one
The Customers help states that First name and Last name are required to create a customer record. That makes the initial information requirement smaller. Paid until belongs to the subscription, alongside its service, price and period. “A name and a date” can express a simple organizing idea, but it compresses decisions that should remain identifiable.
A name helps recognize the customer within their context. A date becomes useful when you know which service it covers and where it came from. Copying the last date in a chat without establishing which renewal it described can produce a record that looks complete but is unreliable for the next communication. Adding unrelated fields does not resolve that uncertainty.
The Subscriptions documentation distinguishes Start date from Paid until. Both initially use today’s date when a subscription is created. That starting value does not replace checking which day the actual service is paid through. Before using it in a business communication, establish that it represents the agreement you are recording.
Sending notices also requires the appropriate contact details and a prepared channel. Email uses the customer’s email address; SMS and WhatsApp use their phone number. Entering a name does not provide those destinations. A new account also has no reminder rules prepared. Creating a simple customer record and preparing a send are different stages of the work.
You can keep that simplicity without collecting every possible detail. Ask which information identifies the relationship, represents the service or directs the notice. When a date is unclear, resolving it is more useful than writing a long note around the uncertainty. The article on organizing GPS customers explains how customer records and their services fit together.
A payment appearing after a notice does not establish its cause
Imagine an entirely fictional situation, with every time expressed in the same time zone. A customer executes a bank transfer at 07:50. A reminder goes out at 08:00, and your team verifies that transaction at 08:20. Assume you know those times from independently checked references. We are not assuming Plaspy automatically obtains the execution time of a transfer at any bank.
Looking only at when your team checked the payment could tempt you to credit the notice. Yet the transfer had already been executed ten minutes before that message. The 08:00 reminder did not initiate an operation performed at 07:50. An earlier communication might have influenced the customer; this example does not examine its effect.
The practical difference lies in explaining the outcome. “We verified the payment after the reminder” preserves the observed sequence. “The customer paid because of that reminder” adds a cause contradicted by the sequence in this example. The first statement describes your team’s work; the second claims to explain the customer’s decision.
Now change one condition of this example: the transfer is executed at 08:10, after the 08:00 message, and verified at 08:20. That chronology allows the notice to have played a part, but still does not prove it did. The customer could have planned to pay then for another reason. Coming later in time is compatible with an influence, without being sufficient evidence of it.
This distinction is useful when evaluating automation. You can recognize payments made after communications and respond to customers without crediting each notice with all the money received afterwards. You do not have to deny that the message could have helped. Describe what you know and which explanation still needs evidence.
The daily review of a transaction serves another purpose: checking the payment and its relationship to the renewal. The article on reviewing outstanding GPS customer payments develops that task. Here, the question is different: what can the observed sequence tell you about the reminder’s effect?
Getting paid eventually and getting paid on time are different outcomes
Consider another invented example, separate from the first. There are four subscriptions with identified renewals. In one period, all four are eventually paid: two by their due dates and two afterwards. In another period, the same four renewals are paid by their due dates. We assume the services remain comparable and that you can verify payment timing against each relevant due date.
If you count only renewals that eventually received payment, the result is four in each period. Under that measure, nothing changed. If your question concerns timeliness, the result differs: there were two payments by the due date before, compared with four later. Preserving the outcome you intended to examine makes that difference visible.
To keep the assumptions clear, we are counting renewals whose corresponding full payment has been checked. A payment attempt or a partial amount that does not cover a renewal does not become the same outcome for convenience. This does not propose a procedure for processing partial payments; it defines what the four payments in our comparison mean. Without that definition, two people could use the same number to count different events.
The reference for timeliness must remain clear as well. Changing the date used to evaluate an earlier period can reclassify the outcome without changing when anyone actually paid. Distinguish a legitimate record correction from the due date of the agreement being examined. Evaluating that period requires knowing which date you are comparing the transaction against. The example assumes you know it; today’s displayed date is not automatically evidence of every earlier condition.
This example does not report actual customers’ behavior or demonstrate an improvement caused by reminders. It is a small comparison between fictional periods. Even if you observed it in your business, other circumstances might have changed. Its purpose is to explain why the outcome needs defining before a tool is described as effective.
A consistent observation period matters too. Waiting for late payments in the first period, but looking only on the due date in the second, does not give both the same opportunity to show eventual payment. Timeliness requires the relevant payment and due dates. Discussing later payments also requires retaining how long you observed them.
This avoids two opposite mistakes. Equal totals of paid renewals can conceal a change in when they were paid. At the same time, more timely payments do not automatically explain what produced that change. You can recognize the difference and leave its cause open while still valuing carefully documented work.
The Ugandan experiment used random assignment and a control group. Our four-renewal example does not make that comparison between groups: it observes two periods for the same services. If an agreement was clarified or payment conditions changed at the same time, the before-and-after comparison does not separate those changes from a possible reminder effect. You can record an improvement in timeliness without turning that observation into a trial result. This methodological difference helps put research to use carefully: its conclusion does not automatically give the same evidential strength to every comparison you later make within your own customer base.
Plaspy brings together customers, subscriptions, payments and notifications in their respective sections. These examples propose a way of reasoning from checked references. They do not describe a causal attribution report or an automatic reminder-effectiveness metric available in the platform. Information becomes useful when it answers the actual question being asked.
A useful first experience makes the learning clear
Beginning with a small part of your customer base can help check whether the information and communication make sense. You might discover a date needing clarification, an unclear service description or a question nobody knew who should answer. Those findings can already improve preparation. A group chosen for convenience, however, does not necessarily represent every customer you serve.
Before expanding that experience, decide what is worth retaining: a communication the customer recognizes, a clarified date or a question directed to a responsible person. If the goal is better payment timeliness, you still need to observe that outcome consistently. The number of notices prepared describes your team’s activity; it does not independently explain what happened to payments.
The expiry reminder rules organize sends around the subscription and configured channels. Preparing that relationship allows communication to be reused while your team handles the questions it raises. The article on reminders customers understand develops the calendar and wording. There is no need to reproduce every configuration screen here.
Channels have their own conditions. SMS consumes account balance, and WhatsApp requires your WhatsApp Business account to be configured with the appropriate Meta template. The customer still needs to make the payment through the relevant method. Sending a link is not an automatic recurring charge to their card.
Saving information in My customers requires at least one hundred licensed devices, adding Standard and Professional. The menu appears from fifty; below one hundred, the section is a preview without saving. The free version is excluded. The My customers guide also explains access according to user privileges.
The cover and video are illustrative. The idea of beginning with simple information still has value when that information describes a service and supports a prepared communication. To discuss a first use, contact Plaspy with an account of how you manage dates and notices today . A concrete conversation helps identify what you can organize and which outcome you will need to check within your own customer base.
