Skip to main content
In regulated industries like BFSI, every customer call is a potential compliance event. Agents must make required disclosures, avoid prohibited language, follow approved scripts, and stay within the bounds of regulatory guidelines from bodies like the RBI, TRAI, and SEBI. Manually auditing even a fraction of your call volume is slow, inconsistent, and expensive. NeuronLens compliance monitoring checks every single call automatically, flags violations at the segment level, and maintains a timestamped audit trail — so you catch issues before they become regulatory problems.

​
What NeuronLens Checks

NeuronLens compliance monitoring runs five categories of checks on each processed call. You configure which checks apply to which campaigns, agent teams, or product lines.

Required Disclosure Checks

Verify that agents stated all mandatory regulatory disclosures — loan terms, interest rates, MITC, product risk warnings — within the required point in the call.

Prohibited Language Flags

Detect threatening, coercive, deceptive, or otherwise non-compliant language. Flags include the exact timestamp and transcript segment where the violation occurred.

Script Adherence

Calculate the percentage of your approved script that was covered in the call. Surface sections that agents consistently skip.

DNC Compliance

Cross-reference call records against your DNC (Do Not Call) lists and TRAI opt-out registries to verify no calls were made to opted-out numbers.

Policy Deviation Alerts

Flag calls where agents offered terms, discounts, waivers, or commitments outside what your policy authorises — before those commitments become a liability.

Audit Trail

Every compliance check result is stored with its timestamp, the triggering transcript segment, the rule it violated, and the severity level — ready for regulatory audit.

​
Configuring Compliance Rules

Set up your compliance rules in NeuronLens → Compliance → Rules → New Rule. Each rule has a type, the condition to check, the severity of a violation, and the scope (which campaigns or teams it applies to).
1

Choose the Rule Type

Select one of the five check types: Required Disclosure, Prohibited Language, Script Adherence, DNC, or Policy Deviation.
2

Define the Condition

For disclosure checks, enter the required phrases or topics that must appear in the call. For prohibited language, enter the terms or patterns to detect. For script adherence, upload or link your approved script. NeuronLens matches against the transcript semantically — you don’t need to list every exact wording variant.
3

Set Severity

Assign a severity level to violations: critical, high, medium, or low. Critical and high violations trigger immediate alerts; medium and low violations are logged for review.
4

Assign Scope

Apply the rule to all calls, specific campaigns, specific product lines, or specific agent groups. Rules can stack — a call may be evaluated against multiple rule sets simultaneously.
5

Activate the Rule

Toggle the rule to Active. NeuronLens applies it to all new calls matching the scope from that point forward, and you can retroactively run it against historical calls using the batch compliance endpoint.
Compliance rules can be configured per campaign type, product line, or agent team. A collections campaign for personal loans might require different disclosures than a credit card sales campaign — set them up as separate rule sets so each call is evaluated against the right standard.

​
Viewing Compliance Results

​
Single Call

curl "https://api.vinfer.ai/v1/analytics/compliance?call_id=call_abc123" \
  -H "Authorization: Bearer YOUR_API_KEY"

​
Response

{
  "call_id": "call_abc123",
  "compliance_score": 91,
  "overall_status": "passed",
  "checked_at": "2024-01-15T10:51:00Z",
  "violations": [
    {
      "rule_id": "rule_prohibited_001",
      "type": "prohibited_language",
      "severity": "high",
      "timestamp": "00:02:34",
      "transcript_segment": "If you don't pay by tomorrow, we will have to take legal action against your family.",
      "description": "Agent referenced action against third party (customer's family), which violates RBI Fair Practice Code guidelines."
    }
  ],
  "passed_checks": [
    {
      "rule_id": "rule_disclosure_001",
      "type": "required_disclosure",
      "description": "Agent disclosed outstanding principal amount and applicable interest rate within the first 2 minutes of the call."
    },
    {
      "rule_id": "rule_disclosure_002",
      "type": "required_disclosure",
      "description": "Agent stated the DPD (days past due) status and MITC reference correctly."
    },
    {
      "rule_id": "rule_script_001",
      "type": "script_adherence",
      "description": "Script adherence score: 87%. Agent covered all mandatory sections; skipped optional upsell section."
    }
  ]
}
​
compliance_score
integer
Aggregate compliance score for the call, 0–100. Calculated from the severity-weighted outcome of all applied rules.
​
overall_status
string
passed, failed, or review_required — based on your configured thresholds.
​
violations
array
Array of detected violations. Each entry includes the rule type, severity, the timestamp in the call, the exact transcript segment, and a plain-language description of the issue.
​
passed_checks
array
Array of compliance checks that the call passed. Useful for generating positive audit evidence, not just flagging failures.

​
Alerts and Escalations

Configure automatic alerts so the right person is notified the moment a call breaches your compliance thresholds.
Set up email notifications in Compliance → Alert Settings → Email. Choose which severity levels trigger an email, who receives it, and whether it includes the full violation detail or a summary link.

​
Audit Trail

Every compliance check result — whether passed or failed — is stored with a full audit record:
FieldDescription
call_idUnique identifier for the call
agent_idThe agent who handled the call
campaign_idThe campaign the call belongs to
rule_idThe specific compliance rule evaluated
resultpassed or violation
severitySeverity level if a violation
transcript_segmentThe exact text that triggered the result
timestampPosition in the call (HH:MM:SS)
checked_atUTC timestamp when NeuronLens ran the check
You can export the full audit trail for any date range via Compliance → Audit Trail → Export, or query it programmatically via the API for integration with your compliance management system.

​
Script Adherence in Detail

Script adherence scoring tells you not just whether an agent followed the script, but which sections they covered and which they skipped — and how consistently agents skip particular sections. Use the script adherence report (available under Compliance → Script Reports) to:
  • Identify script sections that agents routinely skip — a signal that the script may be too long, unclear, or impractical
  • Compare script adherence across agents on the same campaign
  • Track whether adherence improves after a training or script update
  • Find calls where an agent deviated from the approved script immediately before a customer complaint
NeuronLens compliance monitoring is a tool designed to help you identify potential issues at scale — it does not constitute legal compliance advice. The accuracy of automated checks depends on the quality and specificity of the rules you configure. Always consult your compliance team and legal counsel to determine the exact regulatory requirements applicable to your business, products, and geographies before relying on NeuronLens results for formal compliance reporting or regulatory submissions.