Clients stopped calling. The portal answered every question.

Rajan Krishnamurthy runs ShieldForce Security Solutions, a Chennai-based security services company with 22 active sites across 8 corporate clients. Each client has between 2 and 5 sites — a mix of IT parks, manufacturing plants, and financial offices.

Every month, Rajan spent the better part of a working day compiling incident reports for his clients. Each client had their own format preference. Two wanted Excel. Three wanted PDF. One wanted a narrative summary email alongside the data. Two asked for site-specific breakdowns only — they didn't want to see incidents from their other locations in the same report.

Beyond the monthly reports, the calls were the real problem. Roughly three clients called every month asking about a specific incident: when it happened, who responded, what the resolution was. Rajan would have to search through a WhatsApp group history that sometimes stretched back weeks, find the relevant message thread, cross-reference with his supervisor's notes, and come back to the client — sometimes a day later.

One enterprise client raised the reporting issue in a quarterly review. They wanted SLA tracking — response times, escalation frequency, closure rates. Rajan had no way to produce that from WhatsApp history without building a spreadsheet from scratch.

Rajan's primary requirement was client-facing: he needed to stop being the middleman between his operations data and his clients. The client portal in SentinelIQ — scoped per client, showing only their sites — was the feature that made the decision straightforward.

He also needed the reporting to be automatic. He wasn't going to rebuild his operations process around a new tool only to still spend the same day each month in Excel. SentinelIQ's export — filterable by site, by date range, by incident type — would eliminate the manual compilation step entirely.

The WhatsApp reporting flow for field staff was the third factor. ShieldForce's security personnel work rotating shifts across different sites. Training them on a new app was impractical. Several of them operated in areas with poor data connectivity and preferred SMS-like simplicity. WhatsApp worked. That requirement was non-negotiable.

Rajan spent an afternoon setting up his 8 clients and 22 sites. He assigned each client to their respective sites and sent portal login links to the primary contact at each client organisation.

Three clients logged in within 24 hours of receiving the link. Two of them called Rajan — not to ask about an incident, but to say they could see everything they needed and hadn't realised the data was this clean.

Field officer onboarding happened site by site over one week, during shift handovers. Supervisors introduced the WhatsApp flow. Most field staff were submitting structured reports within their first shift.

The first month-end report cycle came 18 days after deployment. Rajan logged into SentinelIQ, filtered by client, exported PDF. Eight reports generated in under 25 minutes total. He sent them all before noon. No client called to ask for changes. Two clients responded with a thank-you.

The monthly report compilation that used to consume most of a working day is now a 25-minute task. Rajan considers that a conservative estimate — as the team gets more comfortable with the export filters, he expects it to drop to 10.

The client calls asking about specific incidents stopped almost immediately after portal access was provisioned. Clients now look up incidents themselves. When they do call, it's to discuss a pattern they've noticed in their own data — a more productive conversation than chasing down a WhatsApp message thread.

The enterprise client that had raised SLA tracking in the quarterly review received their first SLA compliance report 30 days after deployment. Response time averages by site. Escalation frequency. Closure rates. Rajan sent it as a one-page export directly from SentinelIQ.

That client expanded their contract two months later — two additional sites added to their ShieldForce agreement. Rajan attributes the renewal directly to the visibility the portal created. The client could see that the team was responding, escalating when needed, and closing incidents properly. The data made the case.