Skip to content
The estimate request

A missed call becomes a scoped estimate request by lunch.

A homeowner calls about a kitchen redo, gets voicemail, and starts typing into the site instead. Six questions later the office has a scoped estimate request waiting: the project, the property, and roughly when. Free to start, live in five minutes.

You automate contractor estimate intake by putting a conversational agent in front of the request. It asks for the project, the property, the scope and the rough timeline one question at a time, types the answers into a structured job record, and posts it to your CRM before anyone calls back.

01 · They talk

Your GnosariAnswering
What’s the project, and where’s the property?
Finally doing our kitchen, it’s straight out of the 90s. House is at 1420 Birchwood Lane.
Got it. Roughly when would you like it done?
No rush really, sometime this fall if that works

02 · It becomes a record

project_type
Kitchen remodel
property_address
1420 Birchwood Lane
project_description
Full remodel, kitchen is original from the 90s
desired_start_timeframe
This fall, no rush

typed · validated · deduped

03 · Your stack acts

  • Office pinged
  • Zap into your CRM
  • Or the same via Make
  • Signed webhook at your endpoint
The process

The process this page is about

Not "AI for contractors". One process, the one that decides whether a scoped project reaches your crew or the next contractor on the search results: the estimate request, the message that arrives before anyone has picked up the phone.
  • Who starts it

    Someone who finally wants the kitchen done, or just found a leak, usually on a phone, usually not during business hours.

  • What it costs today

    A phone line that rings out on more than a quarter of calls, or a contact form that asks about a bathroom refresh the same way it asks about a full addition.

  • What it has to produce

    A scoped job record: the project, the property, the timeframe, and anything urgent enough to need a crew today rather than next month.

27%

of inbound calls to contractors go completely unanswered, and most callers just call the next name on the list

Ring Eden

The schema

What it asks, and what it never asks

You name the fields your estimate form already has. It does the asking, in whatever order the story comes out, and it keeps asking until the required ones are filled.
FieldTypeRequiredWhy it is there
full_nametextYesIdentity on the job record
phonephoneYesHow the office calls back
property_addresstextYesWhere the crew would actually go
project_typetextYesRoutes to the right crew and trade
project_descriptiontextYesThe scope, in their own words
desired_start_timeframetextYesTiming the office checks, never the agent
safety_hazard_presentbooleanFlags anything urgent enough to escalate right now
zip_codetextFeeds the service-area check, never a coverage promise
had_prior_quotesbooleanContext for how competitive the estimate needs to be
reasontextWhy someone is cancelling or concerned, if that is why they are here

And what it will not do

  • It never quotes, estimates or ballparks a price, a day rate or a cost range, no matter how the question is phrased.
  • It never commits to a start date, an arrival time or a completion date. Scheduling is confirmed by the office.
  • It never says whether a job needs a permit, an inspection or HOA approval, or whether a project meets code.
  • It never diagnoses the cause of a structural, electrical or plumbing problem, and never calls a repair simple or minor.
  • The moment anything sounds like an active hazard, it stops asking questions and says to call emergency services now.
  • It never invents a field. If they did not say it, the record says "Not captured" instead of a guess.
The live run

Try the run yourself

Six situations a contractor’s office actually handles, each running its own agent with its own fields. Pick one and answer it the way a real homeowner or crew lead would, out of order and mid-thought, and watch it ask the follow-up instead of accepting the blank.
Open this one full screen
I need some work doneConnecting
The live conversation is loading.
Where the records land

What the office opens in the morning

Every conversation that produced something useful arrives here as a row someone can read in two seconds. Every value keeps the sentence it came from, and anything the agent itself said can never become your data.

Collected data

187 collected26 this week5 need attention

Export CSV
  • Marisol Vega New estimate, kitchen remodelEstimate Request · 1h ago
  • Derek Combs No heat, escalatedEmergency Callout · 3h ago
  • Priya Shah Asked about coverage areaService Area & Scope Check · Yesterday
  • Owen Whitfield Returning, bathroom nextReturning Client Check-In · Yesterday
  • Nate Boyer Framing done, needs sign-offSite Update · Fri

Marisol Vega

Captured 1h ago · Estimate Request · joina.chat

Captured data 6 of 7 fields

full_nameMarisol Vega
phone+1 512 555 0173
property_address1420 Birchwood Lane
project_typeKitchen remodel
project_descriptionFull remodel, kitchen is original from the 90s
desired_start_timeframeThis fall, no rush
financing_statusNot captured

From the conversation

“It’s been on our list for years, not sure if we need a permit for the layout change , the last contractor we called never really explained it.”

Every value keeps the sentence it came from, and a value the visitor never said is never stored. A Gnosari cannot quote itself into your data.

From here a record can go straight on to Slack, a sheet, a Zap or your own API. The inbox is where you read them, not where they get stuck.

Where it goes next

Your CRM gets the job, not another login

