Keylane integration and reporting
Connecting to SiteView, and what to do if we cannot
What we know
SiteView was built by 360Globalnet, which Keylane acquired. Keylane describes SiteView as a no-code platform for digital claims handling that can be deployed in modules and integrated with existing core systems, including Keylane's own Axon platform. That suggests integration is possible, but we found no public documentation of a programming interface, and availability often depends on the licence and the hosting arrangement.
So the honest answer to "does it have an API?" is: probably, in some form, but only Keylane can say what One Claim's installation allows, and at what cost.
What Postbot needs from SiteView
| Need | Direction | Used for | Essential? |
|---|---|---|---|
| Search claims by reference, registration, name, date of loss | Read | Matching email to claim | Yes, for good folder accuracy |
| Claim summary: status, handler, client, key dates | Read | Routing to the right handler or folder | Yes |
| Documents on a claim (including medical reports) | Read | Medical report analysis | Useful |
| Add a note or file an email to the claim | Write | Saves staff re-keying | Later phase |
| Create a task or diary entry | Write | Category 1 follow-up | Later phase |
We recommend starting read-only. Writing into the claims system should wait until Postbot's accuracy is proven.
Options, most to least preferred
| Option | How it works | For | Against |
|---|---|---|---|
| A. Keylane interface | Postbot calls SiteView's own interface to search and read claims. | Live data, supported by the vendor | May need licence changes and Keylane involvement; timescale unknown |
| B. Scheduled export | SiteView produces a report of open claims (reference, parties, registration, handler, status) every hour or so, delivered as a file. Postbot keeps a local copy. | Usually possible with standard reporting tools; low risk | Up to an hour out of date; read only |
| C. Reporting database | If Keylane provides a read-only copy of the database for reporting, Postbot reads from that. | Full data, no load on the live system | Depends on the hosting arrangement |
| D. None | Postbot matches on references and threads only, with no claim lookup. | Works immediately | Lower accuracy, cannot route by handler |
The demonstration uses a mock claims database with the same shape as option B, so it can be switched to A or C later without changing how Postbot works. We would not recommend screen-scraping SiteView: it is fragile and may breach the licence.
The reporting gap
The note that "the system does not provide the data they need" could mean several things. Postbot itself generates data that SiteView does not hold today:
- Inbound volume by email type, client, broker and sender, per day
- Category 1 items: when they arrived, when they were picked up, how long they waited
- Chaser counts per claim, as an early warning of service problems
- Tariff and non-tariff mix from medical reports, by client and representative
If the missing data is something else (for example, claim lifecycle figures SiteView holds but will not report), option B or C also makes it possible to build that reporting outside SiteView.
Which report or figure do you want that you cannot get today? A mock-up or an example spreadsheet would be ideal.
Questions to put to Keylane
- Does One Claim's SiteView installation include a programming interface, and is it covered by the current licence?
- Is there documentation and a test environment we can use?
- Can it search claims by reference, registration and party name, and read claim summaries and documents?
- Can it add notes, documents and tasks to a claim?
- If not, what scheduled exports or reporting database options exist?
- Does SiteView already connect to the Official Injury Claim portal for One Claim?
- Are there restrictions on third-party access, and what does Keylane need from One Claim to authorise it?