How our website inquiries reach the CRM
An implementation note on connecting a website inquiry form to Twenty, with saved submissions, retries, and a clear handoff.
A contact form has two jobs: make it easy for someone to explain what they need, and get that information to a place where the business can follow up. An email notification helps, but an inbox alone is a fragile place to manage the handoff.
This is an implementation note about Bransford Media’s own website. It describes the system we use, not a client case study or a claim of measured time savings.
Start with a durable submission
The website saves the inquiry in Payload, the CMS behind the site. That saved record matters: notification delivery and CRM synchronization are separate steps, and either can fail after a visitor submits a form.
The visitor should get a truthful result from the form. Internally, the team needs enough information to find the original submission and determine what happened next. A reassuring screen is not a substitute for a saved record.
Connect the handoff to Twenty
A background job synchronizes the inquiry to Twenty, our CRM. It looks for a person using the supplied email address, links the company when appropriate, and adds an inquiry note. The form and the CRM have different responsibilities: the website collects the request; the CRM gives it a place in the business relationship.
Matching people by email helps avoid creating another contact every time someone reaches out. Company names need more care because spelling and naming conventions vary. The system should preserve what was submitted without treating an uncertain match as a verified fact.
Treat failures as part of the workflow
The synchronization job has bounded retries with increasing delays. If the CRM is briefly unavailable, the website does not need to ask the visitor to retype the inquiry. The original submission remains the reference for checking or recovering the handoff.
Retries also introduce a design question: what if part of the work completed before the error? Finding an existing person reduces duplicate contacts, but that does not make every write automatically duplicate-proof. Notes and follow-up actions need their own duplicate handling and operational checks. That is something to inspect when adapting this pattern to another business.
Measure the meaningful step
The website records a lead event after a successful form submission. That is more useful than counting every click on a contact button as a lead. A separate booking event distinguishes a completed calendar booking from simply opening the booking page.
Neither event proves that an inquiry was qualified or became a project. Those outcomes belong in the CRM. Website analytics can explain how people arrived and which pages helped them take the next step; the business still needs to assess the conversation.
Applying this to your website
Before choosing an integration tool, map the handoff. Where is the original request saved? How is an existing contact matched? Who owns the next action? What happens when synchronization fails? Can you identify and recover a missing handoff without asking the prospect to submit again?
A small system with explicit answers is easier to operate than a long chain of automations whose final result no one checks. Our marketing systems work starts with that map and the tools your team already uses.
Talk through a workflow or read how we separate website content from code.