We designed NotPanel around two decisions: what to buy and what to do after buying. Customers need enough information to choose a service, then clear records of the order, the money and any follow-up. Those needs shape the catalog, average start-time display, order feedback, Wallet history and support experience.
This is our explanation of those product choices. The most useful way to judge them is to follow the customer journey: compare a service, inspect an order and find the next action when something needs attention.
Make the service choice specific
A platform name and a low starting price are not enough to select an order. Buyers need the exact service’s description, target requirements and quantity limits. A refill option on one service does not establish a refill option on another. The catalog puts those comparisons at the service level, where the purchase decision actually happens.
Consider a buyer choosing a scheduled order. They need to know both whether the service supports the requested schedule and when delivery is likely to begin. Those are different questions. Making both visible helps the buyer avoid choosing a service simply because a familiar word appears in its name.
Show the beginning of delivery as its own useful signal
“How long does it take?” often means “When will I see it start?” A completion estimate does not answer that question, especially for larger quantities or scheduled work. NotPanel’s average start-time display focuses on the beginning of delivery so customers can compare suitable services on that basis.
Read the timing estimate together with the available evidence and sample information. Buyers can use it alongside price and service conditions to choose a better fit for their schedule. The average start-time article explains the measurement, examples and distinctions for scheduled orders.
Let previous orders inform the next choice
A service description explains the offer. Feedback from eligible orders adds another perspective: how customers judged those purchases. NotPanel shows likes and dislikes with their counts, rather than asking buyers to treat an isolated percentage as the whole story.
These votes concern the service experience; they are separate from social-media likes sold in the catalog. Each eligible order can receive one final vote. Read the ratings guide for the eligibility rules and places where the feedback appears. We want the information to help a buyer ask a better question, not to replace their judgment with a score.
Keep the order and the money easy to check together
An order state answers a delivery question. A Wallet entry answers a money question. They should be easy to connect without treating them as the same thing. A payment sent still needs its deposit status checked; an amount owed as a refund is different from a credit already available to spend.
For example, a service’s catalog price may change after a purchase. The customer should check the accepted order charge in their own records, rather than trying to reconstruct that purchase from today’s catalog. An investigation should have an order reference and the related payment or Wallet record to work from.
Orders and Wallet history are available after sign-in. The refund guide explains ordinary-order cancellation and unresolved-order protection. The Refund Policy governs eligibility.
Make a retry understandable for the reseller
A connection can disappear after an order is accepted but before the caller sees the response. Creating a fresh order to find out what happened risks making a second purchase. NotPanel’s API supports a caller-supplied request ID so an integration can retry the same purchase and recover its original result under the documented rules.
That is a concrete benefit for the customer using the reseller’s storefront: an uncertain response has a recovery path. The order-creation documentation defines the contract; our API v3 guide explains it in context. The timeout guide covers what to do when a response is missing.
Give a question a place to be resolved
A customer should be able to ask about an order without assembling its history again in every message. Support tickets keep the order or payment reference, the question and subsequent replies together. That makes a follow-up more useful than opening another disconnected conversation.
Routine AI assistance helps the support team explain recorded information and service choices. Questions involving a payment mismatch, an account problem or a disputed result need the appropriate human review. Our support guide explains the difference between a first answer and resolution, plus what evidence helps.
We will keep improving how clearly NotPanel answers those questions. Current features and written policies should carry the explanation; a buyer should not need a promise about a future release to understand the purchase they are making today.
