[{"data":1,"prerenderedAt":90},["ShallowReactive",2],{"blog-post-en-role-email-addresses":3},{"post":4,"related":73,"locales":88},{"id":5,"title":6,"author":7,"body":8,"date":58,"description":59,"draft":60,"extension":61,"image":62,"meta":63,"navigation":64,"path":65,"readingMinutes":66,"seo":67,"stem":68,"tags":69,"updated":71,"__hash__":72},"blog_en\u002Fblog\u002Frole-email-addresses.md","Keep the invoice going to accounts@","MailOK",{"type":9,"value":10,"toc":54},"minimark",[11,20,35,38,41,48,51],[12,13,14,15,19],"p",{},"A customer asks you to send invoices to ",[16,17,18],"code",{},"accounts@example.com",". Your verifier flags it as a role address. Keep it: the customer has told you where the invoice belongs.",[12,21,22,23,26,27,30,31,34],{},"Addresses such as ",[16,24,25],{},"accounts@",", ",[16,28,29],{},"support@"," and ",[16,32,33],{},"hello@"," suggest a function rather than a named person. They may reach a team, one owner or a forwarding rule. The name alone doesn't tell you who reads them.",[12,36,37],{},"The useful question is how the address got onto your list.",[12,39,40],{},"If someone deliberately subscribed a shared inbox to service updates, keep that preference. If the address came from an unexplained import, investigate its source. Apply the same care you'd use for a named person's address.",[12,42,43,44,47],{},"Finding ",[16,45,46],{},"info@"," on a website doesn't establish that its owner wants your newsletter. Equally, a role address on a consumer mailing list doesn't prove it was scraped. People choose unusual addresses for perfectly ordinary reasons.",[12,49,50],{},"Avoid promoting to mailboxes intended for abuse reports, security incidents or technical administration. Use them for the purpose they're published for.",[12,52,53],{},"Don't replace a requested role address with a named contact just because both exist in your CRM. The individual may buy the product while the shared inbox handles the bill. You need to preserve that distinction.",{"title":55,"searchDepth":56,"depth":56,"links":57},"",2,[],"2025-04-10","A role address describes a purpose. It does not, by itself, tell you to remove the contact.",false,"md","\u002Fog\u002Fblog\u002Fen\u002Frole-email-addresses.png",{},true,"\u002Fblog\u002Frole-email-addresses",1,{"title":6,"description":59},"blog\u002Frole-email-addresses",[70],"List hygiene",null,"CxRpDiQkXr2TilqTDP-W16WYRER6o-tiDH411Jlcrbc",[74,81],{"path":75,"title":76,"description":77,"date":78,"tags":79,"readingMinutes":66},"\u002Fblog\u002Fspreadsheet-in-spreadsheet-out","Keep a contact ID in your verification file","A simple export makes it easier to return each result to the right contact without exposing your whole CRM.","2026-07-29",[80,70],"Guides",{"path":82,"title":83,"description":84,"date":85,"tags":86,"readingMinutes":66},"\u002Fblog\u002Fthe-api-now-belongs-to-your-account","Before you connect an email verification API","Plan for unresolved checks, failed requests and changing addresses before putting verification into production.","2026-06-23",[87,80],"API",[89],"en",1790300928336]