30 Claude Prompts for Calendly

You are a business development writer who sends first touch outreach emails. <context> I am reaching out cold to [RECIPIENT ROLE] to offer a [MEETING TYPE] and want to include my Calendly link without the email reading like a mass template. </context> <inputs> - Recipient role: [RECIPIENT ROLE] - Reason I am reaching out now: [TRIGGER OR REASON] - What is in it for them: [SPECIFIC BENEFIT] - My Calendly link placeholder: [CALENDLY LINK] - Sender name and company: [YOUR NAME, COMPANY] </inputs> <task> Write a cold outreach email under 120 words that ends with a single clear invite to book time on the Calendly link. </task> <constraints> One specific reason for reaching out in the first line, not a generic opener. No more than one link in the whole email. Do not ask "do you have 15 minutes", instead point straight to the link. Avoid the words "just wanted to" and "circling back". </constraints> <format> Return subject line, then the email body, then one alternate subject line option. </format>

You are a client relations specialist who writes warm introduction emails after a referral. <context> Someone was referred to me by [REFERRER NAME] and I need to send a friendly first email that references the referral and invites them to book a [MEETING TYPE]. </context> <inputs> - Referrer name: [REFERRER NAME] - Recipient name and context: [RECIPIENT NAME, WHAT THEY DO] - What the referrer told me about their need: [STATED NEED] - Calendly link placeholder: [CALENDLY LINK] </inputs> <task> Write a warm introduction email that opens by naming the referrer, connects to their stated need, and closes with the booking link. </task> <constraints> Under 100 words. Mention the referrer by name in the first sentence, not buried later. Keep tone conversational, not salesy. No bullet lists, this should read like a normal email. </constraints> <format> Return subject line and email body only, no extra commentary. </format>

You are an executive assistant who writes internal meeting invitations for a busy team. <context> I need to invite [NUMBER] colleagues to a [MEETING TYPE] scheduled through Calendly and want the invite email to set expectations so people show up prepared. </context> <inputs> - Meeting purpose: [MEETING PURPOSE] - Attendees: [LIST OF ATTENDEES OR ROLES] - Topics to cover: [2 TO 3 TOPICS] - Anything attendees should bring or read first: [PREP ITEM] - Calendly link placeholder: [CALENDLY LINK] </inputs> <task> Write an internal meeting invite email that states the purpose, lists the topics, and tells attendees what to prepare before the call. </task> <constraints> Under 90 words. Use a short bulleted agenda, not a paragraph. State the prep item as an action, for example "review" or "bring", not a vague mention. No corporate throat clearing like "per our discussion". </constraints> <format> Return subject line, then body with a short bulleted agenda section. </format>

You are a client success manager who schedules recurring check ins with existing clients. <context> I need to send [CLIENT NAME] a short email inviting them to book our regular [MEETING TYPE] using my Calendly link, and I want it to feel personal rather than automated. </context> <inputs> - Client name: [CLIENT NAME] - Last topic discussed: [LAST TOPIC OR PROJECT] - Reason for this check in: [REASON, E.G. QUARTERLY REVIEW] - Calendly link placeholder: [CALENDLY LINK] </inputs> <task> Write a short email that references the last conversation by name and invites the client to pick a time on the Calendly link. </task> <constraints> Under 80 words. Reference the specific last topic, not a generic "checking in". No apology for reaching out. End with the link and nothing after it, no extra sign off paragraph. </constraints> <format> Return subject line and email body as plain text. </format>

You are a coordinator who schedules calls across multiple time zones. <context> I am inviting [NUMBER] people across different time zones to a [MEETING TYPE] via a Calendly group event and want to avoid the usual time zone confusion in the invite. </context> <inputs> - Meeting purpose: [MEETING PURPOSE] - Time zones involved: [LIST OF TIME ZONES] - Calendly link placeholder: [CALENDLY LINK] - Deadline to book by: [BOOKING DEADLINE] </inputs> <task> Write a group invite email that clearly explains the Calendly link will show each person their own local time, and gives a deadline to book by. </task> <constraints> Under 90 words. State plainly that the link auto-adjusts to their time zone so nobody needs to do math. Include the booking deadline as its own short sentence. No listing every time zone's exact hour by hand. </constraints> <format> Return subject line and body, plus one short reminder line I can reuse as a follow up two days before the deadline. </format>

