A flexible data model
Twenty supports custom objects, fields and relations. That is how we added projects and project tasks alongside customers and deals.
Optional CRM plans
On CRM plans, Twenty CRM is deployed alongside the workspace with their connection already configured. CRM retains its own users and permissions.
Two connected environments
Twenty stores contacts, companies and deals, plus Projects and Project Tasks prepared by AI-COMFORT. After signing in to their own CRM account, an employee can work with that data from the workspace chat.
‘Show this customer's open deals and related project tasks needing attention.’
CRM data is available in chat within the employee's permissions, without opening another interface for every question.
Agent workspace
Chats, knowledge, files and the tools permitted for the team.
Twenty CRM
Contacts, deals, projects and project tasks with separate accounts and permissions.
A CRM should adapt to the company's work, rather than forcing the company into a fixed set of fields.
Twenty supports custom objects, fields and relations. That is how we added projects and project tasks alongside customers and deals.
Records can be organized in tables, boards and calendars, with saved views for different teams.
Sales can follow deals by stage while project teams see tasks and related records in their own structure.
Twenty is developing AI capabilities that operate within its data and permission model. AI-COMFORT uses Twenty's native MCP connection to bring CRM data into the shared chat.
Native CRM AI features are configured separately; to use permitted CRM data from the workspace, employees connect their own CRM accounts.
Manage contacts, companies, deals and other work objects in Twenty CRM.
AI-COMFORT prepares additional Projects and Project Tasks objects.
The MCP connection to Twenty is already configured. An employee selects the integration, clicks Connect and signs in to their own CRM account. The model can then use data available to that account without manual API-key setup.
CRM users are created separately from workspace users, and their count is not tied to workspace seats. Each employee gets the right CRM permissions; authorization links their work across the two systems.