> For the complete documentation index, see [llms.txt](https://tereatv.gitbook.io/tereatv-official-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tereatv.gitbook.io/tereatv-official-documentation/docs/tereatv-reseller-panel-checklist.md). # TereaTV Reseller Panel Checklist: Credits, Support and a 7-Day Pilot Verify the official TereaTV reseller route, understand panel responsibilities and test credits, support, privacy and renewals before scaling. If you are researching a **TereaTV reseller panel**, begin with process verification rather than a large credit purchase. A panel can make customer creation and renewal more efficient, but it also moves real operational responsibility to the reseller: access control, credit reconciliation, support triage, privacy, and continuity. > **Disclosure:** This is an owner-published TereaTV guide, not an independent review. It was prepared with AI assistance and reviewed for link accuracy and unsupported claims on 4 September 2026. It does not promise earnings, licensing status, uptime, or a guaranteed outcome. ### Start with the official route Open the [TereaTV reseller information page](https://tereatv.net/reseller) directly and confirm that your browser remains on the expected domain. Do not rely on a look-alike domain, a shortened link, or a private message as the only evidence that a seller represents TereaTV. Before sharing payment or customer information, record: * the exact domain and HTTPS status; * the date you reviewed the offer; * the contact and support route shown on the official page; * the current credit, refund, and expiration terms; * any territory or marketing restrictions. If a term is unclear, ask for a written answer before you buy credits. ### What a reseller team must own A reseller panel is not just an affiliate dashboard. Depending on the current offer, a reseller may become responsible for creating lines, selecting durations, monitoring expiration dates, handling renewals, and responding to first-line support questions. Define one owner for each function: 1. **Sales and eligibility:** confirms what the customer is requesting and avoids promises that are not written in the current offer. 2. **Provisioning:** creates or renews only after the order record is complete. 3. **Support triage:** records the device, app, error, time, and troubleshooting already attempted. 4. **Credit reconciliation:** compares the expected credit balance with the balance shown after every action. 5. **Access management:** grants the minimum access required and removes access when a team member leaves. Small teams can combine roles, but they should not leave responsibilities undefined. ### Seven-day pilot before scaling Ask whether a limited test is permitted. Use only test data allowed by the provider and avoid using a real customer as the first experiment. #### Day 1 — Identity and terms Verify the official route, current terms, support path, credit rules, and refund conditions. Save a dated record of what you checked. #### Day 2 — Roles and access List every operator who needs panel access. Prefer individual logins where available and record how access can be revoked. #### Day 3 — Creation workflow Document each permitted test step from selecting a package through confirming the resulting duration and credit change. #### Day 4 — Support evidence Create a sample support note with no unnecessary personal data. Include the time, device type, app, exact error wording, and one-change troubleshooting results. #### Day 5 — Renewal exceptions Write down what the team should do after an early renewal, late renewal, duplicate action, or wrong duration. Confirm whether history or audit records are visible. #### Day 6 — Reconciliation Compare opening credits, recorded actions, expected deductions, and the closing balance. Pause if the difference cannot be explained. #### Day 7 — Go or no-go Review open support questions, access gaps, discrepancies, time per task, and customer-facing wording. Scale only when the process can be repeated consistently. ### Credit questions that need written answers Do not assume that “one credit” has the same meaning across every package or duration. Ask: * What does one credit create? * Do unused credits expire? * Are credits refundable or transferable? * Is there a minimum purchase or mandatory top-up? * What happens to active customers if the reseller panel is suspended? * Can an incorrect action be reversed? * Which events appear in the panel history? Avoid guaranteed-income claims. Revenue can be affected by demand, acquisition costs, refunds, support time, taxes, provider terms, and other factors that no panel can guarantee. ### Privacy and account safety Collect only information needed for the current task. Never publish customer credentials in a ticket, screenshot, article, or shared document. Blur identifiers before using a screenshot for training, and do not reuse customer passwords. Keep these records separate: * order and payment record; * panel action record; * support note; * renewal date; * escalation reference. If the panel supports individual roles or logs, use them. If it does not, reduce the number of people with access and maintain an external action record. ### Support triage template ``` Case ID: Date and time: Device type: Player or app: Stage of failure: open / login / library / playback / renewal Exact error wording: One change tested: Result: Escalation reference: Next follow-up: ``` Do not place a password, full payment detail, or unnecessary personal information in this note. ### Related verification resources * The longer [25-point IPTV reseller panel due-diligence guide](https://bestiptvservice2023.blogspot.com/2026/09/iptv-reseller-panel-due-diligence-25-checks.html) covers comparisons across reseller offers. * The [NextViewGuide research hub](https://nextviewguide-2026.amr-abdelnaser91.chatgpt.site/) provides neutral navigation and owner-network disclosure. * Review the TereaTV account-safety and official-domain pages in this documentation before relying on a new contact route. ### Decision rule Proceed only when the official route, written terms, credit logic, role access, support escalation, privacy handling, and reconciliation record are all clear. If one of those elements is missing, keep the pilot small or stop until the gap is resolved. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://tereatv.gitbook.io/tereatv-official-documentation/docs/tereatv-reseller-panel-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.