Skip to content

Software does the work. You make the call.

It reads the documents, reaches the insurers and compares the quotes. The final approval is always yours.

Lines of business

Across an intermediary's lines, in one flow.

Quoting runs for motor own damage, motor liability, liability extensions, earthquake, home, supplementary health, travel and foreigners' health. Documents, insurers and approvals follow the same flow in every line.

  • 01

    Motor own damage

    Quotes from several insurers at once, with vehicle details filled from the registration.

  • 02

    Motor liability

    Liability, short-term liability and liability extension quotes from one form.

  • 03

    Home

    Home quotes and policy tracking, together with the address.

  • 04

    Earthquake

    Compulsory earthquake insurance quotes and policy documents.

  • 05

    Supplementary health

    Supplementary health quotes and insured persons' details.

  • 06

    Travel

    Travel and foreigners' health insurance quotes.

Why

Most software in insurance intermediation is a ledger. Telesurety builds a system that does the work.

Today, staff enter the data and the software stores it. We build the opposite: software reads the document, reaches the insurers and prepares the comparison.

One request reaches all 14 connected insurers at once. Drawing: the rows of a hand-kept 14-row ledger lift off and become 14 connections on a single request node. The request reaches all of them at once, a comparison is built from the insurers that answer, and the choice stays with the user.

How it works

It reads. It understands. It prepares. You approve.

  1. 01 / 04

    Reads

    Reads the document and the insurer's response, and scores every field.

  2. 02 / 04

    Understands

    Matches common coverage names with rules and ties each field read to its place in the document; the full common coverage language is on the roadmap.

  3. 03 / 04

    Prepares

    Gets the record, the comparison or the action ready for approval.

  4. 04 / 04

    You approve

    Uncertain fields and every irreversible action wait for your approval.

Products

Products born from real work. Each one with today's status next to it.

From the operations panel to the customer app, the products in use today and in development. Each one grew out of a real workflow in a brokerage operation.

All products
  1. Operations panel, Live

    All of an intermediary's work on one screen.

    Customers and their vehicles, multi-insurer quotes, policies, renewal and new-business tracking, claim files, reports, the calendar and team work in one workspace.

    Details: Operations panel
    • Quotes from 14 insurers at once, comparison and policy issuance
    • Endorsements, renewal tracking, new-business tracking and policy import
    • Claim files: document checklist, e-mail threads and service-time tracking
    • Chat, announcements, calendar, leave and request approval flow
  2. Quick quote, Pilot

    Enter it once; insurers price at the same time.

    Customer and vehicle details are entered once; insurers price in parallel, the best offer is flagged and the policy is issued from the chosen price.

    Details: Quick quote
    • Motor liability and own-damage quotes; quote documents for liability, earthquake and health
    • Bulk quotes, comparison and printing
    • The same quote engine runs in the operations panel
  3. Registration reading, Live

    Fill it from the registration.

    Plate, chassis, document serial, make, model, model year and owner are read from a photo of the vehicle registration and filled into the form.

    Details: Registration reading
    • Text recognition fine-tuned for vehicle registrations
    • 85.7% field accuracy on real registrations
    • Runs in-house and writes nothing to disk
  4. Document management, Partly live

    Document handling inside records is live; central document management is on the roadmap.

    Every document in the record it belongs to.

    Expected-document checklists with progress, drag-and-drop upload, preview and sending by e-mail in claim files. A categorized document vault with validity dates for customers.

    Details: Document management
    • Expected-document checklist and requests for new document types
    • PDF and image preview, with who uploaded each file
    • Document vault: policy, registration, licence, ID, accident report; validity dates and expiry flags
    • Central document management (folders, versions, search, retention) is on the roadmap
  5. Customer app, Pilot

    The app's back end is live; the app is at pilot stage.

    Policies and documents in the customer's pocket.

    Policies, quote requests, claim notices and a document vault in one app. A customer's request lands in the panel, staff publish the offer, the customer chooses.

    Details: Customer app
    • One-time code and biometric sign-in
    • Policy document, emergency card, renewal request
    • Step-by-step claim notice and missing-document requests
    • Reading policy documents uploaded from elsewhere
  6. Support center, Live

    Tickets, service times and a knowledge base.

    A support portal where organizations open tickets, run by service-time targets and escalation rules.

    Details: Support center
    • Board and table views, service-time targets and escalation
    • Knowledge base, canned replies, satisfaction ratings
    • Meeting invites, planning and a shared whiteboard
  7. Channel integrations, Live

    Direct links to dealer and partner systems.

    A quote and policy API that serves a corporate partner's dealer network and connects to its ERP system, and a lead hub that forwards dealer requests to a call center and receives feedback.

    Details: Channel integrations
    • Quotes and policies from the dealer's system
    • Lead intake, routing and feedback
    • Reliable message delivery and analysis screens
  8. In-house language model, Prototype

    Ask your policy documents; get answers with sources.

    A prototype for question answering with citations over policy documents using a local language model. An in-house model adapted to Turkish insurance is at the center of our research agenda.

    Details: In-house language model
    • Answers quote the document and show the page; learning to abstain without a source is still research
    • Runs in-house; documents never leave
    • The foundation for contract intelligence and coverage comparison

