Adjuster thread
Need revised moisture log before approval
8:42 AM · carrier follow-up
For restoration PMs, claim managers, and operations leaders.
Know today's claim move and its blocker.
Scattered email, evidence requests, adjuster follow-ups, and unclear waiting states stall claims; Carbon shows what needs action today and what is blocking claim movement.
- Read-only sources
- human review
- no automatic source-system mutation
Carbon · Claim movement
Source stack
Moisture log
Kitchen dry-out readings attached
PDF · latest field packet
Room photos
North wall and cabinet base
6 images · source evidence
Next move
Send the revised log.
Carbon has the adjuster request, field log, and photo set ready for PM review.
Draft line
Attached are the updated readings and kitchen photos for supplement approval.
Why claim movement stalls
The work is happening. The waiting is hidden.
Carbon starts with the operational mess restoration teams already live in, then separates PM action from outside waiting.
Unanswered adjuster and customer emails
Important replies arrive in different inboxes while the claim looks quiet from the outside.
Missing evidence and document requests
Photos, logs, invoices, and revised packets get requested faster than teams can track them by hand.
Unclear waiting party
PMs lose time figuring out whether the next move belongs to the carrier, customer, subtrade, or internal team.
Stale claims with no next action
Open claims sit idle when no one can quickly see the blocker, source request, and next reviewed move together.
Product workflow
From source request to tracked claim movement.
Carbon turns scattered operational signals into a reviewed loop: detect, match, classify, confirm, prepare, and track.
Carbon · Detect
Source request
Adjuster needs revised log
8:42 AM · read-only capture
Step 1 of 6 · Detect
Incoming email or source item arrives.
Carbon captures the request, attachment, photo, or transcript as a source item without changing the source system.
Carbon · Match
Claim match
Nguyen · Claim 4281
High confidence · thread history
Step 2 of 6 · Match
Carbon matches it to a claim or sends it to review.
Strong claim signals route the item to the file; uncertain matches stay in review with reasons and candidate claims.
Carbon · Classify
Movement state
Evidence gap
Moisture log requested
Step 3 of 6 · Classify
The claim movement state is identified.
Carbon separates action items, blockers, waiting states, deadlines, and evidence gaps so the PM sees what actually needs movement.
Carbon · Review
PM review
Confirm next action
Human control
Step 4 of 6 · Review
The PM confirms and acts.
The recommendation stays in a human review lane; Carbon never sends, archives, or mutates source systems automatically.
Carbon · Prepare
Prepared support
Draft + 3 evidence items
Source evidence attached
Step 5 of 6 · Prepare
Carbon prepares the draft or evidence packet.
Draft replies, reminders, and supporting evidence stay attached to the original source request for inspection before use.
Carbon · Track
Waiting on
Carrier approval
2 days idle · follow-up ready
Step 6 of 6 · Track
Timeline, blockers, and claim movement stay visible.
After the PM acts, Carbon keeps the waiting state, open blockers, and movement history visible instead of letting them fall back into email.
Guided product tour
Inspect the Carbon loop before a sales call.
This static tour shows the concrete product states a PM would review: source queue, claim match, next action, draft support, and waiting-state tracking.
Carbon · Inbox/source request
Step 1 of 5
Carrier email enters the source queue.
Carbon shows the subject, sender, timestamp, and extracted request while keeping the original source item attached.
What the PM inspects
- Adjuster requested revised moisture log
- Kitchen photo set and dry-out readings detected
- No email status changed in the source system
Carbon · Matched claim
Step 2 of 5
The request lands beside the right claim.
Claim number, homeowner name, and thread history explain why Carbon matched the item; uncertain evidence remains reviewable.
What the PM inspects
- Nguyen · Claim 4281
- Match reasons: claim number + prior thread
- PM can confirm, reject, or send to review
Carbon · Recommended action
Step 3 of 5
The next move is separated from the noise.
Carbon frames the work as a PM-reviewed action item, blocker, waiting state, or evidence gap instead of a generic notification.
What the PM inspects
- Action: send revised log to adjuster
- Blocker: approval waiting on evidence
- Priority: today because approval is stalled
Carbon · Draft/evidence prep
Step 4 of 5
Draft support is ready, not released.
The PM can inspect the draft line, evidence packet, and source trail before copying, editing, or dismissing it.
What the PM inspects
- Draft reply prepared for review
- Moisture log + 6 photos attached
- PM approves before anything leaves Carbon
Carbon · Waiting-state tracking
Step 5 of 5
The claim remains tracked after the action.
Carbon records who the team is waiting on, last contact, days idle, and the next recommended follow-up date.
What the PM inspects
- Waiting on carrier approval
- Last contact: 2 days ago
- Next follow-up reminder stays tied to the claim
Role-based value
One claim movement loop, four operating views.
Carbon is built for the buying committee around the claim: the PM who acts, the manager who spots stalls, the coordinator who routes evidence, and the admin who controls access.
PM / claim manager
Know what to work today.
Start from claim movement instead of inbox order: open blockers, waiting states, source requests, and PM-reviewed draft support stay together.
Manager / operations lead
See stalled claims and team-wide bottlenecks.
Review where claims are waiting, which requests keep repeating, and where handoffs or evidence gaps are slowing movement across the team.
Coordinator / intake or admin
Route unmatched messages and evidence into the right claim.
Use claim-match reasons and review lanes to move email, attachments, photos, and transcripts out of limbo without creating new claims automatically.
Owner / admin
Connect sources, control permissions, and audit decisions.
Keep read-only source posture, role capabilities, human confirmation, and source provenance visible while the firm expands Carbon from pilot to operating rhythm.
Operational outcomes
ROI starts with idle time Carbon can expose.
Carbon's value logic is operational: reduce hidden waiting, shorten follow-up loops, and make evidence requests easier to move from source item to PM action.
Fewer idle claims
Open blockers and waiting states stay visible instead of disappearing after the first email pass.
Faster follow-up cycles
Prepared reminders and draft replies shorten the path from request review to PM action.
Fewer missed evidence and document requests
Requests, attachments, photos, logs, and supporting items remain tied to the claim and source thread.
Clearer handoffs
Claim context, waiting party, latest source item, and next action travel together when ownership changes.
Shorter time from request to PM action
Carbon separates actionable work from external waiting so the PM can see the next reviewed move quickly.
Less manual inbox triage
Claim matching and review queues reduce repeated searches across scattered messages and evidence.
Integrations and data sources
Built around the systems restoration teams already use.
Carbon complements the systems restoration teams already use by organizing the source material around claim movement, not by asking teams to abandon their estimating, file, email, field, or carrier workflows.
Email-first ingestion
Carbon starts where restoration claim movement already happens: Gmail / Outlook threads, adjuster requests, customer replies, and carrier follow-ups.
Attachments, photos, files, and transcripts
Evidence and context stay organized as source items, including attached logs, room photos, shared files, call transcripts, and manual uploads.
Future connectors
Drive / shared folders, Xactimate / XactAnalysis exports, Encircle and field documentation tools, and carrier portals can connect around the same source-item model over time.
Existing tool fit
Gmail / OutlookDrive / shared foldersXactimate / XactAnalysisEncircle and field documentation toolsCarrier portals
Trust, security, and human control
Carbon prepares the work without taking control away from the operator.
Current pilot posture is practical and explicit: permissioned access, visible provenance, human review, and a security and compliance roadmap without implying completed enterprise certification.
Access & permissions
Read-only connector posture in MVP
Carbon can ingest and organize source material without marking messages read, archiving, editing, deleting, sending, or writing back to connected systems.
Human confirmation before inclusion or action
PMs decide whether a source item belongs in a claim, whether it should affect analysis, and whether a prepared draft or evidence packet is used.
Role and capability permissions
Admins can shape who manages connectors, confirms matches, reviews notifications, sees assigned claims, or audits firm-wide work.
Operator control
Source provenance and audit trail
Recommendations point back to the original email, attachment, file, photo, transcript, or source link so teams can inspect why Carbon suggested an action.
No automatic sending
Carbon prepares copy-ready draft support inside the workflow; a person reviews, edits, and decides what leaves Carbon.
No deleting or modifying source systems
The MVP promise is explicit: no removing source data, no changing source records, and no source-system side effects hidden behind AI output.
Category fit
What Carbon is, and what it is not.
Carbon sits around existing restoration tools as the claim movement layer: it organizes source context, surfaces blockers, and prepares the next reviewed action.
What Carbon is
Operational intelligence layer around claims
Carbon reads the work created across source systems and turns it into claim movement context.
Claim movement action queue
The main object is the next reviewed move: action item, blocker, waiting state, draft, or evidence packet.
Email-first source organization and next-action prep
The first wedge is source organization that prepares PM action instead of becoming another destination for generic notes.
Not trying to be
- Not estimating software
- Not a generic CRM
- Not a field documentation app
- Not an autonomous claim decision-maker
- Not a full project-management replacement
Pilot-ready proof
Trust the workflow evidence before the market proof matures.
Carbon is early, so the proof is concrete and constrained: product artifacts, QA evidence, human-control commitments, and an honest pilot path.
Product artifacts, not logo claims.
The page shows the actual Carbon buying narrative: source request, claim match, recommended action, draft support, waiting state, permissions, and audit posture.
Guided source-to-action tour
Buyers can inspect how a carrier request moves from email capture to PM-reviewed draft and tracked waiting state before a sales call.
QA-backed guardrails
Focused landing checks protect the accepted product-screen direction, rejected pattern removals, source non-mutation language, and unsupported-claim boundaries.
Transparent pilot limits
Carbon is presented as pilot-ready: read-only first, human-reviewed, security-roadmap honest, and measured around idle time before financial impact claims.
Pilot review checklist
Use this section to review pilot checklist items before deciding whether Carbon fits the next claim cohort.
- 1. Confirm the claim sources Carbon can read first.
- 2. Pick a small active-claim cohort and PM review lane.
- 3. Validate match reasons, draft support, and evidence packets with operators.
- 4. Review idle-time patterns before expanding to broader workflow coverage.
FAQ and objections
Answers for the buying questions that slow a pilot decision.
The goal is a focused workflow review, so the page handles setup, access, AI reliability, human override, tool fit, security posture, team fit, and pilot process directly.
8 questions for pilot decisions
A pilot should start with a narrow claim cohort, read-only email/source access, role permissions, and a review lane for unmatched items before broader backfill.
Carbon starts with permissioned source access such as email threads, attachments, photos, files, transcripts, and claim identifiers used for matching.
AI suggestions must show reasons and evidence. PMs can confirm, reject, reroute, or edit suggested matches, action items, drafts, and evidence packets.
No. Carbon prepares reviewed support inside the workflow and keeps MVP connectors read-only, with no sending, deleting, archiving, or source record changes.
Carbon complements Gmail, Outlook, Drive, Xactimate, XactAnalysis, Encircle, field documentation tools, and carrier portals by organizing claim movement around them.
The pilot posture is permissioned access, source provenance, audit trails, human confirmation, and a security roadmap without implying completed enterprise certification.
Carbon is aimed at medium-to-large restoration teams where multiple PMs manage enough active claims for hidden waiting and manual triage to compound.
A practical pilot reviews source access, a focused claim cohort, match quality, PM override behavior, draft usefulness, waiting-state visibility, and idle-time patterns.
Operator guardrails
Prepared by Carbon. Released by the PM.
Read-only by default
Carbon does not mark, archive, send, or mutate source systems in this landing flow.
PM remains in control
Drafts are prepared for review, not sent automatically.
Evidence stays attached
Every suggested action points back to the source request and supporting material.
Sales motion
Create account for pilot review.
Create an account for the current pilot path, then use the checklist to bring one active claim workflow, the source systems around it, and the review decisions your PMs need to trust before a review expands.
Already have an account?