By the Kith Team · 23 August 2026
If you're running online therapy sessions on Google Meet, you've probably already worked out the basics by trial and error — most therapists do. But there's a difference between "it worked last time" and having a setup you don't have to think about mid-session. Here's a practical walkthrough: how to set up the link, what to check before a session, what to do when the connection drops, and where automatic notetaking fits into the picture without adding another thing to manage.
Google Meet has a few things going for it that matter specifically for therapy, not just video calls in general. Clients can join from a link in their browser — no account, no app download, no software to troubleshoot on their end, which matters when the person joining is anxious, on an older device, or simply not tech-confident. It integrates natively with Google Calendar, so a session link can live in an invite rather than a message you have to dig up and re-send. And because it's a mainstream consumer product, most clients have already used it for something else, which lowers the "is this actually going to work" anxiety before a first session.
The tradeoff is that Meet itself has none of the practice-management layer you actually need — no patient records, no automatic conflict checking against your other appointments, no clinical notes. It's a video call, not a practice tool. Whether that's fine depends on how you're managing the rest of your practice around it.
There are two ways to generate a link, and they behave differently:
Either way, a few settings are worth locking in once rather than re-checking every time:
Most disrupted sessions trace back to one of a small number of causes, and all of them are checkable in under a minute:
If you're using any AI notetaking tool alongside Meet — Kith or otherwise — there's a step here worth being deliberate about rather than assuming it's handled invisibly. Recording an online session and using AI to process what was recorded are two separate actions with two separate ethical and legal weights, and they should be consented to separately, not bundled into one blanket "I agree" at intake.
In Kith specifically, this is built as two distinct consent gates — one for recording the session, one for AI processing of that recording — both required, and both tracked server-side rather than just noted in a paper file. That's a deliberate design choice, not an incidental one: a client can decline AI processing of their session while still consenting to you keeping a plain record, or vice versa, and the distinction is preserved rather than collapsed.
For online sessions, the actual mechanism is a bot that joins the Meet call as a participant (similarly to how a human notetaker would sit in), captures the conversation, and feeds it into the same two-layer note pipeline used for in-person sessions — a first pass that compresses the raw transcript, a second that structures it into a SOAP note, key points, a session summary, and homework. We've covered how that pipeline works in more detail in our guide to ambient transcription; the online version is functionally the same idea, just triggered by joining a call instead of a device microphone.
Worth knowing either way: if you're in India, the DPDP Act governs how you're expected to handle this kind of recorded, structured client data — we cover that separately in our DPDP 2023 explainer. If you're in the UK, it's UK GDPR, covered in our GDPR and AI notetaking guide. Neither law is specific to video call platforms, but both apply directly to anything an AI tool generates from one.
If you book a video session directly inside Kith, it creates the Google Meet link automatically as part of the booking — you don't separately open Calendar, add conferencing, and copy a link across. It also checks for scheduling conflicts against your existing appointments before confirming a booking, so double-bookings get caught at the point of scheduling rather than discovered later.
Worth being precise about the calendar piece, since it's easy to overstate: Kith pulls events from your connected Google Calendar in, so it knows what you're already booked for — it doesn't write changes back out to Google Calendar except for creating that one Meet event for a booking made inside Kith itself. If you're managing your real calendar of record in Google Calendar and only sometimes booking through Kith, keep that one-way direction in mind so you don't assume a change made in one place shows up automatically in the other everywhere.
None of this requires a paid plan to try — Kith's free plan covers this without a card up front, which matters if you just want to see whether the workflow fits before committing to anything.
None of this replaces good judgment about what a client can safely access. If someone has spotty broadband or shares a computer with family members and no private space to take a session, a slicker video setup doesn't solve that — it's worth having a real conversation with them about whether video is the right format at all, or whether phone, or eventually in-person, serves them better. The setup above will make the technical side close to invisible on a good day. It won't fix a bad-fit modality.
Related reading
An honest look at Kith as a SimplePractice alternative for solo therapists in India and the UK — pricing, AI notes, and where each one fits best.
Why therapy sessions get missed, and which parts of therapy scheduling software genuinely reduce no-shows versus which parts just feel like they should.
How UK GDPR actually applies to AI-assisted session notes — special category data, who's the controller, and the cross-border question AI tools raise.