Catch and qualify enquiries
LiveBring your book across in an afternoon.
Export from OpenGI, Applied Relay or a spreadsheet and hand the file over. Columns, dates, policy types and consent flags are worked out for you, and you review the mapping before a single record is written.
- SOURCE
- opengi-export-2026-07.xlsx · 1,842 rows
- POL_TYP
- → Policy type · 7 codes mapped to 5
- INFERRED
- RNW_DT
- → Renewal date · DD/MM/YYYY
- INFERRED
- MKT_OK
- → Marketing consent · Y/N
- INFERRED
- STATUS
- Nothing written yet
- HELD
Example data, fictional.
How it works
Smart importer, step by step.
Whatever your system exports.
CSV, XLSX and XLS, with the real format read out of the file itself, so a mislabelled export still lands correctly. Exports from OpenGI and Applied Relay are recognised by their shape, so a file you have produced a hundred times is understood on the first upload.
The mapping is the work. We do the mapping.
Working out that a column called POL_TYP holds policy types, and that its seven codes mean five things, is the part that costs a day of somebody’s life. That inference happens for you, on the columns and on the values inside them. The vocabulary it maps into is the ordinary Irish and UK one: motor, home, health, travel, commercial vehicle, motor fleet, commercial combined, farm, public and employers liability, combined liability, professional indemnity, medical malpractice, property owners, office, shop, contractors all risks, cyber, pension and income protection. So a farm combined lands as farm rather than as a variant of something else.
Nothing is written until you approve it.
The proposed mapping is shown back to you before any record enters the book. You correct anything wrong and approve it. There is no version of this where an import silently writes a thousand rows into the wrong fields.
Dates and consent come across too.
Renewal dates are parsed into real dates, not left as strings, and marketing consent flags are carried into per-channel consent records. Those are the two things most likely to be dropped in a migration, and the two you are most likely to be asked to evidence later.
Works with
The same client record, handed to the next capability.
Upload an OpenGI, Applied Relay or spreadsheet export and have the column mapping worked out for you, behind a review gate.
A daily read across the whole book surfacing cross-sell gaps, dormant clients, insurer concentration and renewals worth a call.
Structured intake across every product line and every channel, running out of hours, with a broker takeover that freezes the AI mid-thread.
Customer, insurer and assessor threads on the same claim gathered into one matter, across whichever channel each party uses.
Questions
Smart importer, in detail.
- Does Aoibhe connect directly to OpenGI or Applied Relay?
- No. You export from your existing system and upload the file; there is no live connection or API link to either platform, and nothing is read out of them automatically. What we take off you is the mapping work. That is the part of a migration that actually costs a day.
- Which policy types and classes of business does the importer handle?
- The standard Irish and UK vocabulary, personal and commercial: motor, home, health, life, travel, pet and gadget on the personal side; commercial, commercial vehicle, motor fleet, commercial combined, farm, combined liability, public liability, employers liability, professional indemnity, medical malpractice, property owners, office, shop, contractors all risks, cyber, pension and income protection on the commercial and financial side. Your export’s own codes are mapped into those classes and you approve the mapping before anything is written. Anything outside the list comes across as other rather than being forced into the nearest match.
- Which file formats can I import?
- CSV, XLSX and XLS. The format is read from the contents of the file, so a spreadsheet saved under the wrong name still imports correctly.
- What if my column names are unusual?
- That is the normal case. Column names and the values inside them are both inferred, so a column called POL_TYP holding a set of internal codes is mapped without anyone writing a lookup table by hand. You see the result and correct anything that is wrong.
- Can an import overwrite my existing book by mistake?
- The mapping is reviewed and approved before anything is written, so an import cannot commit on its own. Nothing enters the book until a person has looked at the proposed mapping and accepted it.
- Do consent flags and renewal dates survive the import?
- Yes. Renewal dates are parsed into structured dates and marketing consent is carried across into per-channel consent records, so the brokerage can evidence what a client agreed to, instead of reconstructing it from a spreadsheet two years later.
See it working
See Aoibhe handle a real enquiry.
Bring a sample enquiry to a 30-minute demo. We'll show the client file, the draft and the broker handoff, on your own data if you'd rather.
Or email support@aibroker.ie.