The demo field guide
One claim. A clear next step.
A visual route through ClaimCompass, from first call to final check. Rehearse six stops, follow the workflow, and keep the answers close.
Before you present
0 of 5 ready. This checklist stays on this page until you leave or reload.
Your 15-minute demo
Select a stop to rehearse the clicks, the explanation and the recovery route.
STOP 1 / 6 · 0–2 min
Orient the audience
Today → Claims → Overview
“Every file has an owner, a current phase and a next step.”
- Open the prepared claim from Claims.
- Point out the owner, phase and next action on Overview.
Confirm: The audience can tell who owns the file and what happens next.
If you get stuck: Return to Claims and open the prepared example if the fresh claim is incomplete.
1. Orient the audience · 0–2 min
Today → Claims → Overview
“Every file has an owner, a current phase and a next step.”
- Open the prepared claim from Claims.
- Point out the owner, phase and next action on Overview.
Confirm: The audience can tell who owns the file and what happens next.
If you get stuck: Return to Claims and open the prepared example if the fresh claim is incomplete.
2. Create one claim · 2–5 min
New → Claim → What happened
“We capture the event, damaged items and claimed losses together.”
- Enter fictional insured and property details, cause and date of loss.
- Describe what happened and add the damaged items. Save, then reopen the claim.
Confirm: The saved details and claimed items appear on the claim.
If you get stuck: Read any field error. Use the prepared claim if setup would take too long; do not invent completion.
3. Review the policy · 5–8 min
Documents → Details → Policy & coverage
“Policy reading gives us a starting point. We verify the limits and both deductibles against the source.”
- Open an already processed declarations page in Documents.
- Review the limits and Hurricane/Wind and All other perils deductibles under Details.
- Correct one field, save and confirm it remains after reopening.
Confirm: The corrected value is saved and the change appears in Timeline.
If you get stuck: If a new upload is processing, use the processed example. Do not keep uploading the same file.
4. Schedule the next action · 8–10 min
Schedule → Week → New event
“An inspection or deadline stays connected to its claim.”
- Choose Inspection / site visit and link the prepared claim.
- Set the date and time, save, then show the event on the claim’s Overview.
Confirm: The event has the right claim, time and type.
If you get stuck: Check claim access and required fields. A Google connection is separate from creating an event here.
5. Explain the money · 10–12 min
Claim → Money → Fee
“The fee and payment records explain the money on this file. Recording a payment does not transfer funds.”
- Show a prepared payment example and its status.
- Show the PA fee: percent or flat amount, with a cap if used. If demonstrating an edit, save and verify the result.
Confirm: The displayed fee terms and payment status match the prepared example.
If you get stuck: If Money is unavailable, check the signed-in role. Show the prepared example without changing permissions mid-demo.
6. Close the story · 12–15 min
Claim → Timeline → Overview
“The history explains what changed; Overview tells us what to do next.”
- Show the policy correction and scheduled follow-up in Timeline.
- Return to Overview. Take questions and show at most one additional requested feature.
Confirm: You can explain the next action without opening every menu.
If you get stuck: Capture any unanswered question and follow up. Use the FAQs below for common workflow questions.
The claim journey
These are operational checkpoints, not nine selectable app phases. The current phase bar reads Intake → Signing → Policy → Build → Submitted → Negotiating → Payment → Closed. Carrier review, estimates and determination must still be tracked explicitly; Submitted alone is not a coverage decision.
- CHECKPOINT 01
Intake
Create the claim profile
Insured, property, event, damaged items and claimed losses.
New claim → Details
Next: Signing - CHECKPOINT 02
Signing
Secure representation
Agreement, LOR and required authorizations. Verify the PA fee.
Overview → Workflow · Documents
Next: Policy - CHECKPOINT 03
Policy
Verify coverage and limits
Compare all listed limits and both deductibles against the policy. No carrier acknowledgment is needed to finish coverage review.
Details → Policy & coverage
Next: Build & submit - CHECKPOINT 04
Build & submit
Assemble the initial claim package
Deliver the intended documents, then record what was sent, when and how. Recording a send does not email the carrier.
Documents → Carrier submission
Next: Carrier review - CHECKPOINT 05
Carrier review
Track the inspection
Follow up on receipt, adjuster assignment and inspection. Save an acknowledgment if received.
Schedule · Timeline · Documents
Next: Estimates - CHECKPOINT 06
Estimates
Collect and compare estimates
Save the carrier estimate and prepare the PA estimate, with dated supporting evidence.
Documents · Timeline
Next: Determination - CHECKPOINT 07
Determination
Record the carrier’s decision
Pending, accepted, partly accepted or denied. Save the supporting correspondence and explicitly note the determination in Timeline.
Timeline · Documents
Next: Resolution - CHECKPOINT 08
Resolution
Follow the appropriate path
Coverage open → negotiate the covered loss. Coverage disputed or denied → document the chosen dispute or referral path.
Overview · Timeline
Next: Payment & close - CHECKPOINT 09
Payment & close
Confirm the final check and closeout
Record actual payments, check status, fees and disbursements before closing. Agreed settlement does not mean money received.
Money → Overview
At determination, choose the path
Coverage open
Negotiate the covered loss → settlement → payment.
Denied or disputed
Record the decision → chosen dispute or referral path → track the outcome.
Still pending
Set a follow-up → save carrier correspondence → update Timeline.
Questions you can answer confidently
What does Submitted mean, and is that the same as a coverage decision?
Submitted means a package has been recorded as sent to the carrier. It does not establish coverage, prove an inspection happened, or mean a settlement was agreed. Track carrier review, inspection, estimates and determination as separate checkpoints before negotiation.
What if the carrier never sends an acknowledgment letter?
Keep the submission date, delivery evidence, carrier claim number and follow-up history. Upload an acknowledgment if one arrives. Do not create a fictional letter or use its absence alone to hold coverage review open.
What should I do if policy reading is still processing during the demo?
Check the document's processing status, then show a previously processed example. Avoid uploading the same file repeatedly. Compare extracted values with the original and correct missing or incorrect fields; automated reading is a starting point.
Does Record sent actually email the carrier?
No. It records documents already delivered, along with the date and any delivery link. Use the appropriate sending action to send an email or signature request, and check the recipient and contents first.
Does connecting an app move my existing claims into ClaimCompass?
A connection and a migration are separate operations. Importing brings existing records over; a connection enables the supported exchange with that service. Confirm the direction and scope of the particular integration before promising synchronization.
Why is a button missing or disabled?
Check the signed-in role, current claim state, required fields, and any required connection. Also confirm the feature is deployed in the environment being presented. Local changes and coming-soon features should not be presented as live functionality.
What does Submitted mean, and is that the same as a coverage decision?
Submitted means a package has been recorded as sent to the carrier. It does not establish coverage, prove an inspection happened, or mean a settlement was agreed. Track carrier review, inspection, estimates and determination as separate checkpoints before negotiation.
What if the carrier never sends an acknowledgment letter?
Keep the submission date, delivery evidence, carrier claim number and follow-up history. Upload an acknowledgment if one arrives. Do not create a fictional letter or use its absence alone to hold coverage review open.
What should I do if policy reading is still processing during the demo?
Check the document's processing status, then show a previously processed example. Avoid uploading the same file repeatedly. Compare extracted values with the original and correct missing or incorrect fields; automated reading is a starting point.
Does Record sent actually email the carrier?
No. It records documents already delivered, along with the date and any delivery link. Use the appropriate sending action to send an email or signature request, and check the recipient and contents first.
Does connecting an app move my existing claims into ClaimCompass?
A connection and a migration are separate operations. Importing brings existing records over; a connection enables the supported exchange with that service. Confirm the direction and scope of the particular integration before promising synchronization.
Why is a button missing or disabled?
Check the signed-in role, current claim state, required fields, and any required connection. Also confirm the feature is deployed in the environment being presented. Local changes and coming-soon features should not be presented as live functionality.
A safe route out of a dead end
“This step needs a document, permission or connection that is not ready in this demo. I’ll show the prepared example and confirm the setup afterward.”
- Return to the claim's Overview. Read the missing requirement or error before clicking another action.
- Switch to the prepared claim if processing is pending. Avoid repeated uploads or repeated sends.
- Capture the action, error, claim reference and time for support. Do not mark an event complete or a document received just to get past a warning.
Watch, then practice
The video is a product introduction, not a complete workflow training recording. Use the rehearsal above for the demo sequence and verify each action in the environment you will present.
Setup, detailed notes and in-app tutorials require sign-in. This visual guide can be shared without an account.