01
Complaint complexity
A pilot can define how uncertain outputs reach a reviewer. Confidence-based routing to reviewers is not built.
Financial services / pilot use cases
Test complaint categories against your rules
Gyde can test complaint category suggestions against your own categories and count the errors that matter to your team. The US test used real public complaints; the India preview used synthetic complaints. Statement analysis has less evidence: the current test covers transaction labels, not statement-level or borrower outcomes.
These pilots scope suggestions for complaint and statement workflows. Your institution defines review steps and owns consequential decisions.
GYDE / INFERENCEILLUSTRATIVE PILOT FLOW
ONE WORKLOAD / PILOT PATH
01WorkloadTask + test cases
02ModelQualified candidate
03PolicyAllowed route
04ServingApproved capacity
05EvidenceOutcome + cost
Decision: proceed, redesign or stop
01Complaint operations
Start with the categories your team already uses.
Keep each regulator's required categories. Map them to shared reporting categories only when that helps your team compare results.
01Complaint→︎
02Category suggestion→︎
03Review step to agree→︎
04Case system
02Statement analysis
Check line labels before relying on a summary.
The volunteer test measured transaction labels only. A pilot must check material EMI and bounce events, income errors and the summary a reviewer would see. Statement-level outcomes remain unproven.
01Statement→︎
02Transaction labels→︎
03Calculated summary→︎
04Reviewer step to define
03Exception design
Decide where a person needs to review.
02
Transaction ambiguity
Unfamiliar merchants, unclear income and material obligation lines need manual checks.
03
Regulatory variation
Taxonomy, language, location, retention and review rules are set for each institution and jurisdiction. A demo does not establish compliance.
04Pilot design
Measure the case that reaches the reviewer.
Use consented, de-identified representative data in an approved location, blind domain adjudication, a lender baseline and a frozen test split. Measure cost per correctly processed case. Do not send customer records to the marketing form or an unapproved labeller.
See Gyde's broader financial-services work?Buyer questions
Questions to settle before a pilot.
Can the model make a credit decision?
No. This pilot scope covers categorisation, extraction and triage suggestions with human review. The lender owns decision rules and consequential actions.
Do you have proven accuracy on our lender data?
No. That is a primary question for the pilot's representative, permissioned test set.
Can we keep our own complaint categories?
Yes. The pilot starts with your categories, including those required by a regulator. Map them for shared reporting only where useful.
What is the evidence for statement analysis?
The current evidence is a small exploratory volunteer-statement line-label check with weak lending-critical coverage. Statement-level income, obligation and borrower outcomes still need a lender pilot.
Gyde Inference pilot
Start with a workload you can measure.
Describe the task, data boundary and decision you need to make. We will scope the test and operating conditions together.
Discuss a workload Do not submit sensitive records through the marketing form.