{"id":527,"date":"2025-04-09T13:49:04","date_gmt":"2025-04-09T13:49:04","guid":{"rendered":"http:\/\/gogetmuscle.com\/?p=527"},"modified":"2025-04-09T17:39:40","modified_gmt":"2025-04-09T17:39:40","slug":"meeting-reminders-and-confirmations-being-sent-from-hubspot-domain-instead-of-our-own","status":"publish","type":"post","link":"http:\/\/gogetmuscle.com\/index.php\/2025\/04\/09\/meeting-reminders-and-confirmations-being-sent-from-hubspot-domain-instead-of-our-own\/","title":{"rendered":"Meeting reminders and confirmations being sent from HubSpot domain instead of our own"},"content":{"rendered":"<p><P class=\"\" data-start=\"279\" data-end=\"302\">Hi HubSpot Community <span class=\"lia-unicode-emoji\" title=\":waving_hand:\">\ud83d\udc4b<\/span><\/P><br \/>\n<P class=\"\" data-start=\"304\" data-end=\"510\"><BR \/>We\u2019re currently facing an issue with <STRONG data-start=\"341\" data-end=\"386\">meeting reminders and confirmation emails<\/STRONG> being sent from a HubSpot-generated domain (e.g., <CODE data-start=\"437\" data-end=\"460\">notifybf2.hubspot.com<\/CODE>) instead of our <STRONG data-start=\"477\" data-end=\"509\">authenticated company domain<\/STRONG>.<BR \/><BR \/><\/P><br \/>\n<P class=\"\" data-start=\"512\" data-end=\"728\">This affects not only the <STRONG data-start=\"538\" data-end=\"578\">professionalism of our communication<\/STRONG> with clients, but also may impact <STRONG data-start=\"613\" data-end=\"641\">deliverability and trust<\/STRONG>, especially when these emails land in spam folders or appear suspicious to recipients.<BR \/><BR \/><\/P><br \/>\n<P class=\"\" data-start=\"730\" data-end=\"978\">We already use a <STRONG data-start=\"747\" data-end=\"774\">custom connected domain<\/STRONG> for marketing emails, and SPF\/DKIM are correctly configured. However, it seems that <STRONG data-start=\"859\" data-end=\"907\">calendar-related reminders and confirmations<\/STRONG> from the meeting tool are still being routed through a HubSpot domain.<\/P><br \/>\n<P class=\"\" data-start=\"980\" data-end=\"997\">We\u2019d like to ask:<\/P><br \/>\n<UL data-start=\"998\" data-end=\"1300\"><br \/>\n<LI class=\"\" data-start=\"998\" data-end=\"1082\"><br \/>\n<P class=\"\" data-start=\"1000\" data-end=\"1082\">Is there a way to configure <STRONG data-start=\"1028\" data-end=\"1054\">meeting-related emails<\/STRONG> to use our custom domain?<\/P><br \/>\n<\/LI><br \/>\n<LI class=\"\" data-start=\"1083\" data-end=\"1195\"><br \/>\n<P class=\"\" data-start=\"1085\" data-end=\"1195\">If not natively supported yet, are there any <STRONG data-start=\"1130\" data-end=\"1145\">workarounds<\/STRONG> or <STRONG data-start=\"1149\" data-end=\"1167\">best practices<\/STRONG> the community recommends?<\/P><br \/>\n<\/LI><br \/>\n<LI class=\"\" data-start=\"1196\" data-end=\"1300\"><br \/>\n<P class=\"\" data-start=\"1198\" data-end=\"1300\">Has anyone successfully dealt with this and managed to make these reminders appear more brand-aligned?<\/P><br \/>\n<\/LI><br \/>\n<\/UL><br \/>\n<P class=\"\" data-start=\"1302\" data-end=\"1409\">This is becoming increasingly important as we scale our use of HubSpot meetings with clients and prospects.<BR \/><BR \/><\/P><br \/>\n<P class=\"\" data-start=\"1411\" data-end=\"1476\">Any guidance would be greatly appreciated!<BR \/><BR data-start=\"1453\" data-end=\"1456\" \/>Thanks in advance <span class=\"lia-unicode-emoji\" title=\":folded_hands:\">\ud83d\ude4f<\/span><\/P><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Hi HubSpot Community \ud83d\udc4b We\u2019re currently facing an issue with meeting reminders and confirmation emails being sent from a HubSpot-generated domain (e.g., notifybf2.hubspot.com) instead of our authenticated company domain. This affects not only the professionalism of our communication with clients, but also may impact deliverability and trust, especially when these emails land in spam folders [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"_links":{"self":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/527"}],"collection":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/comments?post=527"}],"version-history":[{"count":1,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/527\/revisions"}],"predecessor-version":[{"id":528,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/posts\/527\/revisions\/528"}],"wp:attachment":[{"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/media?parent=527"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/categories?post=527"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/gogetmuscle.com\/index.php\/wp-json\/wp\/v2\/tags?post=527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}