
Sauna intakes new claims, checks each against policy and documentation, drafts the adjudication note, and chases the missing paperwork so the queue keeps moving.
What it does
Sauna reads incoming claim forms from Jotform, logs each into the claims sheet with policy number and loss date, and flags anything missing a required field.
It compares each claim to the policy terms and submitted documents, notes coverage, deductible, and any exclusion that applies, and drafts the adjudication rationale.
Sauna lists every claim waiting on a document, drafts the request email per claimant in Outlook, and tracks who has and hasn't responded.
It maintains the daily queue in Google Sheets — claims received, in review, pending docs, and decided — so the team sees exactly where each one sits.
Put Sauna to work on this.
Get started for freeIn context
Sauna shows up where you already work — the web app, Slack, email, iMessage, and Superhuman. It reads what it needs, does the task, and comes back with the draft for your approval.
Try it
The literal prompt for this job. Open it in Sauna and it picks up from there.
“Read today's new claims from Jotform, log each into the claims sheet with policy number and loss date, and flag any claim missing the documents we need to adjudicate.”
Plugs into the tools you already run — and thousands more, or any MCP server.
Good to know
No. Sauna drafts the adjudication note and rationale from the policy and documents. A processor reviews and you make the decision before anything is finalized.
No. It cites the policy clause and the submitted document behind every note. If the documents don't support a decision, it flags the gap instead of filling it in.
Sauna reads only what you connect, and acts only after you approve. Your workspace and its memory are yours, not training data.
Keep exploring