Flowpeak ConsultingFlowpeak Logo Mark

Zoho implementation for EV Charging Operators

Zoho for EV charging operators: sign host sites, run charger rollouts, track uptime and faults, support drivers and settle host revenue shares.

Business process workflow

How ev charging operators work flows in Zoho

Zoho connects site hosts, charger rollouts, uptime and maintenance, driver support and revenue share for charge point operators.

Common problems we fix

  • Site deals, grid applications and installs are tracked in scattered spreadsheets
  • Charger faults reach field teams late, so uptime suffers
  • Revenue share statements for site hosts take days to prepare

The process, step by step

  1. 1

    Sign host sites

    Retail, hospitality, workplace and fleet sites are surveyed and signed on host agreements.

  2. 2

    Plan and install

    Each site rollout runs as a project covering grid connection, civil works, install and commissioning.

  3. 3

    Monitor the network

    Charger status and faults from the charging platform are pulled in and turned into tickets.

  4. 4

    Maintain chargers

    Field technicians fix faults and run planned maintenance with parts from stock.

  5. 5

    Support drivers

    Drivers get help with payments, access and faults by phone, chat and email.

  6. 6

    Settle and report

    Session revenue is reconciled, hosts are paid their share and uptime is reported.

Department by department

How every department of a ev charging operators business works in Zoho

A charge point operator signs host sites, builds and commissions chargers, keeps them working and earns from each charging session. In Zoho, business development, deployment, network operations, field maintenance, stores, driver support, accounts and HR share one site, one charger and one host record, alongside the charging platform that runs the sessions.

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. 1Business Development and Site Hosts to Network Deployment: Signed site with survey and charger plan
  2. 2Business Development and Site Hosts to Finance and Accounts: Host agreement terms for settlement
  3. 3Network Deployment to Network Operations: Live chargers with serials and site details
  4. 4Network Deployment to Equipment and Stores: Charger and parts requirements
  5. 5Network Operations to Field Maintenance: Faults needing a site visit
  6. 6Network Operations to Driver Support: Known outages for driver messages
  7. 7Field Maintenance to Network Operations: Repaired chargers to confirm online
  8. 8Field Maintenance to Equipment and Stores: Parts used and warranty returns
  9. 9Equipment and Stores to Network Deployment: Chargers ready for install
  10. 10Equipment and Stores to Finance and Accounts: Supplier bills and maker credits
  11. 11Driver Support to Network Operations: Driver-reported faults
  12. 12Driver Support to Finance and Accounts: Approved refunds
  13. 13Finance and Accounts to Management and Reporting: Monthly revenue, payback and cash summary
  14. 14HR and Payroll to Finance and Accounts: Payroll summary for posting
  15. 15HR and Payroll to Field Maintenance: Technician availability
  16. 16Management and Reporting to Business Development and Site Hosts: Target site types and regions
  17. 17Management and Reporting to Network Deployment: Rollout 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.

Business Development and Site HostsFinds and signs host sites and fleet customers for the charging network.

Workflow

  1. 1

    Build the site pipeline

    Retail parks, hotels, offices, depots and car parks are tracked as site leads with traffic and parking details.

  2. 2

    Survey the site

    A site survey records bays, power supply, distance to the board and civil work needed.

  3. 3

    Propose the model

    Hosts are offered owned, leased or revenue share models with the charger mix.

  4. 4

    Sign the host agreement

    Term, revenue share, tariffs and access hours are agreed and signed.

  5. 5

    Win fleet accounts

    Depot charging and fleet card deals are set up for logistics, taxi and corporate fleets.

Entity diagram: Business Development and Site Hosts

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

surveyed in (1:1)signed as (1:1)may use (N:N)Site LeadCRMLocationBaysStageSite SurveyCreatorSupplyDistanceCivil worksHost AgreementContractsModelShare pctTermFleet AccountCRMCompanyVehiclesTariff
  • Zoho CRM
  • Zoho Creator
  • Zoho Contracts
Read the relationships as text
  • Site Lead surveyed in Site Survey (1:1)
  • Site Lead signed as Host Agreement (1:1)
  • Fleet Account may use Host Agreement (N:N)
Who does the work
  • Business development manager
  • Site surveyor
  • Commercial manager
Approvals and controls
  • Revenue share above the standard needs the commercial manager
  • Sites needing major grid upgrades need management approval
