You can remind GPS tracking customers about expiry dates without writing every notice individually. In Plaspy's My customers section, rules determine when a reminder is due and which channels it uses; templates supply the message and the relevant subscription details. Automation becomes useful when those two parts agree. An accurate date still needs wording that makes sense on the day the customer receives it.
Imagine preparing a friendly email: “Your service expires tomorrow.” It reads clearly, so you decide to reuse it a week before expiry, on the expiry date and a few days afterwards. The sentence worked for one particular conversation. Repeated at different points in the renewal cycle, it can confuse a customer even when their name and phone number are recorded correctly.
The challenge is not to write a longer reminder. It is to make the communication identify the service, establish its date and show what to do next. From there, it helps to understand what previewing, testing and reviewing a send actually demonstrate. They are different stages of a communication that will still need someone's attention when the customer replies.
The reminder calendar begins with the subscription
Expiry reminders use each subscription's Paid until date as their reference. A negative number of days means a notice before expiry, zero means the same day and a positive number means afterwards. Plaspy accepts values from −365 to 365, with a different day offset for each rule. You do not need a separate rule for every customer whose service expires on a different date.
Consider a hypothetical subscription with a Paid until date of November 12. A −7 rule corresponds to November 5, zero to November 12 and +2 to November 14. Assume the customer remains active, the subscription is not cancelled and November 14 still falls within its grace period. These are illustrative dates, not customer records or a recommended communication frequency for every business.
Reminders are scheduled for 8:00 a.m. in your account's time zone on the day specified by the rule. That does not mean the customer reads them at that time. If the customer operates in another time zone, it should not be described as their local morning without checking. The system's calendar and the moment a person attends to a message serve different purposes.
The problem with “expires tomorrow” now becomes clear: it does not correctly describe any of the three dates in our example. Automatic sending does not make the sentence appropriate. Wording built around the expiry date can preserve an understandable reference before, on and after that date, without depending on someone rewriting the sentence each morning to keep it accurate.
There is another timing limit to recognize. Creating a rule today does not send reminders for days that have already passed. A notice scheduled seven days before expiry cannot recover that opportunity when only three days remain. The rule organizes reminders that are due; it does not turn an earlier missed opportunity into a communication the customer received in advance.
The reference is also the subscription, rather than a single notice per customer. If one company has two services with the same expiry date, the rule can apply to both. An apparent duplicate should not be assessed solely by the recipient’s name: check which service each message identifies. That distinction makes a recognizable service description even more valuable to the customer.
Reusable wording needs details the customer recognizes
Instead of relying on “tomorrow,” you can build the message around the service and its date. As an example of wording, rather than a template ready to activate: “Hello, [name]. The expiry date for [service] is [date]. You can review the available options at [link], or contact us if you need clarification.” The brackets represent details that need to be completed correctly. They are not Plaspy's variable syntax.
The message has a limited purpose: identify a subscription and provide an understandable next action. Its service description needs to be recognizable to the recipient. If it uses an abbreviation understood only by your team, the customer may recognize the sender without knowing which renewal the notice concerns. Adding their name does not resolve an ambiguous description of the service.
Message templates can include customer and subscription variables, such as the description, amount with currency, expiry date and payment link. Those values are replaced when the message is sent. This lets you reuse the structure without placing one company's name, amount or date directly into fixed wording intended for many different customers.
Consider the next renewal as well. If Paid until changes from November 12 to December 12, a date typed into the fixed wording will still say November until someone corrects it. The expiry-date variable takes its value from the subscription when the message is sent. This matters even when the reminder calendar works correctly: scheduling a notice for the right day does not update a date left as a permanent part of its wording.
Personalization also means understanding what each value represents. For example, the subscription description variable falls back to the plan name when no separate subscription description exists. Knowing what the recipient will see in that case matters. The result may be technically correct but commercially unclear if the plan name only means something to the person who originally created it.
The next action deserves equal care. Providing a link does not establish that payment has taken place, and sending a reminder does not automatically charge the customer. The notice helps them recognize what needs attention and where to continue. If they have a question about the service or a payment already made, they need a way to raise it and someone able to respond.
Each channel carries the same purpose differently
Email provides a subject line and a formatted body. The subject should help the customer recognize the communication without opening it simply to discover what it concerns. The body can explain the service and date. According to the documentation, emails use your organization's name and replies go to your account email address. That inbox is therefore part of the follow-up you are offering.
SMS has different space and cost considerations. Plaspy permits up to 600 characters in its template and displays a counter; beyond 160 characters, it indicates how many SMS messages are charged. Your account needs SMS balance, while daily limits and destination availability can also matter. The decision is not to copy a long email wholesale into another channel, but to preserve what the recipient needs to understand the notice.
WhatsApp uses templates approved in your Meta WhatsApp Business account, configured in Plaspy. Fixed wording is prepared in Meta, and its parameters are connected to customer or subscription information. Saving a WhatsApp template is not enough to send a reminder. It must be selected for that message type, and WhatsApp must also be included in the relevant reminder rule.
Reviewing only the email wording therefore leaves part of the communication unchecked when WhatsApp is enabled too. The WhatsApp templates guide explains the relationship between approved wording and variables. One commercial purpose can be expressed in different formats, but the service, date and amount should retain the same meaning. A change made in one channel should not be assumed to have corrected the others.
Language needs similar attention. Plaspy has Spanish and English template versions; the customer receives messages in the language of their Plaspy user or, without an associated user, your account's language. Preparing both versions means checking that their action and conditions are equivalent. A translation can sound natural while omitting the date or contact route that made the original reminder useful.
A preview and a test answer different questions
A preview helps you read the notice as a communication: how the subject appears, what happens to the service name and whether the final action makes sense. In the Templates tab, Preview uses the editor's content with sample data, even when the content has not yet been saved. It is useful for examining the wording, but does not establish that those changes already belong to the saved configuration.
Test in that same tab sends the saved template, also using sample data. Email goes to your account's email address, while SMS or WhatsApp goes to its mobile phone number. Seeing a recent correction in Preview but receiving the previous wording in a test can therefore be consistent if the change has not been saved. You may be comparing two versions rather than two interpretations of the same text.
Precision matters here because the separate WhatsApp templates tab offers a different test. It lets you enter a test phone number and send the template with sample data even before saving it. The statement that testing uses saved content should not be extended to every test button in the platform. What matters is knowing which version the particular screen is testing.
None of these tests confirms that a specific customer's contact details are correct or that their subscription meets a reminder rule on a real date. A test examines the message sent to the test recipient. The calendar, customer record and service status still need their own checks. Receiving a well-presented message on your phone is useful evidence, but it is not a guarantee about every customer account.
Return to “expires tomorrow.” A preview can help you notice the phrase, but the relevant task is to assess its meaning on the planned dates and retain the correction in the appropriate version. Testing should resolve a concrete question about the communication. A message can arrive successfully and look good while still making an incorrect statement about when the service expires.
A send record does not preserve the whole conversation
After sending, Sent notifications lets you review the date, channel, recipient, customer, message type and result. You can distinguish reminders, payment received notices, service suspended notices and tests, as well as inspect failure reasons. This helps establish which attempt took place and which email address or phone number it targeted, instead of relying on someone's recollection of having sent it.
There is a significant limit when reviewing wording: Plaspy keeps the result of a send, not the message body. Opening the template today does not establish exactly what an earlier notice said if the template changed afterwards. The current version explains what is configured now. A record of an earlier send should not be presented as a copy of the wording delivered at that time.
If a customer questions a sentence in a notice, identify which communication they mean. The record's date, channel and recipient provide useful references for that conversation. A message retained by the recipient can supply the received wording. There is no need to reconstruct it from memory or automatically assign it the text currently visible in the editor.
A send result does not establish that the person read, understood or paid for the service either. Those are separate events. Keeping them distinct helps you address an inquiry without using “we already notified you” as if that resolved every question. The communication is useful when its recipient can recognize it and continue, rather than solely because a record exists.
Failures also have a practical consequence: a failed reminder is not retried. Correcting the contact details afterwards supports subsequent reminders that become due, but does not repeat that earlier send. The remaining customer conversation still needs consideration. Adding an address or running the reminder check again should not be assumed to turn the previous failed attempt into a completed communication.
Automation works better when someone understands its boundaries
A new account has no reminder rules already prepared. Alongside defining them, you need an enabled channel and the relevant customer details: an email address for email, and a phone number for SMS or WhatsApp. Inactive customers and cancelled subscriptions are excluded from these notices. A customer who has unsubscribed from your emails will not continue receiving them through that channel.
Subscription status can change the message as well. If the subscription is already suspended, Service suspended is used instead of the reminder. Suspension notices are provided by email and, when configured, WhatsApp; SMS is used for reminders. That distinction makes reviewing the relevant template types worthwhile, rather than treating every communication during the cycle as the same repeated email.
For access, My customers appears for the main account from fifty licensed devices, counting standard and professional licenses together, and permits saving information from one hundred. Between those levels, a preview is available without saving. The section is unavailable in the free version. The My customers guide explains those conditions and access for subusers.
Actions depend on privileges too. Viewing Settings does not automatically permit changing rules or sending tests, and consulting Sent notifications requires its corresponding permission. The person responsible for the message needs either the access appropriate to their role or coordination with someone authorized to perform the necessary checks. Automation does not remove that division of responsibility within the team.
Begin by reviewing a template alongside an example subscription and asking whether a customer could identify the service, date and next action at each planned point in the cycle. The cover illustrates that communication; it does not show real sends or guarantee timely payments. If the relationship between rules, channels and messages needs clarification, contact Plaspy with your particular case . That review helps prepare a coherent communication while leaving room to address what the customer has to say.
