Freud, in practice.

A working catalogue of the moments where a private practice loses time, context, or follow-through — and what Freud can do about it.


▾ 1 - Day one15
1. Calendar freedom

THE SITUATION

Every booking costs a round of messages: the client asks what is available, you check the calendar, propose two slots, they pick the one that just filled, you propose again. It happens in the evening, between sessions, on weekends.

FREUD DOES

The public agent reads your live availability rules, offers real open slots in conversation, collects name and contact, and prepares the booking. Where your flow has payment and a Google Meet or Zoom link configured, the request carries them, so the confirmed session has everything attached from birth.

THE BOUNDARY

The slot comes from your calendar rules, not from invention. The visitor is only ever told what your flow actually confirmed, never more.

THE RESULT

Clients book real sessions without ever seeing your calendar, and the hours you spent on scheduling ping-pong go back to your week.

Public agent; widget; Calendar

⭢Try Freud
2. The midnight inquiry

THE SITUATION

Anxious people search for a therapist at 1 a.m. Your website shows a contact form and a promise to reply soon. By morning, half of them have moved on or booked elsewhere.

FREUD DOES

The public agent answers their practical questions immediately — services, fees, approach, location, next steps — grounded only in content you approved, and captures their details with consent so the morning starts with a warm inquiry instead of a cold form.

THE BOUNDARY

It answers from your knowledge, not the open internet, and it never speculates about anyone's condition or what treatment they might need.

THE RESULT

After-hours visitors stay engaged instead of bouncing, and you wake up to qualified contacts instead of a form queue.

Public agent; widget

⭢Try Freud
3. Consent-first capture

THE SITUATION

Inquiries arrive scattered across WhatsApp, email, LinkedIn and the website, each with different amounts of information, and none of it in one place.

FREUD DOES

In every conversation the agent collects the minimum useful set — name, preferred contact, what they are looking for — records their consent explicitly, and creates a tracked contact in the CRM with the conversation attached.

THE BOUNDARY

Only the fields you configured are collected, nothing extra is pried for, and the consent record is per-contact and per-purpose.

THE RESULT

One pipeline of leads instead of five inboxes, each contact traceable from first message to first session.

Public agent; Relationships

⭢Try Freud
4. Fit-check triage

THE SITUATION

A third of inquiries are a poor fit — wrong specialization, wrong availability, wrong fee range — but you only find out after a phone call you did not need to have.

FREUD DOES

The agent asks two or three gentle qualifying questions in natural conversation, explains who you work with and how, and marks the contact with what it learned so the right next step is obvious.

THE BOUNDARY

It is transparent that it is an assistant, it performs no clinical assessment of anyone, and a fit mismatch is described only in terms of your stated practice profile.

THE RESULT

Better-fit people reach your calendar, and mismatched inquiries resolve kindly without consuming your time.

Public agent; Relationships

⭢Try Freud
5. The waiting list that remembers

THE SITUATION

Your calendar is full, so interested people get told to try again later. Most never do.

FREUD DOES

The agent collects their details and preferences with consent, explains the waiting process honestly, and the contact lands in your CRM tagged as waiting, so they are a person on a list rather than a message in the void.

THE BOUNDARY

It never promises a date it cannot see, and it stores nothing beyond what a waiting list needs.

THE RESULT

Full calendars stop leaking future demand, and when a slot opens you know exactly who is next.

Public agent; Relationships

⭢Try Freud
6. Instant FAQ

THE SITUATION

The same ten questions arrive every week — fees, session length, insurance, parking, online options, cancellation policy — and each one costs a reply you have written a hundred times.

FREUD DOES

The public agent answers them instantly and consistently, in your words, quoting the policies and service descriptions you approved.

THE BOUNDARY

Answers come only from your approved knowledge; if something is not in there, the agent says so instead of improvising.

THE RESULT

Repetitive email drops to near zero and every visitor hears the same accurate answer.

Public agent; widget

⭢Try Freud
7. Services in plain words

THE SITUATION

Your services page was written by someone who already understands the vocabulary, for people who do not yet.

FREUD DOES

The agent explains your modalities, session formats and fees conversationally, meeting visitors at whatever level of familiarity they have, always anchored to the descriptions you wrote.

THE BOUNDARY

It rephrases your content in plain language but never adds claims, outcomes or promises that are not in it.

THE RESULT

Fewer confused inquiries, and more visitors who arrive already understanding what you offer.

Public agent

⭢Try Freud
8. Widget on every page

THE SITUATION

Your contact page has a form; the rest of your site has nothing. Visitors with questions on any other page just leave.

FREUD DOES

The agent widget sits on whichever pages you choose, inheriting the same knowledge and rules as your main agent, so a question can be answered the moment it arises.

THE BOUNDARY

