Table of Contents

Contacting Support: Verifying Your Identity

When you call ClaimRev support — or when one of our agents answers a chat or video call from outside the in-app support flow — they need to confirm you are who you say you are before discussing claim details, account configuration, or anything else tied to your account.

This guide explains why ClaimRev does this and how the identity check works on your end. The whole thing takes about ten seconds.

Why We Verify Identity

The phone number a call comes from, the name on Caller ID, and the email address someone gives over the phone are all easy to fake. Without a way to confirm the caller is actually who they claim to be, anyone who knows a little bit about your organization could call us, pretend to be one of your users, and try to extract patient data, change account settings, or send claim files somewhere they shouldn't go.

It's ClaimRev's policy to verify identity on every off-portal contact before disclosing or modifying anything customer-specific. This protects:

How the Check Works

The agent will send a one-time six-digit code to your ClaimRev-registered email address and your in-portal notification inbox. You read the code back to the agent. The agent enters it on their end. Done.

The code:

Two Ways to Verify

Option 1: Let the Agent Send the Code (Most Common)

This is the default. You don't have to do anything ahead of time — the agent drives the process.

  1. The agent asks for your name and the customer organization you're calling about.
  2. They search you up in their dashboard. They'll read your email address back to you and ask whether it's correct — this is your chance to confirm they've got the right person.
  3. The agent clicks Send code. Within a few seconds the code arrives:
    • In your email inbox (subject line: Your ClaimRev support verification code), and
    • As a notification in the ClaimRev portal (bell icon in the top-right).
  4. You read the six-digit code to the agent.
  5. The agent types it in. Your call continues.

Option 2: Generate the Code Yourself

Useful if you're on the phone and either:

You'll need to be logged in to the ClaimRev portal in your browser to do this. Then:

  1. In the left sidebar, click Support, then Verify Me to Support.
  2. Click Generate code. A six-digit code appears on your screen, and is also delivered to your email and portal notification inbox.
  3. Read the six-digit code to the agent over the phone.
  4. The agent's dashboard automatically detects that you've started a verification — your name pops up in their Waiting to verify list with a small phone-callback icon. They click your card and enter the code.
  5. The popup on your screen flips to Support has confirmed your identity. You're verified.

If you don't see Verify Me to Support inside the Support page, your role doesn't have the permission turned on. Your account administrator can enable it in the portal's Communication Settings under the Self-Verify to Support toggle.

If Something Goes Wrong

"I never got the code."

"It says my code is wrong."

"It says I've reached a rate limit."

You've started more than five verifications in the last hour. This usually means something else is going wrong — a wrong email on file, a delivery issue, or you genuinely needed several attempts. Either:

"I'm not getting emails from ClaimRev at all."

The email on file for your user may be stale. Your account administrator can update it in User Management. We won't update an email address over the phone — that itself would be a security risk.

What the Agent Will and Won't Do

Will

Won't

What Happens to the Verification Record

Every verification — successful, failed, expired, or cancelled — creates an audit record in ClaimRev's systems. The record includes who the agent was, who the user is, the account, the channels the code was sent through, and the outcome with timestamps. The plaintext code is never stored — only a one-way cryptographic hash of it.

Records are retained for at least 30 days and may be retained longer when needed for incident investigations.

You can request a copy of your own verification history from your account administrator or by contacting support.

Frequently Asked Questions

"I'm logged in to the portal right now. Do I still need to verify when I call?"

Yes, if you're calling on the phone or contacting us through any channel other than the in-portal video call feature. The fact that somebody is logged into your account in some browser doesn't tell the agent that the person on the phone is you. The verification code is what closes that gap.

"What if I'm calling about an emergency and don't have time?"

The verification takes under a minute. The agent will hold off on disclosing anything until your status shows verified on their dashboard. If you're in a genuine emergency and can't access your email, tell the agent and they can escalate the situation.

"Can I be verified for the whole day after a single check?"

No. Verification covers the current support interaction only. If you hang up and call back tomorrow — or even later the same day — you'll verify again. Standing verifications would defeat the purpose: a fresh impersonator could just claim to be you on a follow-up call.

"What if I want to opt my organization out of this entirely?"

You can't opt out of verification when calling ClaimRev — it's how we keep your account safe. You can disable the user-side Verify me to support menu item for your account: an admin can flip the Self-Verify to Support toggle off in the portal's Communication Settings. With that off, only the agent-initiated path (Option 1 above) is available. The verification itself still happens on every call.

"Will I see this for in-portal video calls too?"

No. When you click the support help button in the portal and start a video call from inside your authenticated session, the agent already knows who you are — your portal session itself is the identity check. No code needed.

Questions

For help with verification or anything else, contact ClaimRev support at help@claimrev.com or call 1-918-842-9564.