XactaClaim Mobile Companion: Field Claim Workflows for Public Adjusters and Claim Teams

Property claim work does not wait for you to get back to a desk. Inspections, client follow-ups, and documentation gaps often happen in the field — when details are fresh and delays are costly. The XactaClaim mobile companion is built for that reality: a Pro/Premium staff extension of the same workspace, not a separate product and not a client-facing app.

Why mobile matters in claim workflows

Field visits, drive-time follow-ups, and quick status checks are where mobile access pays off. When adjusters can open a claim, capture an internal note, or review the next task without reconstructing context from memory, the claim file stays closer to reality. Mobile does not replace careful review on web — it reduces the gap between what happened in the field and what lands in the file.

• Capture inspection and client context while details are fresh.
• Review pending tasks between files without opening a laptop.
• Open claim detail for quick orientation before a call or site visit.
• Keep staff aligned with the same workspace data — not a shadow spreadsheet.

What the XactaClaim mobile companion is

The mobile companion is a staff app for Pro and Premium workspaces. It connects to the same claim records, notes, and tasks you use on web — with mobile access gates that require verified email, workspace readiness, and eligible plan access. Solo Trial does not include mobile access. Insureds continue to use the secure web PIN client portal; there is no client mobile app.

Available features vary by release. Think of mobile as a focused field layer — not full parity with every web workflow. Deeper policy review, estimate comparison, portal administration, and billing are examples of work that often still belongs on web.

Mobile claim access and quick claim setup

Staff can browse the claims list, open claim detail, and use Claim Quick Create to open supported claim records from the field when a new file needs to start quickly. Quick create uses the same authenticated claim APIs as web — one claim credit still opens one new claim file. For complex intake, document packages, or review prep, web remains the better primary surface.

Mobile Claim Notes for field context

Internal Claim Notes on mobile are staff-only — clients cannot see them in the portal. Notes created from mobile are tagged with a mobile source so your team can distinguish field capture from desk review. Use them for inspection observations, follow-up reminders, documentation gaps, and handoff context. Notes are operational context, not legal or coverage advice.

Tasks and Work Queue on mobile

Mobile supports reviewing and updating tasks where implemented, so follow-up ownership does not stall between site visits. Pair mobile task checks with your team conventions on web: who owns the next action, what is client-facing vs. internal, and when a task should escalate to a fuller review pass on desktop.

Damage photos, files, and communications

Depending on release, mobile may support damage photo workflows, file access, and communications views tied to the claim record. Capabilities expand over time — always confirm what your current build supports before training the team. Communications and voice features still depend on workspace configuration and plan entitlements on web.

AI Claim Brief beta on mobile

AI Claim Brief on mobile generates a structured per-claim summary from backend AI — not on-device models and without API keys stored on the phone. Staff open the brief from claim detail; the app calls the workspace claim-brief API with a Firebase bearer token. The brief may draw on claim context such as notes, tasks, file metadata, saved analyses, photos, and communications when available.

AI Claim Brief is a beta staff tool. Review every summary before acting or sharing. It does not make coverage determinations and does not replace reading source documents. Web Claim Brief UI is not yet available — mobile is the current staff surface for this beta feature on eligible plans.

What mobile does not do yet

• Offline mode — connectivity is required.
• Client mobile app — insureds use the web PIN portal only.
• Full replacement for the web workspace — estimate comparison, demand drafting, and deep admin often stay on web.
• Legal, insurance, or coverage determinations — AI outputs are assistive only.
• Official Xactimate/XactAnalysis integration — export remains a separate beta workflow.
• In-app voice or microphone recording as a native mobile feature.

How teams should roll out mobile access

1. Confirm Pro or Premium plan eligibility for staff who need mobile.
2. Verify staff emails and workspace profiles before rollout.
3. Define when to use Claim Quick Create vs. full web intake.
4. Set mobile note conventions (what belongs in Claim Notes vs. client updates).
5. Train staff on task updates and handoff expectations.
6. Explain AI Claim Brief beta boundaries — verify before sharing.
7. Keep client portal communication separate from internal notes.
8. Document which workflows remain web-only for your agency.

This article describes general product workflows and is not legal, insurance, engineering, or public adjusting advice. AI Claim Brief and other assistive features require human review. Plan features and mobile capabilities may change; confirm current details on Pricing, Terms, and Privacy.