Clarifying Terminology for AI: Participant, User, and Contact Equivalence

·Feb 27, 2025 07:17 PM·

❓ are the terms participant, user, contact equated in the backend for the AI? In addition to new filter options (contacts, contact fields), having these terms equated would allow us to tighten our prompts within Search/Ask. That is, we could be confident the AI is not analyzing text/raw data from non-users/contacts/participants.

👀2

2 comments

· Sorted by Oldest

Product Advice

Clarifying Terminology for AI: Participant, User, and Contact Equivalence

Maegan P.

·Feb 27, 2025 07:17 PM·

❓ are the terms participant, user, contact equated in the backend for the AI? In addition to new filter options (contacts, contact fields), having these terms equated would allow us to tighten our prompts within Search/Ask. That is, we could be confident the AI is not analyzing text/raw data from non-users/contacts/participants.

👀2

2 comments

· Sorted by Oldest

Peter W.
·
·
Hi Maegan P., I'm from the engineering team at Dovetail. To give the AI the strongest understanding of what you want it to do, I recommend using either "user" or "interviewee" or "contact." From my testing, it doesn't understand "participant" as well (surprisingly), due to ambiguity. However, this depends on the raw data you have, so your results may vary!
👍1
Maegan P.
·
·
Thank you! I hope the team considers adding the two filters as that would help without needing to change language.
👍1

Peter W.
·
·
Hi Maegan P., I'm from the engineering team at Dovetail. To give the AI the strongest understanding of what you want it to do, I recommend using either "user" or "interviewee" or "contact." From my testing, it doesn't understand "participant" as well (surprisingly), due to ambiguity. However, this depends on the raw data you have, so your results may vary!
👍1
Maegan P.
·
·
Thank you! I hope the team considers adding the two filters as that would help without needing to change language.
👍1