Thanks for hunting @bentossell. Let me share the back story. Tooltip.io (it's an SEO name, really) was born out of our own need. Basically, we wanted to answer FAQs and provide help to new users. I always felt like sending a user to an FAQs page or messaging them later over email was too late. After all if you're trying to figure out the product, you want help right there right now.
The product is in open beta, would love your thoughts, comments, suggestions. Feel free to ask us anything.
@danflopes Thank you Daniel. Quite a few customers we get use Tooltip.io in conjuction with Intercom. The feedback we get is that they need more flexibility in addressing user issues. That's where Tooltip comes in. We employ 6 message types (a couple more in the works) from simple tooltips to draw user's attention to a menu item or decode unfamiliar term to page specific FAQs (see example - http://bit.ly/2bf9mr6) and more.
Looks great - quite tempted. However, I don't see the two way messaging... seems like we can create messages, even contextual help tips, but what if a customer has a question in response to a message?
@batsirai_chada Thank you Batsirai. Valid point. The use case we had in mind is eliminating those 50% of customer support tickets that usually deal with repetitive user questions about product functionality, i.e. What does LTV mean? or How do I add a team member? so you can answer them in-app as they arise in context of the page or task at hand.
Here's an example of what I'm talking about - http://bit.ly/2bf9mr6
Report
@romanzadyrako Totally agree. So for your intercom integration - do you see providing an option to end users to contact support if the tooltip didn't supply the right answer. B e also great if we could then see which tooltips resulted in tickets... so we could improve those tooltips?
This is a really cool tool, must for all SaaS applications. Provide realtime and relevant assistance to your customers to guide them in your software usage.
@keithwhor Thanks Keith. Tooltip.io was born out of our own need. Basically, we wanted to answer FAQs and provide help to new users. I always felt like sending a user to an FAQs page or messaging them later over email was too late. After all if you're trying to figure out the product, you want help right there right now.
A personal pain for me was being able to add these without help from developers. I remember fighting over wrongly named Mixpanel events with our CTO, and I felt powerless. So we wanted to make it easy to add, setup and preview in-app messages without coding.
Report
Really like your UX, extremelly simple to use!
Is ot possible to get metrics, such as where are users having more problems, or when do they leave my website?
This is a simple but powerful tool, can ser how it can help me with user retention, congratulations!
@carlosleisantos Thank you Carlos. That's the goal. Each in-app message has tracker, and we're working on unifying this data in a meaningful way to show you where users struggle and where you can intervene with a help message to get them over the hurdle.
signalayer
Remotes.in
signalayer
Reverb
signalayer
signalayer
Retainly Email Content Spam Checker
signalayer
signalayer
Autocode
signalayer
signalayer