Visual website editing
Build the public pages, content, theme, and placement surfaces with the normal Cogo Site editor and publishing workflow.
WEBSITE + LEAD WORKFLOW
A website builder with CRM where the lead path stays traceable
Cogo Site keeps Site Builder, Forms, and CRM as explicit product owners. Publish the site, use a real Form, configure CRM Mapping when you want lead ingestion, then manage the resulting contacts, tags, notes, and lifecycle in the same workspace without pretending every visitor action is a CRM event.
A traceable path from page to submission to CRM contact
The public page does not become the CRM source record. Site Builder owns pages and placements, Forms owns definitions, published revisions and submissions, and CRM owns contacts and customer-management activity.
Canonical Forms workflow
Create and publish supported forms, bind them to site placements, and receive public submissions through the existing Forms domain instead of embedding fake template-only forms.
Workspace CRM
Manage website leads with contact details, tags, notes, lifecycle actions, and the existing Forms-to-CRM ingestion path where configured.
How the website-to-lead path fits together
01
Publish the site and a real Form
Create or edit the website and use a canonical published Form. Trusted Local Service templates can provision their approved inquiry Form at site creation; other placements continue through the normal Forms builder and binding lifecycle.
02
Configure CRM Mapping explicitly
Enable CRM Mapping on the Form and map compatible fields such as Name, Email, Phone, Company, Job Title, Locale, or marketing-consent input. The CRM ingestion path uses that published mapping instead of guessing field names.
03
Keep the submission and manage the contact
Forms keeps the submitted record. When CRM ingestion is enabled and allowed, CRM resolves or creates the contact, records a Form submission activity, and leaves tags, notes, and lifecycle available for workspace follow-up.
What actually moves from a Form into CRM
The integration is intentionally narrower than an all-purpose sales suite: configured identity and consent fields can become CRM context, while the original submission remains owned by Forms.
Data step 1
Map only compatible fields
CRM Mapping can explicitly map Name, Email, Phone, Company, Job Title, Locale, and marketing consent from compatible published Form fields. Unmapped answers are not silently promoted into contact identity.
Data step 2
Preserve submission provenance
The Form submission remains the canonical submitted record. CRM ingestion carries the submission/site/Form provenance and records a Form submission activity against the resolved contact instead of replacing the Forms inbox.
Data step 3
Manage the customer record deliberately
CRM can resolve or create the contact without overwriting established manual values, then the workspace can use tags, notes, and lifecycle states. Broad visitor tracking, campaign sequences, and guaranteed follow-up are outside this page's claim.
The four current trusted Local Service templates — HVAC, Roofing, Cleaning, and Landscaping — include approved inquiry Forms, but this does not mean every Cogo Site template provisions a Form and a provisioned Form is not automatically CRM-connected. CRM ingestion still depends on the Form's explicit CRM Mapping and current entitlement/quota rules.
Follow the canonical product owners
Site Builder, Forms, and CRM stay separate owners with explicit integration seams rather than becoming one opaque marketing workflow.
Website builder with CRM FAQ
Does every template automatically create a CRM-connected form?
No. The four current trusted Local Service templates — HVAC, Roofing, Cleaning, and Landscaping — provision an approved inquiry Form at site creation, but not every Cogo Site template does. A provisioned Form is also not automatically CRM-connected: CRM ingestion still requires explicit CRM Mapping plus the applicable entitlement and quota checks.
What form fields can map into CRM?
The current CRM Mapping supports compatible fields for name, email, phone, company, job title, locale, and marketing consent. The published mapping is authoritative; ingestion does not guess arbitrary answer names.
Does CRM track every visitor action automatically?
No. The current CRM focuses on contacts, tags, notes, lifecycle, and supported lead ingestion. Broad behavioral journey tracking is not implied by this solution page.
Are Forms and CRM separate website runtimes?
No. They are workspace capabilities that integrate with the published site through explicit APIs and placements; the public website still uses the normal site renderer.
Which plan includes the current Forms and CRM capabilities?
The current product configuration exposes the full customer-engagement workflow on Pro. The Pricing page remains the source of truth for current plan coverage.
Connect a real website to a traceable lead workflow
Build the site, publish the Form, then enable the supported CRM mapping when structured lead ingestion belongs in your workflow.