The widget carries the agent's public permissions only — it is the same bounded face, not a back door to practice data.

THE RESULT

Every page of your site becomes a place where a question can be answered and a contact can begin.

Widget

⭢Try Freud
9. The agent page as living landing page

THE SITUATION

You could update your website copy, or you could spend a week and a budget doing it.

FREUD DOES

Your published agent has its own public route, so visitors meet an explanation of the practice that can actually converse, clarify and route to booking, instead of a static page that cannot.

THE BOUNDARY

The public page exposes only the agent and its approved knowledge — no staff information beyond what you published, no internal anything.

THE RESULT

A landing page that stays accurate because it answers from your knowledge rather than from frozen copy.

Public agent page

⭢Try Freud
10. Policy clarity

THE SITUATION

Cancellation windows, late fees, telehealth rules — explaining these after a conflict is the worst possible time to explain them.

FREUD DOES

The agent quotes your actual policy before it is ever a problem, in conversation, whenever fees, cancellations or scheduling rules come up.

THE BOUNDARY

It states the policy you wrote, without softening it into something untrue or hardening it into something unkind.

THE RESULT

Fewer disputes and fewer awkward conversations, because expectations were set before the first session.

Public agent

⭢Try Freud
11. Boundaries, visibly held

THE SITUATION

People in distress sometimes ask an AI for diagnosis, certainty or urgent intervention, and most AI tools will try to provide something.

FREUD DOES

The agent explains what it is and is not, describes your services and how to reach a human, and declines clearly and kindly when someone asks for clinical judgment.

THE BOUNDARY

No diagnosis, no labels, no clinical certainty, no pretending to be a therapist — by design, not by accident.

THE RESULT

Visitors in serious need are guided toward a human, and your public tool never oversteps what it actually is.

Public agent

⭢Try Freud
12. LinkedIn inquiries tracked

THE SITUATION

Professional inquiries arrive in LinkedIn messages, and LinkedIn is where leads go to be forgotten.

FREUD DOES

Conversations and contacts from your configured LinkedIn connection are brought into the CRM with a drafted reply waiting for your approval.

THE BOUNDARY

Nothing is posted or sent to LinkedIn without your review, and only the configured connection's scope is used.

THE RESULT

Your professional network becomes part of the pipeline instead of a parallel universe.

Apps; Relationships; Emails

⭢Try Freud
13. WhatsApp front door

THE SITUATION

In much of the world the first message does not come by email — it comes by WhatsApp, and it usually comes at dinner time.

FREUD DOES

The same grounded agent greets the conversation on WhatsApp Business, answers the practical questions, and captures the contact with consent into your CRM.

THE BOUNDARY

The agent uses your WhatsApp Business connection within its configured permissions, and a human approves anything consequential before it happens.

THE RESULT

The channel clients actually use stops being a second, unmanaged inbox.

Public agent; Apps

⭢Try Freud
14. Knowledge you control

THE SITUATION

The fear with any public AI is simple: what exactly will it say, and based on what?

FREUD DOES

The agent answers only from the website content, articles and documents you approved, and every answer stays tied to that source material.

THE BOUNDARY

You decide what goes in. Nothing becomes public knowledge by being uploaded casually, and nothing from other clients or staff areas is reachable from the public side.

THE RESULT

A public agent whose contents you could explain to any client in one sentence.

Knowledge; public agent

⭢Try Freud
15. Overnight booking queue

THE SITUATION

Booking requests that arrive while you sleep either wake you up or wait until morning, and by then the slot may be gone.

FREUD DOES

The agent collects the request, checks it against your real availability rules, holds what your flow allows, and queues everything for your morning review, sorted and ready to confirm.

THE BOUNDARY

Requests wait for human confirmation wherever your flow requires it — the visitor is never promised more than actually happened.

THE RESULT

You wake to an orderly queue instead of a scramble, and early risers get morning slots before office hours.

Public agent; Calendar

⭢Try Freud
▾ 2 - Daily load15
16. Morning briefing

THE SITUATION

The first half hour of the day is spent reconstructing context: what came in overnight, what is unconfirmed, who is waiting on you.

FREUD DOES

Ask Freud what needs attention today and get one grounded answer: new inquiries, unconfirmed bookings, threads that went quiet, approvals waiting — in priority order, with links to act.

THE BOUNDARY

It reads your workspace and connected systems only; nothing leaves the tenancy to build the briefing.

THE RESULT

A five-minute standup with yourself that replaces forty minutes of archaeology.

Ask Freud

⭢Try Freud
17. Session prep card

THE SITUATION

Back-to-back sessions leave no room to remember who this person is, where you left off, and what is open.

FREUD DOES

Before each appointment, Freud assembles a short card: who is coming, when you last interacted, what is pending, and what the next step was supposed to be.

