3.9 out of 5 (42 Ratings)
Apr 20, 2017
I have had success with this vendor because it is widely used amongst our industry professionals.
Mar 16, 2017
Salesforce Chatter is easy to use and right before one's eyes when viewing a record, thus encourages participation. It works for an exchange of low-information content messages and short one-to-three message "conversations". It keeps information centralized--ie, within Salesforce--for a given issue or record. That's also a plus. However, it is not quite as quick or adaptable as email, and it discourages the more involved exchanges that are sometimes essential. For example, email text formatting options are superior, and one can typically attach prior emails to a new one. Chatter is lacking in these areas, just to name a couple. Also, while Chatter will auto-email message recipients, the email lacks some essential details that could be automatically provided at least in some cases, such as the Salesforce object and/or record number, or the record's description or title. This would be especially easy to do with Salesforce Case object, for which we use Chatter extensively.
Mar 14, 2017
Working with Salesforce is always enjoyable. They have superb customer service and knowledgable team members able to help with any and all issues that may arise.
Mar 14, 2017
Mar 7, 2017
Detail oriented and wide breadth of subject matter to choose from.
Mar 6, 2017
Mar 4, 2017
We moved our helpdesk (incident / request) system into salesforce. The experience we had was a somewhat painful as we wanted to get it going on a deadline. We had some major problems with our own adaption of the service versus our client/server helpdesk system. We have yet to move all of our inventory and change management system into salesforce. We use chatter and it's adoption was pushed by leadership. We still use other instant message systems for real time collaboration. Chatter is more of a "mood setting" device. We post messages both personal and enterprise wide on chatter.
Feb 27, 2017
Overall the first go at the project failed. The second go was more successful but still improving implementing.
Feb 24, 2017
Its a useful technology, takes some getting used to
Feb 21, 2017
Working with 3rd party developers/trainers has been critical