Why automated forwarding rules don't work
Email-in intake only accepts forwards sent by a real team member from their own address. It's tempting to set up a Gmail filter or Outlook rule to auto-forward every rep email to your intake address, but that doesn't work, by design.
Why auto-forwarding is blocked
When CoverQueue receives an inbound email, it routes the message to your org by the address, then verifies the sender: the From address must match an active member's verified email and pass SPF/DKIM alignment checks. A match means the forwarding member is recorded as the logger: that's how exec-versus-assistant attribution gets attached to the record.
Automated forwarding rules break this because they preserve the original sender's From header. The message arrives looking like it came from the rep, not from your team member, so sender verification can't recognize it.
This is deliberate. Requiring a person to forward keeps spoofed or unsolicited submissions out of your log; the sender is always someone you trust.
What to do instead
Forward the rep's email yourself, from your own work address, attachment included. It's two taps from your phone if you save the intake address as a contact.
From: you@yourcompany.com ← must be a verified member
To: acme-3f2@mail.coverqueue.com
Subj: Fwd: GLASSHOUSE, Marcus Bell (WME)
What happens to blocked mail
Nothing is silently dropped. An email from an unrecognized sender (including anything an auto-forward rule mangled) lands in the Quarantine tab of Intake Review, where you can accept the sender or discard it.
Common questions
Can I whitelist a rep to submit directly? No. v1 targets rep-submitted material forwarded by your team. There's no public or gated intake yet.
My legitimate forward went to quarantine. Confirm you sent it from your verified member address, not an alias or a rule. Accept the sender from Quarantine to turn it into a draft.