← Agent catalogue

AI Agent Profile · LendingIQ · Bengaluru

CX Strategy Officer AI

Invoked via: internal orchestration APIRuntime: AWS Bedrock · ap-south-1Model: Claude Sonnet 4Context window: 200K tokens

DivisionCustomer Marketing

Resume

What this agent does

The CX Strategy Officer AI reads the customer experience data — funnel drop-offs, NPS scores and verbatims, grievance patterns, and journey stage performance — diagnoses the root causes of friction and dissatisfaction, benchmarks LendingIQ's journey against NBFC and fintech standards, designs the NPS improvement strategy, and specifies the personalisation operations that tailor the customer experience by segment. It gives the human CX Head the analytical infrastructure to make faster, evidence-based decisions about the customer journey. It does not contact customers, manage grievances, or implement journey changes.

Primary functions

Drop-off Root Cause Analysis

Weekly and on funnel anomaly alert

Invoked when: weekly funnel data available, a drop-off spike is detected at any journey stage, or a new channel or segment shows unexpectedly low conversion

  • Reads the stage-wise funnel data — applicant volume, conversion rate, time-in-stage, and exit reason where captured — and diagnoses the specific stage where the most volume is being lost and the most likely cause of that loss, distinguishing between journey design friction (a step that is genuinely too hard), product-market mismatch (borrowers who start the journey but are not eligible or interested enough to complete it), and operational friction (process delays or errors that cause abandonment).
  • Cross-references funnel drop-off patterns with NPS verbatims and grievance data from the same time period — a drop-off spike at the VKYC stage that coincides with NPS verbatims mentioning "video call keeps cutting out" and grievances about "KYC technical issues" triangulates to a VKYC technical problem, not a journey design issue. The root cause diagnosis uses all three data sources, not just funnel numbers.
  • Proposes specific, testable interventions for each diagnosed drop-off — the intervention type matched to the root cause: a journey design change for friction, an eligibility pre-screen for product mismatch, an ops process fix for operational friction. Does not implement changes; produces the intervention specification for the Onboarding Head AI and product team to build and test.
Output: Drop-off root cause report — stage-wise funnel analysis, root cause diagnosis per major drop-off point (design / product-market / ops), supporting evidence from NPS verbatims and grievances, and proposed intervention specification for each diagnosed cause.

Journey Benchmarking

Quarterly and on major journey change

Invoked when: quarterly CX review, new competitor journey is launched, or LendingIQ is considering a major journey redesign and external benchmarks are needed

  • Reads LendingIQ's journey performance metrics alongside available NBFC and fintech benchmarks from the CX benchmark corpus — application-to-sanction TAT, VKYC completion rate, disbursement-to-customer-confirmation time, grievance resolution rate and time — and produces a gap analysis showing where LendingIQ's journey is ahead of, at, or behind benchmark performance.
  • Identifies the journey dimensions where LendingIQ has the largest opportunity relative to benchmark — because improving a metric that is already at best-in-class creates minimal competitive differentiation, while closing a significant gap in a metric that borrowers care about creates real loyalty impact. The benchmarking report prioritises by opportunity size and borrower-stated importance (from NPS driver analysis), not by absolute metric gap.
  • Cannot access competitor internal metrics; benchmarks are drawn from published industry data, regulatory disclosure data, and industry research in the CX benchmark corpus. Where competitor data is not available for a specific metric, the gap is labelled as unknown rather than estimated.
Output: Journey benchmarking report — LendingIQ's performance vs benchmark on each measured journey dimension, gap magnitude and direction, opportunity prioritisation by NPS driver importance × gap size, and a benchmark-grounded target for each dimension the human CX Head can use to set improvement goals.

NPS Strategy

Monthly analysis and quarterly strategy cycle

Invoked when: monthly NPS data available, quarterly NPS strategy review due, or NPS drops materially triggering an immediate diagnostic

  • Reads the NPS scores — overall and by touchpoint (application, VKYC, sanction communication, disbursement, first EMI, customer service interaction) — and the verbatim responses, categorising verbatims by theme (speed, transparency, staff behaviour, digital ease, communication clarity) to identify which touchpoints and themes are driving promoter vs detractor outcomes.
  • Identifies the highest-leverage NPS improvement opportunities: the touchpoints where LendingIQ has the most detractors and where the verbatims cluster around a specific, addressable issue. A touchpoint with many detractors citing "I didn't know what was happening with my application" is an addressable communication design problem. A touchpoint with detractors citing "the interest rate was too high" is a product and pricing issue outside the CX strategy's scope to fix.
  • Designs the NPS improvement strategy — which touchpoints to focus on, what specific interventions address the identified verbatim themes, what the target NPS is per touchpoint, and how to measure whether interventions are working. Explicitly distinguishes CX-fixable NPS drivers (communication, speed, digital ease) from product-fixable drivers (pricing, eligibility) and commercial drivers (competitors offering better terms).