THE BOUNDARY

The card is drawn from that one contact's record only — no other client's information is ever mixed in.

THE RESULT

Thirty seconds of prep between sessions instead of ten minutes of digging.

Calendar; Ask Freud

⭢Try Freud
18. Reminder prep, human send

THE SITUATION

Reminder messages cut no-shows dramatically, but writing and sending them every single day is exactly the kind of chore that gets skipped.

FREUD DOES

Each day Freud prepares tomorrow's reminders as drafts — right client, right appointment, right channel — and lines them up for review.

THE BOUNDARY

You approve and the messages go out; Freud never messages a client on its own, even for something as small as a reminder.

THE RESULT

No-shows drop without a robot texting your clients behind your back.

Ask Freud; Emails

⭢Try Freud
19. Confirmation watch

THE SITUATION

A booking that was made is not a booking that will happen; unconfirmed appointments are the quiet source of most empty hours.

FREUD DOES

Freud watches upcoming appointments, flags the ones without confirmation, and drafts the gentle nudge for each.

THE BOUNDARY

Drafts wait for approval, and what counts as confirmed follows your practice rules, not a guess.

THE RESULT

The appointments most likely to evaporate get caught while they can still be saved.

Calendar; Ask Freud

⭢Try Freud
20. No-show recovery

THE SITUATION

A missed session usually means silence, and silence after a no-show tends to become a permanently lost client.

FREUD DOES

Freud surfaces the missed appointment, drafts a caring, non-guilt-tripping re-engagement message, and offers the next available slots.

THE BOUNDARY

The message is a draft until you approve it, and its tone is yours to edit before it goes anywhere.

THE RESULT

Missed sessions become recovered ones instead of quiet exits.

Ask Freud; Relationships

⭢Try Freud
21. Debrief to note

THE SITUATION

The best moment to write a session note is right after the session — which is exactly when there is no time.

FREUD DOES

Tell Freud in your own words what happened and it lands as a structured note on the contact's record: dated, attributed, searchable later.

THE BOUNDARY

The note lives inside your workspace, attaches only to that contact, and what you dictate is what gets written — Freud adds structure, never interpretation.

THE RESULT

Notes get written on good days and busy ones alike, and they are all in one place when you need them.

Ask Freud; Relationships

⭢Try Freud
22. Contact recap

THE SITUATION

Before a call with a client you have not spoken to in months, you need the story — and the story is scattered across notes, emails and calendar history.

FREUD DOES

Freud produces one tight paragraph: who this person is, the arc of your interactions, where things stand now, and what is open.

THE BOUNDARY

The recap covers this contact only; no other person's data is consulted or included, ever.

THE RESULT

Context in one read before every call, without violating anyone's privacy to get it.

Relationships; Ask Freud

⭢Try Freud
23. Stalled-conversation finder

THE SITUATION

Somewhere in your inbox and CRM are people who asked about sessions, got an answer, and never heard back — including from you.

FREUD DOES

Freud finds the threads that went quiet, orders them by how promising they look, and drafts a restart message for each.

THE BOUNDARY

Every draft waits for your review, and what counts as stalled follows the time windows you set.

THE RESULT

The pipeline stops leaking at the seams you cannot see.

Ask Freud; Relationships

⭢Try Freud
24. Welcome draft

THE SITUATION

The first reply to a new inquiry sets the tone for everything, and it deserves better than a rushed answer typed between sessions.

FREUD DOES

When a new contact lands, Freud drafts a warm, on-voice welcome reply from your approved language and the specifics of their inquiry.

THE BOUNDARY

The draft is yours to edit and approve; it never sends itself.

THE RESULT

Every new person gets the practice at its best, even on your worst day.

Emails; Relationships

⭢Try Freud
25. Reschedule without phone tag

THE SITUATION

A client needs to move Thursday. Now begins the tournament: propose, counter-propose, check, confirm, and update everything.

FREUD DOES

The agent offers your real open slots in conversation, collects the choice, and prepares the change through your calendar flow, including an updated meeting link where telehealth applies.

THE BOUNDARY

Changes follow your rescheduling rules, and the visitor is only ever told what has actually been confirmed.

THE RESULT

Rescheduling becomes one conversation instead of a week of messages.

Public agent; Calendar

⭢Try Freud
26. Cancellation with care

THE SITUATION

Cancellations arrive as apologetic messages that then require policy enforcement, rebooking and slot recovery — all emotionally loaded.

FREUD DOES

The agent acknowledges, applies your cancellation policy kindly and exactly, offers rebooking, and flags the freed slot so it can be filled.

THE BOUNDARY

Policy is applied as written, fees are never charged unilaterally, and anything consequential stays inside your configured flow.

THE RESULT

A cancelled session becomes a rebooking and an open slot instead of a loss and an argument.