Reports they watch
  • Site pipeline by stage
  • Signed sites by region
  • Fleet accounts won
Hands over to
  • Network Deployment: Signed site with survey and charger plan
  • Finance and Accounts: Host agreement terms for settlement
Network DeploymentTakes signed sites through grid connection, installation and commissioning.

Workflow

  1. 1

    Open the site project

    Each site becomes a project with milestones for design, permits, grid, civil works and install.

  2. 2

    Apply for grid connection

    Applications to the local network operator and any planning permits are tracked with dates.

  3. 3

    Manage installers

    Civil and electrical contractors get work packages and submit progress and photos.

  4. 4

    Commission chargers

    Each charger is tested, registered on the charging platform and logged with serial and firmware.

  5. 5

    Go live

    The site is marked live and handed to network operations with as-built documents.

Entity diagram: Network Deployment

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

needs (1:1)installs (1:N)passes (1:N)Site ProjectProjectsSiteMilestoneGo-live dateGrid ApplicationCreatorOperatorCapacityStatusChargerCreatorSerialPowerConnectorCommissioning TestCreatorTestResultDate
  • Zoho Projects
  • Zoho Creator
Read the relationships as text
  • Site Project needs Grid Application (1:1)
  • Site Project installs Charger (1:N)
  • Charger passes Commissioning Test (1:N)
Who does the work
  • Project manager
  • Electrical engineer
  • Contractor coordinator
Approvals and controls
  • Chargers go live only after commissioning tests pass
  • Contractor variations need the project manager
Reports they watch
  • Sites by milestone
  • Days from signing to live
  • Grid applications pending
Hands over to
  • Network Operations: Live chargers with serials and site details
  • Equipment and Stores: Charger and parts requirements
Network OperationsWatches every charger, raises faults fast and keeps uptime high.

Workflow

  1. 1

    Pull charger status

    Status and fault events from the charging platform are pulled in through Flow or an API integration.

  2. 2

    Raise fault tickets

    Offline chargers and repeat errors create tickets with site and charger details.

  3. 3

    Fix remotely first

    Remote resets and configuration fixes are tried before sending a technician.

  4. 4

    Dispatch field work

    Faults that need a visit become field work orders.

  5. 5

    Report uptime

    Uptime and fault trends are reported by site, model and host.

Entity diagram: Network Operations

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

raises (1:N)tries (1:N)rolls into (N:N)Charger StatusCreatorChargerStateLast seenFault TicketDeskError codePriorityStatusRemote ActionCreatorActionResultUptime RecordAnalyticsChargerMonthUptime
  • Zoho Creator
  • Zoho Desk
  • Zoho Analytics
Read the relationships as text
  • Charger Status raises Fault Ticket (1:N)
  • Fault Ticket tries Remote Action (1:N)
  • Charger Status rolls into Uptime Record (N:N)
Who does the work
  • Network operations analyst
  • NOC lead
Approvals and controls
  • Chargers taken out of service need the NOC lead
  • Firmware updates follow a tested rollout plan
Reports they watch
  • Uptime by site and model
  • Open faults by age
  • Remote fix rate
Hands over to
  • Field Maintenance: Faults needing a site visit
  • Driver Support: Known outages for driver messages
Field MaintenanceRepairs chargers and runs planned maintenance at each site.

Workflow

  1. 1

    Receive work orders

    Technicians get fault and planned visits on the mobile app with charger history.

  2. 2

    Diagnose and repair

    Faults are fixed and parts used, readings and photos are recorded.

  3. 3

    Run planned maintenance

    Scheduled checks cover cables, connectors, enclosures, cooling and signage.

  4. 4

    Claim warranty parts

    Failed parts under maker warranty are recorded for a claim.

  5. 5

    Close and confirm

    The job is closed once the charger reports available again.

Entity diagram: Field Maintenance

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

closed by (1:1)generates (1:N)may raise (1:N)Work OrderFSMChargerTypeStatusService ReportFSMFault foundFixPhotosMaintenance PlanFSMSiteFrequencyNext dueWarranty PartCreatorPartMakerClaim status
  • Zoho FSM
  • Zoho Creator
Read the relationships as text
  • Work Order closed by Service Report (1:1)
  • Maintenance Plan generates Work Order (1:N)
  • Service Report may raise Warranty Part (1:N)
