You automate agency client onboarding by putting a conversational agent in front of the kickoff conversation. It asks the objective, the audience and the deliverables one question at a time, types it into a creative brief, and hands it to the team before the first draft starts.
01 · They talk
02 · It becomes a record
typed · validated · deduped
03 · Your stack acts
Who starts it
A new client who just signed, on a kickoff call with an account manager who has to turn an hour of scattered conversation into something the creative team can start from the same day.
What it costs today
A Google Form sent ahead of the call, modified after submission nine times out of ten, or a rebriefing session when the first pass turns out to have missed the actual objective.
What it has to produce
A typed creative brief: the objective, the audience, the one message that matters, what’s actually getting produced, and the brand lines nobody is allowed to cross.
90%
of marketers admit their brief gets modified after they’ve already submitted it
Admation
| Field | Type | Required | Why it is there |
|---|---|---|---|
| client_contact_name | text | Yes | Whose name goes on the brief |
| client_email | email | Yes | Where the brief and confirmation land |
| project_name | text | Yes | Which project this brief is for |
| primary_objective | text | Yes | The objective the whole brief hangs off |
| target_audience | text | Yes | Who the work has to land with |
| key_message | text | — | The one thing the audience should take away |
| deliverables_needed | list | — | What actually gets produced |
| inspiration_or_references | text | — | Direction without dictating the creative |
| hard_constraints | list | — | The brand no-gos, captured before the first draft |
And what it will not do
Collected data
138 collected19 this week5 need attention
Export CSVNaomi Petrov
Captured 1h ago · Kickoff Brief · joina.chat
Captured data 7 of 8 fields
From the conversation
“It’s the whole launch really, social, a landing page, all of it, and it has to feel completely different from anything we’ve done before , but our existing customers can’t feel like we’ve abandoned them either.”
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 brief",
"record_id": 1234,
"attributes": {
"client_contact_name": "Naomi Petrov",
"client_email": "naomi@example.com",
"project_name": "Northlight relaunch",
"primary_objective": "Full product launch, distinct from prior campaigns",
"target_audience": "Younger, digitally-native, without alienating existing customers",
"key_message": "New line feels different, doesn’t abandon loyalists"
}
}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 project.
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 project tool.
Free tier, no app to install, and it fires the moment the brief is complete.
Straight to the desk
Anything that accepts an incoming webhook takes the payload as it is.
No middleman. The team sees the brief before the kickoff meeting notes do.
Your own endpoint
Give us an https address, verify the signature, open the project 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. Asana, Trello, Basecamp and HoneyBook 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 brief.
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 | Form sent ahead of the call | Kickoff call, cold | Gnosari |
|---|---|---|---|
| Completion | 21.5% average form completion | Nobody drops off, but the call runs long | Answered and typed before the call ends |
| What you get back | Whatever fit in the boxes | Whatever got said out loud and half-remembered | The objective in the client’s own words |
| Vague answer | Left blank, or generic | The team spends the call probing | It asks the follow-up |
| Contradictory feedback | Buried in an email thread | Argued out live, or not at all | Captured as given, flagged as opposed |
| Gets into your project tool | Re-typed by hand | Typed into notes after the fact | Signed webhook, the moment it is complete |
| The approval line | Not applicable | Not applicable | Never crossed, and stated at the start |
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 kickoff process already asks for, point the agent at your services pages, and put the link in the contract email. The agent runs the conversation, produces a typed creative brief, and posts it to your project tool through a webhook, Zapier or Make. Setup is minutes, not an implementation project.