Khoros is great for large organizations to keep track of social posting!
Updated January 22, 2018
Khoros is great for large organizations to keep track of social posting!

Score 10 out of 10
Vetted Review
Verified User
Modules Used
- Conversations
- Intelligence
Overall Satisfaction with Khoros Marketing (Formerly Spredfast + Lithium)
Khoros is being used across our marketing (including agency), legal, trademark, and other departments. It addresses the business problem of teams posting directly to a platform before getting appropriate approvals - this allows our corporate reputation to have another layer of security in order to be protected much better than it was previously.
Pros
- Corporate reputation security - extra layer of approvals is very helpful.
- Through intelligence, our teams can monitor talk across social and know when something important surfaces.
- Khoros allows us to see and filter all posts, whether visible on a page or dark and promoted posts.
Cons
- I'm looking forward to having Khoros Audience ready but FB API issue may limit this.
- Khoros can improve some of its search capabilities for larger companies that have many pages of data.
- I would like to see an overall calendar viewing of a sector's initiatives up front vs. having to filter for them on an initiative.
Khoros was more valuable to the company than Sprout Social because it works large scale much better and the organization is superb.
Khoros Social Media Management Feature Ratings
Khoros Marketing (Formerly Spredfast + Lithium) Support
| Pros | Cons |
|---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
Yes - I have reported bugs on behalf of myself and other users and I am always pleased with the quick responses and resolution.
One time there was an issue in Conversations where users couldn't "publish now" and my customer partner immediately looked into it and got the engineers involved. They had a fix published to production within a couple days with an explanation I could share with my users. So great!
Comments
Please log in to join the conversation