Feature Requests

It would be fantastic if Rolodex supported the Model Context Protocol (MCP). MCP provides a standardized way for large language models (such as ChatGPT) to securely and contextually interact with external data sources through a clean API abstraction. By implementing MCP, Rolodex would enable AI systems to ask intelligent, high-level questions about contacts, companies, communication history, and relationship data — without requiring custom API work for each use case. Example AI use cases: “Who on my team has had a lot of recent interactions with CFOs in the past 6 weeks?” “Give me a list of CEOs we've been in touch with who work in construction companies.” “Who have we talked to about ERP recently?” (based on email and calendar subjects) “I'm organizing an event about SAP in Brussels for C-level executives — which contacts from my network should I invite?” “What are the top 5 industries that my colleague [name] has engaged with over the past 12 months?” “For each Rolodex team member, show the top 5 companies they've interacted with during the selected period.” “Give me a list of companies we’ve had contact with in the last 24 months that have between 20–500 employees and are active in one of the following sectors: fire detection, access control, or video surveillance.” Benefits: Smarter, context-aware assistance from AI, powered by real-time Rolodex data No need for one-off API integrations or ad hoc queries Interoperability with AI platforms that support MCP (e.g., OpenAI, Anthropic Claude, Microsoft, Google DeepMind, LangChain, N8N, MuleSoft, ...) High value for knowledge-driven sales, business development, and relationship teams Enables a new class of conversational analytics and opportunity discovery based on existing relationship data

Get notified everytime somebody adds e.g "Stealth" to their titles

Scanning the meta data of previous interactions and calendar appointments, suggest follow-ups with contacts. Integrate AI capability to draft a message to the respective contact based on most recent interactions, and other user context like linkedIn profile updates.

We propose adding a feature that encourages Rolodex users to connect on LinkedIn with people they’ve interacted with via email or calendar meetings. This option should be configurable by each user—meaning everyone can decide individually whether to enable or disable this prompt. Why is this important? Richer Contact Data: When users establish a 1st-degree LinkedIn connection with their contacts, Rolodex can access richer data—such as profile photos, job titles, locations, and more—directly from LinkedIn, significantly enhancing the contact profiles. Greater LinkedIn Reach and Impact: By proactively building a larger LinkedIn network with contacts from their email and calendar, both individuals and teams can increase their reach. For organizations like research or consultancy firms, this translates to greater impact and visibility when posting updates, insights, or achievements on LinkedIn. Additionally, when you ask questions within your network, having more LinkedIn connections increases the likelihood of receiving helpful answers. Some consultants and professionals value a well-developed LinkedIn network as a key part of their business development and personal branding strategies. Feature Details: Rolodex should identify contacts with whom the user has interacted via email or calendar but is not yet connected to on LinkedIn—and where no invitation is currently pending. Users should receive non-intrusive suggestions or reminders to connect with these contacts on LinkedIn. The feature should be optional and user-configurable in the settings. Summary: Encouraging users to connect with relevant contacts on LinkedIn will enrich Rolodex data and empower users and teams to expand their professional networks and influence.

Ability to create a custom field type where you can mark another contact within the workspace. Similar to Custom field type "workspace user" but with another contact stored in the database as the data value.

When importing a CSV file of contacts into Rolodex, it is currently not possible to include multiple email addresses or phone numbers per contact—despite the fact that Rolodex supports this at the contact level. Additionally, it would be very useful to have the ability to map custom fields, tags, and lists during the import process. This would enable more accurate and complete data entry and reduce the need for manual corrections after import. Suggested improvements: Support for importing multiple email addresses and phone numbers per contact Field mapping for custom fields, tags, and lists during the import process After uploading and mapping the CSV file, display a summary before execution, including: * How many new contacts will be created * How many duplicates have been found * How duplicate contact data will be merged or overwritten * A confirmation step before committing changes to the Rolodex database This would make bulk imports more transparent and safer, especially in environments where data integrity and deduplication are critical.

Show a timeline of all workspace users activity (emails, meetings, notes)