Who does the work
  • Field technician
  • Maintenance supervisor
Approvals and controls
  • Electrical isolation follows a permit-to-work checklist
  • Charger replacements need the maintenance supervisor
Reports they watch
  • Mean time to repair
  • Planned maintenance completed
  • Repeat faults by model
Hands over to
  • Network Operations: Repaired chargers to confirm online
  • Equipment and Stores: Parts used and warranty returns
Zoho apps for this team:Zoho FSMZoho InventoryZoho Creator
Equipment and StoresBuys chargers, cables and spares and keeps stock at depots and with technicians.

Workflow

  1. 1

    Plan equipment

    Charger and spares needs come from the rollout plan and fault history.

  2. 2

    Order from makers

    Purchase orders go to charger makers and distributors with serial tracking.

  3. 3

    Receive by serial

    Chargers and key parts are received with serial numbers and stored by depot.

  4. 4

    Return faulty parts

    Warranty returns go back to the maker and credits are tracked.

Entity diagram: Equipment and Stores

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

tracked as (1:N)ordered on (N:N)returned on (1:1)ItemInventoryModelTypeReorder levelSerial UnitInventorySerialLocationStatusPurchase OrderInventoryMakerETARMACreatorSerialReasonCredit
  • Zoho Inventory
  • Zoho Creator
Read the relationships as text
  • Item tracked as Serial Unit (1:N)
  • Item ordered on Purchase Order (N:N)
  • Serial Unit returned on RMA (1:1)
Who does the work
  • Procurement officer
  • Storekeeper
Approvals and controls
  • Charger orders above the set value need the operations director
Reports they watch
  • Spares by depot
  • Serial units by status
  • Open RMAs
Hands over to
  • Network Deployment: Chargers ready for install
  • Finance and Accounts: Supplier bills and maker credits
Zoho apps for this team:Zoho InventoryZoho Creator
Driver SupportHelps drivers start sessions, resolve payment issues and report faults.

Workflow

  1. 1

    Take contacts

    Calls, chat, app messages and email create tickets with site and charger ID.

  2. 2

    Resolve sessions

    Agents check the session, help start or stop it and fix payment or access issues.

  3. 3

    Refund where due

    Failed or overcharged sessions are refunded under the policy.

  4. 4

    Pass on faults

    Charger faults reported by drivers go to network operations.

Entity diagram: Driver Support

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

raises (1:N)may need (1:1)Driver TicketDeskChargerIssueStatusDriverCRMNameAccountVehicleRefund RequestDeskSessionAmountReason
  • Zoho Desk
  • Zoho CRM
Read the relationships as text
  • Driver raises Driver Ticket (1:N)
  • Driver Ticket may need Refund Request (1:1)
Who does the work
  • Support agent
  • Support lead
Approvals and controls
  • Refunds above the set amount need the support lead
Reports they watch
  • Tickets per 1,000 sessions
  • First response time
  • Refunds by cause
Hands over to
  • Network Operations: Driver-reported faults
  • Finance and Accounts: Approved refunds
Zoho apps for this team:Zoho DeskZoho SalesIQZoho Books
Finance and AccountsReconciles session revenue, pays host shares and tracks capital spend per site.

Workflow

  1. 1

    Import session revenue

    Session totals from the charging platform and payment provider are reconciled.

  2. 2

    Bill fleets

    Fleet accounts are invoiced for depot and network charging with GST, VAT or sales tax as it applies.

  3. 3

    Pay host shares

    Monthly statements show each host's sessions and share, and payouts are made.

  4. 4

    Track site capex

    Charger, install and grid costs are recorded against each site.

  5. 5

    Handle grants

    Where grants or incentives apply, claims and conditions are tracked against sites.

Entity diagram: Finance and Accounts

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

drives (1:N)compared with (N:N)adds to (N:N)Session RevenueBooksSiteMonthAmountHost StatementCreatorHostSessionsShareFleet InvoiceBooksAccountkWhAmountSite CapexBooksSiteItemCost
  • Zoho Books
  • Zoho Creator
Read the relationships as text
  • Session Revenue drives Host Statement (1:N)
  • Session Revenue compared with Site Capex (N:N)
  • Fleet Invoice adds to Session Revenue (N:N)