The moment the estimate request is complete, Gnosari posts it to whatever address you give it. Signed, versioned and retried. From there it is a webhook, which reaches almost anything a contractor already runs.
POST https://hooks.zapier.com/hooks/catch/2345678/bcdefgh

Signed headers

webhook-id
msg_2f9a41c8
webhook-timestamp
1786518862
webhook-signature
v1,K7Qd…8xPm

Body

{
  "type": "data.collected",
  "event_id": "1b6f9c02-4d1a-4f7e-9b3c-2a5e8d0f1c44",
  "created_at": "2026-08-11T09:14:22Z",
  "payload_version": "v1",
  "data_kind": "New estimate request",
  "record_id": 1234,
  "attributes": {
    "full_name": "Marisol Vega",
    "phone": "+1 512 555 0173",
    "property_address": "1420 Birchwood Lane",
    "project_type": "Kitchen remodel",
    "project_description": "Full remodel, kitchen is original from the 90s",
    "desired_start_timeframe": "This fall, no rush"
  }
}
  • Two events

    data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when someone corrects something.

  • Signed, so you can trust it

    Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before it opens a job.

  • Quotes are opt-in

    The provenance block, the homeowner’s verbatim words, is absent unless you turn it on for that destination.

  • Zapier or Make

    Paste a Catch Hook URL into your Gnosari destination, then point the Zap at your CRM.

    Free tier, no app to install, and it fires the moment the estimate request is complete.

    • Salesforce
    • HubSpot
    • Calendly
    • Mailchimp
  • Straight to the office

    Anything that accepts an incoming webhook takes the payload as it is.

    No middleman. The office sees the request before the crew does.

    • Slack
    • Teams
    • Sheets
    • Twilio SMS
  • Your own endpoint

    Give us an https address, verify the signature, open the job yourself.

    A few lines of code, and the delivery log tells you when something did not land.

    • Postgres
    • Supabase
    • Retool

And you can see every attempt

WhenEventOutcomeDetail
14:12:07data.collectedDelivered200 OK
14:11:58data.collectedFailed503, retrying in 30s
Yesterday 16:40data.updatedDelivered200 OK
Yesterday 08:15data.collectedDelivered200 OK

Every attempt is kept, newest first, with the reason when there is one. Failures retry on their own, and the signing secret lives in your dashboard so you can rotate it without calling anybody.

These are examples, not a partner list. ServiceTitan, Jobber, Housecall Pro and Buildertrend are all reachable the same way: through a Zap, or straight to an endpoint you control. If it takes an HTTP request, it takes the job.

Two ways it can look

On your site, or a link you text after a missed call

Both are live right now. The widget in the corner takes the estimate request from someone reading your services page. The link is what you text back to a missed call, and it works before the office opens.
chat

The widget on your site

A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.

  • One line of HTML, anywhere on your site
  • Bubble, sidebar, sidebar-push or drawer
  • Opens over the page, closes again
conversation

A page of its own

No chat window and no widget. Your headline leads, the thread sits under it, and it reads like you asked rather than like software collecting.

  • Sent as a link, or scanned from a QR
  • Its own headline, caption and greeting
  • Every link counted separately
  • One responsive page: phone, tablet or desktop

Every screen on this page is a published Gnosari, embedded from the app. Type into any of them.

Put it on your site

One snippet, four ways to wear it

Paste one line of HTML anywhere on your site. How the widget sits on the page is a setting, not a rebuild, and you can change it after you ship.

Bubble

display_mode="bubble"

A floating button in the corner. Opens over your page and closes again. The default, and the one nobody has to be taught.

Four corners to choose from

Sidebar

display_mode="sidebar"

A fixed panel down one side, always open. For pages where the conversation is the point rather than an aside.

Left or right, any width

Sidebar push

display_mode="sidebar-push"

The same panel, but your content moves over to make room instead of being covered. Nothing on the page is ever hidden.

Left or right, any width

Drawer

display_mode="drawer"

Slides in over the page when it is called, then slides away. The middle ground between a bubble and a sidebar.

Left or right

Where else it lives

Not every conversation starts on a website

The same Gnosari, reached three other ways. A link, a code, or a piece of paper. All of them land in the same record.

01 · A link you send

joina.chat/l/your-slug

Put it in an email, a text, a booking confirmation or a signature. Each link carries its own opening line and headline, and counts its own visits, so you can tell which channel actually worked.

  • Its own greeting and headline
  • Optional expiry date
  • Counted separately

02 · A code they scan

The same link, printed

Every link comes with a QR. On a table card, a receipt, a delivery note, a door. Someone points a phone at it and the conversation starts, with no app and no typing.

  • PNG or SVG, print resolution
  • Points at the same slug
  • Old printed codes keep working

03 · A flyer you hand over

posters.gnosari.com

A builder for the printed thing itself. Pick a template, restyle it, edit the words on the page and export a print-ready poster or card with the QR already placed.

  • Posters, cards and flyers
  • Print or PNG export
  • No account needed
Whose brand it wears

Your brand, down to the font

