TidyCal currently supports Microsoft Calendar and Microsoft Teams conferencing. When someone books time through TidyCal, the appointment lands on the organizerβs Microsoft calendar and includes a Teams join link.
Meetings booked via TidyCal do not consistently show Microsoft Teams "Recap" or "Transcript" options during or after the call. In contrast, meetings created manually in Outlook or Teams reliably display Recap and the transcript UI.
This breaks a key workflow for teams that rely on recordings and transcripts for internal documentation, follow-ups, and operational continuity.
A meeting created manually inside Outlook/Teams is recognized by Microsoft as a true Teams meeting.
The Recap panel appears.
The Transcript button is available when the organizerβs tenant settings allow it.
But for TidyCal-created bookings:
The Recap panel is missing.
Transcription options are not exposed to attendees as expected.
The experience is inconsistent versus native scheduling.
Based on the support response:
TidyCal appears to insert a Teams join URL into the calendar event rather than provisioning a native Teams onlineMeeting resource for each booking.
Microsoft does not always classify link-invited events as "native" onlineMeeting objects, so Recap/Transcript UI does not appear.
There is also discussion of Microsoft Graph meeting creation settings:
The Graph API exposes an allowTranscription option tied to the onlineMeeting resource.
If the meeting is not created as a proper onlineMeeting - or if allowTranscription is set to False - the transcript UI may not be available.
Support suggested:
Create a Teams meeting manually and reuse that link in TidyCal.
Use a static or recurring Teams link.
Manually manage transcription during the call.
These are workable short-term, but they create real downsides:
Using a static or recurring Teams meeting link can expose prior chat, notes, or transcript context to future invitees.
This undermines the value of TidyCal as a clean, per-appointment booking system.
Manual pre-creation adds friction and defeats the automation benefit.
Manual transcription control is not reliable and depends on the organizer remembering to manage settings each time.
TidyCal should upgrade the Microsoft integration so that every booking can optionally be created as a fully native Microsoft Teams meeting, not just a calendar event with a pasted join link.
This would ensure:
Microsoft recognizes the event as an official Teams onlineMeeting.
The Recap experience appears consistently.
Transcript controls behave the same as Outlook/Teams-created meetings.
Add an integration option such as:
"Create true Teams meetings for every booking (recommended)"
When enabled:
TidyCal uses Microsoft Graph to create an onlineMeeting resource per booking.
TidyCal attaches that onlineMeeting to the calendar event in the supported Microsoft-native way.
The meeting is treated equivalently to a meeting created directly in Outlook/Teams.
To support different org policies, the integration could offer:
Default transcription behavior setting at the booking type level:
Follow tenant policy (default)
Prefer transcription on (if allowed by tenant)
Prefer transcription off
Teams meeting creation mode:
Native onlineMeeting per booking
Insert join link only (legacy)
Use static link (explicitly labeled with warning about chat history)
A successful implementation should meet these outcomes:
For Microsoft 365 business/enterprise accounts, a TidyCal booking:
Provisions a native onlineMeeting.
Shows the Teams Recap UI after the call.
Shows Transcript controls consistent with tenant policies.
The meeting generated by TidyCal behaves the same as a manually created Teams meeting.
Each booking generates a unique meeting thread to avoid cross-meeting chat and recap leakage.
Admins can control defaults centrally, with booking-type overrides.
This feature would:
Remove a high-friction gap for Teams-heavy organizations.
Bring TidyCal up to modern expectations as Teams features evolve.
Strengthen a critical enterprise credibility point:
"Bookings created by TidyCal are first-class Microsoft meetings, not second-class link placeholders."
Increase retention and upgrades among users who depend on transcripts and meeting intelligence.
This is not just a minor UI bug - it directly affects:
Meeting documentation workflows
Sales calls and discovery notes
Customer success handoffs
Internal technical reviews and sprint rituals
For organizations that treat transcripts as operational memory, inconsistent Recap support is a significant reason to churn.