Flowpeak ConsultingFlowpeak Logo Mark

Zoho implementation for Telecom and ISPs

Zoho for telecom resellers and internet providers: leads, activations, field installation, tickets and recurring billing.

Business process workflow

How telecom and isps work flows in Zoho

Run activation, installation, support and recurring billing for subscribers and enterprise accounts.

Common problems we fix

  • Installations are scheduled by phone
  • Support tickets lack account context
  • Recurring billing and collections are manual

The process, step by step

  1. 1

    Lead and plan sale

    Capture and qualify leads.

  2. 2

    Activation request

    KYC documents and approvals.

  3. 3

    Field installation

    Schedule and track engineer visits.

  4. 4

    Support

    Tickets and SLAs by account.

  5. 5

    Recurring billing

    Plans, usage and renewals.

  6. 6

    Churn analysis

    Churn and revenue trends.

Entity diagram: the data behind telecom and isps in Zoho

Each box is a record type, coloured by the Zoho app that holds it, with its key fields. Lines show how records connect, so a customer, an order and an invoice stay linked instead of being retyped. We refine this model with you during discovery.

holds (1:N)raises (1:N)may need (1:N)installs (1:N)billed by (1:N)CustomerCRMNamePlanAccount statusSubscriptionBillingPlanStartRenewal dateTicketDeskTicket noCategorySLAField VisitFSMJob noTechnicianStatusDeviceInventorySerialModelStatusInvoiceBooksInvoice noUsageDue date
  • Zoho CRM
  • Zoho Billing
  • Zoho Desk
  • Zoho FSM
  • Zoho Inventory
  • Zoho Books
Read the relationships as text
  • Customer holds Subscription (1:N)
  • Customer raises Ticket (1:N)
  • Ticket may need Field Visit (1:N)
  • Field Visit installs Device (1:N)
  • Subscription billed by Invoice (1:N)

Department by department

How every department of a telecom and isps business works in Zoho

An ISP or telecom operator sells connections, installs them, keeps the network up and bills every subscriber each month. In Zoho sales, provisioning, field installation, the network operations team, support, billing, accounts and HR share one subscriber and one connection record, so a new order, a fault and an invoice all point to the same line.

How the departments hand work to each other

Each arrow is a handover. Because every team works on the same Zoho records, the next department picks up the work without re-entering it.

  1. 1Sales and Subscriber Acquisition to Provisioning and Activation: Signed service order with plan, address and preferred install date
  2. 2Provisioning and Activation to Field Installation and Maintenance: Installation job with address, CPE and port details
  3. 3Provisioning and Activation to Billing and Collections: Activation date and plan for the first invoice
  4. 4Field Installation and Maintenance to Provisioning and Activation: Installation completed with test results and CPE used
  5. 5Network Operations Centre to Customer Support: Known outages and expected restore times
  6. 6Customer Support to Field Installation and Maintenance: Repair requests with fault details
  7. 7Customer Support to Billing and Collections: Approved service credits
  8. 8Billing and Collections to Finance and Accounts: Billing and collections summary
  9. 9Billing and Collections to Provisioning and Activation: Accounts to suspend or restore
  10. 10Finance and Accounts to Management and Reporting: Monthly financial results
  11. 11HR and Payroll to Finance and Accounts: Payroll summary for posting
  12. 12Management and Reporting to Sales and Subscriber Acquisition: Target areas and plan priorities

Each department in detail

Open a department to see its workflow, its own entity diagram, who does the work, what needs approval, the reports it watches and what it hands over.

Sales and Subscriber AcquisitionSigns up home and business subscribers on the right plan and books a feasible installation.

Workflow

  1. 1

    Capture enquiries

    Leads from the website, call centre, walk-ins and resellers land in Zoho CRM with address, building and plan interest.

  2. 2

    Check coverage

    The address is checked against covered buildings and areas, with a feasibility request to the network team when it is unclear.

  3. 3

    Offer plans

    The salesperson picks a plan by speed, data cap and contract term, adds router or static IP add-ons, and sends the offer.

  4. 4

    Collect KYC and sign

    Identity documents are uploaded and the subscriber agreement is signed electronically.

  5. 5

    Create the order

    A signed order creates the subscriber and an installation request with preferred dates.

Entity diagram: Sales and Subscriber Acquisition

The records this team creates and updates, their key fields, and how they link.

needs (1:1)converts to (1:1)places (1:N)LeadCRMAddressPlan interestSourceFeasibility CheckCreatorBuildingResultPort freeSubscriberCRMAccount noTypeKYC statusService OrderCreatorPlanAdd-onsInstall date
  • Zoho CRM
  • Zoho Creator
