← All posts
Example CRM structure linking a person, an opportunity and a next action.

technology

Twenty CRM: give enquiries a place beyond the inbox

  • A second enquiry from the same person belongs to an existing relationship.
  • Twenty connects people, companies and opportunities, with fields you can adapt to your work.
  • Self-hosting gives you a choice of where it runs. You also take on backups, updates and access management.

Someone asks about a website. Six months later, the same person wants a workshop. You want to see both conversations when you open their record, without searching two inbox folders and a spreadsheet.

That’s the useful starting point for a CRM. Who is this person, what have they asked for, and what happens next?

Give each record a job

Twenty provides People, Companies and Opportunities as connected records. Its custom fields and saved views let you adapt that structure to your business.

For a studio that offers websites, video and workshops, I would keep the relationship together and put the service type on the opportunity. One person can discuss several pieces of work without becoming three unrelated contacts.

This is an example setup, using invented details:

RecordExampleWhat you need from it
PersonAlex, the person making the enquiryContact details and the related company
CompanyExample StudioThe organisation behind the work
OpportunityWebsite redesignService type, stage, owner and next action

The fields should answer questions you ask during the week. A stage such as “Proposal sent” tells you where the conversation stands. An owner and next action tell you who needs to do something about it. If nobody uses a field, I’d question why we’re asking someone to fill it in.

Connect the form after the process is clear

Twenty has REST and GraphQL APIs for reading and updating its records. Custom objects also receive API endpoints. That gives a developer a way to connect a website form or another business tool to the same data. Twenty API documentation .

A possible client workflow would accept a website enquiry, look for a matching contact, and attach a new opportunity to that person. Someone on the team would then review it and choose the next action. This is a proposed integration, not a description of an automation already running at the studio.

Before building it, I’d settle what counts as a duplicate and what happens when the connection fails. Otherwise you can end up with two contact cards for Alex and no clear record of which one needs a reply.

The hosting is part of the work

The studio’s Twenty work currently includes a local Docker configuration for the application and database. That configuration alone doesn’t establish a working enquiry pipeline.

For a client, I would agree where the system runs, who can access it, and who maintains it. Twenty’s self-hosting guide covers persistent storage, backups and restoring the database. A restore test belongs in the handover.

I wouldn’t promise that installing a CRM fixes follow-up. You still need someone to read the enquiry and act on it. Think of the CRM as the reception desk: useful when the person taking over can see what happened before they arrived.

Tell me how an enquiry reaches your team . We can map the records, the next action and the connection your website needs.

Interested in this?

Learn about Technology →