You are a scheduling operations specialist who reduces meeting no-shows through better reminders. <context> My Calendly reminders go out 24 hours before a [MEETING TYPE] and the default text is bland enough that people forget to actually read it. </context> <inputs> - Meeting type: [MEETING TYPE] - Date and time merge fields: [DATE/TIME PLACEHOLDER] - What they should have ready: [PREP ITEM] - Reschedule link placeholder: [RESCHEDULE LINK] </inputs> <task> Write a 24 hour reminder email that restates the time, names one prep item, and makes rescheduling easy if needed. </task> <constraints> Under 60 words. Time and date must be the first thing mentioned. Include the reschedule link as an easy out, not as a guilt trip. No exclamation points, no "can't wait to chat". </constraints> <format> Return subject line and body only. </format>

You are a scheduling assistant who writes short SMS and chat style reminders. <context> I want a very short reminder that goes out one hour before a [MEETING TYPE] booked through Calendly, meant for SMS or a messaging app rather than email. </context> <inputs> - Meeting type: [MEETING TYPE] - Time merge field: [TIME PLACEHOLDER] - Join link or location: [JOIN LINK OR LOCATION] - Sender first name: [YOUR FIRST NAME] </inputs> <task> Write a one hour reminder message under 300 characters suitable for SMS, including the join link and time. </task> <constraints> No subject line needed. One sentence, two at most. No emoji. Include the exact time and the join link, nothing else. Sign off with first name only. </constraints> <format> Return the message as plain text, single block, ready to paste into an SMS reminder tool. </format>

You are a lifecycle email writer who builds reminder sequences for scheduled events. <context> People register for a [EVENT TYPE, E.G. LIVE WEBINAR] through a Calendly event and I want a short sequence of reminders leading up to it, not just one email. </context> <inputs> - Event type: [EVENT TYPE] - Event date and time: [DATE/TIME PLACEHOLDER] - Number of reminders wanted: [NUMBER, E.G. 3] - Join link placeholder: [JOIN LINK] - One reason to actually show up live: [LIVE VALUE REASON] </inputs> <task> Write a sequence of reminder emails at 3 days before, 1 day before, and 1 hour before the event, each one different in content, not copies of each other. </task> <constraints> Each email under 80 words. The 1 hour email must be noticeably shorter than the 3 day one. Each one should reference the live value reason differently, not repeat the same sentence. No repeated subject lines. </constraints> <format> Return 3 labeled sections, one per email, each with subject line and body. </format>

You are a client operations manager who handles paid appointment logistics. <context> A client has paid for and booked a [MEETING TYPE] through Calendly and I want the reminder email to also confirm payment and set expectations for the session itself. </context> <inputs> - Meeting type: [MEETING TYPE] - Amount paid and what it covers: [PRICE, WHAT IS INCLUDED] - Time merge field: [DATE/TIME PLACEHOLDER] - Cancellation policy summary: [CANCELLATION POLICY] - Join link placeholder: [JOIN LINK] </inputs> <task> Write a reminder email that confirms the paid booking, restates what is included, states the cancellation policy plainly, and gives the join link. </task> <constraints> Under 100 words. State the cancellation policy in one neutral sentence, not defensively worded. Do not repeat the price more than once. Keep tone professional, not apologetic about the policy. </constraints> <format> Return subject line and body, with the cancellation policy line clearly separated from the rest of the paragraph. </format>

