You automate photography client intake by putting a conversational agent in front of the first inquiry. It asks for the session type, the date they hope for, the headcount and the style they are picturing one question at a time, types it into a structured record, and never holds a date, quotes a price or interprets usage rights.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
Someone who just got engaged, needs a headshot before Monday, or is scrolling a portfolio at midnight with a date in mind and a vague sense of budget, usually on a phone.
What it costs today
A static questionnaire with a dozen or more questions that most clients start and never finish, or a DM thread in an app built for chatting with friends, not running a business.
What it has to produce
A typed enquiry record: the kind of session, the date they hope for, roughly how many people, the style they described, and a budget range for understanding priorities, with no date held and no price quoted.
67%
of people who start an intake questionnaire never finish it
Zuko
| Field | Type | Required | Why it is there |
|---|---|---|---|
| contact_full_name | text | Yes | Identity on the enquiry record |
| contact_phone | phone | Yes | How the studio calls back |
| contact_email | email | — | A second way to reach them, if they gave one |
| session_type | text | Yes | Portrait, family, commercial, product or event |
| date_hoped_for | date | Yes | The date they are hoping for, never held or confirmed |
| subject_count_estimate | number | — | Roughly how many people, for planning fit |
| style_vision | text | — | The style or feeling they are picturing, in their own words |
| budget_range | text | — | Understands priorities, never produces a quote |
And what it will not do
Collected data
148 collected19 this week3 need attention
Export CSVPriya Anand
Captured 25m ago · New Session Enquiry · joina.chat
Captured data 7 of 8 fields
From the conversation
“We’re a family of six, well five and the dog, and we want something candid, nothing too stiff or posed , maybe golden hour if that works for you.”
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 session enquiry",
"record_id": 1234,
"attributes": {
"contact_full_name": "Priya Anand",
"contact_phone": "+1 512 555 0148",
"session_type": "Family portraits",
"date_hoped_for": "October (hoping for)",
"subject_count_estimate": "6",
"style_vision": "Candid, warm tones"
}
}Two events
data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a client 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 client’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. You see 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 |
|---|---|---|---|
| 23:41:09 | data.collected | Delivered | 200 OK |
| 23:41:02 | data.collected | Failed | 503, retrying in 30s |
| Yesterday 16:27 | data.updated | Delivered | 200 OK |
| Yesterday 11:05 | 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, Sprout Studio 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 | Email and DMs | Static intake form | Gnosari |
|---|---|---|---|
| After hours | Sits unread until morning | Downloaded, rarely finished | Answered, typed, delivered |
| What you get back | Whatever they thought to type | Whatever fit in the boxes | The style they described, in their own words |
| Half-told story | You reply to ask what they meant | Submitted half empty | It asks the follow-up |
| The date question | Sounds held, then it is not | A field with no owner | Taken as hoped for, never confirmed |
| Usage rights questions | Answered off the cuff, inconsistently | Not asked at all | Never granted or interpreted, referred to the contract |
| 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 a photographer would otherwise answer late at night from a phone: the session type, the date, the location, how many people, the style they like and how to reach them. It asks one question at a time on your portfolio pages or through a link, then posts a typed enquiry record to your CRM. You reply in the morning with a proposal instead of a list of questions.