Every roadworks claim made on time
Liam is an independent insurance broker in Dublin. His clients are small shops, cafes and pubs.
Listen to the story:
The challenge
Their cover pays out when roadworks close the street and customers cannot get in. But nobody tells Liam. A cafe owner mentions it six weeks later, after the deadline to claim. Last year, five clients lost money they were owed.
How the flow works
With xMap Flows, Liam built Robin. Robin is an AI employee: a flow of 7 blocks.
Every morning at seven,
Every morning at 7 (Schedule)
Robin takes every client's shop,
His clients' shops (My data)
checks for closures and roadworks outside,
Closures and roadworks (Traffic incidents)
keeps the ones right on their street,
Right on their street (Filter)
works out the date the claim is due,
Claim deadline (Calculated field)
waits for Liam's nod,
Liam checks first (Approval)
and emails each owner how to claim, the same morning.
How to claim (Gmail)
What it solves
- Nobody tells Liam: solved by Traffic incidents and Filter
- Deadlines missed: solved by Calculated field
- Money left unclaimed: solved by Approval and Gmail
The result
This spring, Robin spotted roadworks outside eleven of his clients, from Temple Bar to Rathmines. Every one heard from Liam on the first morning, every claim went in on time, and nine have already been paid.
Liam's clients used to miss what they were owed. Now he finds it for them.
An illustrative scenario: the figures are modelled to show what the flow produces, not a customer's results.
The flow, block by block
- 1
- 2
His clients' shops
Brings in a table you uploaded or a list you saved on the My data page: your stores, customers, target accounts or sites.
- 3
Closures and roadworks
Road closures, roadworks and other incidents on online maps right now, with where they are.
- 4
- 5
- 6
- 7
Templates to build it
Ready-made flows with the same blocks. Open one, change the city and the kind of place, and run it.
- Where growers need a cold storeGrower areas with the fewest cold stores, scored for a packhouse, approved.
- Expansion committee pack, every monthA monthly expansion committee pack: every block scored, the best 20 investigated, approved, mapped.
- Road closures near my schools before the buses leaveRoad closures near your schools sent to bus drivers before each run.
- Roadworks and closures near my projectsRoad closures and roadworks near each of your sites, every morning.
- Road closures near my depots, every hourClosures and roadworks near each depot every hour, to dispatch on WhatsApp.
- Stores competing with each otherYour stores that sit within 1 km of each other, with the people around them.
Industries
Learn how it works
- Reverse geocodingTurning coordinates into a street, district or address.
- Data enrichmentAdding details to records you already have.
- How to score candidate store sitesCompare sites on residents, competitors and neighbours, with an AI score and a reason.
- Traffic incidents and road closuresClosures and roadworks in an area or near each of your places.
- Your own tables and lists (My data)Upload a CSV, save lists of results, and use them in flows.
- Approve before anything goes outA person says yes, for the whole list or item by item.
More stories from Insurance
- Two days of warning before the stormMia is an independent insurance broker in Auckland, with three hundred clients, from homes on the North Shore to boatyards in Westhaven.
- From crash to garage in one callBeatriz leads car claims at a large insurer in Rio de Janeiro. Two hundred drivers report a damaged car every day.
- Closing the gaps in the care networkMegan runs provider contracts at a health insurer in New York. Members keep writing: there is no urgent care near me in your network.
- Trusting the road, not doubting the driverSipho leads the claims team at a car insurer in Cape Town.
Build this flow on your own city
Run a live search on the home page without an account, or let Ask xMap build the flow from one sentence.