⌘ K

Search

Search portal content

AI customer support in one tabAI customer support in one tab
⌘ K

Search

Search portal content

AI customer support in one tabAI customer support in one tab
  • Reply to a ticket
  • Ticket statuses
  • Start a new ticket
  • Assign tickets
  • Add internal notes
  • Use saved replies
  • Send and view attachments
  • Tag tickets
  • Set ticket priority
  • Snooze a ticket
  • Follow up with customers
  • Replies to closed tickets
  • Search and filter tickets
  • Save ticket views
  • Update tickets in bulk
  • Merge tickets
  • Change the requester
  • Move to another inbox
  • Report spam
  • Translate messages
  • Use Cc and Bcc
  • Sender verification
  • Handle sensitive requests
  • Manage customers
  • Manage companies
  • Ticket analytics
  1. Home
  2. Manage tickets

Sender verification

See what the warning above a message means, why a real email can trigger it, and what to do before you act on a request.

Sender verification

See what the warning above a message means, why a real email can trigger it, and what to do before you act on a request.

initdesk checks whether each incoming message really came from the address it shows. When the check fails or can't be completed, a warning card appears above that message. The warning never stops you from replying, and it doesn't hide anything.

What the warnings mean

Every warning card shows the sender's address, the line "Be careful with links, attachments, and requests for data or payment.", and a Learn more link to this article.

Warning What it means
Warning: this sender may be fake The check failed. The sender's domain didn't confirm that it sent this email. It may be a spoof, or a real sender with a broken email setup.
Warning: this sender's checks disagree initdesk got mixed results about this sender. Treat it like a failed check.
We could not verify this sender initdesk couldn't get a usable result. It doesn't mean the message is safe or unsafe.

A message with no card passed the check, doesn't need one, or was never checked. No card does not mean safe. A hacked account or a lookalike address such as acme-support.co can pass.

The warning belongs to one message. The first message of a ticket shows the result for whoever opened it, and each reply has its own result. A warning on one message doesn't change the others.

How initdesk checks email

Email has no built-in proof of who sent it, so anyone can type any address in the From line. Three standard checks let a domain prove it sent a message:

  • SPF lists which servers may send email for a domain.
  • DKIM adds a signature that proves the email wasn't changed and came from the domain.
  • DMARC tells receivers what to do when SPF and DKIM don't match the visible From address, and reports the combined result.

initdesk uses the DMARC result that its email provider records when the message arrives. A DMARC pass means no warning, and a fail shows the "may be fake" warning. If the domain gives no usable result, for example because it has no DMARC record, you see "We could not verify this sender".

Many domains haven't set these checks up, or set them loosely. Forwarders and mailing lists can also change an email on the way, which breaks the signature on a real message. So a failed check doesn't prove fraud.

Forwarding

If you forward your support address into initdesk from Google Workspace, Gmail, or Microsoft 365, initdesk keeps the original sender's result. Other forwarders and mailing lists can make real email fail the check. See Forward your support address.

Messages that never show a warning

  • Messages from your team. A signed-in teammate's reply or note counts as verified, and some system messages need no check.
  • Older messages. Messages that arrived before the check existed aren't rechecked.
  • Imported tickets. An import doesn't check senders.

On these messages, no card means "not checked", not "passed".

Other channels

  • WhatsApp and Telegram: initdesk compares the message against the account the provider reports. When the provider confirms it, there's no warning.
  • Help center and AI chat: a customer who signed in with their email counts as verified.

What to do when you see a warning

Slow down before you act on anything that:

  • changes an email address, phone number, or password,
  • sends money, an invoice, or bank details,
  • shares personal or account data.

Confirm through a channel you already trust, such as a call to the number on file. For the full steps, see Handle sensitive requests.

If a customer's real emails keep showing the warning, ask their IT team to review their domain's SPF, DKIM, and DMARC records.

Related

  • Handle sensitive requests
  • Manage customers
  • Report spam
Use Cc and Bcc

Copy colleagues on a reply with Cc, send a hidden copy with Bcc, and see who receives each message on an email ticket.

Handle sensitive requests

Check who is really asking before you change an account, move money, or share data, using the checks initdesk already shows you.

Powered by initdesk
On this page
  • Sender verification
  • What the warnings mean
  • How initdesk checks email
  • Forwarding
  • Messages that never show a warning
  • Other channels
  • What to do when you see a warning
  • Related