Read the relationships as text
  • Lead needs Feasibility Check (1:1)
  • Lead converts to Subscriber (1:1)
  • Subscriber places Service Order (1:N)
Who does the work
  • Sales executive
  • Reseller or channel partner
  • Sales manager
Approvals and controls
  • Waiving installation charges or custom business pricing needs the sales manager
  • Orders do not move to installation until KYC is verified
Reports they watch
  • New connections by area and plan
  • Lead to activation conversion
  • Reseller sales against target
Hands over to
  • Provisioning and Activation: Signed service order with plan, address and preferred install date
Provisioning and ActivationReserves network resources, schedules installation and activates the service on the right plan.

Workflow

  1. 1

    Reserve resources

    A port, splitter or access point and an IP address are reserved against the service order.

  2. 2

    Assign the CPE

    A router or ONT with serial number is allocated from stock in Zoho Inventory, which is reordered when it runs low, and linked to the subscriber.

  3. 3

    Schedule the install

    An installation job is created for the area's field team with the time slot confirmed with the subscriber.

  4. 4

    Activate and start billing

    After the field team confirms, the account is activated and the subscription starts from that date.

Entity diagram: Provisioning and Activation

The records this team creates and updates, their key fields, and how they link.

uses (1:1)activated by (1:1)ConnectionCreatorCircuit IDPortIP addressCPE DeviceInventorySerial noModelStatusActivationCreatorActivated onPlanActivated by
  • Zoho Creator
  • Zoho Inventory
Read the relationships as text
  • Connection uses CPE Device (1:1)
  • Connection activated by Activation (1:1)
Who does the work
  • Provisioning executive
  • NOC engineer
Approvals and controls
  • Static IP or dedicated bandwidth allocations need NOC approval
Reports they watch
  • Orders pending activation by age
  • Average order to activation time
  • CPE stock allocated versus installed
Hands over to
  • Field Installation and Maintenance: Installation job with address, CPE and port details
  • Billing and Collections: Activation date and plan for the first invoice
Field Installation and MaintenanceInstalls connections at subscriber premises and fixes faults that need a site visit.

Workflow

  1. 1

    Plan the day

    Dispatchers assign installation and repair jobs to technicians by area and skill.

  2. 2

    Install on site

    The technician lays the drop cable, fixes the CPE, tests speed and records photos and cable length on mobile.

  3. 3

    Get subscriber sign-off

    The subscriber signs on the technician's phone to confirm the installation or repair.

  4. 4

    Fix faults on site

    Repair jobs from support record the root cause, parts replaced and time spent.

Entity diagram: Field Installation and Maintenance

The records this team creates and updates, their key fields, and how they link.

consumes (1:N)records (1:1)Field JobFSMJob typeAreaStatusMaterial UsedInventoryItemQtyJobSite TestFSMSpeed resultSignal levelPhoto
  • Zoho FSM
  • Zoho Inventory
Read the relationships as text
  • Field Job consumes Material Used (1:N)
  • Field Job records Site Test (1:1)
Who does the work
  • Field technician
  • Dispatcher
  • Field supervisor
Approvals and controls
  • Cable runs beyond the standard length need supervisor approval and may be charged
Reports they watch
  • Installs and repairs per technician per day
  • First visit fix rate
  • Missed appointments
Hands over to
  • Provisioning and Activation: Installation completed with test results and CPE used
Zoho apps for this team:Zoho FSMZoho Inventory
Network Operations CentreMonitors the network, handles outages and plans capacity so subscribers stay online.

Workflow

  1. 1

    Log network incidents

    Outages and degradations from monitoring alerts are logged with affected area, nodes and start time.

  2. 2

    Notify affected subscribers

    Subscribers in the affected area get an SMS or email, and support sees the known outage.

  3. 3

    Restore and record cause

    The incident is closed with root cause, fix and duration, and repeat sites are flagged.

  4. 4

    Plan capacity

    Utilisation by node and uplink is reviewed to plan upgrades before congestion.

  5. 5

    Schedule maintenance windows

    Planned work is logged with a window and subscribers are told in advance.

Entity diagram: Network Operations Centre

The records this team creates and updates, their key fields, and how they link.

affected by (1:N)scheduled in (N:N)Network IncidentCreatorAreaStart timeRoot causeNetwork NodeCreatorNode IDLocationCapacityMaintenance WindowCreatorDateDurationAreas
  • Zoho Creator
Read the relationships as text
  • Network Node affected by Network Incident (1:N)
  • Network Node scheduled in Maintenance Window (N:N)
Who does the work
  • NOC engineer
  • Network manager
Approvals and controls
  • Planned maintenance in business hours needs the network manager
Reports they watch
  • Network uptime by area
  • Incidents by root cause
  • Node utilisation above threshold
