Run Sales Meetings From Calendly Booking to tl;dv Follow-Up
Combine Calendly booking context and a completed tl;dv transcript into call preparation, deal evidence, proposed HubSpot updates, and a Gmail draft. Configure the trigger explicitly rather than assuming a booking starts a run.
Four one-page reports across the sales meeting lifecycle
Okou prepares four standalone reports, each designed to be opened and reviewed on its own: a pre-call account brief from Calendly and HubSpot, a call intelligence report grounded in the tl;dv transcript, a deal update report for HubSpot, and a customer follow-up report with a mutual action plan and the correct next Calendly link. Move through the carousel to read each live HTML one-pager, then open it to select and copy the text. The data is illustrative; the report formats are the real outputs Okou prepares.
What is a Calendly and tl;dv sales workflow?
A Calendly and tl;dv sales workflow connects the context collected when a prospect books a meeting with the conversation captured during the call. Combine Calendly booking context and a completed tl;dv transcript into call preparation, deal evidence, proposed HubSpot updates, and a Gmail draft. Configure the trigger explicitly rather than assuming a booking starts a run.
Why scheduling and call intelligence still leave a handoff gap
A prospect books a discovery call through Calendly and answers three qualification questions. Those answers contain the reason they booked, the size of the rollout, and their target date, but they normally disappear into the calendar invite. Before the meeting, Okou combines that context with the account and deal history in HubSpot to prepare the rep. tl;dv records the call and produces the transcript. Once the configured trigger starts the run and the transcript is available, Okou matches it back to the booking, scores the deal, quotes the risks, logs both sides' promises, prepares the HubSpot update, and leaves a personalized follow-up in Gmail with the next Calendly link. The rep reviews four prepared handoffs instead of reconciling four tools.
How Okou connects Calendly and tl;dv for sales
1. Choose the accounts and access
2. Start in the Okou conversation
3. Review and reuse the workflow
How Calendly, tl;dv, HubSpot, and Gmail work together
Calendly and tl;dv are the core inputs. HubSpot and Gmail turn the combined context into sales execution. Each connector stays scoped to the part of the workflow it owns.
Calendly integration: the booking context Okou reads
RequiredOkou reads the event type, scheduled time, organizer, invitees, meeting link, booking-question answers, and available reschedule history. It uses those fields to identify the account, understand why the prospect booked, and prepare the rep before the call. This workflow does not cancel, reschedule, or book meetings automatically.
tl;dv integration: the conversation Okou analyzes
RequiredWhen the meeting transcript is ready, Okou reads the meeting metadata, attendee and speaker labels, transcript text, timestamps, notes, and highlights available from tl;dv. It matches the recording to the Calendly event by meeting link, attendee email, and start time, then grounds every sales signal in what was actually said.
HubSpot integration: the deal record Okou updates
OptionalOkou matches the contact, company, and deal from available identifiers, reads prior notes, and prepares the meeting update with evidence, risks, and commitments. Review ambiguous matches and proposed field changes before authorizing the CRM write.
Gmail integration: the follow-up Okou drafts
OptionalOkou creates a follow-up draft addressed to the customer attendees. It restates their goals, records both sides' commitments, proposes the next step, and includes the correct Calendly link when another meeting is needed. The message remains an unsent draft until the rep reviews and sends it.
Okou vs. manual handoffs vs. tl;dv alone
Calendly captures intent before the call and tl;dv captures the call itself. The sales value appears when those records drive the next action together.
Manual handoff
The rep copies booking answers into notes, watches the recording, updates HubSpot, and writes the follow-up. Each system has the data, but the rep still does the reconciliation.
tl;dv alone
The transcript and meeting summary are searchable, but the booking questions, deal history, CRM update, and customer follow-up remain separate tasks.
Okou with Calendly and tl;dv
Okou joins the booking and transcript, prepares the rep before the call, then turns the conversation into deal evidence, a HubSpot note, and a Gmail draft after it. The rep reviews decisions instead of assembling context.
Tips for better results
Frequently asked questions
How do Calendly and tl;dv work together for sales?
Calendly supplies the booking context: who booked, why they booked, their answers, and when the meeting happens. tl;dv supplies the conversation: speakers, transcript, timestamps, notes, and highlights. Okou matches both records and uses the combined context for prep, qualification, CRM updates, and follow-up.
How does Okou match a tl;dv recording to the right Calendly event?
Okou first looks for a shared meeting link or provider event ID. When those are unavailable, it uses the organizer, external attendee email, title, and start time within a narrow window. If more than one meeting or deal matches, Okou asks you to choose before writing anything.
What happens when a prospect books through Calendly?
Okou reads the available booking questions, finds the contact and deal in HubSpot, and prepares a short pre-call brief with account history, known stakeholders, open commitments, three questions to validate, and a suggested agenda. This begins only when you run the workflow or configure a supported webhook or schedule; connecting the service alone does not subscribe to those events.
What happens when the tl;dv transcript is ready?
After you run the workflow or configure a supported webhook or schedule, Okou uses the accessible transcript to prepare deal evidence, proposed HubSpot updates, and a Gmail follow-up draft. Missing transcript details remain missing; connecting tl;dv alone does not start a run.
Will Okou send emails or change the HubSpot deal stage automatically?
No. The default workflow creates an unsent Gmail draft and suggests any stage change with supporting evidence. The rep reviews the email and explicitly approves CRM stage changes.
Connect your next booked sales call end to end
Start in the Okou conversation with your sources and the result you need. Review the first result, then decide which parts to save as a workflow.
