Skip to content
The pre-session intake

The midnight message becomes a typed intake record by nine.

Someone decides to try therapy at midnight, typing instead of calling because the line only reaches voicemail until nine. A few questions later a client record is waiting for the practice in the morning: the presenting concern in their own words, whether they have done this before, and when they are actually free. Free to start, live in five minutes.

You automate therapy intake by putting a conversational agent in front of the pre-session conversation. It asks for the presenting concern, prior therapy experience and preferred format one question at a time, types the answers into a structured client record, and posts that record to your practice software before the first session.

01 · They talk

Your GnosariAnswering
What’s bringing you to therapy right now?
Work has been a lot lately and I think I need to talk to someone, I’ve never done this before
That’s a good reason to start. Would you rather meet in person or by video, and roughly when during the week works for you?
Video would be easier, maybe evenings after 6

02 · It becomes a record

presenting_concern
Work stress, first time in therapy
prior_therapy_experience
No, first time
preferred_format
Telehealth
availability_preference
Evenings after 6pm

typed · validated · deduped

03 · Your stack acts

  • Front desk pinged
  • Zap into your practice software
  • Or the same via Make
  • Signed webhook at your endpoint
The process

The process this page is about

Not "AI for therapists". One process, the one that decides whether someone who has finally decided to try therapy reaches your practice or gives up before the first session: the pre-session intake, the message that arrives before anyone has spoken to a person.
  • Who starts it

    Someone who has decided, often after putting it off for a long time, that they want to talk to someone - usually outside office hours, usually on a phone, usually a little nervous about what they are about to say.

  • What it costs today

    An 8-page intake packet emailed as a PDF, asking about trauma history and medications in the same tone for a first-timer with a rough week as for someone with years of prior treatment, or a phone line that goes to voicemail until morning.

  • What it has to produce

    A typed client record: who is reaching out, the presenting concern in their own words, whether this is their first time in therapy, and the format and availability that will actually get them to a first session.

20%

of therapy dropouts happen between assessment and the first session - the exact window intake runs in

PMC dropout meta-analysis

The schema

What it asks, and what it never asks

You name the fields your intake 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 client record
phonephoneYesHow the practice calls back
emailemailFor records that are easier by email
presenting_concerntextYesThe presenting concern, in their own words
prior_therapy_experiencebooleanWhether this is a first time in therapy
preferred_formattextIn-person or telehealth
insurance_providertextFeeds the eligibility check, never a coverage promise
specialty_area_neededtextRoutes to the right clinician
availability_preferencetextWhen sessions would realistically fit
current_mood_ratingnumberThe self-reported number a between-session check-in carries, never interpreted by the agent

And what it will not do

  • The moment anything sounds like self-harm or a mental health emergency, it stops asking questions, says plainly it is not a crisis service, and tells them to call 911 or go to the nearest emergency room right now.
  • It never diagnoses, never names a condition, and never says a feeling or situation is serious, minor or normal.
  • It never recommends a therapist, a modality, or a number of sessions - that match is made by a clinician.
  • It never confirms insurance coverage, a copay, or a fee. The front desk verifies both and follows up.
  • It never gives a coping technique, a grounding exercise, or any other therapeutic content. It collects information, it does not deliver care.
  • 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 front desk actually handles, each running its own agent with its own fields. Pick one and answer it the way a real person 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 want to start therapyConnecting
The live conversation is loading.
Where the records land

What the front desk 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

148 collected19 this week3 need attention

Export CSV
  • Dana Whitfield New client, first timeNew Client Intake · 1h ago
  • Marcus Oyelaran Needs to be seen soonerNeed To Be Seen Sooner · 3h ago
  • Priya Anand Asked about coverageInsurance And Fit Check · Yesterday
  • Els Bakker Returning after 2 yearsComing Back After A Break · Yesterday
  • Tom Ferreira Pausing sessionsEnding Or Pausing Therapy · Fri

Dana Whitfield

Captured 1h ago · New Client Intake · joina.chat

Captured data 7 of 8 fields

full_nameDana Whitfield
phone+1 512 555 0148
presenting_concernWork stress, first time in therapy
prior_therapy_experienceNo, first time
preferred_formatTelehealth
availability_preferenceNot captured
insurance_providerBlue Cross
current_mood_rating6

From the conversation

“Work has been a lot lately, I think I need to talk to someone , I’ve never done this before so I’m not really sure how it works.”

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 practice software gets the client, not another login

The moment the intake 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 practice already runs.
POST https://hooks.zapier.com/hooks/catch/1234567/abcdef

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 client",
  "record_id": 1234,
  "attributes": {
    "full_name": "Dana Whitfield",
    "phone": "+1 512 555 0148",
    "presenting_concern": "Work stress, first time in therapy",
    "prior_therapy_experience": "false",
    "preferred_format": "Telehealth",
    "availability_preference": "Evenings after 6pm"
  }
}
  • 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 chart.

  • 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 practice software.

    Free tier, no app to install, and it fires the moment the client record is complete.

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

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

    No middleman. Whoever runs intake sees the record before the first session does.

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

    Give us an https address, verify the signature, open the chart 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
19:04:22data.collectedDelivered200 OK
19:04:18data.collectedFailed503, retrying in 30s
Yesterday 09:37data.updatedDelivered200 OK
Yesterday 07:52data.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. SimplePractice, TherapyNotes, Jane App and TheraNest 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 chart.

Two ways it can look

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

Both are live right now. The widget in the corner takes the pre-session intake from someone reading your services page. The link is what you text back to a missed call, and it works before the front desk 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 intake packet at the front desk.
What changesPhone tag and voicemailPDF or portal intake formGnosari
After hoursRings outDownloaded, never returnedAnswered, typed, delivered
What you get backA name, if they left oneWhatever fitted in the boxesThe presenting concern in their own words
Half-told storyStaff call back to askSubmitted half emptyIt asks the follow-up
A hint of crisisDepends who picks up the voicemailA form has no ideaStops immediately, says call 911 now
Gets into your practice softwareRe-typed by handCSV, or an integration you pay forSigned webhook, the moment it is complete
The clinical lineDepends who answeredNot applicableNever crossed, 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 intake conversation a practice would otherwise hold on a first phone call or leave to a PDF nobody returns: what brings the person in, in their own words, availability, insurance or self-pay, whether they have seen a therapist before, and how to reach them. It asks one question at a time through a link on your website, then posts a typed intake record to your practice management system before the first session.

Five minutes from now your after-hours enquiries could be typing themselves up.

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