Save first
A website-widget request is saved in GeoQuote Lite CRM before asynchronous connector or webhook delivery starts. Hosted quote-link requests also stay in Lite CRM for review and proposal work.
CRM Connectivity
Contractor CRM integration, without imaginary native connectors.
GeoQuote saves a website-widget request first, then attempts only the configured CRM or webhook paths. Hosted quote-link requests stay in Lite CRM, where contractors can build Good/Better/Best proposals, generate PDFs, send proposals by email, record typed homeowner approval, and manage appointment records. Any roof-area context is preliminary, not a precision, order-grade, or insurance-grade measurement report. A delivery record is not proof of contact, identity, qualification, an appointment, or revenue.
Authenticate
Zoho Bigin, HubSpot, and Salesforce use OAuth. GoHighLevel uses a contractor-owned private integration token and required account IDs.
Map
Only configured mappings are sent; blank or missing request values are skipped, and configured defaults can fill selected CRM fields.
Record status
Each connector attempt records a provider-specific success flag, CRM record ID when returned, timestamp on success, or error on failure.
Retry
Failed CRM pushes enter a retry queue. Due entries are processed in batches, and entries are marked permanently failed after five recorded attempts.
What moves into the CRM?
The goal is clean sales context, not noisy form data. GeoQuote gives contractors a better way to map submitted request fields. GeoQuote Lite CRM can keep the request, proposal, typed approval, and appointment record; a broader downstream system remains responsible for any full field-service production, native payment, material-ordering, crew-scheduling, insurance-estimating, or formal e-sign workflow.
Submitted name, email, and phone fields
Submitted property address and available address-check fields
Selected service and saved estimate context
Preliminary provider-characterized roof-area fields when present
Source, campaign, and referral fields when present
Consent timestamp when separately provided
GeoQuote request ID and created timestamp
What is supported today?
Current connectors
Zoho Bigin, HubSpot, Salesforce, and GoHighLevel are represented in the current connector layer. JobNimbus, AccuLynx, and ServiceTitan are not current native GeoQuote connectors; they require a tested email, webhook, middleware, export, or manual handoff.
submitted-number code-entry result
The accepted GeoQuote request shows whether the homeowner entered the texted code. The standard CRM mapping does not currently expose that stored result as a dedicated mappable field. It also does not establish identity, homeowner status, intent, qualification, reachability, or booking.
Email and website-widget webhook paths
Contractor email notification is attempted only when a valid lead-notification address and delivery service are configured. A separately configured notification address takes priority; otherwise GeoQuote uses the account email. For website-widget submissions, active HTTPS webhooks receive only subscribed events, use HMAC-signed payloads, and are saved to a durable outbox before an immediate attempt. Retryable failures use a stable delivery ID and bounded scheduled retries; delivery is at-least-once, so receivers should deduplicate that ID. Neither path guarantees receipt or action.