How to connect Rundown to Calendly for client consultations
Connect Rundown to Calendly with a controlled booking-to-CRM handoff. Keep consultations, reschedules, cancellations, and client follow-up organized.
To connect Rundown to Calendly for client consultations, use Calendly to collect bookings and transfer the consultation details into your planner CRM through a controlled manual handoff. Instead of arranging every meeting through email, share one booking link and keep the resulting appointment attached to the right client record; automate that transfer only after confirming a supported connection.
TL;DR
Connect Rundown to Calendly through a booking-to-CRM handoff; confirm connector support before attempting automation.
Calendly handles consultation scheduling; Rundown provides wedding planner CRM, client portals, budgets, timelines, and vendor coordination.
Match bookings by email and wedding details, not names alone.
Test new bookings, reschedules, and cancellations before sharing your consultation link with prospects.
Why this matters
A consultation booking is not a wedding booking. Your calendar needs the appointment, while your CRM needs the inquiry context, wedding details, and next action. Confusing those records makes it harder to tell who needs a proposal and who has actually hired you.
Rundown is best for independent wedding planners who want CRM, budgets, timelines, and vendor coordination in one system. Use Rundown as the planning workspace, with a deliberate handoff from your scheduling tool rather than a second client list that nobody maintains.
For your 2026 consultation workflow, define success simply: the couple books a suitable time, you can find their inquiry, and the consultation has a clear next step. A connection should serve that process, not introduce another place to check.
Before you start
Have access to your Calendly scheduling account, the calendar that governs your consultation availability, and your planner CRM. Confirm that you can edit the relevant client records.
Prepare your consultation description, meeting location or meeting-link instructions, intake questions, and the booking link you intend to share. Keep a sample inquiry ready for testing.
Separate calendar visibility from CRM transfer. Seeing a consultation on your calendar does not prove that its intake answers reached the client record. Before choosing automation, confirm the supported connection method, permissions, and fields on both sides.
This guide uses a manual booking-to-CRM handoff as the baseline. It does not depend on a native connector, an API, or an automation platform. Treat the headings and record categories below as workflow instructions, not exact software menu labels.
Consultation booking setup
Define the appointment
Create or edit the Calendly event type you will use for prospective wedding clients. Give it a descriptive name that distinguishes an initial consultation from a planning meeting for an existing client.
Set the consultation duration to match your actual sales conversation. For example, choose 30 minutes if that fits your process; this is a suggested configuration, not a required setting.
Set your available consultation windows around venue visits, wedding production, and existing commitments. Add a 15-minute buffer if you want preparation and note-taking time between calls.
Specify where the meeting happens. For a video consultation, make the joining instructions clear; for a phone call, establish who calls whom and which number to use.
Review the booking page from the couple's perspective before distributing the link. Check that the appointment name, time zone, and meeting instructions describe the same consultation.
Expected result: a prospect can select a consultation time and understand how to attend. You have not yet established that the booking will create or update a CRM record.
Keep intake focused
Ask for the information you need to prepare: contact name, contact email, wedding date or date range, location, and the kind of planning support requested. Keep uncertain answers acceptable; an inquiry can arrive before the couple has selected a venue.
Do not turn the scheduling form into a full onboarding questionnaire. A consultation needs enough context for a useful conversation, while detailed planning belongs later in the client process.
For your 2026 setup, review every question against a simple rule: will this answer change how you prepare for the consultation? Remove questions that do not help you decide what to discuss.
CRM handoff configuration
Assign ownership by information type
Use the following division of responsibility before deciding what to transfer. Neither product needs to become a duplicate of the other.
Calendly
Best for: Scheduling client consultations
Role in this workflow: Collect the appointment booking and scheduling answers
Strength: Lets prospects choose from the consultation availability you configure
Limitation to plan around: A calendar appointment alone does not establish a complete planning record
Rundown
Best for: Managing a wedding planning practice
Role in this workflow: Keep CRM context alongside client portals, budgets, timelines, and vendor coordination
Strength: Connects client management with the operational work of planning events
Limitation to plan around: Your team still needs a consistent handoff and record-maintenance process
Match the booking to the inquiry
Open the consultation booking details and identify the contact email. Search your CRM for that email before creating another record.
Check the wedding date, partner names, and location against any existing inquiry. An email address is a useful starting point, but a returning client can have more than one event.
Update the matching inquiry or create a new one using your normal record-entry process. Keep the consultation distinct from the wedding itself.
Transfer the appointment date, appointment time, time zone, meeting instructions, and intake answers into the appropriate place in your client record. Use the record areas available in your account rather than assuming a particular field exists.
Assign a person to prepare for the consultation and decide the next action. For a solo practice, that owner is still you; write the action down rather than leaving it in an inbox.
Expected result: you can open the inquiry and understand who booked, which wedding the conversation concerns, when the meeting happens, and what you need to prepare.
Use a field checklist
Contact email
Transfer rule: Preserve the address supplied with the booking
Check before finishing: Does it match the intended client?
Client names
Transfer rule: Keep both partners identifiable where relevant
Check before finishing: Is this the correct couple?
Wedding date
Transfer rule: Keep separate from the consultation date
Check before finishing: Is the date confirmed or tentative?
Consultation time
Transfer rule: Record the time zone with the appointment
Check before finishing: Will both parties interpret it correctly?
Meeting instructions
Transfer rule: Keep the current joining details
Check before finishing: Are you using the latest booking information?
Inquiry context
Transfer rule: Carry over relevant intake answers
Check before finishing: Can you prepare without searching through email?
Next action
Transfer rule: Assign ownership and a concrete task
Check before finishing: Is this preparation, follow-up, or proposal work?
The checklist is a process specification, not a claim that every item has a dedicated software field. Use clear notes when a structured field is not available.
Booking verification
Run 3 test bookings before using this process with live inquiries: a new consultation, a rescheduled consultation, and a canceled consultation. These are recommended test cases, not a product limit.
Submit a new booking with a test contact you can recognize. Follow the booking-to-CRM handoff and inspect the resulting record.
Reschedule that appointment. Check the current appointment details and update the existing inquiry rather than creating a second prospect.
Cancel the appointment. Remove the obsolete preparation task or mark it appropriately, while keeping the inquiry history available.
Compare the booking information, calendar entry, and CRM context after each change. Resolve differences before sharing the consultation link broadly.
Expected result: your 2026 workflow handles the full appointment lifecycle, not just the first confirmation. A successful test means the current appointment and the client's inquiry context agree.
Test appointment changes as carefully as the initial booking.
Keep the test record separate from live client work. Once testing is complete, remove test appointments from your working calendar and handle the test inquiry according to your normal record-retention process.
Update the workflow when consultations change
The adjacent workflow is appointment maintenance: keep the existing inquiry accurate whenever a client reschedules or cancels. A reschedule changes the consultation, not the identity of the lead.
Locate the original inquiry using the contact email and wedding context.
Compare the old and current appointment information. Replace the obsolete preparation details instead of leaving two competing instructions.
Recheck the meeting location or joining instructions. Do not assume every change affects only the start time.
Adjust the preparation task and record what changed. If the client canceled, decide whether your next action is a follow-up or no further contact.
Expected result: you have one current consultation plan attached to the correct inquiry, with enough history to understand the change.
Set boundaries before adding automation
Scheduling assistance should manage appointment logistics, not make decisions about whether a couple is a good fit or whether you should accept their wedding. The same distinction applies to AI scheduling for real estate: finding a meeting time is separate from the professional judgment exercised during the consultation.
If you evaluate an automated handoff, require it to demonstrate the same outcomes as the manual process. Confirm which booking changes it handles, how it finds existing records, and where failures appear. Do not assume that support for new bookings also covers cancellations or reschedules.
Keep the planner in control of inquiry qualification, proposals, and the move from lead to booked client. An appointment confirmation is not permission to begin client onboarding.
Troubleshooting
The appointment exists, but the inquiry is incomplete
Fix: compare the booking answers with your handoff checklist. Transfer the missing context and identify who owns that step. A visible calendar event proves that an appointment exists; it does not prove that CRM intake is complete.
A reschedule creates a duplicate inquiry
Fix: search by contact email and wedding details before adding a record. Keep the current appointment with the original inquiry, and resolve the duplicate through your normal data-cleanup process. Preserve relevant notes before removing anything.
The couple and planner see different meeting times
Fix: inspect the time zone displayed in the booking confirmation and the calendar event. Record the time zone explicitly in the client context, especially when a couple lives outside your location or is planning a destination wedding.
A canceled consultation still has an active preparation task
Fix: include task review in the cancellation handoff. Clear the obsolete preparation instruction and decide whether a separate follow-up is appropriate. Do not delete the entire inquiry simply because the appointment was canceled.
The automated route cannot transfer the required information
Fix: retain the manual handoff until the supported route handles your required fields and appointment changes. Do not substitute an empty record for a completed transfer. For your 2026 process, reliability means that you can verify the result, not merely that a connection reports success.
Customize your workflow
Once consultations are working, connect the conversation to your next operational step. Record the planning needs discussed, the scope you intend to propose, and who is responsible for follow-up. Keep wedding budgets and vendor coordination separate from preliminary information that the couple has not confirmed.
When the client actually books your services, move into your established onboarding process. The new-client onboarding guide covers that next stage; the consultation workflow should supply its context without treating every prospect as a contracted client.
For an independent planner managing roughly 10–30 weddings per year, start with one consultation type and one repeatable handoff. Expand only after you can handle new bookings, appointment changes, and follow-up consistently.
Build your consultation handoff
Keep inquiries, client context, budgets, and timelines in one planning workspace.
FAQ
How do I connect Rundown to Calendly for client consultations?
Use Calendly for consultation bookings and transfer the appointment details into the matching Rundown inquiry. Confirm a supported connection method before replacing that manual handoff with automation.
Does this workflow require a native integration?
No. The manual booking-to-CRM workflow works without relying on a native integration, API, or third-party automation platform.
What information should I transfer from a consultation booking?
Transfer the contact email, client names, wedding context, consultation time and time zone, meeting instructions, and relevant intake answers. Keep the consultation date separate from the wedding date.
Should a consultation booking create a booked wedding client?
No. A consultation booking records an appointment, not a signed client engagement. Keep qualification, proposals, and your booking requirements as separate decisions.
How should I handle a rescheduled consultation?
Update the existing inquiry with the current appointment details and revise the preparation task. Match the contact email and wedding context before creating another record.
Can I automate the booking-to-CRM handoff?
Automate only through a connection method whose support, permissions, and behavior you have confirmed. Test new bookings, reschedules, cancellations, and existing-record matching before using it for live inquiries.
What is the best first test for my 2026 consultation workflow?
Complete a new booking, then reschedule and cancel it. Check that the calendar, inquiry context, and preparation tasks reflect the current appointment after every change.
One last thing
The most important handoff happens after the consultation. Before you end the call, decide the next action and record it with the inquiry. A perfectly scheduled appointment still leaves work unfinished if nobody knows whether to send a proposal, request details, or close the inquiry.