{"id":127,"date":"2026-10-30T08:15:00","date_gmt":"2026-10-30T02:45:00","guid":{"rendered":"https:\/\/ispsquare.com\/blog\/?p=127"},"modified":"2026-10-30T08:15:00","modified_gmt":"2026-10-30T02:45:00","slug":"switch-isp-as-lco","status":"publish","type":"post","link":"https:\/\/ispsquare.com\/blog\/switch-isp-as-lco\/","title":{"rendered":"How to Switch ISP as an LCO Without Losing Records"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Learn how to switch isp as lco without losing customer history, KYC files or control of your daily collections. The safe method is to treat the change as a data and operations project: take a clean snapshot, agree the new ISP process, test a small group, then move customers in batches.<\/p>\n\n\n\n<aside class=\"ap-card\" aria-label=\"ISP Square Growth\">\n<span class=\"ap-card__badge\">Best for multi-ISP<\/span>\n<div class=\"ap-card__body\"><p class=\"ap-card__name\">ISP Square Growth<\/p><p class=\"ap-card__best\">Best for operators reselling several ISPs<\/p><ul class=\"ap-card__features\"><li>3 ISP accounts<\/li><li>Up to 2,000 customers<\/li><li>50 partners and sub-partners<\/li><li>5 staff logins<\/li><li>Own retail prices and commission per level<\/li><li>Everything in Starter<\/li><\/ul><\/div>\n<div class=\"ap-card__side\"><p class=\"ap-card__price\">\u20b9699\/month (\u20b96,990\/year) <small><\/small><\/p><a class=\"ap-card__btn\" href=\"https:\/\/ispsquare.com\/#pricing\">See plans \u2192<\/a><\/div>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Why operators add or change ISPs<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You may want a second ISP for a new pocket, a different plan mix, or more choice at your shop. Sometimes the right decision is not a full replacement. You can keep the existing ISP for active customers and add another one for new connections or selected areas.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The important question is not only, \u201cWhich ISP has the best plan?\u201d It is also, \u201cWhere will my customer relationship, payment history, KYC and device records live after the change?\u201d If these records are spread across one portal, WhatsApp chats and a notebook, a switch becomes difficult to control.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An LCO should own a working copy of its business records. The upstream ISP may have its own account and service records, but your shop still needs a clear view of customers, expiry dates, payments, equipment and partner work.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What you need before changing ISP<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Collect these items before you promise a customer a new connection or migration:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>A current customer list with mobile number, address, connection ID, plan, expiry date and payment status.<\/li>\n\n\n<li>A separate KYC index showing which customer documents you hold and where they are stored. Do not make extra copies casually.<\/li>\n\n\n<li>A plan map showing the old plan, the proposed new plan, selling price, ISP cost and validity.<\/li>\n\n\n<li>A device register for routers, ONUs and other equipment issued to customers or partners.<\/li>\n\n\n<li>A list of active partners and sub-partners, with the customers and areas they handle.<\/li>\n\n\n<li>Written answers from the new ISP about onboarding, recharge, settlement, support and equipment.<\/li>\n\n\n<li>A cutover date, customer message and a person responsible for checking every batch.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Keep the original export or register unchanged. Work from a copy when you clean phone numbers, combine duplicate records or map old plan names to new ones. This gives you a reference if a customer asks about an earlier payment or device.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Decide whether to add or fully switch<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> A full switch changes every active connection. Adding an ISP can solve a coverage or plan problem with less movement.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Write down the reason for the change in one sentence. For example: \u201cAdd a second ISP for customers in Area B,\u201d or \u201cMove active customers to a new partner account after the current agreement ends.\u201d Then mark each customer as <strong>stay<\/strong>, <strong>move<\/strong>, or <strong>review<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the result against your actual network and shop capacity. Ask the current and proposed ISP about serviceability, plan availability, installation work, recharge steps and any partner agreement terms. Do not assume that an old customer ID, remaining validity or device will transfer automatically.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> You have a customer-level decision, not a vague instruction to \u201cmove everyone\u201d. You also know which connections will remain on the old ISP while the new setup is being checked.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Take a clean snapshot of customer and device records<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> A switch is easier when you can compare the old position with the new position customer by customer.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Make one row for each connection. Use a consistent customer ID that is meaningful in your own shop, even if the upstream ISP uses a different account number. Your snapshot can include:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Record<\/th><th>Capture before the switch<\/th><\/tr><\/thead><tbody><tr><td>Customer<\/td><td>Name, mobile, address and your internal customer ID<\/td><\/tr><tr><td>Service<\/td><td>Current ISP, ISP account ID, plan, speed or package name and expiry<\/td><\/tr><tr><td>Money<\/td><td>Last payment date, amount received, pending amount and any wallet note<\/td><\/tr><tr><td>Equipment<\/td><td>Router or ONU serial number, issue date, current holder and condition<\/td><\/tr><tr><td>Documents<\/td><td>KYC status, document location and last review note<\/td><\/tr><tr><td>Ownership<\/td><td>Operator, partner or sub-partner responsible for the connection<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Remove duplicate rows only after checking the customer and account number. Keep a note when two people share a mobile number or when one customer has more than one connection.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For stock, use a simple chain: <strong>store \u2192 partner \u2192 installed at customer \u2192 written off<\/strong>. Count the physical devices against the register before the change. If a device belongs to the ISP or must be returned, record that separately and follow the signed partner terms.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> Your customer count, active-expiry list, payment position and physical stock can be checked without opening the new ISP portal.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Confirm the new ISP process in writing<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> A partner conversation can cover a lot of ground, but your staff need a repeatable process after the first week.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ask the new ISP or partner team to confirm these points:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>How a customer or connection is created.<\/li>\n\n\n<li>Which plan names and validity periods are available in your area.<\/li>\n\n\n<li>How you add money to the partner wallet and how a customer recharge reaches the ISP account.<\/li>\n\n\n<li>How failed, pending or duplicate recharge cases are handled.<\/li>\n\n\n<li>How installation, shifting, suspension and cancellation requests are raised.<\/li>\n\n\n<li>Which equipment can be reused and which must be replaced or returned.<\/li>\n\n\n<li>Where invoices, receipts and account statements are found.<\/li>\n\n\n<li>Who handles technical, billing and customer-service escalations.<\/li>\n\n\n<li>What happens to an unpaid balance, unused validity or refundable deposit when a connection is closed.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/www.eservices.dot.gov.in\/sites\/default\/files\/2024-11\/ISP%20License%20Agreement.pdf\" target=\"_blank\" rel=\"noopener\">Department of Telecommunications ISP licence agreement<\/a> describes access through an authorised cable operator and says arrangements for network resources between parties are mutually agreed. That is useful context, but your signed partner agreement and the ISP&#8217;s current operating instructions control your actual move. Check the details with the ISP and your CA where tax or contract questions are involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> A new staff member can explain the recharge, support and settlement flow without relying on a personal phone chat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Map plans, balances and expiry dates<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> A plan name is not enough. The customer needs to know what they will receive, when it expires and what they must pay.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Create a mapping table before the first move:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Existing service<\/th><th>New service<\/th><th>Customer price<\/th><th>New expiry rule<\/th><th>Checked by<\/th><\/tr><\/thead><tbody><tr><td>Old plan name<\/td><td>New plan name<\/td><td>Your approved price<\/td><td>Add validity, reset date or other agreed rule<\/td><td>Name\/date<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Use the rule that the ISP has confirmed for each case. Do not promise that unused days, wallet balance or an old plan will transfer unless the responsible ISP has agreed it. If a customer has already paid, show how that payment is being recognised before you deactivate the old service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a mixed base, make three lists: customers expiring soon, customers with plenty of validity remaining, and customers with an open payment or service issue. Start with a small set from the first list only when the new process is ready. Keep the other two lists visible so no one moves a customer by accident.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> Every moved customer has one written answer for price, plan, validity and payment treatment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Keep KYC and customer history with your business<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> You should not have to rebuild your shop&#8217;s customer history every time you add or change an upstream ISP.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Store your operating record under your own account with controlled staff access. Link each document to your internal customer ID, not only to an ISP login. Record the document type and status without putting sensitive document numbers into a general WhatsApp group or an open spreadsheet.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ask both ISPs what they require for a new or transferred connection. KYC requirements and record-handling duties can depend on the service arrangement, so follow the ISP&#8217;s instructions and confirm compliance questions with your CA or the relevant authority. For the wider regulatory reference, keep the <a href=\"https:\/\/www.trai.gov.in\/release-publication\/consolidated-regulations\/telecom\" target=\"_blank\" rel=\"noopener\">TRAI telecom regulations index<\/a> handy and check the current rule that applies to your service.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">ISP Square is designed for this operator-owned record: KYC is uploaded to your ISP Square account rather than being tied only to an ISP account, and it remains with your operator account if you leave an ISP. Keep access limited to the staff who need it, and make sure the person collecting a document knows why it is being stored.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> You can find the customer\u2019s KYC status, connection history, payment history and current ISP from your own account, even when that customer changes service.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Run the old and new ISP side by side<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> A short parallel period lets you check the new flow while your existing customer service continues in an orderly way.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Choose a small pilot group from different situations: one normal recharge, one partner-managed connection, one new connection and one customer with a device record. Tell each customer what is changing, what is staying the same and whom to contact at the shop.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the whole journey for every pilot connection:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Create or connect the ISP partner account.<\/li>\n\n\n<li>Add the customer and select the mapped plan.<\/li>\n\n\n<li>Check the selling price and the expiry date.<\/li>\n\n\n<li>Complete a recharge using the confirmed process.<\/li>\n\n\n<li>Match the payment, wallet entry and customer history.<\/li>\n\n\n<li>Check the device and KYC links.<\/li>\n\n\n<li>Ask the customer to confirm that the service and receipt are clear.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">ISP Square connects ISP partner accounts, including OneBroadband and GTPL today. Customers, plans and balances sync every minute. It also gives you one customer list across connected ISPs, so a customer can be found by connection, plan, expiry, payment or history instead of by a portal name alone. Read the <a href=\"https:\/\/ispsquare.com\/blog\/onebroadband-partner-login-gtpl-together\/\">One Broadband partner login guide<\/a> for the multi-ISP workflow.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> The pilot has matching records in your operator account and the relevant ISP account, with no unclear payment or expiry entry.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 7: Move customers in controlled batches<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> Batches make mistakes visible. Moving the whole base at once makes it harder to find the first wrong record.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Move one area, partner or expiry group at a time. Give each batch a date and owner. A simple status board can use these states:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Status<\/th><th>Meaning<\/th><\/tr><\/thead><tbody><tr><td>Ready<\/td><td>Snapshot checked and new plan selected<\/td><\/tr><tr><td>Customer informed<\/td><td>Customer knows the plan, price and expected date<\/td><\/tr><tr><td>Submitted<\/td><td>New ISP or partner setup request is complete<\/td><\/tr><tr><td>Verified<\/td><td>Recharge, expiry, KYC and device records match<\/td><\/tr><tr><td>Follow-up<\/td><td>A person owns the remaining question<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">At the end of each batch, compare three totals: customers moved, payments recorded and devices assigned. Do not close the old record until the new service and the customer-facing receipt have been checked. Keep the old ISP reference in your history so your staff can answer questions later.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Success looks like:<\/strong> Every customer is in one clear status, and no batch is marked complete because of an unverified bulk upload.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 8: Reconcile wallets, partners and stock<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why this matters:<\/strong> A service switch can change who sells a plan, who collects money and who is responsible for an ONU.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you use partners or sub-partners, publish the new plan and commission rule before the batch starts. Make sure each person knows their own customer list, wallet position and price. The structure should be visible as <strong>operator \u2192 partner \u2192 sub-partner<\/strong>, with each level using its own login and responsibilities.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At the end of the day, reconcile:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>New ISP wallet opening balance and recharge entries.<\/li>\n\n\n<li>Customer payments received by cash and UPI.<\/li>\n\n\n<li>Commission posted to each partner wallet.<\/li>\n\n\n<li>Customers still waiting for activation or verification.<\/li>\n\n\n<li>Routers and ONUs moved, returned or installed.<\/li>\n\n\n<li>Open questions assigned to a named staff member.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">With ISP Square, you can set your own retail price per plan and level, while the ISP cost stays out of the partner view. Commission is posted to the relevant wallet on each recharge, and the wallet ledger is append-only. The system also keeps a log of staff actions, which gives you a clearer audit trail during a change.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the broader basics of keeping billing and customer records in one place, see <a href=\"https:\/\/ispsquare.com\/blog\/isp-billing-software-india-resellers\/\">ISP billing software in India: a reseller\u2019s practical guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What should stay with you after the switch?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Your long-term operating file should include the customer identity and contact details, service history, payment and receipt history, plan changes, KYC status, equipment movement, partner ownership and support notes. The upstream ISP account should contain the service-side information it needs, but your business should not depend on one login to answer a customer\u2019s basic question.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use a monthly record check even after the switch is complete. Compare active customers, upcoming expiries, wallet entries and stock. If you add another ISP later, the same record structure can support it. ISP Square\u2019s <a href=\"https:\/\/ispsquare.com\/#features\">features page<\/a> and <a href=\"https:\/\/ispsquare.com\/#how\">operator workflow<\/a> explain how its customer, recharge, KYC and partner records fit together.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Common mistakes during an ISP switch<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Moving customers before writing the old-to-new plan map.<\/li>\n\n\n<li>Treating the ISP portal export as the complete shop record.<\/li>\n\n\n<li>Forgetting partner-owned customers and devices.<\/li>\n\n\n<li>Promising a transfer of unused validity without written confirmation.<\/li>\n\n\n<li>Changing the price without telling the customer first.<\/li>\n\n\n<li>Keeping KYC documents in personal phones or unprotected group chats.<\/li>\n\n\n<li>Closing the old record before checking the first new recharge.<\/li>\n\n\n<li>Retrying a timed-out recharge blindly instead of checking its status.<\/li>\n\n\n<li>Letting two staff members update the same batch without an owner.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The fix is simple: one customer ID, one batch owner, one status and one verification check before closure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the move<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before you call the switch complete, check this list:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Every moved customer has a new ISP, plan and expiry date.<\/li>\n\n\n<li>The customer can see or receive the correct recharge confirmation.<\/li>\n\n\n<li>The payment appears in the correct customer and wallet history.<\/li>\n\n\n<li>KYC status is available in your operator account.<\/li>\n\n\n<li>The router or ONU serial number is still assigned correctly.<\/li>\n\n\n<li>The partner or sub-partner responsible for the customer is correct.<\/li>\n\n\n<li>Old ISP references remain in history for questions and reconciliation.<\/li>\n\n\n<li>Staff know where to raise a billing or technical issue.<\/li>\n\n\n<li>The old and new customer totals have been compared.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">If the checks pass, send the customer a short confirmation with the plan name, expiry date, payment record and support contact. Keep the message factual and easy to find.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Can an LCO switch ISP without changing every customer at once?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. You can add or test another ISP for selected areas or new connections, then move customers in batches. Whether a particular customer, plan or device can be transferred depends on the ISP and your partner terms, so confirm it before promising the move.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What customer data should an LCO keep during an ISP change?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Keep your own customer ID, contact and address details, plan and expiry, payment history, KYC status, equipment record, partner ownership and support notes. Store sensitive documents with controlled access and follow the current instructions of the ISP and relevant authority.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does KYC stay with the LCO after changing ISP?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It should be organised in the operator\u2019s own business record, subject to the applicable ISP and compliance requirements. ISP Square stores uploaded KYC in your ISP Square account rather than tying it only to an ISP account, so your operator history remains organised when you add or change an ISP.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I avoid duplicate recharge entries during a switch?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use a batch status and check the recharge result before trying again. Match the customer, amount, ISP account and wallet entry, and keep a named person responsible for resolving pending cases.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I manage OneBroadband and GTPL customers together?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">ISP Square connects OneBroadband and GTPL partner accounts today and provides one customer list across connected ISPs. You can see each customer\u2019s connection, plan, expiry, payments and history in the operator workflow; ask the team about the ISP you resell if it is not listed.<\/p>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Keep your customer record\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">Plan your switch<\/p><p class=\"ap-cta__title\">Keep your customer record<\/p><p class=\"ap-cta__text\">Manage ISP accounts, recharges, KYC, partners and stock from one operator account.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/ispsquare.com\/#pricing\">See current plans<\/a><\/aside>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Can an LCO switch ISP without changing every customer at once?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Yes. You can add or test another ISP for selected areas or new connections, then move customers in batches. Whether a particular customer, plan or device can be transferred depends on the ISP and your partner terms, so confirm it before promising the move.\"}}, {\"@type\": \"Question\", \"name\": \"What customer data should an LCO keep during an ISP change?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Keep your own customer ID, contact and address details, plan and expiry, payment history, KYC status, equipment record, partner ownership and support notes. Store sensitive documents with controlled access and follow the current instructions of the ISP and relevant authority.\"}}, {\"@type\": \"Question\", \"name\": \"Does KYC stay with the LCO after changing ISP?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"It should be organised in the operator\u2019s own business record, subject to the applicable ISP and compliance requirements. ISP Square stores uploaded KYC in your ISP Square account rather than tying it only to an ISP account, so your operator history remains organised when you add or change an ISP.\"}}, {\"@type\": \"Question\", \"name\": \"How do I avoid duplicate recharge entries during a switch?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Use a batch status and check the recharge result before trying again. Match the customer, amount, ISP account and wallet entry, and keep a named person responsible for resolving pending cases.\"}}, {\"@type\": \"Question\", \"name\": \"Can I manage OneBroadband and GTPL customers together?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"ISP Square connects OneBroadband and GTPL partner accounts today and provides one customer list across connected ISPs. You can see each customer\u2019s connection, plan, expiry, payments and history in the operator workflow; ask the team about the ISP you resell if it is not listed.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Learn how to switch isp as lco with a clear customer, KYC, plan and device checklist. Keep your records with you and move customers in controlled batches.","protected":false},"author":1,"featured_media":128,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[8],"tags":[11,120,121,46,119],"class_list":["post-127","post","type-post","status-publish","format-standard","has-post-thumbnail","category-partner-management","tag-broadband-reseller","tag-customer-records","tag-kyc","tag-lco-business","tag-switch-isp","cs-entry"],"_links":{"self":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts\/127","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/comments?post=127"}],"version-history":[{"count":1,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts\/127\/revisions"}],"predecessor-version":[{"id":315,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts\/127\/revisions\/315"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/media\/128"}],"wp:attachment":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/media?parent=127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/categories?post=127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/tags?post=127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}