A telecom operator doesn't employ most of the people activating its SIMs. It contracts them — through DSAs (direct selling agents), franchisee outlets and third-party field agencies — and pays per successful activation, per FTTH install, per collection closed. That arrangement scales distribution fast. It also means the operator has almost no first-hand visibility into what its largest field workforce is actually doing.
This is a structurally different problem from FMCG or pharma field force management, where the people on the ground are the company's own employees. In telecom, feet-on-street is mostly someone else's payroll, working under a payout formula that rewards volume — which is exactly the condition under which ghost visits, mis-sold plans and fabricated activations show up.
Why telecom's field-agent problem is different
Three things make telecom feet-on-street management harder than a typical field sales rollout:
The agents aren't employees. A DSA or franchisee outlet works for the operator, but also often for a competing operator down the street. There's no employment relationship to lean on for compliance — only the terms of the agency contract and whatever the field app can verify.
Payment is per-transaction, not per-visit. A pharma MR gets measured on call quality and coverage. A telecom DSA typically gets paid a per-SIM-activation commission (published operator commission structures put this in the roughly ₹100–400 range, varying by plan tier) or a fixed FTTH install fee. That payout structure creates a direct financial incentive to inflate activation counts — which is a fraud-prevention problem, not just a productivity one.
Regulatory exposure sits with the operator, not the agent. Under DoT's Subscriber Verification norms, an improperly verified SIM activation is the operator's liability, not the DSA's. If a franchisee activates a connection against a fake or reused KYC document, the fine and the compliance flag land on the telecom company.
The three field-agent models telecom actually runs
Model 1: DSA agents for prepaid/postpaid SIM activation. Individual or small-team agents working retail counters, kirana corners and street kiosks, activating connections against a per-SIM payout. High volume, high turnover, thin per-transaction verification.
Model 2: FTTH installation and service technicians. Franchisee or contracted technicians visiting homes to install fibre connections, run ONT/router setup, and close service tickets. Longer visit duration, higher-value transaction, more complex proof-of-work requirements (signal readings, photos of the installed equipment, customer sign-off).
Model 3: Franchisee outlet field collections and retention agents. Agents visiting existing subscribers for plan upgrades, bill collection on postpaid accounts, or retention calls ahead of a competitor port-out. Lower per-visit payout, high volume, and the segment most exposed to "visit logged, call never made" fraud because there's no physical asset changing hands to prove otherwise.
Most operators run all three simultaneously across different franchisee layers, often with three different reporting spreadsheets feeding into a manual reconciliation process once a month. By the time a fraud pattern shows up in that reconciliation, the payout has already gone out.
Ghost visits and mis-sold plans: what the data actually looks like
A "ghost visit" is a field activity logged in a franchisee's own reporting tool — usually a shared Excel sheet or a WhatsApp photo — that never happened, or happened somewhere other than the claimed address. In DSA networks running on unverified self-reporting, this isn't a rare edge case; it's a predictable outcome of a payout formula that rewards volume over verification.
Mis-sold plans follow the same root cause from a different angle: an agent paid on activation volume has no incentive to explain plan terms accurately, and no supervisor is present to catch it. The fix isn't a training module. It's making the sale itself produce a verifiable record — geo-tagged, timestamped, with the customer's confirmation captured on the same device, in the same visit.
What geo-verified activation proof actually requires
For SIM activation and FTTH installs specifically, "verified" needs to mean more than a GPS pin:
- Geo-fenced activation — the transaction is logged only when the agent's device is physically inside the claimed outlet or customer address radius, not filed later from a different location.
- Timestamped, non-editable photo evidence — of the KYC document at the point of capture, the installed ONT/router, or the signed activation form — not a gallery upload that could be from any date.
- Dwell time thresholds — an FTTH install logged in 90 seconds is not a real install. A minimum plausible duration per transaction type catches the fastest fraud pattern outright.
- Payout tied to the verified event, not the claimed one. If the activation record fails geo-fence or dwell checks, it doesn't auto-qualify for commission — it routes to a review queue instead.
None of this is exotic. It's the same GPS-truth-test discipline that FMCG distribution teams use to catch phantom beat calls, applied to a payout-per-transaction model instead of a call-per-outlet model.
Where this fits alongside existing systems
Most telecom operators already run a CRM or billing system (often a heavyweight platform like a custom OSS/BSS stack) that owns subscriber records and provisioning. The field-agent verification layer doesn't need to replace that — it needs to sit in front of it, capturing the field transaction with proof before it ever reaches the billing system as a completed activation. Trying to bolt fraud checks onto a billing platform after the fact is usually why operators end up doing monthly reconciliation instead of real-time flagging.
An offline-first mobile capture layer matters more here than in most field-ops contexts, because DSA outlets and FTTH install locations regularly sit in exactly the low-signal areas telecom is trying to serve — the app has to work as well on a franchisee's entry-level Android device in a Tier 3 town as it does in a metro showroom.
Kinematic Field Force handles this kind of geo-verified activity capture — geo-fenced check-ins, timestamped photo evidence and dwell-time enforcement — across large distributed agent networks, and the Lead Management layer gives franchisee retention and upsell agents a proper pipeline instead of a WhatsApp thread. If you run a DSA or franchisee field network and want to see what geo-verified activation proof looks like against your own outlet list, book a demo.
Field Force · Lead Management · Supply Chain — one mobile-first platform, live in 48 hours.
Book a demo →