Public agent; Calendar; Workflows

⭢Try Freud
27. Inbox triage

THE SITUATION

The practice inbox mixes clients, referrers, suppliers and spam, and the one client email that matters is hiding in all of it.

FREUD DOES

With your mail connected, Freud sorts by urgency, groups what belongs together, and drafts a reply for each item that needs one.

THE BOUNDARY

Drafts only — nothing leaves your mailbox without a human decision, and the connection reads only what its permissions allow.

THE RESULT

The inbox becomes a fifteen-minute task with a queue of ready replies.

Emails; Apps

⭢Try Freud
28. Question becomes knowledge

THE SITUATION

The third time you type the same answer, you know it should live somewhere permanent — but nobody has time to maintain a FAQ.

FREUD DOES

Freud notices when the same question recurs across conversations, drafts the answer as a knowledge entry, and suggests adding it.

THE BOUNDARY

You decide what enters the knowledge base; suggestion is not publication.

THE RESULT

The agent's knowledge compounds from your real workload instead of from a documentation project you never start.

Ask Freud; Knowledge

⭢Try Freud
29. First-session scheduling for hesitant clients

THE SITUATION

The people who most need a first session are often the least able to navigate the logistics of arranging one; every extra step is a reason to stop.

FREUD DOES

The agent walks them through it gently — what a first session is, what it costs, what happens next — and then books, in the same conversation, without a form or a phone call.

THE BOUNDARY

The agent explains logistics, never therapy content, and stays transparent that it is an assistant.

THE RESULT

The step that loses the most people becomes the easiest one.

Public agent

⭢Try Freud
30. Multi-practitioner routing

THE SITUATION

In a practice with several clinicians, the question of who should see whom gets answered by whoever happens to read the message, based on vibes.

FREUD DOES

The agent matches the inquiry against each practitioner's published focus, availability and intake rules, and routes the request to the right calendar and the right desk.

THE BOUNDARY

It matches against what each practitioner published about their own practice — never against anything resembling clinical assessment of the client.

THE RESULT

The right client reaches the right clinician without a coordination meeting.

Public agent; Calendar

⭢Try Freud
▾ 3 - Connected12
31. Two-way Google Calendar

THE SITUATION

The practice calendar and Google Calendar drift apart, and the afternoon a client appears in one but not the other is the afternoon you get double-booked.

FREUD DOES

With Google Calendar connected, Daddyfreud bookings flow into your Google Calendar and external events block your availability, so both views stay honest.

THE BOUNDARY

Google Calendar is an integration, not the source of truth — a Daddyfreud booking succeeded when Daddyfreud confirmed it, not when a sync caught up.

THE RESULT

One calendar in your head, zero double-bookings from drift.

Calendar; Apps

⭢Try Freud
32. Meeting links born attached

THE SITUATION

For telehealth, every confirmed session needs a meeting room, and creating a link, pasting it into an invite and sending it is three tasks repeated two hundred times a year.

FREUD DOES

When a telehealth session is confirmed through the configured flow, a Google Meet or Zoom link is generated and attached to the booking automatically.

THE BOUNDARY

Link creation happens inside the supported booking flow; a session without a completed booking never gets a link.

THE RESULT

Every online session has its door open before anyone asks for it.

Calendar; Apps

⭢Try Freud
33. Docs on demand

THE SITUATION

Agreements, intake confirmations and session prep sheets are the same documents every time, rebuilt from the last copy every time.

FREUD DOES

From a template in your library, Freud generates the document in Google Docs with the client's and session's real details filled in.

THE BOUNDARY

Templates and what can be auto-filled are under your control, and generating a document sends nothing anywhere.

THE RESULT

Paperwork happens at document speed instead of copy-paste speed.

Apps; Library

⭢Try Freud
34. Files, filed

THE SITUATION

Intake PDFs, documents and signed forms pile up in downloads and email attachments, destined for the folder system you will reorganize someday.

FREUD DOES

When a document belongs to a client, Freud files it to the right Drive or Dropbox location and keeps it findable from the contact's record.

THE BOUNDARY

Filing follows the folder structure you configured, within the connection's granted permissions only.

THE RESULT

A filing clerk that never forgets, never misspells a folder, and never lets a document die in downloads.

Apps; Relationships

⭢Try Freud
35. Sheets exports

THE SITUATION

At some point someone — an accountant, a partner, your own spreadsheet habit — will want the practice's data in a spreadsheet.

FREUD DOES

Appointments, inquiries and contact updates flow to a Google Sheet on the cadence you set, structured and current.

THE BOUNDARY

The export contains what you configured and nothing more; it is a copy, and the CRM remains the source of truth.

THE RESULT

Your data leaves the app without leaving your hands.

Apps; Ask Freud

