Maddy

Hi Jocelyn S.! Ah yes, sorry about the link... it’s not a public one. I’ve noted your interest in the source request and added it on your behalf ➕ And great point on the transitions between clips. I’ve shared that with the team as well, it’s on their radar, and your feedback helps reinforce it 🙌

Hey Jazz! 👋 Love this idea!!! It can definitely get tricky keeping track of participants in a reel. This isn’t something we support right now, but I’ve added it to our backlog as a feature request so we can keep it on the radar. Thanks for sharing!

Hi Julee P., thanks so much for sharing this and so great to hear you're loving the integration! 🎉 We’re currently moving away from Canny and back to manually created feedback and feature request tickets for our product team. I’ve linked your post to an existing ticket we’re tracking that looks to improve the flexibility of calendar configuration, including use cases like yours. Really appreciate you taking the time to highlight this!

Hi Juhani, Great call out! We've created a Linear ticket to track this as a feature request for enabling "User" in data fields. It’s helpful to understand how people are using participant assignment. Appreciate the insight, we’ll keep you posted!

Hi Alia K., Thanks so much for picking that up! We’ve actioned a bug request related to that, and Michal S. will be fixing it up soon. Regarding the merging ability, at the moment, you can merge speakers in a transcript, but you’re not able to merge Contacts themselves. I’ve added a linear feature request ticket to ensure this gets prioritised. To merge speakers within the transcript, first unlink the contacts you don’t want associated with the data, then assign them to the contact you want to be the primary. This will bring up the “Merge participants in transcript” dialog, which will ask you to confirm that all instances of Participant X will be merged with the primary contact you're assigning. Once you click confirm, you can delete the unused contacts within Contacts. Hope this helps! Let me know if you have any questions

Hey Emi, Right now, you can track where someone has contributed across the platform through search and their user profile page, though we know there’s room to refine this experience. As Dovetail evolves, you’ll eventually be able to see a user’s contributions more clearly with dedicated search filters and a more comprehensive view on their profile. We really appreciate you sharing these nuances 🙌, it’s super helpful as we think about contacts and speaker attribution. We hear you on the need for more flexibility when handling speakers who don’t neatly fit into users or contacts, and we’re keeping this top of mind as we improve these workflows. Thanks again for your insights!

Hi Emi F., If the speaker isn’t a user and you don’t want to add them as a contact, you’ll need to leave them unassigned for now. Out of curiosity, is there a reason you wouldn’t add them as a viewer? Since viewer seats are free, adding them would ensure their contributions are recognised if they engage with Dovetail in the future. We’re also exploring the connection between users and contacts, as there’s often overlap. Even at Dovetail, we have users who act as contacts and vice versa, so we understand the need for more flexibility here. We really appreciate you sharing these use cases with us!

Hi Emi! 👋 At this point in time, Admins can update permissions in Security settings to control who can access and use the Contacts database. For example, restricting it to Managers and Contributors means that Viewers will see a “Person hidden” experience. We also recognise that some teams need a way to reference contacts without full access to individual metadata. We’re actively exploring how a “view only” experience could better meet the needs of users like yourself who want visibility without the ability to create or edit contacts. Thanks for raising this, your feedback is really helpful!

Thanks for sharing your feedback! We totally hear you on wanting flexibility when working with participant names. Dovetail does intend for participants to be assigned to a contact, as this helps keep data connected across your workspace. However, if your company prefers not to create real contacts due to PII concerns, we recommend either:

The reason we moved away from free-text participant names on a page is to ensure data is better linked throughout the platform. Contacts play a key role in Dovetail’s future as a customer insights hub, with ongoing improvements to the contacts database, CRM integrations, and linking insights across your workspace. That said, we understand this change impacts different teams in different ways. Your feedback is really helpful in shaping how we think about PII needs and how we can improve this update further. We also recognise that not all contributors may be familiar with managing contacts, if there’s anything we can do from a change management perspective (e.g, guidance, settings, or workflows) to help, we’d love to hear your thoughts. We appreciate you taking the time to share your experiences