Live: in daily operational use. Pilot: being tried in real work. Partly live: part of it is in daily use, the rest is in development. Prototype: a research experiment. Roadmap: in development, not yet in use.

Illustrative. Names and values shown are examples.

AI Assistant and Agents · Roadmap

An assistant that will know insurance and understand you. Its agents will do the work; the final approval will stay with you.

The assistant will run on an in-house language model of at least 12 billion parameters. It will understand your request in Turkish, answer from the policy with its source, and do the work through the panel's own endpoints with your permissions, or prepare it for your approval. Today the staff app and policy Q&A are prototypes, and server-side permission checks are live.

  • The model in-house, the data in Türkiye
  • Every answer with its source, or “not found”
  • No irreversible action without an approval card
  1. 01 / 04

    It will understand your request in Turkish

    Type a question or ask for a task: “When does this customer's own-damage policy expire?” or “Prepare an own-damage quote request for this plate.” The assistant will work out the request and the record it refers to; if it fits more than one record, it will ask instead of guessing. It will work by text first; in-house Turkish speech-to-text is a planned research topic.

  2. 02 / 04

    It will find the answer at its source

    The in-house model of at least 12 billion parameters will know insurance terms; the facts themselves will come from the policy, the coverage terms and the agency's own records. Every answer will come with the page or record it rests on; if the data is not there, the assistant will say it could not find it.

  3. 03 / 04

    Agents will work through the panel's endpoints

    Every job the panel does is already an API endpoint. The agents will use those endpoints as tools, with your permissions, so no separate business logic is written for them. The panel's rules, not the model, will decide which insurers to call; premiums will come only from the insurer's response.

  4. 04 / 04

    Irreversible work will wait on an approval card

    Sending a quote, issuing a policy or cancelling will first show a card stating who it is for, which insurer and which premium. Nothing will happen until you tap it, and the action will be logged as done through the assistant with your approval.

  5. Illustrative. Names and values shown are examples. An assistant that will know insurance and understand you. It will understand your request in Turkish, It will find the answer at its source, Agents will work through the panel's endpoints, Irreversible work will wait on an approval card.

Today

Where we are today.

  • In use

    Live

    The operations panel is used every day in a real intermediary operation.

  • Insurer connections

    14

    insurers connected via web services: quotes, policy import and documents.

  • Document reading

    85.7%

    field accuracy on real vehicle registrations, measured on real documents.

  • Data

    Türkiye

    Personal data is processed on in-house servers in Türkiye.

  • Decisions

    People

    Uncertain fields and irreversible actions wait for human approval.

Platform

One workspace: quotes, policies, claims and documents.

The operations panel brings customers, quotes, policies, renewals, claims, reports, the calendar and team work together in one place.

Workspace

Menus shaped by role and department, permission levels, Turkish and English interface.

Connections and API

Web service connections to 14 insurers. A quote and policy API for corporate partners is live in a dealer network.

Illustrative. Names and values shown are examples.

Three foundations. One goal: less manual entry.

  • Built in the field

    The product was developed in the daily work of a live intermediary operation. The live modules replace a real workflow in that operation.

  • In-house AI

    The models that read documents run in-house. Customer data is never sent to an outside AI service.

  • Driven by research

    We work on document intelligence, confidence calibration and a coverage ontology, and measure the results.

Trust

Built to be trusted.

Personal data is processed on in-house servers in Türkiye. Every field read shows its place in the document; premium, insurer connection and permission decisions are never left to AI.

  • Data protection and in-house models

    Personal data is never sent to an AI service outside the organization.

  • Human approval

    Fields below the confidence threshold go to a person; AI never starts a binding action.

  • Outputs with sources

    Every field read shows its place in the document. In the Q&A prototype, each answer comes with the page it relies on.

    Read our trust principles

How we start

From demo to rollout in four steps.

Request a demo
  1. 01

    Demo call

    We show the products with sample data, then map your current workflow and the task that takes the most time.

  2. 02

    A written goal

    If you want to continue, we set a measurable goal, such as less manual entry.

  3. 03

    A trial on your documents

    Within a scope we agree on together, we run the platform on your documents and your workflow.

  4. 04

    Measure and roll out

    We compare the result with the baseline and decide together which parts to roll out.

Questions

Frequently asked questions

Where is our customer data processed?

Personal data is processed by models running on in-house servers in Türkiye; it is never sent to an outside AI service.

Which insurers do you connect to?

Today we have web service connections to 14 insurers. We share the list in the demo call.

What happens if the AI misreads a field?

Every field comes with a confidence score. A field below the threshold is never written to the record on its own; it goes to you for approval.

Do I have to give up my current agency software?

No. A general API that lets you use these capabilities from your own software is on our roadmap. A quote and policy API for corporate partners runs today.

How does a demo work?

We show the products with sample data, following your workflow, and say plainly where each one stands today. If you want to continue, we write down a measurable goal, try the platform on your documents and measure the result together.

How is pricing set?

We discuss the pricing model in the demo call, based on your needs.

Demo request

See Telesurety in your own workflow.

In the demo we show the products with sample data, following your workflow. If you want, the next step is a trial on your own documents, within a scope we agree on together.

  • 01A demo that follows your workflow
  • 02Each product's current status, in plain words
  • 03Your customer data stays in-house and in Türkiye