⭢Try Freud
36. The Microsoft practice

THE SITUATION

Plenty of practices live in Outlook and Teams, and a tool that quietly assumes Gmail excludes them.

FREUD DOES

Mail and calendar run through the Outlook connection, and Teams stays in the connector set for the communication pieces your flow uses.

THE BOUNDARY

Each connector's read and write behavior is its own — the Microsoft stack is supported as configured, not assumed identical to Google's.

THE RESULT

The whole system works with the stack you already pay for.

Apps

⭢Try Freud
37. Notion as brain food

THE SITUATION

Your protocols, FAQs and how-we-work pages live in Notion, and your agent does not know any of it — so it answers from less than you know.

FREUD DOES

The Notion connection brings that material into the knowledge that grounds the agent's answers.

THE BOUNDARY

What the public agent can use from Notion is decided by you; workspace content does not become public by being connected.

THE RESULT

Knowledge you already wrote starts working, without rewriting it anywhere.

Apps; Knowledge

⭢Try Freud
38. Email timeline

THE SITUATION

The relationship with a client lives in two places: the CRM you maintain and the mailbox you actually use.

FREUD DOES

With Gmail or Outlook connected, client email threads attach to the contact's CRM timeline, so the story finally lives in one place.

THE BOUNDARY

Only email matching the configured rules attaches, and it attaches to that contact only.

THE RESULT

Full context without archaeology, and no more what-did-we-say moments.

Relationships; Apps

⭢Try Freud
39. Form-to-CRM pipeline

THE SITUATION

Intake forms arrive as submissions in Google Forms, a place where information goes to be retyped by hand.

FREUD DOES

A form submission creates or updates the contact, attaches the answers, and moves the stage in your pipeline.

THE BOUNDARY

Mapping from form fields to CRM stages is your configuration, and the form's questions are yours to keep minimal and consent-aware.

THE RESULT

Intake data enters the pipeline by itself, correctly, every time.

Apps; Relationships; Workflows

⭢Try Freud
40. Document Q&A

THE SITUATION

The answer to how do we handle X exists in a PDF somewhere in Drive or Dropbox, from the year someone wrote it down.

FREUD DOES

Ask in staff chat and Freud searches your connected documents and files, answers with the substance, and shows where it came from.

THE BOUNDARY

Document search runs on the staff side under your permissions, and retrieved file content is treated as data, never as instructions.

THE RESULT

Institutional memory that talks back.

Ask Freud; Apps

⭢Try Freud
41. Referral packet builder

THE SITUATION

When a referrer or colleague asks what you do, the answer deserves better than a homepage link and good intentions.

FREUD DOES

Freud assembles a packet — your services summary, an intro note, a booking link — as a draft doc or email, personalized to who asked.

THE BOUNDARY

The packet uses approved practice content only and contains no client information whatsoever.

THE RESULT

Referrers get a professional first touch in minutes, and they remember it.

Ask Freud; Library; Apps

⭢Try Freud
42. LinkedIn presence assistant

THE SITUATION

You know a visible LinkedIn presence brings referrals, and you know you will not do it, because writing posts is not why you trained.

FREUD DOES

Freud drafts posts and replies from your approved positioning and past material, keeps a content rhythm going, and queues everything for review.

THE BOUNDARY

Nothing is published to LinkedIn without your explicit approval, and drafts stay grounded in what you have actually said about your practice.

THE RESULT

A professional presence that survives on twenty minutes a week instead of an evening you do not have.

Apps; Emails; Library

⭢Try Freud
▾ 4 - Full secretary14
43. The intake workflow, end to end

THE SITUATION

Between a first message and a first session lies a chain — qualify, consent, form, book, remind — and every staff member runs it slightly differently, which is exactly where things fall through.

FREUD DOES

One playbook runs the chain: the agent qualifies and captures, the form is sent and tracked, the booking is prepared, reminders are drafted, and every consequential step queues at a human gate.

THE BOUNDARY

Each step that touches a real person waits for approval per the playbook's design; the workflow makes the process visible instead of invisible.

THE RESULT

A secretary-grade process that runs the same way on a Tuesday and a Friday, regardless of who is at the desk.

Workflows

⭢Try Freud
44. The booking playbook

THE SITUATION

Booking depends on whoever handles it: one person checks availability twice, one forgets the meeting link, one forgets the confirmation.

FREUD DOES

The playbook checks real availability, collects identity and contact details, prepares the booking, attaches the meeting link where telehealth applies, and drafts the confirmation.

THE BOUNDARY

The booking is created through your calendar flow, and the visitor is told only what is actually confirmed.

THE RESULT

Bookings stop depending on who is at the desk.

Workflows; Calendar

⭢Try Freud
45. Rebooking rhythm

THE SITUATION

