Claimory integrates with the tools collision shops already pay for

Gmail and Outlook OAuth, two-way SMS on real workspace-owned Telnyx numbers, estimate import from CCC ONE, Mitchell, and Audatex, Stripe billing with hardened webhook processing, and Resend transactional email. Claimory connects to what is already in the shop, instead of forcing a rip-and-replace.

Email: Gmail and Outlook OAuth, two-way sync

Connect the shop's Gmail or Outlook account through OAuth. The integration layer pulls new messages on a schedule and matches them against open claims by claim number, VIN, carrier name, or thread address. Matched messages land on the claim's Emails tab. Unmatched messages stay in the inbox for manual triage. Compose a new email from any claim, reply inline, or use AI to draft the reply. Sends route through the connected OAuth account so carrier replies come back to the right mailbox. Smart folders organize adjuster threads, customer threads, and carrier threads separately.

SMS: real workspace numbers with two-way threading

Each workspace is provisioned a dedicated Telnyx number with a real area code. Outbound messages send from that number. Customer replies thread back to the claim record so any team member can pick up the conversation without losing context. Inbound SMS webhooks are processed with idempotency so duplicate deliveries do not create duplicate messages. SMS templates let the team send consistent updates without rewriting each time. Opt-outs are stored and respected.

Estimate import: CCC ONE, Mitchell, and Audatex

The parse-estimate-xml edge function reads the XML each estimating system exports, normalizes line items, and presents a side-by-side review screen before lines land on the claim. The shop keeps writing estimates in the system it already uses. CCC ONE, Mitchell Cloud Estimating, and Audatex Estimating are all supported. Bulk historical migration is offered on Elite and Enterprise plans.

Five supporting pillars

  • Connect a shop Gmail or Outlook mailbox through OAuth. Adjuster threads sync into the claim record automatically. Inbound email matches against open claims by claim number, VIN, or carrier so messages land on the right file.
  • Each workspace gets a real Telnyx number, not a shared shortcode. Outbound texts go from that number. Customer replies thread back to the claim. The shop never has to touch a Telnyx dashboard.
  • Drop the estimate XML from CCC ONE, Mitchell, or Audatex into the import dialog. Line items preview in a side-by-side review screen before being saved to the claim. The estimating system stays where it is.

Key capabilities

  • Gmail and Outlook OAuth with automatic inbound email matching to open claims
  • Compose, reply, and AI-draft emails from any claim record
  • Smart inbox folders: adjuster, customer, and carrier threads separated
  • Telnyx workspace-owned SMS number with two-way threading back to the claim
  • Idempotent inbound SMS webhook: no duplicate messages on retry
  • Estimate XML import from CCC ONE, Mitchell, and Audatex with side-by-side review
  • Stripe billing with PCI-compliant processing and webhook deduplication
  • Resend transactional email for welcome, trial reminders, and alerts
  • 14-day free trial, no credit card required

Common questions

Does Claimory replace CCC ONE, Mitchell, or Audatex?

No. Claimory does not write estimates. The shop keeps using whichever estimating system it already pays for. Claimory imports the estimate XML and tracks the claim lifecycle: supplements, adjuster follow-up, customer portal, cycle time, and payment. Pair the two and stop losing money between the estimate and the check.

Can the shop use its existing email domain for adjuster communication?

Yes. Gmail and Outlook OAuth connect the shop's existing mailbox. Adjuster replies come back to the same address the shop already uses. Claimory routes the message into the claim record without changing the shop's email setup.

Do customers get texts from a recognizable local number?

Yes. Each workspace gets a dedicated Telnyx number with a real area code. Customers see a local number, not a shared shortcode. Replies thread back to the claim so the front desk can respond from Claimory without switching to a personal phone.