You automate wedding planner intake by putting a conversational agent in front of the first enquiry. It asks for the date they hope for, the guest count, the venue status and a budget range one question at a time, types it into a structured record, and never holds a date or quotes a price.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A couple who just got engaged, or one who is three venues deep in comparison shopping, messaging late at night with a date they are hoping for and a budget they are still guessing at.
What it costs today
A multi-page questionnaire with 40 to 50 questions that most couples never finish, or phone tag that stretches the qualifying step out past the point most couples have already messaged someone else.
What it has to produce
A typed enquiry record: the date they hope for, the guest count, whether they have a venue, a budget range for understanding priorities, and the style they described, with no date held and no price quoted.
10%
of wedding inquiries become a booking, industry-wide
WedInspire
| Field | Type | Required | Why it is there |
|---|---|---|---|
| contact_names | text | Yes | Identity on the enquiry record |
| contact_phone | phone | Yes | How a planner calls back |
| contact_email | email | — | A second way to reach them, if they gave one |
| wedding_date_hoped_for | date | Yes | The date they are hoping for, never held or confirmed |
| guest_count_estimate | number | Yes | Roughly how many guests, for venue and budget fit |
| venue_status | text | Yes | Whether a venue is already booked or still needed |
| budget_range | text | — | Understands priorities, never produces a quote |
| style_vision | text | — | The feeling they are picturing, in their own words |
And what it will not do
Collected data
211 collected34 this week5 need attention
Export CSVPriya Anand
Captured 40m ago · New Enquiry Intake · joina.chat
Captured data 7 of 8 fields
From the conversation
“We just got engaged and are still figuring out numbers, but we’re thinking somewhere around 120 people , give or take, we honestly are not sure yet.”
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.
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 enquiry",
"record_id": 1234,
"attributes": {
"contact_names": "Priya Anand",
"contact_phone": "+1 512 555 0148",
"wedding_date_hoped_for": "June 14 (hoping for)",
"guest_count_estimate": "120",
"venue_status": "Still searching",
"budget_range": "$30,000 to $40,000 (estimate)"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a couple 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 client file.
Quotes are opt-in
The provenance block, the couple’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 record is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. A planner sees the enquiry before the inbox does.
Your own endpoint
Give us an https address, verify the signature, open the record 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 |
|---|---|---|---|
| 21:12:47 | data.collected | Delivered | 200 OK |
| 21:12:41 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 14:03 | data.updated | Delivered | 200 OK |
| Yesterday 09:18 | 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. HoneyBook, Dubsado, Aisle Planner and a plain spreadsheet 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 enquiry.
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 voicemail | Multi-page intake form | Gnosari |
|---|---|---|---|
| After hours | Rings out or goes to voicemail | Downloaded, rarely finished | Answered, typed, delivered |
| What you get back | A name and a callback number, if they left one | Whatever fit in the boxes | The vision in their own words |
| Half-told story | You call back to ask what they meant | Submitted half empty | It asks the follow-up |
| The date question | Told it is held, then it is not | A field with no owner | Taken as hoped for, never confirmed |
| The budget question | Guessed at, or avoided entirely | A dropdown nobody trusts | Understood as priorities, never a quote |
| Gets into your CRM | Re-typed by hand | CSV, or an integration you pay for | 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.
Gnosari runs the enquiry conversation a planner would otherwise take by email at midnight: the date, the venue or the search for one, the guest count, the style the couple wants, budget range and how to reach them. It asks one question at a time on your site or through a link, then posts a typed enquiry record to your CRM. You open the consultation with the brief already written.