Currently when a review request goes out and the contact is assigned to a user, the email will come from the assigned user's email address (which usually does not match the dedicated sending domain).

This can lead to landing in SPAM because the sender email is being masked, or in some cases (like mine) where a DMARC reject policy is in place, the email won't be sent at all.

Receipts, Invoices, Estimates all have this sender details customization functionality. Even marketing email templates have the ability to set custom sender details (but not Reputation Management templates for some reason).

I have a workaround, which is to send review requests from a workflow, which splits into an if/else according to assigned user > unassigns the user > sends the review request > then re-assigns the user. This allows the review request to be sent from the default dedicated sending domain.

Unfortunately, follow-up review requests still won't work in my case (unless I hold the contact in the workflow, unassigned, until a review has been received). -- But this is obviously a far from elegant approach. And in a company with many users, will not be realistic to accomplish.

I'm categorizing this as a "Bug", even though it might technically be an "Enhancement", because it seems like a huge oversight to not allow this type of customization in a module as important as Review Management.