block email from creating tickets and conversations
ART-17650_KNOWLEDGE_NODE-8
correct team with preserved context\n* Minimize handoff loss and shorten time-to-resolution\n\n**Controlling support entry points**\n\nThe company deployed a custom Snap-in that restricts ticket creation to verified email domains. This has:\n\n* Cut down on ticket noise\n* Prevented duplication\n* Ensured high-quality, accountable issue tracking\n\n#### The email Snap-in changed our entire intake game. It's security-conscious by design, and that's crucial for us.\xe2\x80\x9d\n\n**Improving
American cybersecurity leader unifies security & support with DevRev
ART-1478_KNOWLEDGE_NODE-47
only, not as a direct mailbox to which anyone can send their emails. Emails received (either directly or by forwarding) from senders who aren\xe2\x80\x99t in the allowlist are dropped. There are a few exceptions to this like Google\xe2\x80\x99s forwarding confirmation emails.\n\nThe allowlist can either contain an email address or an entire domain. Strict matching is done for domains, meaning that subdomains are not included.\n\n#####\n\nThe email protocol regarding forwarding is not very well
Event sources — DevRev | Docs
ART-1981_KNOWLEDGE_NODE-29
originated, usually someone from customer success or sales.\n* Ask follow-up questions to get the full context of the problem.\n* If the article suggestion didn't help the user, search in the customer-facing documentation or knowledge base and share any relevant results.\n* If you receive any spam messages, you can choose the **Mark as Spam** option, which will prompt a pop-up. To mark the sender as spam, select the **Mark all as spam** option in the pop-up.\n* If you are tagged on a
Support best practices | Computer for Support Teams | DevRev
ART-2027_KNOWLEDGE_NODE-46
is added to the user. The user can be removed from the spam list by navigating to the contact and removing the spammer tag from the contact.\n\nIf you want to allow a user to send emails without rate limits, add the power-user tag to the user.\n\nBy providing explicit tuning for specifying the rate limit, DevRev ensures that legitimate support emails are not affected by potential spam attacks or mail loops.\n\n[PreviousGoogle Calendar
Email | Integrate | Snap-ins | DevRev