Add more ways to fix: "Fin did not try to answer because the sender could not be authenticated" | Community
Skip to main content
Submitted

Add more ways to fix: "Fin did not try to answer because the sender could not be authenticated"

Related products:Fin & AI
  • Apr 21, 2026 10:35 AM UTC
  • 1 reply
  • 22 views

When Fin is deployed over E-mail there is a DMARC security (setting) before Fin will answer to the e-mail. In my case; like 20-30% of the incomming e-mails aren’t getting answered because of this problem: 

 "Fin did not try to answer because the sender could not be authenticated"

Fin escalates the conversation immediately, even when Fin could answer the e-mail so easily. 

 

Right now, there aren’t any options to troubleshoot this problem or any triggers to solve it automatically. So my question is: Can you guys find a way to automate the process what fixes the error and so can Fin the e-mail that was sent in the first place? 

1 reply

We see the same thing. 26 genuine emails were skipped in 10 days for us. In our case the cause is forwarding: our support address is a Google Workspace mailbox that forwards to Intercom. Intercom support confirmed that the check ignores ARC seals. I've filed a specific request to use the ARC seal from trusted forwarders: https://community.intercom.com/ideas/use-the-arc-seal-from-trusted-forwarders-in-fin-s-email-authentication-check-15866 If your mail is forwarded too, an upvote there would help.