You are a team operations coordinator who manages recurring internal meetings. <context> Our team has a recurring [MEETING TYPE, E.G. WEEKLY STANDUP] booked as a standing Calendly event and attendance has been slipping because people stop noticing the reminders. </context> <inputs> - Meeting type: [MEETING TYPE] - Frequency: [FREQUENCY, E.G. WEEKLY] - Recent attendance issue: [ISSUE, E.G. HALF THE TEAM SKIPPING] - What changes this week specifically: [THIS WEEK'S FOCUS OR AGENDA ITEM] </inputs> <task> Write a reminder email for a recurring meeting that includes one thing specific to this week's session, so it does not read as an identical copy of last week's reminder. </task> <constraints> Under 70 words. The specific this-week detail must be in the first line. No generic phrase like "don't forget about our meeting". Address the attendance issue indirectly through relevance, not by scolding anyone. </constraints> <format> Return subject line and body only. </format>

You are a client relations manager who handles missed appointments without sounding annoyed. <context> A prospect booked a [MEETING TYPE] through Calendly and did not show up or send a message, and I need to follow up in a way that keeps the door open. </context> <inputs> - Meeting type: [MEETING TYPE] - Prospect name: [PROSPECT NAME] - Original date and time: [DATE/TIME PLACEHOLDER] - New booking link placeholder: [CALENDLY LINK] </inputs> <task> Write a short follow up email after a no-show that assumes something came up, not that they blew me off, and offers a new link to rebook. </task> <constraints> Under 70 words. No guilt trip language like "I waited" or "I was disappointed". One clear next step: the rebooking link. Give them a graceful out if they are no longer interested. </constraints> <format> Return subject line and body only. </format>

You are a professional who occasionally needs to move a meeting due to a conflict. <context> I have a [MEETING TYPE] booked with [CLIENT NAME] through Calendly but I have a conflict and need to ask them to reschedule, and I want to do it without sounding careless. </context> <inputs> - Client name: [CLIENT NAME] - Original date and time: [ORIGINAL DATE/TIME] - Reason for the conflict, kept brief: [SHORT REASON] - Reschedule link placeholder: [CALENDLY LINK] </inputs> <task> Write an email asking to reschedule that briefly states the reason, apologizes once, and gives the link to pick a new time. </task> <constraints> Under 60 words. Apologize exactly once, do not repeat sorry multiple times. State the reason in one short clause, do not over explain. Offer to keep the original time if it turns out to still work. </constraints> <format> Return subject line and body only. </format>

You are an operations manager who sets boundaries around chronic no-shows without losing the relationship. <context> A client has now missed [NUMBER] scheduled [MEETING TYPE] sessions booked through Calendly without notice, and I need to address it directly but professionally in an email. </context> <inputs> - Client name: [CLIENT NAME] - Number of missed sessions: [NUMBER] - Policy I want to introduce going forward: [NEW POLICY, E.G. REQUIRE 24H NOTICE OR FORFEIT DEPOSIT] - Relationship value, why I still want to keep them: [WHY THEY MATTER] </inputs> <task> Write an email that names the pattern factually, introduces the new policy plainly, and confirms I still want to work with them. </task> <constraints> Under 100 words. State the number of missed sessions as a fact, not an accusation. Introduce the policy as a standard update, not a punishment aimed at them specifically. End on the relationship, not the policy. </constraints> <format> Return subject line and body, with the policy statement as its own short paragraph. </format>

You are a client operations coordinator who processes cancellations that come in past the cutoff window. <context> A client canceled a [MEETING TYPE] booked through Calendly less than [CANCELLATION WINDOW, E.G. 24 HOURS] before the start time, which is inside our late cancellation window, and I need to acknowledge it and explain what happens next. </context> <inputs> - Meeting type: [MEETING TYPE] - Cancellation window: [CANCELLATION WINDOW] - Consequence per policy: [FEE OR CREDIT LOSS, IF ANY] - Rebooking link placeholder: [CALENDLY LINK] </inputs> <task> Write an acknowledgment email that confirms the cancellation was received, states the policy consequence plainly, and offers the rebooking link. </task> <constraints> Under 80 words. State the consequence as policy fact, not personal judgment. No passive aggressive tone. Offer the rebooking link as a genuinely helpful next step, not an afterthought. </constraints> <format> Return subject line and body only. </format>

You are a scheduling coordinator who manages a waitlist for a fully booked calendar. <context> My Calendly for [MEETING TYPE] has been fully booked and a slot just opened up, so I need to notify the next person on my manual waitlist before the slot fills again. </context> <inputs> - Meeting type: [MEETING TYPE] - Person on waitlist: [WAITLIST PERSON NAME] - Newly open slot: [DATE/TIME OF OPENING] - Time limit to claim it: [CLAIM WINDOW, E.G. 2 HOURS] - Calendly link placeholder: [CALENDLY LINK] </inputs> <task> Write a short email that tells the waitlisted person a slot opened, gives the claim window, and links to book it. </task> <constraints> Under 60 words. State the claim window clearly as a deadline, not a soft suggestion. Make clear that the slot goes to whoever books first if there are multiple people on the waitlist. No unnecessary preamble. </constraints> <format> Return subject line and body only. </format>

You are a sales professional who writes post call follow up emails that move deals forward. <context> I just finished a [MEETING TYPE] booked through Calendly with [PROSPECT NAME] and need to send a recap email that captures what we agreed on and pushes toward a next step. </context> <inputs> - Prospect name: [PROSPECT NAME] - Key points discussed: [2 TO 3 POINTS] - Objection or question raised: [OBJECTION OR OPEN QUESTION] - Agreed next step: [NEXT STEP] - Next step Calendly link if applicable: [CALENDLY LINK] </inputs> <task> Write a follow up email that recaps the key points, addresses the objection briefly, and confirms the agreed next step with a date if one was set. </task> <constraints> Under 130 words. Recap points as a short bulleted list, not a paragraph. Address the objection in one or two sentences, do not re-pitch the whole product. End with a specific next step, not "let me know if you have questions". </constraints> <format> Return subject line, then body with a short bulleted recap section and a closing next step line. </format>

You are a project coordinator who turns raw meeting notes into a clean internal summary. <context> I had a [MEETING TYPE] booked via Calendly and took rough notes during the call that I now need turned into a clean summary to share with people who were not there. </context> <inputs> - Meeting purpose: [MEETING PURPOSE] - Raw notes: [PASTE ROUGH NOTES] - Decisions made: [DECISIONS, IF ANY] - Owners for follow up items: [NAMES OR ROLES] </inputs> <task> Turn the raw notes into a structured summary with sections for what was discussed, decisions made, and action items with owners. </task> <constraints> Use three clear sections, do not merge decisions and action items together. Each action item must have a named owner, mark it [UNASSIGNED] if the notes do not say who. Cut filler chatter from the raw notes, keep only substance. </constraints> <format> Return the summary with headers: Discussed, Decisions, Action Items (owner in parentheses after each item). </format>

You are a service provider who collects client feedback after paid sessions. <context> A client just completed a paid [MEETING TYPE] booked through Calendly and I want to ask for honest feedback without it feeling like a form email. </context> <inputs> - Meeting type: [MEETING TYPE] - Client name: [CLIENT NAME] - Specific thing to ask about: [SPECIFIC ASPECT, E.G. CLARITY OF ADVICE] - Feedback link or reply-to-this-email option: [FEEDBACK LINK OR NONE] </inputs> <task> Write a feedback request email that asks one specific question about the session rather than a generic "how did it go". </task> <constraints> Under 70 words. Ask exactly one specific question, not a survey of five. Make replying easy, one sentence is a fine answer. No incentive language like "leave us 5 stars". </constraints> <format> Return subject line and body only. </format>

You are a consultant who sends proposals shortly after a discovery call. <context> I had a [MEETING TYPE] booked via Calendly with [PROSPECT NAME] where we discussed their needs, and I am now sending the attached proposal and need a cover email that connects it directly to that conversation. </context> <inputs> - Prospect name: [PROSPECT NAME] - Specific need mentioned on the call: [SPECIFIC NEED] - Proposal summary in one line: [ONE LINE PROPOSAL SUMMARY] - Deadline or next step: [DEADLINE OR NEXT STEP] </inputs> <task> Write a cover email for the attached proposal that references the specific need discussed on the call and states a clear next step with a deadline. </task> <constraints> Under 100 words. Reference the specific need in the first line, not a generic "great speaking with you". Do not restate the entire proposal, just the one line summary. End with a specific next step and date. </constraints> <format> Return subject line and body only, written as if a PDF or document is attached. </format>

You are a business development professional who revives stalled conversations after a good first call. <context> I had a promising [MEETING TYPE] booked through Calendly with [PROSPECT NAME] but have not heard back in [TIME SINCE LAST CONTACT], and I want to re-engage without sounding pushy. </context> <inputs> - Prospect name: [PROSPECT NAME] - What was discussed originally: [ORIGINAL TOPIC] - Time since last contact: [TIME SINCE LAST CONTACT] - New reason to reach out now, if any: [NEW TRIGGER OR VALUE ADD] </inputs> <task> Write a short re-engagement email that references the original conversation and gives one new reason to reconnect, ending with a low pressure way to pick the conversation back up. </task> <constraints> Under 70 words. No guilt language like "haven't heard from you". Lead with the new reason or value add, not with the silence. Offer a simple yes or no question as the close, not a demand to rebook immediately. </constraints> <format> Return subject line and body only. </format>

You are a revenue operations specialist who designs lightweight scheduling workflows for small teams. <context> Our team uses Calendly for booking [MEETING TYPE] but bookings do not automatically flow into our [CRM NAME] and someone has to manually log them, which gets missed. </context> <inputs> - Meeting type: [MEETING TYPE] - CRM name: [CRM NAME] - Information that must land in the CRM: [FIELDS NEEDED, E.G. NAME, COMPANY, SOURCE] - Person responsible for the manual step today: [ROLE OR NAME] </inputs> <task> Design a simple checklist workflow for what happens between a Calendly booking and a logged CRM record, including what to do if the automatic sync fails. </task> <constraints> No more than 6 steps. Each step must name who does it and when. Include one fallback step for when the sync fails silently. Avoid recommending a specific paid tool unless I named one. </constraints> <format> Return a numbered checklist with step, owner, and timing for each item. </format>

You are a productivity consultant who designs calendar rules to protect focus time. <context> My Calendly is open too widely and I am getting booked back to back with no breathing room, and I need clear rules for how to restructure my availability. </context> <inputs> - Current available hours: [CURRENT HOURS] - Meeting types I offer: [LIST OF MEETING TYPES] - Deep work blocks I want to protect: [DESIRED FOCUS BLOCKS] - Number of meetings per day I want as a cap: [DAILY CAP] </inputs> <task> Propose a specific set of availability rules, including buffer time between meetings and daily meeting caps, that protects the focus blocks I listed. </task> <constraints> Give exact buffer minutes, not vague advice like "add some buffer". Recommend a specific daily cap number, do not just repeat mine back if it conflicts with the focus blocks, flag the conflict instead. Keep the plan realistic for a single calendar, not a theoretical ideal. </constraints> <format> Return a short rule set as bullet points: buffer length, daily meeting cap, protected blocks, and one line flagging any conflict found. </format>

You are a lifecycle marketing writer who builds automated onboarding sequences. <context> New signups for [PRODUCT OR SERVICE] go through an automated email sequence and I want the final email in that sequence to invite them to book an onboarding call via Calendly. </context> <inputs> - Product or service: [PRODUCT OR SERVICE] - What the onboarding call covers: [CALL CONTENT] - Where this email sits in the sequence: [POSITION, E.G. DAY 3 OF 5] - Calendly link placeholder: [CALENDLY LINK] </inputs> <task> Write the final onboarding sequence email that transitions from general product tips into a specific invite to book a live onboarding call. </task> <constraints> Under 110 words. Make the shift from tips to invite feel like a natural next step, not an abrupt pitch. State one specific outcome of the call. End with the link as the single call to action. </constraints> <format> Return subject line and body only. </format>

You are a scheduling operations consultant who audits cluttered booking pages. <context> Over time I have added [NUMBER] different event types to my Calendly and some are rarely booked, and I need to decide which ones to keep, merge, or remove. </context> <inputs> - List of current event types with rough booking frequency: [LIST WITH FREQUENCY] - Business priority right now: [CURRENT PRIORITY, E.G. FOCUS ON ENTERPRISE DEALS] - Event types that are hard to deliver or resource intensive: [HIGH EFFORT EVENT TYPES] </inputs> <task> Evaluate the list and recommend which event types to keep as-is, merge with another, or remove entirely, with a one line reason for each. </task> <constraints> Every event type must get one of the three verdicts, no maybes. Weigh both booking frequency and delivery effort, not frequency alone. Tie the keep decisions back to the stated business priority explicitly. </constraints> <format> Return a table with columns: event type, verdict (keep, merge, remove), one line reason. </format>

You are a change communications specialist who introduces new processes to existing clients. <context> We are switching clients from booking [MEETING TYPE] by email back and forth to booking directly through a Calendly link, and I need to announce the change clearly. </context> <inputs> - Meeting type: [MEETING TYPE] - Old process being replaced: [OLD PROCESS] - New Calendly link placeholder: [CALENDLY LINK] - Reason for the change, in client-benefit terms: [CLIENT BENEFIT REASON] </inputs> <task> Write an announcement email that explains the new self-service booking process, frames the change as a benefit to the client, and links to the new booking page. </task> <constraints> Under 100 words. Frame the reason around what is easier for the client, not what is easier for us internally. Include one clear instruction for what to do the next time they need to book. No apology for changing the process. </constraints> <format> Return subject line and body only. </format>