Qubit - A useful Customer Experience Tool
December 05, 2016

Qubit - A useful Customer Experience Tool

Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

Overall Satisfaction with Qubit

One department controls the roadmap, which is inputted into by many different departments. Qubit is primarily used as an A/B testing tool. We have tried to use their personalisation features but with limited success. We purchased professional services, which acted as a 'middle man' between our commercial organisation and the Qubit development team.
  • Professional services is incredibly knowledgeable. Many experiences we wanted to create would not have been possible without this.
  • Quick to fix issues we have raised in production.
  • Commitment to engaging our internal teams by running workshops across Europe.
  • Industry leading personalisation product. A shame we didn't get a chance to use it!
  • Delivery times. More often than not, delivery dates were missed. This was very frustrating throughout our relationship.
  • Production issues. We had several issues in production due to Qubit product changes that we were unaware of. This was unacceptable.
  • Professional services spread too thinly. Sometimes, our contacts took too long to respond, which was exacerbated massively when employees were on annual leave.
We opted for Qubit due to their personalisation features compared to the other market offering, as we felt their Visitor Cloud was a USP in the industry. The Visitor Cloud allows further personalisations, such as social proofs, to complement internal data we have gathered and transform it into a live, front end product.
Well Suited for:

  • Verify internal changes made by A/B testing.
  • Using social proof to improve customer journeys.
  • Segmenting customers based on locations/languages/previous actions.
  • Targeting specific users by uploading CSVs.
  • Personalising the experience based on all of the above.
Not Suited:

  • Large builds take a long time and have many defects. This takes further time to fix them.
  • Quick wins can take a long time due to the build/QA queues that come as a result of the shared resource pool that's split amongst several clients.