CommitCRM Email Updates to Customer

[anthonyatech]

Hi all,

Thanks ahead of time for any input! We utilize the email connector for tickets by email from customers. In addition, as many of you most likely do, we will utilize CommitCRM to send an email regarding a ticket back to the client. The question I have is this: Is there a way to configure who CommitCRM sends the email as? For example, when I send a ticket update to a client from within CommitCRM it utilizes my name as the sender as the email connector account, not the email connectors account name (Support). In the future when a client sends me an email directly, they will send it not knowingly to the support system because when they start typing my name, the email connector email address populates instead of mine due to the way CommitCRM labels the sent email and this is becoming more troublesome than anything else. I would like if someone can explain how to get the email sending via CommitCRM to utilize the email connector's address and name it accordingly instead of using my name or my tech's name.

Thanks!

[Support Team]

Re: RangerMSP Email Updates to Customer

Thank you for posting this.

Currently there is no option to overwrite the sender name in the employee replies with a generic support name. We have such request on our list and will add your comment there.

[Vowcorp]

Re: CommitCRM Email Updates to Customer

We need this too. It is a pain, and we don't want customers to only then work with 1 person because that is who's name is on the email. They should be able to work with any of our employees, but CommitCRM puts the tech's name on it, and now customers think they can only work with that one tech.

I know it is on the list, but any ETA for this?

[Support Team]

Re: RangerMSP Email Updates to Customer

Thank you for posting this.

The option to use a unified Sender name for Employee replies was introduced in version 18.

In case you already use version 18, you can change the settings for the Email Connector to use a generic Sender Name using these instructions.

Restarting the 'RangerMSP Server' service on your server is required to have the change applied immediately.

Hope this helps.