Meeting follow-up workflow in Caletus: from booking to recap

A good meeting follow-up workflow covers everything after someone clicks your booking link: the right times, a clear booking page, optional payment, a confirmation with the join link, reminders, an accurate record and a recap someone actually sends. Caletus handles the scheduling, reminders and meeting tools. A few steps, like reviewing notes and sending the recap, still need a person who owns them.

This walkthrough follows a consultant, Maya, and her client, Leo, through one 45-minute advisory session. For each step, it shows what to set up in Caletus and what Maya still does herself.

Define the consultation before you set anything up

Maya offers a focused session to review one onboarding problem and agree on the next thing to investigate. She isn't promising a full redesign during the call, and Leo should know that before he picks a time.

The example uses one host, one client and a 45-minute meeting, plus 10 minutes to prepare and 15 minutes for notes afterward. So each booking takes about 70 minutes of Maya's day. Test how the buffers actually show up before going live.

There's also an optional paid version at US$150. That's Maya's made-up service price, not a Caletus subscription price or a suggestion for what you should charge.

The whole Caletus meeting workflow at a glance

The point of the table: Caletus supports each step, but Maya is still responsible for her promises and for an accurate record.

Step 1: connect the right calendars and protect your time

Caletus checks Google and Outlook calendars for conflicts, lets you choose where new bookings land, and supports buffers, limits and date-specific changes.^[1][2]

Maya connects her work account and picks the calendars that hold real commitments. She chooses where new consultations should appear, sets her time zone and picks working hours she can keep.

Before sharing anything, she adds a test busy event and checks the times on offer. She also checks a holiday, a slot near the end of her day and the prep and note-taking buffers.

These checks matter more than a connected label. The right account can still have the wrong calendars selected, and strict rules can combine to leave no times at all.

Step 2: build a booking page that explains the offer

The meeting is called “Onboarding review consultation.” The description covers the 45-minute scope, who's hosting, what to prepare and what Leo gets: a discussion of one problem and an agreed next step.

Maya asks Leo for a short description of the issue and the outcome he hopes for. A link to an example is optional. The form doesn't ask for passwords, private customer records or a full project brief just to book a call.

Caletus lets Maya edit the booking page text, branding and which hosts appear, and the page is built to work on phones. She uses the settings her plan includes and checks the public page as well as the editor. The guide to setting up your first Caletus booking page covers this step in detail.^[3]

A simple branded page is enough to start. Add a custom domain, extra qualifying questions or team pools later, when the service needs them.

Step 3: make payment a clear, optional step

For the free consultation, Leo shouldn't hit a surprise payment step. For the US$150 paid version, the price, currency, what's included and the cancellation policy should be clear before checkout.

Caletus supports paid booking pages with Stripe checkout on Professional and Enterprise, with a 0% Caletus fee. Check your Stripe account, currency and plan before you offer the paid version publicly. For more on charging for sessions, see how to accept payments for online consultations.^[4][6]

In a test, check two records after checkout: did the payment go through, and is the meeting confirmed at the right time? Also try an abandoned or failed payment, so you know what the client sees.

Taking a payment and receiving the payout are separate steps. And cancelling a meeting doesn't mean the money was refunded. Decide who handles exceptions and where they check the Stripe record.

Step 4: check the confirmation Leo receives

The confirmation screen and email should show the host, purpose, full date, time zone, length, location, prep request and how to reschedule. Leo shouldn't have to dig through old emails for the join link.

Caletus sends confirmations and reminders and keeps track of changes to the meeting. Test the actual confirmation email and calendar invite in your account, including who it's from, where replies go and whether another connected tool sends a duplicate.^[4][5]

For the paid version, the booking confirmation isn't proof of payment. Stripe may send its own receipt, so don't call a booking email an invoice.

Maya also checks her own side. A client confirmation isn't enough if the meeting landed on the wrong calendar or shows the wrong organizer.

Step 5: send prep notes and reminders that fit

A simple reminder plan might be one prep message the day before and a short join reminder closer to the start. Adjust the timing to how far ahead people usually book. Email reminders come with every Caletus plan, and SMS reminders start on Professional.^[6]

Don't send a “see you tomorrow” message right after a same-day booking. Check what happens to reminders whose send time has already passed, and make sure your calendar and other tools aren't sending reminders too. These appointment reminder email templates can help with the wording.

A useful prep line: “Please bring one onboarding example you're allowed to share and the main question you want answered.” It's specific without turning a short call into a long intake form.

Step 6: check the meeting room and run the meeting

Caletus connects to outside video tools and also has a built-in video room. Picking Zoom or Google Meet for a meeting doesn't mean every Caletus collaboration or AI feature works inside that room.^[1][5]

Maya tests the guest path before the client meeting. She checks the join details, the host name, how guests get admitted and what happens when the guest isn't signed in. A join link doesn't get around the video provider's own access rules.

During the call, Maya confirms the goal and keeps to the promised scope. When Leo raises a bigger question, they decide together whether it fits this session or needs a separate proposal. That's a judgment call no scheduling tool makes for you.

Step 7: take notes that capture the agreement

The notes should cover the problem discussed, evidence reviewed, decisions, open questions and accepted actions. “Explore a redesign” and “A redesign was approved” are very different. Give each accepted next step an owner and a full date.

Caletus's meeting tools include shared notes, and its paid plans include AI meeting notes with action items. Check who can see them and whether they work with your video setup before a client call.^[5][6]

If shared notes fit the project, Maya uses them with the right audience. If not, she keeps the record in another approved document and sends it herself.

Maya reviews any AI recap against the source before sharing it, paying close attention to names, amounts, conditions and commitments. A polished summary doesn't prove the client agreed to everything in it. This AI meeting summary review checklist covers what to check.

Step 8: close the follow-up loop

Maya sends a short recap with the agreed investigation, who's doing what and the next review date. She checks the permissions on any linked notes, so Leo can open them without them being public.

In this example, the outcome might be: Maya reviews the approved onboarding example, Leo sends one missing process detail, and they decide whether more work makes sense. No sales or revenue result is implied.

Unless a tested automation sends this exact follow-up, it's Maya's job. A completed appointment record doesn't prove the recap went out or that anyone accepted their action.

Step 9: record the outcome before you analyze it

Caletus analytics cover bookings, completed meetings, cancellations, where bookings came from and outcomes by host. Check how each status gets set and what your plan shows before you build reports on them.^[7]

A meeting that's past its end time didn't necessarily happen. Keep cancellations, no-shows, unclear outcomes and real completions apart. When a booking is rescheduled, track it as the same meeting so it doesn't count twice.

For a solo consultant, the useful questions are simple. Do clients understand the offer? Does follow-up happen on time? Bigger funnel reports can wait until you have clean data and someone to read them.

Launch checklist for your meeting follow-up workflow

1. 1Confirm your plan, video tool and payment provider support everything you need together.
2. 2Check that availability, conflicts, buffers, holidays and time zones work as expected.
3. 3Make sure the booking page describes the service accurately and asks only useful questions.
4. 4Give the optional payment flow, including failed payments, an owner.
5. 5Check that the confirmation, calendar entry and join details all match.
6. 6Test that rescheduling and cancelling update the original meeting.
7. 7Review notes and any AI summary, then share them with the right people.
8. 8Name the follow-up owner, and record outcomes that match what actually happened.

Get one complete meeting working from start to finish, then expand. The workflow earns its keep when a client moves from a first question to a clear next step, and that matters more than switching on every feature.

• Caletus workflow
• client consultation
• meeting follow-up
• meeting management