Currenly, we have rules to autoreply to emails. When we are on annual leave and our vacation reponser is set, it still sends the 'rules', so they get our usual autoreponser, in addition to the vacation responser.
As an administrator, I would like to set the following rule: If message received in any inbox AND to OR cc recipients are part of an accountassign message to account owner The reason is we have several vendors and internal notifications that go to...
We are transitioning out of manual tagging each client name and properly using the account contact feature. Some are having a harder time not seeing it so obvious so I would like to pitch that account name can have a preview tag the same way a Jir...
Would love to have the ability to generate company rules, such as SLAs, company wide but geared towards specific shared inboxes. The intention is to create uniformity in company based rules as opposed to individual shared inbox rules.
It would be helpful to be able to limit contact lists to only certain teammates. We have contacts will similar names and other departments accidentally send to the wrong address at times.
Add Tags as a new field in the composer (i.e. To, CC, BCC, Subject, Tags)
Could you please move the Tags in the message composer UI to facilitate the use of TAB to add tags? Meaning that after entering the "To" field into the composer field, you'd be able to TAB to the tags and more easily add a tag to an email.
While in Front, we would like to be able to click a button to have Front search the Autotask system to find the ticket created so we can put time in against the ticket. It would be great if Front actually pulled up the ticket in Front or as a star...
Select Timezone to display based on user vs reciever
Timezone issues & request: The timezones in Front display dates and times of custom date/time field in the Front User (ie, Employee) timezone. However, when we are communicating with our clients we communicate the time of their appointments in...
When a contact is created in the SFDC P4 Plug-in, there is no definitive confirmation that the contact has been created. This leads to confusion and duplicate entries of the same contact into our SFDC database