Casually scheduled next sessions evaporate, and the practice drifts from steady cadence to sporadic contact without anyone ever deciding that.

FREUD DOES

After each session, the playbook proposes the next appointment and drafts a short follow-up note, so the rhythm is offered, not left to chance.

THE BOUNDARY

Proposals become bookings only through the normal flow, and follow-ups wait for approval like any outbound message.

THE RESULT

A steady cadence that no one has to personally remember to maintain.

Workflows; CRM; Calendar

⭢Try Freud
46. No-show recovery playbook

THE SITUATION

Every practice has an unwritten protocol for a no-show; the protocol lives in one person's head, and that person is on holiday.

FREUD DOES

The playbook detects the missed appointment, drafts the caring re-engagement with next available slots, logs the outcome, and escalates to a human where the pattern repeats.

THE BOUNDARY

Sending waits for approval, and escalation is always to a person, never to a further automated step.

THE RESULT

Missed sessions handled with the same care every time, by anyone on staff.

Workflows

⭢Try Freud
47. Reactivation playbook

THE SITUATION

Former clients and old inquiries who would genuinely benefit from returning sit untouched, because reaching out feels delicate and never rises to urgent.

FREUD DOES

The playbook finds contacts quiet beyond your threshold, drafts a personal, respectful check-in for each, and batches them so review stays manageable.

THE BOUNDARY

Every message is reviewed before sending, batch sizes are yours to set, and anyone who opted out stays out.

THE RESULT

A dormant list becomes a living one, one approved batch at a time.

Workflows; Relationships; Emails

⭢Try Freud
48. The approval queue

THE SITUATION

The alternative to automation anxiety is not doing everything by hand; it is having one place where everything consequential waits.

FREUD DOES

Every send, booking and change that Freud prepares collects in a single review queue, with the context needed to approve in seconds.

THE BOUNDARY

Nothing consequential happens outside this gate — that is the design, not a setting.

THE RESULT

Automation with a steering wheel.

Ask Freud; Workflows

⭢Try Freud
49. Holiday coverage

THE SITUATION

Going away means either working from the beach or returning to a wreck.

FREUD DOES

Before you leave, the out-of-office playbook is armed: the agent keeps answering FAQs and capturing inquiries, booking requests queue instead of confirm, and a briefing of everything that happened waits for your return.

THE BOUNDARY

Queued requests are held, not auto-confirmed, and the agent tells visitors honestly what will happen next and when.

THE RESULT

A vacation that is a vacation, and a return that is a review instead of a rescue.

Workflows; Public agent; Calendar

⭢Try Freud
50. Group and workshop scheduling

THE SITUATION

Running a group means herding ten people toward one date, by email, across three weeks.

FREUD DOES

The agent and a form collect attendees and preferences, Freud coordinates toward a date that fits, and confirmations with meeting links are prepared for everyone at once.

THE BOUNDARY

Individual preferences stay individual; the group sees only what you choose to send the group.

THE RESULT

Groups without spreadsheet hell.

Workflows; Apps

⭢Try Freud
51. Payment at booking

THE SITUATION

Unpaid no-shows cost real money, and chasing fees after the fact is the worst version of this job.

FREUD DOES

Where your flow has a payment step configured, the session fee is collected as part of the booking flow before the slot is held, and the confirmation carries the receipt.

THE BOUNDARY

Payment is a step inside the supported booking flow — Freud never charges, refunds or mutates money outside it, and it never claims a payment happened unless it did.

THE RESULT

No-shows become expensive to ignore, and you stop being the person who has to bring up money.

Public agent; Calendar; Workflows

⭢Try Freud
52. Waiting-list automation

THE SITUATION

A slot opens Thursday at 3. The right person for it is the fourth person who asked, not the first, and you will not remember who they were.

FREUD DOES

When a slot frees, the playbook offers it to the waiting list in order, tracks who responded, and confirms the first valid taker through the normal booking flow.

THE BOUNDARY

Offers follow the order and rules you set, and confirmations go through the same booking path as everything else.

THE RESULT

Zero empty hours at peak demand, without a fairness debate running in your head.

Workflows; Calendar; Relationships

⭢Try Freud
53. Prepaid packages

THE SITUATION

Package deals create commitment and calm — and administrative overhead that makes them not worth it.

FREUD DOES

A session package is sold through the agent's configured flow, and each booking draws from the remaining balance, visible to staff and client alike.

THE BOUNDARY

Payments stay inside the supported flow, and balances are recorded, never adjusted silently.

THE RESULT

Commitment up front, calm after.

Public agent; Workflows; Relationships

⭢Try Freud
54. Referral thanks workflow

THE SITUATION

Referrers who feel forgotten stop referring, and gratitude that depends on memory is not gratitude.

FREUD DOES