Who does the work
  • Accountant
  • Revenue analyst
Approvals and controls
  • Host payouts are released after the commercial manager checks the statement
  • Capex above budget needs the finance director
Reports they watch
  • Revenue per site and charger
  • Host shares due
  • Payback by site
Hands over to
  • Management and Reporting: Monthly revenue, payback and cash summary
HR and PayrollHires, certifies and pays engineers, technicians and support staff.

Workflow

  1. 1

    Hire staff

    Engineers, technicians and support agents are hired through Recruit.

  2. 2

    Track electrical certification

    Electrical licences, high-voltage training and maker certifications are recorded with expiry.

  3. 3

    Run on-call rotas

    Technician on-call and support shift rotas are kept in Shifts.

  4. 4

    Pay wages and call-outs

    Salary, on-call and call-out pay run through Zoho Payroll where it is available, or your local payroll provider.

Entity diagram: HR and Payroll

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

holds (1:N)assigned to (N:N)paid by (1:N)EmployeePeopleNameRoleRegionCertificationPeopleTypeExpiryOn-call RotaShiftsWeekRegionPersonPayslipPayrollMonthCall-outsNet
  • Zoho People
  • Zoho Shifts
  • Zoho Payroll
Read the relationships as text
  • Employee holds Certification (1:N)
  • Employee assigned to On-call Rota (N:N)
  • Employee paid by Payslip (1:N)
Who does the work
  • HR officer
  • Operations manager
Approvals and controls
  • Technicians without current electrical certification cannot take work orders
Reports they watch
  • Certifications expiring
  • Call-out hours by region
  • Headcount by function
Hands over to
  • Finance and Accounts: Payroll summary for posting
  • Field Maintenance: Technician availability
Management and ReportingGives leaders one view of rollout, uptime, utilisation and returns.

Workflow

  1. 1

    Combine data

    CRM, Projects, Desk, FSM, Creator and Books data flow into Zoho Analytics.

  2. 2

    Track rollout

    Sites signed, in build and live are tracked against plan.

  3. 3

    Watch network health

    Uptime, utilisation and driver tickets are reviewed weekly.

  4. 4

    Review returns

    Revenue and payback are compared by site type and region.

Entity diagram: Management and Reporting

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

rolls into (N:N)informs (N:N)Network DashboardAnalyticsWeekLive chargersUptimeRollout KPIAnalyticsRegionSignedLiveSite ReturnsAnalyticsSiteRevenuePayback
  • Zoho Analytics
Read the relationships as text
  • Rollout KPI rolls into Network Dashboard (N:N)
  • Network Dashboard informs Site Returns (N:N)
Who does the work
  • CEO
  • Operations director
Approvals and controls
  • Tariff changes are approved by management
Reports they watch
  • Uptime trend
  • Utilisation by site type
  • Payback by region
Hands over to
  • Business Development and Site Hosts: Target site types and regions
  • Network Deployment: Rollout priorities
Zoho apps for this team:Zoho Analytics

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 ev charging operators process from "Sign host sites" to "Settle and report", 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 Contracts 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 "Sign host sites" and one for "Settle and report".
  • Going live without checking reports against numbers you already trust.

A good first win

Start with the problem that hurts most: Site deals, grid applications and installs are tracked in scattered spreadsheets. Fixing one visible problem in the first month builds trust and adoption for everything after it.

What you can measure

  • Charger uptime
  • Utilisation per charger
  • Average days from site signing to live
  • Driver tickets per 1,000 sessions

Questions about Zoho for ev charging operators

Which Zoho apps suit ev charging operators businesses?

A typical ev charging operators setup uses Zoho CRM, Zoho Contracts, Zoho Projects, Zoho Creator, Zoho Flow, Zoho Desk, Zoho FSM, Zoho Inventory, Zoho SalesIQ, 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 ev charging operators?

1. Sign host sites; 2. Plan and install; 3. Monitor the network; 4. Maintain chargers; 5. Support drivers; 6. Settle and report.

Which departments does a Zoho setup for ev charging operators cover?

A full setup covers Business Development and Site Hosts, Network Deployment, Network Operations, Field Maintenance, Equipment and Stores, Driver Support, 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 ev charging operators

  • Zoho CRM
  • Zoho Creator
  • Zoho Inventory
  • 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