Output: NPS strategy brief — score and verbatim analysis by touchpoint, driver categorisation (CX-fixable vs product-fixable vs commercial), top 3 highest-leverage intervention opportunities, specific intervention design for each, target NPS per touchpoint, and measurement framework for tracking improvement.

Personalisation Operations

Triggered at segment review or product launch

Invoked when: new borrower segment is being served and the journey needs to be tailored, or CX data shows that a standard journey is performing poorly for a specific segment

  • Reads the segment-wise funnel and NPS data — where specific borrower segments (first-time MSME borrowers, rural borrowers, repeat borrowers, gig-economy borrowers) are showing different conversion, TAT experience, or NPS scores than the overall population — and identifies the specific journey stages where the standard experience is mismatched to the segment's needs or capabilities.
  • Designs a personalisation specification for each segment variant: what changes to the journey flow, communication language, channel preference, and support touchpoints would make the experience more appropriate for that segment without creating an operationally unmanageable proliferation of journey variants. The specification is a design document for the Onboarding Head AI and product team to implement and test.
  • Designs the personalisation trigger logic — what data signals at or before the point of application identify a borrower as belonging to a segment that benefits from a variant journey. For example: first-time applicant + rural PIN code + vernacular language selection → route to the assisted-journey variant with proactive support prompts rather than the self-serve digital journey.
  • Cannot implement personalisation in live systems, configure A/B test variants, or make changes to the production journey. The personalisation spec is handed to the product and technology team for implementation, and tested in staging before going live.
Output: Personalisation operations specification — segment-wise journey variant design with specific changes to flow, language, channel, and support touchpoints, personalisation trigger logic for each variant, the data signals that identify segment membership at application, and a staged rollout plan for the human CX Head to review and approve before implementation.

Knowledge base

Funnel & Journey Analytics Data

Stage-wise conversion, drop-off, time-in-stage, channel and segment breakdown. Injected as structured export at invocation — the primary data source for drop-off and journey analysis.

NPS / CSAT Survey Data

Score distributions, verbatim responses, touchpoint ratings, and historical NPS trend. The voice-of-customer layer that explains why the funnel numbers are what they are.

Grievance & Complaint Data

Volume, category, resolution time, and repeat rate for all customer complaints. Used to corroborate funnel and NPS signals and identify operational issues before they become systemic.

CX Benchmark Corpus (RAG)

NBFC and fintech CX benchmark data, journey best practice, RBI's fair practice guidelines on customer communication, and consumer experience research in the Indian lending market.

Segment Profile Data

Borrower segment characteristics — channel preference, digital literacy signals, language, geography, and loan purpose — used for personalisation trigger design.

CX Strategy Knowledge

Pre-training knowledge of customer experience design, NPS methodology, personalisation frameworks, and digital lending CX best practice in the Indian market up to knowledge cutoff.

Hard guardrails

Will notContact customers — no outbound calls, messages, or communications of any kind. All customer-facing interactions are managed by human CX and customer service staff.
Will notHandle or resolve escalated grievances. Individual grievance management requires human judgment, empathy, and authority to make commitments. The agent analyses grievance patterns; the CX team resolves individual cases.
Will notImplement journey changes in live systems. Every journey design recommendation is a specification for the product and technology team to build, test, and deploy — with human CX Head approval before it goes live.
Will notRecommend NPS improvement strategies that require the agent to interact with customers directly. All NPS-driven interventions are implemented by human teams or by approved automated systems — not by this agent acting autonomously in the customer relationship.

Known limitations

NPS verbatim analysis is bounded by what customers write or say. Borrowers who are dissatisfied but do not respond to NPS surveys — a particularly common pattern in rural and semi-literate borrower segments — are invisible to verbatim-based driver analysis. The NPS data reflects those who respond, who may systematically differ from those who do not.Supplement NPS with active feedback capture at high-friction journey stages — a simple 2-question in-app prompt immediately after VKYC completion or sanction communication, where the interaction is fresh, captures feedback from borrowers who would not respond to a later NPS survey.
Journey benchmarks are lagged and may not reflect current best-in-class practice. Published industry benchmark data is typically 6–12 months old by the time it is available. The benchmark corpus must be updated annually to reflect current NBFC and fintech journey standards, which evolve rapidly.Commission an annual mystery shopping exercise across 4–5 peer NBFCs and digital lenders, conducted by the human CX team, to capture current competitor journey standards that are not available in published data. This primary intelligence supplements the published benchmark corpus.
Personalisation trigger logic depends on the quality of segment metadata captured at application. If language preference, digital literacy signals, or geography-based segment indicators are not consistently captured in the origination data, the personalisation triggers cannot be applied reliably — and the segment variant journey is applied to the wrong borrowers or not applied at all.Define mandatory segment signal capture fields in the origination flow — language of application, device type, channel, and assisted vs self-serve completion mode. These signals are available at the moment of application without requiring any additional customer input and are the foundation of reliable personalisation trigger logic.
Agent Profile · CX Strategy Officer AI · LendingIQ · BengaluruLast updated April 2026 · For internal use

Important Reads

Learn more about how to deploy CX Strategy Officer AI to your lending workflow.