CASE · INSURANCE
From plate to issued policy, no manual intervention.
From license plate to issued policy with no manual intervention: AI document validation and issuance via API. We built the complete RCV policy activation flow for an insurer: 8-line quoters, AI document validation, and direct issuance against their core REST API.
THE PROCESS BEFORE
Activating an RCV meant re-typing, waiting, and forwarding emails
100% manual issuance
Every RCV policy was activated by hand: look up the vehicle, re-type data in the core system, wait.
Documents that bounced
ID, invoice, and certificate of origin arrived with a field mismatch and went back by email.
No traceability
Nobody knew which step an activation was at or why it had stalled.
HOW WE UNDERSTOOD IT
The bottleneck wasn't the core: it was validating documents
We mapped the activation end-to-end and found that the insurer core already exposed a REST API capable of issuing. The real problem was upstream: data arrived with a field different from the supporting document, and every discrepancy meant an email back and forth.
The opportunity: place an AI validation layer between data capture and the API, and chain the entire process into a single traceable flow that starts with a license plate and ends with a policy number.
EL FLUJO COMPLETO
De placa a póliza emitida, sin manos en el medio
Toda la activación de una póliza RCV en nueve etapas encadenadas. Cada etapa valida antes de dejar pasar a la siguiente: por eso la emisión llega limpia al core de la aseguradora.
Placa del vehículo
El operador ingresa la placaEl flujo arranca con un único dato: la placa. No hay formularios largos por delante todavía — solo el punto de entrada que dispara todo el proceso de activación de la póliza RCV.
VALIDACIÓN DE DOCUMENTOS CON IA
El documento entra, la IA lo lee y lo cruza contra el formulario
Ocho tipos de documento se validan solos. La IA extrae los campos, los compara con lo capturado y, si algo no calza, devuelve una observación en lenguaje humano — no un código de error.
recibiendo documento…
DEVELOPMENT SCOPE
What we built
- 01Multi-step quoters for 8 lines: Individual health, Group health, Auto, Travel, Home, Life, and Business.
- 029-stage RCV activation flow: plate → factory inventory → serial → data → documents → AI validation → API → policy → webhook.
- 03AI validation of 8 document types with human-language observations.
- 04Public inventory upload by factory with column mapping, deduplication, and margin-based pricing.
- 05Hard capture rules: emails ≤70 chars without accents, 4-digit economic activity code, company name without commas.
- 06Admin panel: policies with CSV export, bulk download and reprocessing; catalogs synced with Monday.com; download audit trail.
- 07Integration with the insurer REST API and webhooks to Make.com.
OUTCOMES
What changed day-to-day
Issuance with no manual intervention
The RCV policy is issued end-to-end without anyone re-typing data in the insurer core system.
Automatic validation of 8 documents
ID, certificate of origin, invoice, title, license, tax ID, income tax certificate, and bank reference validate themselves.
Zero bounced documents
Errors are caught before issuance, with a clear observation stating exactly what to fix.
Traceable process
Every activation is visible step by step; reprocessing and download auditing from the admin panel.
YOUR PROCESS IS NEXT
Does your issuance still depend on re-typing and forwarding emails?
If you have a core with an API but the process is still manual, that's exactly what we rebuild. Schedule a 30-minute assessment.