Solutions
Shaped by the work, not by the type of intermediary.
One platform, several doors. Today: the workspace and the API open to corporate partners; the AI assistant and the general API are on the roadmap.
Highlights
- Operations panel
- Live
- Used in the daily work of a real insurance intermediary. The workspace's collections and central document modules are on the roadmap.
- Insurers connected for quotes
- 14
- A request goes to the web services of every connected insurer offering the line, at the same time.
- General API
- Roadmap
- Planned for agencies and agency software vendors; a quote and policy API for corporate partners is live in a dealer network today.
Telesurety is one platform. Agencies, brokers, agency software vendors and channels each come in through the door that fits their work; software reads the document and goes to the insurers, while premium, insurer and permission decisions stay with rules and people. For every door, we state separately what is live today and what is on the roadmap.
Four doors
One platform. Each intermediary comes in through its own door.
Illustrative. Names and values shown are examples. One platform. Agency: the workspace, Broker: comparison, Software vendor: the API, Channel: dealers, fleets, rentals.
- 01 / 04
Agency: the workspace
Staff open the request in the workspace. Software reads the registration, the request goes to every connected insurer offering the line at once, and quotes come back side by side. Staff choose and approve.
- 02 / 04
Broker: comparison
A broker needs different insurers’ coverages measured on one scale. Comparison that translates coverages into a common language, and an assessment report that cites its sources, are on the roadmap; today quotes come side by side in the workspace.
- 03 / 04
Software vendor: the API
An agency software vendor wants the same capabilities inside its own product: document reading, multi-insurer quoting, coverage comparison. This general API is on the roadmap; today the same layer runs connected to a corporate partner’s system.
- 04 / 04
Channel: dealers, fleets, rentals
The dealer network’s system sends quote and policy requests to the API and takes the result back into its own records; dealer leads reach the call center through a single entry point. Issuance follows agreed rules; anything outside them waits for staff approval.
- 01 / 04
Agency: the workspace
Staff open the request in the workspace. Software reads the registration, the request goes to every connected insurer offering the line at once, and quotes come back side by side. Staff choose and approve.
- 02 / 04
Broker: comparison
A broker needs different insurers’ coverages measured on one scale. Comparison that translates coverages into a common language, and an assessment report that cites its sources, are on the roadmap; today quotes come side by side in the workspace.
- 03 / 04
Software vendor: the API
An agency software vendor wants the same capabilities inside its own product: document reading, multi-insurer quoting, coverage comparison. This general API is on the roadmap; today the same layer runs connected to a corporate partner’s system.
- 04 / 04
Channel: dealers, fleets, rentals
The dealer network’s system sends quote and policy requests to the API and takes the result back into its own records; dealer leads reach the call center through a single entry point. Issuance follows agreed rules; anything outside them waits for staff approval.
- Illustrative. Names and values shown are examples. One platform. Agency: the workspace, Broker: comparison, Software vendor: the API, Channel: dealers, fleets, rentals.
Agencies
The main workspace for small and mid‑sized agencies.
Example flow
A client sends a photo of the vehicle registration for a motor own-damage quote. Staff fill the quote form with “Fill from registration”, check any uncertain field against the image cut from the document, and send the request to every connected insurer offering the line at once. Quotes come back side by side, a summary of the differences is written in sentences staff can read to the client, and the chosen quote becomes a policy record in one step.
Need
- Stop retyping the same data into every insurer's portal
- Stop typing registrations and policies by hand
- Give customers a comparison they can understand
On the platform
Brokers
Placement and quote evaluation on the client's behalf.
Example flow
To evaluate quotes on a client's behalf, a broker enters the request once, and it goes to every connected insurer offering the line at the same time. Today the selected quotes open side by side in the workspace, coverage by coverage; “Show differences only” hides rows that are identical across all offers, and any coverage the rules do not recognise keeps the insurer's own wording. A common coverage language that links every difference to its line in the insurer's document, and broker modules, are on the roadmap.
Need
- Compare insurers' coverages on the same scale
- Prepare evaluation reports with sources
- Find clauses in agreements and specifications quickly
On the platform
Agency software vendors
A channel, not a competitor.
Example flow
With the planned general API, when an agency using the vendor's product uploads a registration photo, the product will send the document to the API. Fields will come back with confidence scores and their location in the document; any uncertain field will be marked as awaiting approval, and the agency's team will approve it. The same record will request quotes from connected insurers in one call, and the premium will always come from the insurer's response.
Need
- Add document reading and comparison to their own product
- Avoid building insurer connections one by one
- Keep customer data in Türkiye
On the platform
Channels
Car dealers, fleet and leasing companies.
Example flow
A car is sold at a dealership and the dealer network's system sends a quote request to the API. The vehicle code is mapped to the industry's standard vehicle catalogue, motor liability and own-damage quotes are collected from connected insurers at once, and staff review them in the operations panel and issue the policy. The result is written back to the dealer's own records; in one partner flow, issuance starts automatically for motor liability requests that meet agreed rules, and waits for staff approval when the insurer's amount exceeds the partner's.
Need
- Start the insurance process from their own system
- Get quote and policy results back into their own records
- One workflow between the intermediary and the channel
On the platform
Use cases
What runs behind the doors today.
- 01
Checking approved policies at month end
At an agency, staff pick an insurer that offers policy transfer and a date range on the Transfer screen. The agency's approved policies at that insurer come back in a read-only list; the list opens no record, ID numbers are shown masked, and the list is cleared when staff leave the page. Staff compare it with the workspace records and enter any missing policy from the Policies screen.
- 02
Bulk health quotes for a corporate client
A corporate client asks for health quotes for its foreign employees living in Türkiye and sends the list as an Excel file. Staff upload the list and add the risk address; rows are checked first, each person is priced separately, and a notification arrives when the list is complete. Insurers' quote numbers and premiums go back to the client in one Excel file.
- 03
Dealer leads followed up with the call center
Own-damage, motor liability, earthquake and home leads from dealers arrive through a single entry point, and a lead sent again with the same reference is set aside as a duplicate. Leads are passed to the call center, and the call outcome and agent details flow back to the hub. Management sees on one dashboard which dealers' leads turned into policies and which entries need fixing.
How we start
From demo to rollout.
Whichever door you come through, the first step is the same: seeing the products with sample data, following your own workflow.
- 01
Demo request
On the form you choose your organization type: agency, broker, agency software vendor or channel. If you like, you also tell us which task takes the most time today.
- 02
Demo call
We show the products with sample data, following your workflow. We say plainly where each product stands today, and we discuss roadmap items as roadmap.
- 03
A written goal
If you want to continue, we set a measurable goal, such as less manual entry.
- 04
A trial on your documents
Within a scope we agree on together, we try the platform on your documents and your workflow. We compare the result with the baseline and decide together which parts to roll out.
Questions
Frequently asked questions
Which door fits us?
Your work decides the door, not your type of organization. An agency running daily quote, policy and claims work comes in through the workspace, which is live today. A dealer, fleet or leasing company that wants to start the insurance process from its own system comes in through channel integration, live today in a dealer network. For a broker who wants to compare coverages on one scale, the common coverage language is on the roadmap, as is the general API for a software vendor that wants the same capabilities in its own product. In the demo request you choose your organization type, and in the call we look at it together through your workflow.
What is live today, and what is on the roadmap?
Live: the operations panel, web service connections and parallel quotes with 14 insurers, registration reading, a quote and policy API connected to a dealer network, and the dealer lead intake hub. The customer app is in pilot, and policy Q&A is a prototype. A model that maps all coverage wording to one common language, contract intelligence, the AI assistant and a general API open to agencies and software vendors are on the roadmap.
Does customer data leave Türkiye?
No. Customer data and the models that process it run on servers in Türkiye; personal data is never sent to an AI service outside the organization. An outside model may be used only with anonymized or synthetic data, to generate training examples.
Do we have to give up our own software?
The aim is that you will not have to. A general API that lets you use these capabilities from your own software is on the roadmap. The working example today is on the channel side: a dealer network's system sends quote and policy requests to the API and takes the result back into its own records.
Is a person always the final approver?
Uncertain fields and irreversible actions wait for human approval; a field below the confidence threshold is never written to the record on its own. Rules decide what goes to which insurer, and the premium comes only from the insurer's response. On the channel side there is a rule-based automatic step: in one partner flow, issuance starts automatically for motor liability requests that meet agreed rules. This step uses no AI; when the insurer's amount exceeds the partner's, issuance waits for staff approval, and every issued policy appears in the operations queue.
Can we connect our dealer, fleet or leasing system?
The flow that takes in requests and writes results back runs today in live integrations built for specific corporate partners. A channel and partner gateway that generalizes it is planned: it will take requests from dealer and partner systems, write results back to them and offer a quote widget you can embed in your own pages. We can discuss the scope in a demo call.