TP-2026-CC0FEW · Swiftline Couriers Ltd · third party property damage · opened 6 days ago, by phone

Nothing to request: all 5 answers arrived with it

No register was available, so every item and proof of purchase would need to be requested from the policyholder.

What this one turns on

The 2 answers that decide whether the policy responds, before the account rather than inside it. A person still decides what they mean.

Whose property was damaged, and do you have their details?

The unit is leased. Getting the landlord details from the tenant

A liability claim is settled with somebody else, so the handler needs to know who that is before anything can move.

Was anyone hurt?

No, nobody was near it

Asked separately because an injury changes who has to be told and how quickly, even where the answer is no.

The account, as the policyholder gave it

Their words, not a summary of them. The tool call is shown because it is the answer to the question any handler has about a claim that arrives already populated: the items came off a register that existed before the loss, not out of the conversation.

Policyholder

Driver reversed into a roller shutter door on the way out

Engine

Nothing was attached: this loss is not about property on the register.

{ "tool": "get_asset_register", "args": { "profile_id": "audit_sxzrgq" }, "result": { "items_matching_the_loss": 0, "replacement_value": 0, "with_purchase_record": 0, "with_serial_number": 0, "oldest_line_dated": null } }

Everything else asked

When did the damage happen?: Last Tuesday morning
Where did it happen?: Loading bay at the customer's unit on Penarth Road

The position at the date of loss

What is held against what is on the claim. The two numbers, side by side, and no third number worked out from them.

Public Liability

Swiftline Couriers Ltd

Line	Figure	Source
Cover recorded	none recorded	No premium for this appears in the ledger. A ledger shows what is held and never the absence of anything.
On this claim	not a property loss	No item list belongs on this kind of claim, so nothing was attached.

A person decides this claim. Nothing on this screen computes a settlement, applies a policy term or expresses a view on whether the policy responds.

Flagged before the loss: No Public Liability recorded

Covers the cost when the work injures somebody else or damages their property. £1,000,000 is the usual level for a courier.

Nothing is attached to this one

This business keeps no register, so there is nothing to attach and nothing that can be checked against what was held before the loss. Any property lost would have to be established from the policyholder.

What this needs next

Nothing outstanding

No register was available, so every item and proof of purchase would need to be requested from the policyholder. In a live system the next action here is a decision by a person, and the queue would show this case as waiting on one rather than waiting on the policyholder.

This screen assembles, it does not decide

No step here accepts a claim, declines one, sets a reserve, values anything for settlement or pays. Those are a person's, and the engine has no route to any of them by design rather than because they have not been built yet.

Where the evidence came from

Every attached line was on the policyholder's register before the loss, most of it put there by a bank statement rather than typed. That is what a handler is being asked to rely on, so the register says per line whether a purchase record exists and this screen repeats it rather than flattening both into "evidenced".

Demo case against a fictional business with synthetic transactions. Nothing here is a real claim and no part of this prototype agrees, values or pays anything.