A new customer’s first question is often simple: why is the television app asking for another payment? For a reseller, the answer depends on what that screen belongs to. A service subscription, a third-party player licence, and reseller panel access are separate arrangements. Treating them as one product creates avoidable confusion during onboarding. Prospective resellers who explore Golden OTT should build a clear explanation of those boundaries before offering setup help. The aim is a customer who knows what has been supplied, what remains their responsibility, and where each question belongs.

Define the item being sold

Start the handover with a plain description of the customer’s service entitlement, based on the actual package terms. Keep that description separate from the tools the reseller uses to manage accounts. A reseller dashboard is an administrative interface; it is not automatically the customer’s television player or a licence for that player. Explain the selected service duration, permitted use, and relevant activation process only when documented. Avoid phrases such as everything included unless the scope is genuinely explicit. If a customer has chosen an app independently, record that fact. It helps prevent a later app purchase from being mistaken for a charge imposed by the service provider.

Check application identity before discussing fees

Ask for the exact application name, developer, platform, and device model. A screenshot of a familiar icon alone is insufficient because similar names can describe unrelated products. Confirm that the installation route matches the device and that the current app terms have been read. A reseller should not describe a third-party application as their own software without evidence of that relationship. Nor should they promise that every player is free. The right explanation identifies the app’s role and directs licence questions to the relevant published terms or authorized support route. Customers can then decide whether that player is suitable before entering payment or account information.

Separate the quotation into understandable parts

A useful quote distinguishes the service charge from any hardware or software expense the customer may incur independently. Do not invent a player fee or add an assumed licence charge simply because another application required one. State what is included and which external costs require confirmation. Review Golden OTT reseller panel for the current reseller offering and clarify package units, account creation conditions, and support responsibilities before making downstream promises. If a third-party licence is outside the reseller package, make that boundary visible early. A customer should be able to explain the quote back in ordinary words without needing to understand the reseller’s internal terminology or panel balance.

Explain a licence prompt without guessing

Consider a hypothetical customer whose player opens but displays an application activation request before any service details are entered. That sequence points toward an app-side question, although the exact meaning still depends on the product’s documentation. Ask the customer to read the prompt and identify its issuer. Do not tell them to buy another service term as a reflex. If the prompt appears after login, record the stage and wording instead of assuming the same cause. The Golden OTT player licence and subscription guidance can support the broader distinction while the specific app’s terms settle its licence conditions. Keep the investigation focused on observable information and avoid requesting account secrets in an open chat.

Record enough to support the chosen setup

Maintain a minimal customer setup record containing the device model, operating system where relevant, selected player, version, and public setup guide used. Record whether a licence question was explained and whether the customer needs clarification from the app developer. These notes should describe the setup, not store passwords, private playlist strings, or payment-card details. Use a customer reference to connect support notes to an order held in an appropriately protected system. Keep access limited to people who need it for their work. A short accurate record is more useful than a large collection of screenshots that expose credentials and become outdated after every device change.

Make support responsibilities explicit

Tell customers which issues the reseller can investigate and which may require the service provider or application developer. For example, a licence receipt and an account renewal receipt should not be treated as interchangeable evidence. A player interface problem may need different information from a question about account expiry. Do not promise a developer response time, licence transfer, refund, or device entitlement that has not been verified. Where responsibility overlaps, help the customer assemble a concise report rather than sending them between parties without context. Include the device, app, symptom, and previous checks, while keeping private access values out of the shared report unless an authorized channel specifically requires them.

Prepare one clear answer for a customer who asks whether the app fee is compulsory. Explain that the answer depends on the chosen application and the supported alternatives, then verify those facts. Do not push a paid option by claiming that every alternative fails, and do not recommend an unsupported player simply to avoid discussing cost. The customer’s decision needs accurate options within the service’s documented setup requirements.

A simple handover can label receipts by issuer and purpose. One record might concern the subscription, while another concerns software licensing. Keep any internal reseller purchase separate from both. If a customer later changes televisions, revisit all applicable rules rather than promising that every entitlement transfers together. This approach preserves the distinction throughout the customer relationship, from the first quote through troubleshooting and renewal, instead of explaining it only after an unexpected prompt causes frustration.

Review the explanation before the next handover

After onboarding, ask whether the customer can identify the service account and the player separately. This is a comprehension check, not an invitation to collect more personal information. If they still describe the app purchase as buying television access, revise the explanation with a concrete example from their setup. Keep any reusable handover tied to the correct device and app, and review it when the published conditions change. A clear licence explanation reduces the chance of duplicate purchases, misplaced support requests, and unrealistic expectations. It also gives the reseller a disciplined basis for discussing costs: documented inclusions, separately confirmed software terms, and honest boundaries around what the reseller actually supplies. Recheck licence conditions when customers change players.