Nobody should be able to tell it is us. Start from a curated look, mix your own colour and pattern, or set every design token yourself: every surface follows, from the widget to the conversation page to the link someone opens on their phone.

01 · Start from a preset

Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.

  • plainsky · noneCorporate or formal, or let the content lead
  • clean-dotssky · fine-dotsSaaS, B2B, dashboards
  • ocean-wavesocean · wavesWellness, travel, spa
  • forest-topoforest · topographyOutdoors, sustainability, eco
  • blueprintblue · blueprintEngineering, dev tools, architecture
  • graph-paperindigo · graph-paperEducation, finance, analytical
  • circuitteal · circuitTech, hardware, AI, electronics
  • soft-bubblesrose · bubblesFriendly, lifestyle, community, care
  • sunset-glowsunset · blobsCreative, marketing, bold consumer
  • emerald-gridemerald · gridHealth, growth, productivity
  • confettifuchsia · confettiEvents, kids, playful brands
  • mono-noiseviolet · noiseMedia, publishing, premium and minimal

02 · Or mix your own

22 colour themes and 44 background patterns, each drawn in code at four intensities. That is 3,872 combinations before you touch a single token.

22 colour themes

  • purple
  • blue
  • green
  • orange
  • pink
  • indigo
  • cyan
  • rose
  • amber
  • teal
  • fuchsia
  • sky
  • emerald
  • violet
  • sunset
  • ocean
  • forest
  • neon
  • gold
  • coral
  • lavender
  • mint

44 background patterns

  • dots
  • grid
  • diagonal-lines
  • zigzag
  • hexagons
  • triangles
  • diamonds
  • squares-rotated
  • cross-dots
  • plus-signs
  • waves
  • bubbles
  • clouds
  • topography
  • organic-blobs
  • flowing-curves
  • subtle-grid
  • circuit
  • blueprint
  • isometric
  • graph-paper
  • fine-dots
  • confetti
  • stars
  • hearts
  • sparkles
  • paper-texture
  • noise
  • chat-bubbles
  • speech-marks
  • conversation
  • messages
  • emoji-smileys
  • emoji-hearts
  • emoji-stars
  • emoji-thumbsup
  • social-likes
  • social-reactions
  • paint-splatter
  • brush-strokes
  • doodles
  • squiggles
  • party
  • flowers

Every pattern, four intensities

  • subtle
  • light
  • medium
  • strong

03 · Or set every design token

Exact hex values, fourteen fonts, bubble shape per side, corner radius, density, header and input. Explicit tokens always win over the preset. Two chats can share every line of markup and still wear two different brands: only the tokens differ.

A boutique hotel

fontFamily
Playfair Display
colorPrimary
#A16207
colorSurface
#FAF7F2
bubbles.user.radius
xl
radius
lg
Maison AurelOnline
Is late checkout possible on Sundays?
Until 2pm, and there will be coffee waiting downstairs.

A developer tool

fontFamily
JetBrains Mono
colorPrimary
#34D399
colorSurfaceDark
#0D1117
bubbles.user.radius
sm
radius
sm
relaydbOnline
Does the API rate limit per key?
600 requests a minute per key, with bursts to 1,000 for 30 seconds.

fontFamily accepts fourteen faces

  • Inter
  • system-ui
  • Roboto
  • Open Sans
  • Lato
  • Montserrat
  • Poppins
  • Source Sans 3
  • Nunito
  • DM Sans
  • Lora
  • Playfair Display
  • JetBrains Mono
  • Space Grotesk
  • radius: none · sm · md · lg · xl
  • density: compact · comfortable · spacious
  • intensity: subtle · light · medium · strong

Set with one call, or one click in the designer. Changing it later takes the same one call, and every published surface updates at once.

The alternative

Instead of what you do now

The comparison that matters is not against another chatbot. It is against the voicemail and the contact form on your site.
What changesVoicemail and a callbackPDF or web contact formGnosari
After hoursRings outSubmitted, never openedAnswered, typed, delivered
What you get backA name, if they left oneWhatever fit in the boxesThe scope in their own words
Half-told scopeOffice calls back to askSubmitted half emptyIt asks the follow-up
TimingWhatever they say on the phoneA dropdown with no nuanceCaptured loosely, confirmed by the office
Gets into your CRMRe-typed by handCSV, or an integration you pay forSigned webhook, the moment it is complete
The pricing lineDepends who answeredNot applicableNever quoted, and stated at the start
Common Questions

Frequently Asked Questions

Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.

Still have questions?

Our team is here to help you get started.

Gnosari runs the estimate request a contractor would otherwise take on a missed call: the property, the work wanted, photos and measurements if they have them, the timeline and how to reach them. It asks one question at a time on your website or through a link, then posts a scoped job record to your CRM or field service platform. Your estimator opens a complete request instead of a voicemail.

Five minutes from now your missed calls could be scoped job records.

Build the agent, put it on your services pages, and watch the first estimate request arrive. Free to start, no card.