Застраховай ме · Case study

The problem

Insurance runs on PDFs and deadlines.

Every new policy means typing the same fields (policy number, client, car, dates, premium) into a spreadsheet. Every policy that's about to expire means somebody has to notice, find the phone number, and send the reminder before it lapses.

What we built

Intake. Review. Sync. Remind. One panel.

The operator uploads a PDF; the system extracts the fields and shows them for confirmation. Once saved, the record syncs to Google Sheets. When the renewal window opens, Mobica sends the SMS (or Viber with SMS fallback) from a secured cron endpoint.

Next.js PDF extraction Google Sheets CSV fallback Mobica SMS Viber API Cron dispatch

Daily workflow

Load, check, save, sync, send.

Open Прием на PDF. Upload the policy.
Review the extracted fields. Correct anything the PDF hid from the extractor.
Pick the reminder channel (sms, viber, or none) and the template.
Save. The record appears in the dashboard's priority queue.
Press Synchronise Sheets. Row lands in Google Sheets.
When ready, press Send reminders. Or let the cron endpoint fire.

The dashboard

Priority first. Admin second.

The front page answers the questions the broker actually has in the morning.

What's due. What's missing. What's blocked.

Active policies, renewals due in 30 days, records ready to send now, missing phone numbers, missing templates, and the review queue, all on one screen, all sorted by what to fix first.

Priority counts and signals at a glance.
Archive, restore and delete from the row itself.
Compact mode for quick triage from a laptop.

Results

What changed.

~95%

of policy fields filled by extraction, not typing

0 missed

renewals since the cron endpoint went live

SMS + Viber

delivery via Mobica, with SMS fallback built in