Hands over to
  • Customer Support: Known outages and expected restore times
Customer SupportResolves subscriber issues remotely where possible and sends a technician when needed.

Workflow

  1. 1

    Take the call or chat

    Complaints about no internet, slow speed or billing come in by phone, chat or the app and become tickets on the subscriber.

  2. 2

    Check known outages

    The agent checks for an open network incident in the area before troubleshooting.

  3. 3

    Troubleshoot remotely

    Router restarts and settings are handled remotely or with screen guidance, following a fault script.

  4. 4

    Escalate to field

    If the fault is at the premises, a repair job is booked with the field team.

  5. 5

    Close and survey

    The ticket closes with resolution code, and the subscriber gets a short survey.

Entity diagram: Customer Support

The records this team creates and updates, their key fields, and how they link.

guides (N:N)may raise (1:1)TicketDeskTicket noFault typeStatusFault ScriptDeskSymptomStepsResolutionRepair RequestFSMTicket noSlotStatus
  • Zoho Desk
  • Zoho FSM
Read the relationships as text
  • Fault Script guides Ticket (N:N)
  • Ticket may raise Repair Request (1:1)
Who does the work
  • Support agent
  • Support team lead
Approvals and controls
  • Service credits for downtime need the team lead
Reports they watch
  • Tickets by fault type and area
  • First contact resolution rate
  • Repeat complaints within 30 days
Hands over to
  • Field Installation and Maintenance: Repair requests with fault details
  • Billing and Collections: Approved service credits
Billing and CollectionsBills subscribers on time, applies plan changes and credits, and collects or suspends unpaid accounts.

Workflow

  1. 1

    Run recurring billing

    Monthly or prepaid subscriptions renew in Zoho Billing with pro-rata charges for upgrades and downgrades.

  2. 2

    Collect payments

    Payments by card, auto-debit, bank or the customer portal are recorded and matched.

  3. 3

    Chase overdue accounts

    Reminders go out on a dunning schedule, and accounts past the grace period are flagged for suspension.

  4. 4

    Suspend and restore

    Suspended accounts are restored automatically when payment is received.

Entity diagram: Billing and Collections

The records this team creates and updates, their key fields, and how they link.

generates (1:N)settled by (N:N)may have (1:N)SubscriptionBillingPlanBilling cycleNext renewalInvoiceBillingInvoice noAmountDue datePaymentBillingModeAmountDateSuspensionCreatorReasonSuspended onRestored on
  • Zoho Billing
  • Zoho Creator
Read the relationships as text
  • Subscription generates Invoice (1:N)
  • Invoice settled by Payment (N:N)
  • Subscription may have Suspension (1:N)
Who does the work
  • Billing executive
  • Collections officer
  • Billing manager
Approvals and controls
  • Bill waivers and write-offs need the billing manager
  • Suspension of business accounts needs the account manager to be told first
Reports they watch
  • Billed revenue and churn by plan
  • Overdue accounts by age
  • Suspensions and restorations
Hands over to
  • Finance and Accounts: Billing and collections summary
  • Provisioning and Activation: Accounts to suspend or restore
Finance and AccountsBooks revenue, pays vendors and upstream bandwidth providers, and closes the books.

Workflow

  1. 1

    Post billing revenue

    Subscription invoices and payments flow into Zoho Books, with GST in India or VAT in the UAE and UK.

  2. 2

    Pay bandwidth and vendors

    Upstream bandwidth, pole or right-of-way rent and equipment bills are matched and paid.

  3. 3

    Pay reseller commission

    Commission on reseller activations is worked out and paid each month.

  4. 4

    Close the month

    Bank, payment gateway and deferred revenue for prepaid plans are reconciled.

Entity diagram: Finance and Accounts

The records this team creates and updates, their key fields, and how they link.

posted in (N:N)posted in (N:N)Vendor BillBooksVendorBill noDue dateReseller CommissionCreatorResellerMonthAmountJournalBooksTypePeriodAmount
  • Zoho Books
  • Zoho Creator
Read the relationships as text
  • Vendor Bill posted in Journal (N:N)
  • Reseller Commission posted in Journal (N:N)
Who does the work
  • Accountant
  • Finance manager
Approvals and controls
  • Vendor payments above a set value need two approvers
Reports they watch
  • Revenue per subscriber
  • Payables to bandwidth providers
  • Monthly profit and loss
Hands over to
  • Management and Reporting: Monthly financial results
HR and PayrollHires and manages agents and technicians, runs support shifts and pays salaries and incentives.

Workflow

  1. 1

    Hire staff

    Technicians, support agents and sales staff are hired through tracked openings.

  2. 2

    Roster support shifts

    Round-the-clock support and NOC shifts are rostered and attendance captured.

  3. 3

    Train and certify

    Technicians complete fibre splicing and safety training recorded in their profile.

  4. 4

    Run payroll

    Salaries, night shift allowances and sales incentives are paid through Zoho Payroll where it is available or your local provider.