With consent tracked, the playbook notes when a new client names a referrer and drafts the thank-you at the right moment.

THE BOUNDARY

Referral tracking uses only consented, first-party information, and the draft waits for your send.

THE RESULT

Referrers feel seen, so they keep referring.

Workflows; Relationships; Emails

⭢Try Freud
55. New practitioner onboarding

THE SITUATION

Adding a clinician means rebuilding their piece of the practice — knowledge, workflows, tone — from scratch, while they watch.

FREUD DOES

The practice's knowledge, workflows and voice are cloned into the new staff member's workspace, adjusted for their focus, so day one starts from the practice's accumulated substance.

THE BOUNDARY

The clone copies practice assets, never other clients' data, and the new workspace is its own tenancy boundary.

THE RESULT

A new hire productive in days instead of a quarter.

Knowledge; Library; Workflows

⭢Try Freud
56. Custom playbook from conversation

THE SITUATION

Your practice has a process no template anticipated, and building it as a workflow is the kind of task that never gets done.

FREUD DOES

Describe the process in plain words — what triggers it, what steps happen, where a human must decide — and Freud drafts the workflow for you to refine and save.

THE BOUNDARY

The draft is inert until you approve it, and approval gates are added wherever the process touches a real person.

THE RESULT

Your second custom playbook costs a conversation instead of an afternoon.

Workflows; Ask Freud

⭢Try Freud
▾ 5 - Practice brain16
57. Practice pulse

THE SITUATION

You know the practice works; you could not say how well, or where it leaks.

FREUD DOES

A weekly picture in plain language: inquiries by source, inquiry-to-booking conversion, no-show rate, sessions held, contacts gone quiet — observed from your own data, on your terms.

THE BOUNDARY

It is observation, not diagnosis — of people or of the practice — and every number traces to something real in your workspace.

THE RESULT

You see the practice the way you could never see it from inside a single week.

Ask Freud

⭢Try Freud
58. Capacity planner

THE SITUATION

The calendar fills unevenly — one week crushed, one hollow — and by the time you notice, the month is over.

FREUD DOES

Freud surfaces overloaded weeks, empty holes, and uneven load between practitioners while there is still time to do something about it.

THE BOUNDARY

It reports the shape of the schedule; it does not move anything without a person deciding.

THE RESULT

Schedule shape becomes a decision, not an accident.

Ask Freud; Calendar

⭢Try Freud
59. The funnel, honestly

THE SITUATION

Visitors come, some inquire, fewer book — but where exactly they stop, nobody knows.

FREUD DOES

Freud traces the path from first visit to first session across your public agent and CRM, and shows the step with the biggest drop.

THE BOUNDARY

Counts are grounded in actual records; there is no modeled or invented traffic data anywhere in the picture.

THE RESULT

One number to improve at a time, instead of a vague sense that things could be better.

Ask Freud; Relationships

⭢Try Freud
60. Quiet signals

THE SITUATION

People rarely announce disengagement; they cancel once, then reschedule less, then go quiet, and the pattern is only visible in hindsight.

FREUD DOES

Freud surfaces the operational facts — cancellations clustering, threads going silent, rhythm breaking — and puts them in front of a human.

THE BOUNDARY

Freud flags patterns, never people's states; what care looks like in response is entirely and only the clinician's call.

THE RESULT

You notice earlier, and you stay the clinician.

Ask Freud; Relationships

⭢Try Freud
61. Session economics, observed

THE SITUATION

Booked versus paid versus outstanding is knowable, but knowing it requires an afternoon with a spreadsheet every month.

FREUD DOES

Where payment data exists in your configured flows, Freud reports the picture by service and practitioner — reported, never adjusted.

THE BOUNDARY

Freud reads money, it does not touch money: no charges, refunds, discounts or mutations outside supported flows, ever.

THE RESULT

Money questions answered without anyone becoming an accountant.

Ask Freud; Apps

⭢Try Freud
62. Knowledge curator

THE SITUATION

Knowledge bases decay: overlaps accumulate, answers go stale, and the best reply you ever wrote is buried in an email from March.

FREUD DOES

Freud turns your best approved replies into reusable library assets, flags overlapping or outdated entries, and proposes consolidations.

THE BOUNDARY

Curation proposes; you dispose. Nothing moves, merges or publishes without you.

THE RESULT

The library writes itself from real work, and stays readable.

Library; Knowledge; Ask Freud

⭢Try Freud
63. Answer-gap audit

THE SITUATION

Your public agent is only as good as what it does not have to refuse.

FREUD DOES

Each week, Freud lists the questions the agent could not answer well, so you can close the gaps in knowledge one by one.

THE BOUNDARY

The audit reports what was asked and what was missing — it never fills gaps by guessing.

THE RESULT

