Your brokers work along with you
In the portal, a broker sees their own policies, figures and arrears. If they prefer to work in their own system, they fetch the same data through the partner API.
The screenshots come from a demo environment with fictitious names and figures. The screens are in English; the data itself (bookings, product names) is in Dutch, as at a Belgian office. Click an image to enlarge it.
The intermediary portal
You give an intermediary access from their record. They sign in with two-step verification and see only their own policies. An agent sees only what they sold themselves.
- A home page with their own figures: portfolio, lapses, annual premium and arrears, with charts.
- Their policies, with the policy record, premiums and payments, and the notes and attachments you make visible to them. You choose that per document and per note.
- Export of their policies to Excel.
- They change a customer's address, email and mobile number themselves. The customer and the broker get a confirmation, your back office a task.
- Adding documents to a policy, if that is switched on for them, and ordering printed materials.
- Marketing material per product and per language, to download after accepting the terms.
Their customers' arrears
The arrears list shows their customers' policies with an unpaid premium, the longest arrears first. They filter on the number of unpaid instalments.
- Per policy the policyholder, the premium and payment frequency, the number of instalments paid and the last period paid. From four instalments, a policy shows in red.
- An Info page with their account manager's contact details.
- An email invitation to choose their own password.
- Someone on your team can view the portal as the intermediary sees it, without changing anything. Each time, a line is added to the audit log.
The partner API
A broker with their own system fetches their portfolio directly. Through the API they see exactly what their records see in the portal.
- Keys per partner, with their own permissions, an expiry date and optionally the allowed IP addresses. A key is shown once and never stored.
- Fetching policies, insured persons, premium months, payments, arrears and documents. Personal data and payments are separate permissions.
- Requesting the changes in the portfolio: issue, status, premium, cancellation and arrears, without personal data.
- Webhooks: a short, signed notification for every change, retried for 24 hours, with a test notification.
- A sandbox with fictitious data to test an integration, reset every night.
- Documentation in four languages, with examples in curl, C#, Python, JavaScript and PHP, among others.
- Under Usage you see every request from every key.
Straight into the broker's software
We are connecting Delego to GBO cloud. Whatever changes on a policy will then also reach your broker's software, as a Telebib2 message: the Belgian standard for data exchange in insurance. Your broker no longer has to key anything in twice.
- First new business and endorsements: a new policy or a change also appears in the broker's software. In development
- Then the financial messages. In development
In short
Only their own portfolio
In the portal and through the API, a broker sees only their own policies. An agent only what they sold.
Look up and update themselves
The broker finds figures, arrears and documents themselves. An address change becomes a task for your team.
An integration to test
A sandbox with fictitious data, documentation in four languages and webhooks for every change.
Frequently asked questions
How does a broker get access?
You give them access from their record. They receive an email invitation to choose their own password, and sign in with two-step verification.
Can I see what a broker sees in the portal?
Yes. With the right permission you open the portal as they see it, without being able to change anything. Each time, a line is added to the audit log.
What does a broker need to use the API?
A key that you create for them, with the permissions you choose. In the sandbox they first test their integration with fictitious data.
Does the broker receive personal data through the API?
Only if you give them that permission: personal data and payments are separate permissions. Webhook notifications and the overview of changes never contain personal data.
Does a broker also get the data in their own broker software?
We are working on it, through a connection to GBO cloud: first new business and endorsements, then the financial messages, in Telebib2. For a broker with their own system, the partner API is already there.
Also in Delego
What is missing for your agency?
That is exactly what we want to discuss with design partners: your products, your rates, your insurers.
Talk to us