Entity diagram: HR and Payroll

The records this team creates and updates, their key fields, and how they link.

works (1:N)paid by (1:N)EmployeePeopleEmployee IDTeamAreaShiftShiftsTeamDateHoursPayslipPayrollMonthGrossIncentive
  • Zoho People
  • Zoho Shifts
  • Zoho Payroll
Read the relationships as text
  • Employee works Shift (1:N)
  • Employee paid by Payslip (1:N)
Who does the work
  • HR executive
  • HR manager
Approvals and controls
  • Overtime and night allowances need the team lead's approval
Reports they watch
  • Headcount by team and area
  • Shift coverage gaps
  • Attrition
Hands over to
  • Finance and Accounts: Payroll summary for posting
Management and ReportingTracks subscriber growth, churn, network quality and revenue in one view.

Workflow

  1. 1

    Combine the data

    Zoho Analytics joins CRM, Billing, Desk, FSM and Creator data.

  2. 2

    Subscriber dashboard

    Net adds, churn, plan mix and revenue per user by area.

  3. 3

    Service quality review

    Uptime, fault rates and resolution times are reviewed weekly.

  4. 4

    Exception alerts

    Large outages and spikes in churn or overdue accounts reach leaders on Cliq.

Entity diagram: Management and Reporting

The records this team creates and updates, their key fields, and how they link.

shows (N:N)triggers (1:N)KPIAnalyticsNameTargetActualDashboardAnalyticsAudienceRefreshOwnerAlertFlowTriggerRecipientChannel
  • Zoho Analytics
  • Zoho Flow
Read the relationships as text
  • Dashboard shows KPI (N:N)
  • KPI triggers Alert (1:N)
Who does the work
  • Managing director
  • Head of operations
Approvals and controls
  • Area expansion and plan pricing are decided by management
Reports they watch
  • Net subscriber adds and churn
  • Revenue per subscriber by area
  • Network uptime
Hands over to
  • Sales and Subscriber Acquisition: Target areas and plan priorities
Zoho apps for this team:Zoho AnalyticsZoho FlowZoho Cliq

What to expect when you start

A typical plan for a focused project of one to three apps. Larger scope or messy data takes longer; we confirm the timeline after discovery.

  1. Week 1 to 2

    Map and agree

    We walk through your telecom and isps process from "Lead and plan sale" to "Churn analysis", list the records and fields you really need, and agree the scope.

  2. Week 3 to 4

    Build the core

    We configure Zoho CRM and Zoho Creator with your stages, roles, approvals and templates.

  3. Week 5 to 6

    Connect and migrate

    We clean and import your data, connect email, payments or other tools, and build the reports you will use every week.

  4. Week 7 to 8

    Test and go live

    Your team tests with real cases, we train each role, and we cut over with a checklist.

Mistakes to avoid

  • Copying the old spreadsheet column for column. Keep only the fields that help someone decide or act.
  • Leaving out exceptions such as returns, changes and cancellations. Model them early so the team does not work around the system.
  • No owner per stage. Name one person for "Lead and plan sale" and one for "Churn analysis".
  • Going live without checking reports against numbers you already trust.

A good first win

Start with the problem that hurts most: Installations are scheduled by phone. Fixing one visible problem in the first month builds trust and adoption for everything after it.

What you can measure

  • Installation turnaround
  • First response time
  • Collection efficiency

Questions about Zoho for telecom and isps

Which Zoho apps suit telecom and isps businesses?

A typical telecom and isps setup uses Zoho CRM, Zoho Creator, Zoho Sign, Zoho FSM, Zoho Desk, Zoho Billing, Zoho Books, Zoho Analytics. We confirm the exact apps after mapping your own process in a discovery call.

How does the business process flow in Zoho for telecom and isps?

1. Lead and plan sale; 2. Activation request; 3. Field installation; 4. Support; 5. Recurring billing; 6. Churn analysis.

Which departments does a Zoho setup for telecom and isps cover?

A full setup covers Sales and Subscriber Acquisition, Provisioning and Activation, Field Installation and Maintenance, Network Operations Centre, Customer Support, Billing and Collections, Finance and Accounts, HR and Payroll, Management and Reporting. Each department works in its own Zoho screens, but they share the same customer, order and finance records, so work moves from one team to the next without being retyped.

Zoho apps we set up for telecom and isps

  • Zoho CRM
  • Zoho Creator
  • Zoho Books

Not sure which apps fit your business? Book a free 30-minute call or see all Zoho products we implement

Book a free callWhatsApp