Open
Sort by upcoming KIT dates
Single list sortable by keep in touch by date and includes keep in touch by date as a "property" in the "Views"
Jeremy Foster 8 days ago
Web Product
Open
Sort by upcoming KIT dates
Single list sortable by keep in touch by date and includes keep in touch by date as a "property" in the "Views"
Jeremy Foster 8 days ago
Web Product
Open
Interactions Counting/Analytics
Can we add a feature of counting the number of interactions with a group of people? For example, I want to count how many coffee chats I had with Tesla in the past 3 months ○ Time: Total number of interactions per week, month, quarter○ Filter: Dex tag, Dex group, company/organization○ Interaction type: coffee, meeting, note○ Chart types: line chart and bar chart Current limitation: When I export notes/events as csv, the file doesn't have filters of tag or group for me to create a chart
Nathan Pham 8 days ago
Web Product
Open
Interactions Counting/Analytics
Can we add a feature of counting the number of interactions with a group of people? For example, I want to count how many coffee chats I had with Tesla in the past 3 months ○ Time: Total number of interactions per week, month, quarter○ Filter: Dex tag, Dex group, company/organization○ Interaction type: coffee, meeting, note○ Chart types: line chart and bar chart Current limitation: When I export notes/events as csv, the file doesn't have filters of tag or group for me to create a chart
Nathan Pham 8 days ago
Web Product
Open
Allow Users to Customize Pre-Meeting Brief Delivery Time
Details: Pre-meeting briefs are currently sent at a fixed time before meetings, and users cannot adjust when they’re delivered. In some cases, users have also experienced briefs arriving after a meeting has already started, which defeats the purpose of preparation. Requested improvements: Allow users to configure how many minutes before a meeting they receive the pre-meeting brief (e.g., 10, 20, 30, 60 minutes) Ensure briefs are reliably delivered before the meeting start time Optionally allow different defaults per user or meeting type
CJ 11 days ago
Open
Allow Users to Customize Pre-Meeting Brief Delivery Time
Details: Pre-meeting briefs are currently sent at a fixed time before meetings, and users cannot adjust when they’re delivered. In some cases, users have also experienced briefs arriving after a meeting has already started, which defeats the purpose of preparation. Requested improvements: Allow users to configure how many minutes before a meeting they receive the pre-meeting brief (e.g., 10, 20, 30, 60 minutes) Ensure briefs are reliably delivered before the meeting start time Optionally allow different defaults per user or meeting type
CJ 11 days ago
Open
(API) Retrieve Contacts based on creation or update date
Currently there doesn't appear to be a way to retrieve contacts based on recent changes. One can implement this offline by caching the entire contact list and doing a diff, but that puts unnecessary load on the API server and isn't particular efficient. To address this, it would be create if we could pass in a creation or update date alog with the retrieval API call, and only get back those that match (if any).
Ramon Felciano 12 days ago
Web Product
Open
(API) Retrieve Contacts based on creation or update date
Currently there doesn't appear to be a way to retrieve contacts based on recent changes. One can implement this offline by caching the entire contact list and doing a diff, but that puts unnecessary load on the API server and isn't particular efficient. To address this, it would be create if we could pass in a creation or update date alog with the retrieval API call, and only get back those that match (if any).
Ramon Felciano 12 days ago
Web Product
Open
“hooks” > auto-generated outreach copy
Summary: Provide user-controlled “hooks” and/or guided prompt input instead of fully auto-generated outreach copy. Problem / User Feedback Users perceive the current auto-generated outreach message suggestions as overly familiar and uncomfortable—especially for long-dormant relationships (e.g., no interaction in 25 years). Proposed Solution Add one (or both) of the following options in the reconnect flow: 1. Selectable hooks list• Show a short list of suggested conversation hooks as checkboxes (e.g., shared context, mutual connections, last known location/company, general “catch up” prompt).• User selects which hooks to include (or none).2. User prompt textbox• Provide a short input field: “What do you want to say / what’s the intent?”• AI generates a message only based on explicit user intent and selected hooks.
joe 14 days ago
Web Product
Open
“hooks” > auto-generated outreach copy
Summary: Provide user-controlled “hooks” and/or guided prompt input instead of fully auto-generated outreach copy. Problem / User Feedback Users perceive the current auto-generated outreach message suggestions as overly familiar and uncomfortable—especially for long-dormant relationships (e.g., no interaction in 25 years). Proposed Solution Add one (or both) of the following options in the reconnect flow: 1. Selectable hooks list• Show a short list of suggested conversation hooks as checkboxes (e.g., shared context, mutual connections, last known location/company, general “catch up” prompt).• User selects which hooks to include (or none).2. User prompt textbox• Provide a short input field: “What do you want to say / what’s the intent?”• AI generates a message only based on explicit user intent and selected hooks.
joe 14 days ago
Web Product
Open
Modify Order of Note Types
On https://getdex.com/appv3/settings/note-types, please make note types drag and droppable (modify order). Then have this order displayed in the contact details. Whatever is first here should show as default note type on the contact page.
Josh Bauer 15 days ago
Open
Modify Order of Note Types
On https://getdex.com/appv3/settings/note-types, please make note types drag and droppable (modify order). Then have this order displayed in the contact details. Whatever is first here should show as default note type on the contact page.
Josh Bauer 15 days ago
Open
Optional Prospecting Tools for Identifying High-Value Contacts from Existing Networks
Details: Some users are interested in using Dex to identify potential enterprise or high-value contacts from their existing followers or connections (e.g., LinkedIn, social graphs), even though Dex is primarily designed as a personal relationship CRM, not a sales tool. This use case would involve: Analyzing existing connections or followers Surfacing contacts that may be relevant for enterprise outreach Light segmentation or prioritization (without turning Dex into a full sales CRM) This is likely a niche / optional use case, and not core to Dex’s current positioning. However, documenting it helps clarify product boundaries and could inform future experiments or integrations for users who straddle personal CRM and early-stage founder workflows.
CJ 18 days ago
Open
Optional Prospecting Tools for Identifying High-Value Contacts from Existing Networks
Details: Some users are interested in using Dex to identify potential enterprise or high-value contacts from their existing followers or connections (e.g., LinkedIn, social graphs), even though Dex is primarily designed as a personal relationship CRM, not a sales tool. This use case would involve: Analyzing existing connections or followers Surfacing contacts that may be relevant for enterprise outreach Light segmentation or prioritization (without turning Dex into a full sales CRM) This is likely a niche / optional use case, and not core to Dex’s current positioning. However, documenting it helps clarify product boundaries and could inform future experiments or integrations for users who straddle personal CRM and early-stage founder workflows.
CJ 18 days ago
Open
Client-Only Mode for Manual Engagement Tracking (KIT-Focused CRM)
Details: Some users want to use Dex primarily as a lightweight, client-focused CRM, centered on Keep-in-Touch (KIT) reminders and manual engagement tracking — without relying on social, email, or LinkedIn automations. Use case: Track a small, rotating set of active clients Log meetings, calls, and emails manually Use KIT reminders to ensure thoughtful follow-up No need for: LinkedIn sync Social graph imports Automatic contact creation Contacts are added intentionally and limited to clients only Constraints today: Users who rely on Outlook Desktop (IMAP) or non-web email clients can’t benefit from Dex’s automation Value of Dex becomes clear only after weeks of manual KIT usage, not within a 7-day trial Dex is positioned as a broad relationship manager, while this audience wants a focused client-engagement tool Requested enhancements (conceptual): A “Client Mode” or configuration focused on: Manual interactions KIT-first workflows Reduced emphasis on social/email sync Positioning or onboarding that supports manual-first CRM usage Consideration of: Longer evaluation periods for manual workflows A lighter-weight plan or mode for client-only use cases
CJ 22 days ago
Open
Client-Only Mode for Manual Engagement Tracking (KIT-Focused CRM)
Details: Some users want to use Dex primarily as a lightweight, client-focused CRM, centered on Keep-in-Touch (KIT) reminders and manual engagement tracking — without relying on social, email, or LinkedIn automations. Use case: Track a small, rotating set of active clients Log meetings, calls, and emails manually Use KIT reminders to ensure thoughtful follow-up No need for: LinkedIn sync Social graph imports Automatic contact creation Contacts are added intentionally and limited to clients only Constraints today: Users who rely on Outlook Desktop (IMAP) or non-web email clients can’t benefit from Dex’s automation Value of Dex becomes clear only after weeks of manual KIT usage, not within a 7-day trial Dex is positioned as a broad relationship manager, while this audience wants a focused client-engagement tool Requested enhancements (conceptual): A “Client Mode” or configuration focused on: Manual interactions KIT-first workflows Reduced emphasis on social/email sync Positioning or onboarding that supports manual-first CRM usage Consideration of: Longer evaluation periods for manual workflows A lighter-weight plan or mode for client-only use cases
CJ 22 days ago
Open
Support Multiple Photos per Business Card (Front & Back)
Details: Currently, Dex only supports a single image when scanning or attaching a business card. Many business cards include important information on the back (e.g., notes, alternate contact details, branding, or additional languages). Requested improvement: Allow users to add multiple photos to a business card record (e.g., front and back) Ensure all images sync across devices and remain attached to the contact Clearly label or order images (Front / Back) Value: Preserves complete business card information Reduces data loss from one-sided scans Improves usability for international or non-standard business cards
CJ 23 days ago
Open
Support Multiple Photos per Business Card (Front & Back)
Details: Currently, Dex only supports a single image when scanning or attaching a business card. Many business cards include important information on the back (e.g., notes, alternate contact details, branding, or additional languages). Requested improvement: Allow users to add multiple photos to a business card record (e.g., front and back) Ensure all images sync across devices and remain attached to the contact Clearly label or order images (Front / Back) Value: Preserves complete business card information Reduces data loss from one-sided scans Improves usability for international or non-standard business cards
CJ 23 days ago
Open
Create Notes Linked to Specific Meetings via Zapier (Meeting-Aware Notes)
Details: Today, Dex’s Zapier integration only supports creating generic notes, updating contacts, or creating generic reminders. This limits automation workflows where meeting notes should be attached to a specific calendar event and its associated contacts. Tools like Avoma already provide rich meeting metadata to Zapier (e.g. contact name, email, Zoom/Google Meet ID, meeting ID), which should make it possible to correctly match notes to the exact meeting that just occurred. Current limitation: Zapier can only create a generic note in Dex Notes cannot be associated with: A specific calendar event The meeting ID The correct contact-meeting relationship Users must manually attach notes to meetings after the fact Ideal state: Add a Zapier action such as “Create Meeting Note” or “Attach Note to Meeting” Allow the action to accept identifiers like: Meeting ID (Google Meet / Zoom) Calendar event ID Contact email(s) Automatically attach the note to: The correct meeting The relevant contact timeline Value: Enables fully automated meeting-note workflows (e.g. Avoma → Dex) Eliminates manual cleanup after meetings Preserves accurate context by tying notes to the exact interaction Makes Dex significantly more powerful as a CRM system of record
CJ 23 days ago
Open
Create Notes Linked to Specific Meetings via Zapier (Meeting-Aware Notes)
Details: Today, Dex’s Zapier integration only supports creating generic notes, updating contacts, or creating generic reminders. This limits automation workflows where meeting notes should be attached to a specific calendar event and its associated contacts. Tools like Avoma already provide rich meeting metadata to Zapier (e.g. contact name, email, Zoom/Google Meet ID, meeting ID), which should make it possible to correctly match notes to the exact meeting that just occurred. Current limitation: Zapier can only create a generic note in Dex Notes cannot be associated with: A specific calendar event The meeting ID The correct contact-meeting relationship Users must manually attach notes to meetings after the fact Ideal state: Add a Zapier action such as “Create Meeting Note” or “Attach Note to Meeting” Allow the action to accept identifiers like: Meeting ID (Google Meet / Zoom) Calendar event ID Contact email(s) Automatically attach the note to: The correct meeting The relevant contact timeline Value: Enables fully automated meeting-note workflows (e.g. Avoma → Dex) Eliminates manual cleanup after meetings Preserves accurate context by tying notes to the exact interaction Makes Dex significantly more powerful as a CRM system of record
CJ 23 days ago
Open
Remove or Increase 20-Contact Limit in Quick Actions (Frequency Assignment)
Details: The Quick Action flow for assigning “Keep in Touch” frequencies is very useful, but it currently stops after 20 contacts, forcing users to restart the process each time. For users with large contact lists (e.g., 5,000+ contacts), this limit significantly slows down bulk setup and cleanup workflows. Assigning frequencies at scale would be much faster if users could continue the Quick Action flow without interruption. Requested improvements: Remove the 20-contact limit entirely, or Allow users to configure a higher batch size (e.g., 100, 500, unlimited), or Provide a “Continue next batch automatically” option without restarting the flow Value: Dramatically improves efficiency for large contact databases Reduces repetitive restarting and cognitive overhead Makes Quick Actions viable for serious contact cleanup and onboarding workflows
CJ 25 days ago
Open
Remove or Increase 20-Contact Limit in Quick Actions (Frequency Assignment)
Details: The Quick Action flow for assigning “Keep in Touch” frequencies is very useful, but it currently stops after 20 contacts, forcing users to restart the process each time. For users with large contact lists (e.g., 5,000+ contacts), this limit significantly slows down bulk setup and cleanup workflows. Assigning frequencies at scale would be much faster if users could continue the Quick Action flow without interruption. Requested improvements: Remove the 20-contact limit entirely, or Allow users to configure a higher batch size (e.g., 100, 500, unlimited), or Provide a “Continue next batch automatically” option without restarting the flow Value: Dramatically improves efficiency for large contact databases Reduces repetitive restarting and cognitive overhead Makes Quick Actions viable for serious contact cleanup and onboarding workflows
CJ 25 days ago
Open
Fix CSV Import for contacts
CSV Import does not work as it returns an error message. Tried multiple different files, refreshed the site, cleared cache, and tried also in different browsers.
Mark Bitter 25 days ago
Web Product
Open
Fix CSV Import for contacts
CSV Import does not work as it returns an error message. Tried multiple different files, refreshed the site, cleared cache, and tried also in different browsers.
Mark Bitter 25 days ago
Web Product
Open
Contact Clean Up Mode for Finding & Resolving Edge-Case Duplicates
Details: Reconciling duplicate contacts is one of the most labor-intensive parts of using Dex. Duplicates commonly arise from name changes (e.g., marriage), nicknames, automatic email imports, or inconsistent formatting. Currently, Merge Contacts only surfaces very high-confidence matches and does not help users identify or resolve edge cases. As a result, users are forced to manually search common names (e.g., “Claire”) and visually scan for duplicates. Proposed solution: Introduce a “Contact Clean Up” mode (similar in spirit to Quick Actions) focused specifically on identifying and resolving potential duplicates that require human judgment. Possible capabilities: Surface lower-confidence duplicate candidates for user review (not auto-merge) Detect patterns such as: First/last name + email domain similarities Nickname vs. legal name (e.g., Liz / Elizabeth) Same company + similar names Allow users to: Review uncertain matches one by one Approve, skip, or dismiss merge suggestions Provide search and filtering tools specifically optimized for cleanup workflows Value: Dramatically reduces manual effort in maintaining clean contact data Gives users control over ambiguous merge decisions Improves long-term data quality without risking incorrect automatic merges
CJ 26 days ago
Open
Contact Clean Up Mode for Finding & Resolving Edge-Case Duplicates
Details: Reconciling duplicate contacts is one of the most labor-intensive parts of using Dex. Duplicates commonly arise from name changes (e.g., marriage), nicknames, automatic email imports, or inconsistent formatting. Currently, Merge Contacts only surfaces very high-confidence matches and does not help users identify or resolve edge cases. As a result, users are forced to manually search common names (e.g., “Claire”) and visually scan for duplicates. Proposed solution: Introduce a “Contact Clean Up” mode (similar in spirit to Quick Actions) focused specifically on identifying and resolving potential duplicates that require human judgment. Possible capabilities: Surface lower-confidence duplicate candidates for user review (not auto-merge) Detect patterns such as: First/last name + email domain similarities Nickname vs. legal name (e.g., Liz / Elizabeth) Same company + similar names Allow users to: Review uncertain matches one by one Approve, skip, or dismiss merge suggestions Provide search and filtering tools specifically optimized for cleanup workflows Value: Dramatically reduces manual effort in maintaining clean contact data Gives users control over ambiguous merge decisions Improves long-term data quality without risking incorrect automatic merges
CJ 26 days ago