The agent's weaknesses become next week's knowledge, on a schedule you control.

Ask Freud; Knowledge

⭢Try Freud
64. Multi-staff coordination

THE SITUATION

In a practice with several hands, the failure mode is not lack of work — it is two people both assuming the other one had it.

FREUD DOES

Freud keeps ownership, handoffs and pending approvals visible across the team, and names the bottleneck plainly when there is one.

THE BOUNDARY

Staff see practice operations they are entitled to see, and client privacy boundaries hold within everything shown.

THE RESULT

Nothing falls between two desks.

Ask Freud; Relationships

⭢Try Freud
65. Quarterly operations brief

THE SITUATION

Once a quarter, every practice owner thinks: I should sit down and review how this is actually going. Then the quarter ends.

FREUD DOES

Freud drafts the written review — what grew, what leaked, what changed in the workload, what to decide next — grounded in the quarter's real records and ready for your edits.

THE BOUNDARY

The brief observes operations only; the quality of care and all clinical matters are outside its scope by design.

THE RESULT

Reflect like a company, care like a practice.

Ask Freud; Apps

⭢Try Freud
66. Voice guardian

THE SITUATION

As more drafts get produced, the real risk is not errors — it is the practice starting to sound like software.

FREUD DOES

Every outbound draft is checked against your tone and approved language before it reaches the approval queue, and off-voice phrasing gets flagged, not sent.

THE BOUNDARY

Voice rules come from what you approved; Freud refines your voice, it does not rebrand you.

THE RESULT

The practice sounds like you, at any volume.

Emails; Library

⭢Try Freud
67. The morning command

THE SITUATION

Dashboards show state; owners need direction.

FREUD DOES

Ask Freud what would you do today and get a prioritized answer with reasoning — what to confirm, what to send, what to leave alone — with the tools queued to act on it, gated as always.

THE BOUNDARY

It recommends and prepares; a human approves anything that touches a real person.

THE RESULT

An operator, not a dashboard.

Ask Freud

⭢Try Freud
68. Boundary walkthrough

THE SITUATION

Staff will only lean on a system they trust, and trust starts with knowing exactly where the walls are.

FREUD DOES

On request, Freud walks any staff member through what it can and cannot touch: tenancy walls, approval gates, what the public side can never reach, and how a refusal works.

THE BOUNDARY

The explanation is honest about the limits — including the ones that constrain Freud itself.

THE RESULT

Trust that is inspectable, not promised.

Ask Freud

⭢Try Freud
69. Journey map

THE SITUATION

The pipeline is a list of stages; the actual journey of a person through the practice is invisible inside it.

FREUD DOES

Freud visualizes contacts from first inquiry to active to alumni, with stage-by-stage counts and where people linger.

THE BOUNDARY

The map shows stages and counts, never clinical content, and individuals are inspectable only one contact at a time, as any staff view allows.

THE RESULT

The pipeline becomes a picture you can actually manage.

Relationships; Ask Freud

⭢Try Freud
70. The staff/public wall, demonstrated

THE SITUATION

Every practice owner's real question about an AI front desk is the same: can it leak?

FREUD DOES

The architecture answers before you have to ask: public agents answer from approved knowledge only; internal notes, staff agendas, other clients and private conversations are structurally unreachable from the public side, and the agent refuses to discuss another person's data even when asked directly.

THE BOUNDARY

This is the product's design contract, not a promise layered on top of it: strict tenant isolation, staff/public separation, and refusal of cross-person exposure are enforced at the brain level.

THE RESULT

You can describe the wall to any client in one sentence — and it holds because it is built, not because it is promised.

Public agent; safety contract

⭢Try Freud
71. Consent as a record, not a checkbox

THE SITUATION

Consent to contact someone is claimed verbally, forgotten, and reconstructed from memory when it matters.

FREUD DOES

When the agent or a workflow collects consent, it is recorded on the contact with what was agreed and when, and follow-up playbooks respect it automatically.

THE BOUNDARY

Consent records are per-contact and per-purpose; anything without recorded consent stays out of outreach.

THE RESULT

Consent you can point to, and outreach that respects it without a memory test.

Relationships; Workflows

⭢Try Freud
72. Safe refusal under pressure

THE SITUATION

Sometimes a visitor asks the agent to do something it must not: reveal another person's details, bypass an approval, act outside its permissions, or follow instructions hidden inside pasted text.

FREUD DOES

Freud declines clearly, explains the limit simply, and offers the legitimate path — contacting the practice, booking properly, leaving a message for a human.

THE BOUNDARY

Retrieved and user-supplied content is treated as untrusted data, never as instructions that can override the practice's rules.

THE RESULT

The system holds the line exactly when it would be easiest not to.

Public agent

⭢Try Freud

Use Cases — Daddyfreud — Daddyfreud