Organizing GPS tracking customers starts with distinguishing who buys the service, what they pay for and which devices it covers. In Plaspy's My customers section, those questions correspond to the customer, their subscriptions and the items within each subscription. Keeping those relationships clear makes an account understandable without relying on the person who originally sold the service to remember every detail.
Imagine covering for a colleague for a few days. A business contacts you: “We received a reminder, but we already paid.” You recognize the company and one of its vehicles. You still do not know whether that payment covered the entire fleet, a particular renewal or another service. Replying from the most recent chat message would mean filling the gaps with an assumption.
We will use a hypothetical business with three Plaspy devices. Two belong to a monthly subscription and the third belongs to an annual one. This is not an actual customer account or a pricing recommendation. It provides a way to examine which information should stay connected so that an authorized colleague can understand the relationship and give a specific answer.
The customer remains the same when the contact changes
Running a tracking business can mean speaking to a driver about a vehicle, an administrator about a payment and an owner about renewal. Those conversations do not necessarily represent three different customers. First identify the person or business buying your service, then understand the role of the person contacting you about it.
The Customers record brings together first and last names, company name, identification details and contact information. First and last names are required; the other fields serve particular purposes. A company name helps identify the business, while email and phone fields provide destinations for the corresponding communications. Saving a number because it was the latest one to contact you does not establish that it should receive billing notices.
In our example, the driver of one van might be able to explain a vehicle issue, while someone else handles renewals. The recorded information should reflect that arrangement. There is no need to invent a different customer identity for every conversation, or to assume that anyone who knows the vehicle can answer every commercial question about the account.
Customer search can use personal and business details as well as information about subscription items: device name or code, IMEI, phone number or external identifier. This is helpful when a conversation begins with a particular vehicle. Finding the record gives you access to the commercial context; you still need to establish which service is involved.
You can also associate a Plaspy user when the customer uses a subuser of your account. That optional association has a specific purpose: their devices are proposed when adding a plan, and customer messages use that user's language. Without an associated user, messages use your account's language. A communication destination and a platform login serve different roles.
Returning to the opening conversation, we now know which customer the inquiry concerns. That connection avoids searching only through messages from someone who might have changed jobs. The remaining question is which part of the business relationship the company is asking about.
One business can have more than one subscription status
Subscriptions in My customers describe what a customer pays you for: the service, price, period, Paid until date and covered items. A customer can have several subscriptions. Calling the whole account “up to date” can therefore say more than the evidence supports if you have only examined one service.
Suppose the monthly subscription covering the first two devices is Active, while the annual subscription for the third is Past due and still within its grace period. There is no contradiction. They are separate commitments with their own dates. The business could have paid its monthly renewal while still needing to address the annual one, even though both are managed under the same customer.
The customer's Contracted plans section displays their subscriptions with status and expiry date. A colleague covering customer inquiries can use that view to identify the relevant service. The company name leads to the overall relationship; the subscription description and items help identify the particular agreement within it.
The description deserves care because it also appears in messages and on the payment page. Wording understood only by the original salesperson leaves the next colleague having to reconstruct its meaning. A description the customer recognizes makes it easier to discuss the specific renewal without asking them to decode an internal abbreviation.
You do not need a separate customer record for every vehicle to keep that distinction. In our example, the first two devices share a subscription and the third has another. Their organization follows the services agreed with the customer. The same device can only belong to one subscription that has not been cancelled, which also matters when reviewing those associations.
If the business asks why a notice arrived after payment, begin by identifying the subscription mentioned in the notice and the one associated with the payment. They could concern different services. Incorrect information or a payment awaiting review are other possibilities. A clear structure helps investigate them without deciding in advance which explanation must be true.
Even a matching amount may leave the question unresolved. Suppose two subscriptions belonging to that customer have the same price, and a payment receipt names the company without a reference that distinguishes the services. The amount alone does not establish which subscription it covers. Before recording or interpreting the payment, its connection to the specific service needs to be clarified. Otherwise, apparently consistent information could close an enquiry that remains unresolved. This does not assume that Plaspy can infer the intended subscription from the receipt.
A date and a payment tell different parts of the story
An understandable account needs more than an amount. Paid until identifies the last day covered by a subscription. Start date records when the service began, but it does not replace the date used to manage expiry. Confusing the two can make an account appear newer or further behind than the relevant records establish.
In the three-device example, each subscription has its own date. Sharing a customer does not require both services to expire on the same day. When your colleague finds a payment, they need to connect it to the stated subscription and examine its effect on that subscription's validity. The existence of a payment record does not describe the status of every service.
The Payments documentation distinguishes payments awaiting confirmation. A Pending payment does not renew the subscription while it remains pending. With the appropriate privileges, a payment can also be recorded without renewal. “There is a payment” and “the paid-through date has advanced” therefore need to be checked separately rather than treated as equivalent statements.
Payment details show the subscription, amount, method, reference and previous and new dates where applicable. Those references support an answer about the particular transaction. They do not automatically confirm a screenshot sent by the customer, or justify applying an amount to another service simply because both belong to the same company.
Subscription statuses have defined meanings too. Active means that Paid until is today or a future date. Past due covers the period after that date while grace days remain. Suspended follows the end of the grace period without payment. These labels describe the subscription; they do not diagnose the physical condition of a GPS device.
A useful reply identifies which renewal has been located and which part still needs examination, rather than assigning one label to the customer as a whole. That precision also helps divide the work. A question about a commercial record and an inquiry about a device may require different information, even when they arrive in the same conversation.
Three devices do not mean three administrative records
Understanding the account structure also helps you assess capacity as the business grows. My customers counts records: one for each active customer, one for each subscription that is not cancelled and one for each item in those subscriptions. Price plans created in Settings do not consume those records.
Our example uses six: one active customer, two subscriptions that are not cancelled and three items. The calculation is 1 + 2 + 3 = 6. This is an administrative count for the example, rather than the number of licenses that company requires or the price it should pay. Treating those quantities as interchangeable would produce an incorrect capacity estimate.
Adding a fourth device as an item in an existing subscription adds one record. Adding another active customer with one subscription and one device adds three records. Both changes could increase the number of included devices by one, but the additional commercial structure is different. The record count reflects that difference.
That distinction matters when comparing many small customers with a smaller number of larger fleets. Two businesses with the same device count can have different numbers of customer records and subscriptions. Estimating administrative capacity requires considering that composition, rather than only looking at how many vehicles appear on the Map.
The My customers guide specifies ten records per standard license and fifty per professional license. For example, one hundred standard licenses provide one thousand records. That does not mean room for one thousand customers together with all their subscriptions and devices. The other components of each customer relationship need space as well.
The Customers, plans and items box shows usage, the limit and remaining records. Its label could suggest the price plans configured in Settings, but the documented calculation counts subscriptions and excludes those price plans. Understanding the components prevents reading the counter as a simple number of people or a device quota.
Updating a contact should preserve the account's meaning
Over time, the people handling payments change, vehicles are added and service arrangements are revised. The account should remain understandable through those changes. The aim is to preserve the information needed to identify the customer and explain their current subscriptions, rather than to save every conversation that has taken place.
If the company's administrator provides a new email address, updating the relevant destination is different from ending the commercial relationship. Clearing Active on the customer has broader consequences: the customer disappears from the normal list and no longer receives reminders or suspension notices. Their subscriptions nevertheless remain in force and expire as usual.
That distinction matters when someone tries to tidy the list by removing a contact who no longer works at the company. Hiding the customer does not cancel the company's services. You could preserve their expiry dates while interrupting the notices you expected to send. The decision needs to reflect the customer relationship, rather than only the departure of a particular person.
Notes and tags help retain additional context. A tag might identify the contract or a reference your team uses; subscriptions and their items can carry their own information too. Put a reference where it explains something. A condition belonging to one particular service should not be mixed into general account information in a way that makes it appear applicable to every subscription.
A note also cannot substitute for an action that requires configuration. Writing “send a reminder before expiry” does not create a sending rule. Expiry reminders need their rules and channels configured, and a new account has no reminder rules already in place. The information describing an agreement and the configuration acting on it need to be consistent.
In the opening situation, your colleague can continue the conversation because they understand where each part of the relationship is represented. They recognize the business, find the service, read its date and examine the relevant payment. If information is missing, they can identify what needs clarification instead of rebuilding the entire relationship from disconnected messages.
A well-organized account can be explained to someone else
One way to assess your organization is to choose an account with several services and ask an authorized colleague to explain it from the available information. They should be able to identify the customer, describe what each subscription covers and find the corresponding dates. If every question requires the original salesperson, useful context may still be missing from the record.
This does not mean filling every field simply because it exists. A detail is useful when it identifies the relationship, directs a communication or explains a condition. An unused reference will not resolve an ambiguous description. A longer description will not correct a device associated with the wrong subscription either. The goal is information that helps someone answer the actual customer inquiry.
Before bringing that structure into Plaspy, consider the access available to your account. The My customers menu appears for the main account from fifty licensed devices, counting standard and professional licenses together. Saving information requires at least one hundred. Between those levels, you can explore the preview, but changes are not saved. The section is unavailable in the free version.
Administrator subusers have the same access as the main account. Standard subusers must belong to a My customers user group and can only use the pages and actions that group permits. A colleague able to consult a customer record does not necessarily have permission to change subscriptions or confirm payments. The division of responsibilities should take those differences into account.
Start with the company whose services currently generate the most confusion and examine its structure using the Customers guide. If you need help representing several services within one relationship, contact Plaspy with that particular situation . The useful question is how to organize the agreements you actually have, rather than how to populate a form for its own sake.
The next time a customer says “we already paid,” you will have a starting point for a more precise conversation. You can identify the payment and the service it concerns, recognize what still needs checking and explain the next action. The account becomes less dependent on one person's memory and more useful as a reference the team can consult.
