You automate moving company intake by putting a conversational agent in front of the quote enquiry. It asks for the route, the timing, the rooms, access and any special items one question at a time, types the answers into a structured record, and posts it to your CRM before an estimator ever calls back.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone with a lease ending, a job offer in another city, or a house that just sold, usually browsing quote sites at night and usually not sure yet on the exact date.
What it costs today
A "Request a Quote" web form that asks for an address and a date and nothing about stairs, parking or the piano, or a 45 to 90 minute in-home or video survey that only happens once someone has shown serious intent.
What it has to produce
A typed enquiry record: the route, the timing window, the rooms, the access constraints, and anything unusual enough that an estimator needs to know before quoting.
62%
of moving leads never convert - the bottleneck is the intake, not the lead volume
SmartMoving
| Field | Type | Required | Why it is there |
|---|---|---|---|
| origin_location | text | Yes | Where the truck starts |
| destination_location | text | Yes | Where the truck ends up |
| move_timing | text | Yes | The window an estimator plans around, never a fixed date |
| room_count | text | — | Roughly how much is moving |
| stairs_or_elevator_access | text | — | Access at either end changes crew size and time |
| parking_availability | text | — | Where the truck can actually park |
| what_matters_most | text | — | The detail a form never asks for and the one that predicts a repeat customer |
| special_items | text | — | The piano, the safe, the fish tank - flagged before move day, not on it |
| packing_or_storage | text | — | Whether this is a bigger job than a truck alone |
| full_name | text | Yes | Who the quote goes to |
email | Yes | Where the quote gets sent | |
| phone | phone | — | A backup way to reach them |
And what it will not do
Collected data
148 collected19 this week3 need attention
Export CSVRenee Castillo
Captured 2h ago · Northpoint Moving, Quote Enquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“We’ve had this piano in the family forever, I really don’t want it scratched up , so whoever handles it needs to know that going in.”
Every value keeps the sentence it came from, and a value the visitor never said is never stored. The chatbot 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.
Signed headers
Body
{
"type": "data.collected",
"event_id": "1b6f9c02-4d1a-4f7e-9b3c-2a5e8d0f1c44",
"created_at": "2026-08-11T09:14:22Z",
"payload_version": "v1",
"data_kind": "New move enquiry",
"record_id": 1234,
"attributes": {
"full_name": "Renee Castillo",
"phone": "+1 720 555 0134",
"origin_location": "Denver, CO",
"destination_location": "Austin, TX",
"move_timing": "Early September, date not fixed",
"special_items": "Upright piano"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a customer 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 file.
Quotes are opt-in
The provenance block, the customer’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 enquiry is complete.
Straight to the office
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The estimator sees the enquiry before dispatch does.
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.
And you can see every attempt
| When | Event | Outcome | Detail |
|---|---|---|---|
| 19:04:22 | data.collected | Delivered | 200 OK |
| 19:04:18 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 09:37 | data.updated | Delivered | 200 OK |
| Yesterday 07:52 | data.collected | Delivered | 200 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. SmartMoving, Supermove, MoversTech and Elromco 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.
A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.
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.
Every screen on this page is a published Gnosari, embedded from the app. Type into any of them.
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
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
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
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
01 · A link you send
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.
02 · A code they scan
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.
03 · A flyer you hand over
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.
Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.
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
44 background patterns
Every pattern, four intensities
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
A developer tool
fontFamily accepts fourteen faces
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.
| What changes | Phone tag and a callback | Web quote form | Gnosari |
|---|---|---|---|
| After hours | Rings out, or a callback promise | Sits in an inbox until Monday | Answered, typed, delivered |
| What you get back | Whatever they remember to say | Whatever fit in the boxes | The move, in their own words |
| Special items | Only if they think to mention it | No field for it | Asked about directly, every time |
| Access and parking | Found out on move day | Not asked | Captured before the truck is booked |
| Half-told story | A rep calls back to ask | Submitted half empty | It asks the follow-up |
| Gets into your CRM | Re-typed by hand | CSV export, maybe | Signed webhook, the moment it is complete |
Everything you need to know about getting started. Can't find the answer you're looking for? Reach out to our team.
Name the fields your quote form already has, point the agent at your services pages, and put the link on your site. The agent runs the conversation, produces a typed enquiry record, and posts it to your CRM through a webhook, Zapier or Make. Setup is minutes, not an implementation project.