New claim
tripinsurance
How claims arrive
JotForm
Claimant fills the public form · 96% of claims this month
Slack
Support mentions the bot in the AI channel with files attached
Partner API
POST /v1/intake/* · Bearer key, one issued
Manual — this screen
The exception path: a claim that came by e-mail, or a re-run of something that failed intake
Files
Byte-identical duplicates are dropped on arrival; you will see the count before the run starts.
Required to start
- Tenant
- tripinsurance
- Channel
- manual
- Callback
- internal gateset
Everything else — policy number, claimant, incident date — is read out of the documents. Nothing is typed in twice.
Creating a claim mints a new context_id and starts the run. One claim, one run — documents cannot be added afterwards.
This console runs on one fixture claim. There is no API behind this screen: nothing is uploaded, hashed, stored or sent, and no context_id is minted.