Vowel 2.0 - Turn your meetings into searchable, shareable knowledge

@hanna_dawidko_chudziak Thanks Hanna! Would love to hear your feedback!

@hanna_dawidko_chudziak Thank you! What feature are you most excited to try?

@hanna_dawidko_chudziak @andrew_berman +1 :) Let us know your thoughts once you try it out for a meeting.

@erin_letson1, clips and live transcriptions would be extremely useful for my team and me! Not mentioning security which is a must-have nowadays :)

@samantha_harris_ Thanks! Let us know any feedback!

@samantha_harris_ really excited to hear what you think!

Thank you @samantha_harris_ Let us know how it goes.

@samantha_harris_ thank you so much — looking forward to hearing your thoughts!

@volodarik Thanks! We really appreciate it!

Thanks for the support @volodarik

@volodarik give it a spin and let us know what you think!

@volodarik thanks for the great feedback!

@andrew_berman @shivhpatel I hear this pain for sure! One thing I do it add Action items as I go with the `/action` command in the shared notes panel. That way, at the end of the day, I see everything in one place that I agreed to do. Also, you can bookmark insightful moments with a simple key stroke as you're talking. Just press `B` and at the end of your call, you'll get links to all the moments you bookmarked. You can share those with others, or just use them as reference. 💡 Bonus tip: One thing I've always found to be challenging in user research is recalling exactly who said that one key quote that is all-of-a-sudden-super-important-to-share. With Vowel, you don't have to go back and rewatch a bunch of recordings to find that moment: you can do a quick search for any word or phrase spoken on ANY CALL you've been on, and jump right into the meeting. You can clip that insight and share with others (public to anyone with the link, or private to just your workspace members). This allows me to make so much more use of these calls after they are over. AND If you have decided to prioritize something new, you can quickly search back for any time a user mentioned that feature on a call. Re-watch that little bit for the insight, or use that to find potential users to dive in deeper with. Check it out and drop us a line with any feedback or questions!

@andrew_berman @shivhpatel Looking forward to hearing your feedback after you've taken Vowel for a spin! Research Calls / Meetings are a great use-case for Vowel, as you can take simple notes, add bookmarks, comments, highlights, and define action-items — all of these data points are associated with the specific points in time within the meeting/transcript when they were added, which provides valuable context and helps to identify the most relevant parts of the meeting so that you can easily find them later. And because everything within Vowel is searchable, you have the benefit of being able to search across all of your meetings and identify associations, topics, and threads that can help identify important patterns and trends for your research.

@isha_waheed1 Can't wait to have you as a user!

@isha_waheed1 thanks! Give it a try and let us know what you think!

@ariel_rubin Thank you! Really appreciate it!

Thank you for the support @ariel_rubin

@ariel_rubin Thanks! Give it a try and let us know what you think.

@edward_kogan Thank you! 🎉

@edward_kogan Thanks so much!

@edward_kogan @anna_marie_clifton Thanks Ed!

@edward_kogan very well said! Thank you!

@troisi Thank you for the feedback and explaining your current workflow! Unfortunately, Firefox is not currently in our list of supported browsers, but we hope to expand this list in future. https://help.vowel.com/en/articl...

@troisi Fascinating... can you share more about what you mean in "the app gets unhappy"? I'd love to learn more. There shouldn't be any requirement about chrome profiles, so you may have found a bug. If you can record a Loom and send to support@vowel.com, we can dig in deeper! Thanks for the feedback 🙌

@anna_marie_clifton I'll see if I still have notes/screens from when I did a UX interview. My experience - I would use Chrome to use Vowel. The way that I described switching workflows above is due to having a bunch of different gmail addresses as well as a bunch of additional email addresses from my own domains. At some point - I think when I first got an android phone, I decided that one single gmail address would be the catchall for everything, and the way I built it out it's worked surprisingly well. The reason I like FF is because it's a superior browser, full stop. The reason it helps that workflow is container tabs, where I can be logged into one Google account in a series of tabs (both for Google apps as well as external auth0's), and then another set of tabs can be a different google account. The "unhappiness" that came from using Vowel on Chrome for me - was, okay picture this scenario, my catch-all gmail address isn't known to anyone and I never use it to log in to any services. Mistake? Maybe, but that's the gmail I have open the most, seeing and responding to multiple businesses and music ventures and who knows. My particular issue is that chrome more and more likes to have you somehow logged into the entire browser at all times and will limit some features if you're not. I would use a gmail address to sign up for an account for the first time - I would get past the first user/pass and then I'd get to the second screen of your signup which is connect Gcal, and it would specifically show THAT same address, so everything seemed fine. Once I accepted the calendar permissions, it led me to a page that was some engineer's quick work of an error. But it was literally the saddest thing I've ever seen. I forget what it was but it was just some illustration. That error page also had zero way to go anywhere. No links, all I could do was press back. So that was the signup process. I decided to do it again without being logged into Chrome with any account. Same story, email/pass, calendar permissions, then sad error. I think it was a bear with balloons or something? God this is bizarre. I think what I ended up reasoning, and reporting to your devs (actually not devs, it was your UX lead and then I had another meeting with a product manager) was that: *Vowel would not work for me unless I signed up with an account that I was also logged into Chrome with, and any time I used Vowel I would have to be logged into that account in Chrome.* So I'm not sure if someone who just never used the Chrome login feature would have experienced the same bug, or if I had completely traumatized my local version of Chrome with 20 different gmail logins. I'll take a look and see if I have anything that might be of interest to you. But of course I'm going to test this whole thing again, because I just relived it typing all this. Anyway if I have time I'll go back and see if I can find this stuff I documented.

@anna_marie_clifton Hahaha of course I still have that research and I found it in two minutes: #1: This was what I would get when I'd try to sign up: https://imgur.com/a/bsaVBJk #2: This was the "unhappy" thing I remembered. It looks neither sad nor happy. I'm pretty sure this would be the resolution of an internal link when I was logged in with one address and a different browser login: https://imgur.com/VUZNH8k

@troisi Amazing. Thanks so much for surfacing!! You're right, both of these error states could use some love <3 In the first case, it looks like you signed up for an account with one email address and then linked the calendar of another email address. We don't support account bifurcation like that at this time (but I can look into with the eng team!) This should not have anything to do with your browser authentication... it should only be looking at the Vowel authentication (which requires a google email) and the Vowel calendar sync (which also requires a google email that has to match the auth email). We've worked with google to try to get both the email auth and calendar sync through one connection, but they are insistent that we have to ask for it in two separate steps. If you click on "try again with google" and select the same email address you used for authentication, that will progress you through the rest of the sign up. On the second issue, that looks like a bug that I want the eng team to look into. If you're able to share the email account you were using when you encountered that error (and when this happened) that would be ideal. You can email support@vowel.com

@dennisneil Thanks Dennis!

@dennisneil Thanks for the kind words!

@dennisneil Thank you so much for all of the support and kind words!

@karimsaif thanks for your support!

Thank you @karimsaif

@karimsaif Appreciate it! Love all the yellow. Heh :)