Plan consultation reminders and rebooking Get the source data and prepare the review Documentation-verified component path; proposed adaptation, not tested WHAT WAS CHECKED Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Menus/features are vendor-documented; prompts, field maps and human gates are editorial adaptations. No actual client work, account login, installation, connection, external write or site edit occurred. BEFORE YOU START - Existing Calendly setup and permission to read the relevant event type/meeting history; approved timing, channel/consent and neutral wording policy. - Current Automations documentation lists Professional, Standard, Standard Plus, Teams, Teams Plus and Enterprise; team automation administration needs owner/admin permission. Exact account entitlement is untested. SMS is unavailable during trial and requires separate consent and setup. - Existing firm-approved Acrobat Studio, AI Assistant add-on, or another plan including Acrobat AI; online services/cloud storage, language and region must be permitted. No purchase, login or connection is part of this verification. The manual route works without AI. - Preserve original evidence unchanged in restricted storage. Use synthetic material first. Prepare a separate, explicitly approved minimized AI input; aliases alone do not anonymize narrative or attachments. Do not upload raw originals or an alias key merely because another tab/file is sanitized. DATA ACQUISITION LIMITS - Current UI uses Automations and Calendar; older pages/screenshots say Workflows and Meetings. Do not blindly follow the older labels. - Changing Automations affects future bookings; existing meetings may retain the settings from booking time. Cancellation/reschedule suppression, late-change races and delivery behavior need a separately authorized synthetic end-to-end test. - The output here is a configuration/message plan, not an activated recurring communication. No-show status must be confirmed by staff, never inferred from silence. WHEN THIS CAN RUN Blocked until actual sources, permissions and required human approvals are supplied; no real inputs were available in this verification. STEP 1: Read the real booking and Automation settings Tool: Calendly Open: Scheduling > select Event Type > More options > Notifications and automations; Calendar > select meeting > Timeline Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Manually capture event type ID/name alias, duration/timezone, currently assigned Automation triggers/timing/actions and neutral templates. From selected real meeting timelines record booked/rescheduled/cancelled/no-show evidence and observed Automation activity without changing it. Obtain channel/consent rules and approved follow-up limit from the owner. Expected output: Existing-setting snapshot, observed activity notes and approved communication policy. Use it next: Copy only the approved non-sensitive configuration and alias-based examples into a review-input TXT. Check: Timeline activity is evidence of a run, not proof a recipient read or received it. No-shows are visible in Calendar > meeting Details; do not mark one during this review. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://calendly.com/help/how-to-view-your-automations https://calendly.com/help/how-to-manage-your-meetings https://calendly.com/help/how-to-mark-no-shows-for-meetings STEP 2: Load only the approved AI input Tool: Acrobat PDF Spaces Open: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Add the current-setting snapshot, approved timing/channel/consent policy and sanitized sample state histories. Use clear source/version labels and verify the Files panel. Do not add originals that have not separately been cleared for Adobe processing. Expected output: Visible approved source set in the PDF Space; no account integration is implied. Use it next: Use the AI Assistant message field in this same space for the next prompt. Check: Confirm every named source is actually loaded and readable. PDF Spaces supports up to 100 files, 100 MB and 600 pages per file; unsupported/password-protected/handwritten material blocks affected extraction. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/create-pdf-spaces.html https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/supported-formats-limitations.html https://helpx.adobe.com/acrobat/desktop/explore-pdf-spaces/pdf-spaces-faq.html STEP 3: Run the bounded prompt and inspect citations Tool: Acrobat AI Assistant Open: The PDF Space AI Assistant message field Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Paste the prompt below. Open each source-number citation, check it, and use Copy to transfer the answer into a new local Word document or text file. Correct errors using the originals before reliance. PASTE THIS PROMPT Draft a review-only Calendly Automation plan from this supplied configuration and approved policy. For each reminder or one-time rebooking message return event_type,documented trigger,timing,channel,consent prerequisite,neutral draft text,cancel/reschedule handling requirement and test case. Use only time, location/link and approved rebooking instructions. No-show follow-up requires a staff-confirmed no-show; stop after the approved one invitation. Distinguish verified configuration from required tests and unsupported behavior. Include future versus already-booked meeting settings, cancellation/reschedule races, timezone/DST and opt-out tests. Do not infer representation, penalize prospects, activate Automations, send messages, mark no-shows or connect accounts. Expected output: Draft reminder/rebooking plan, message copy and explicit setup/test blockers. Use it next: Save the checked draft as consult-reminder-plan.docx; carry source IDs, versions and reviewer corrections into the next review step. Check: Confirm every trigger exists and all timing/channel decisions were approved; no implicit recurring outreach. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html STEP 4: Prepare the exact native setup handoff Tool: Human Calendly owner Open: Automations > Create your own automation > When this happens / Do this; or approved template > Use automation Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Map each approved plan row to the documented trigger, action, event-type selection and message variables in a local setup checklist. The separate future operator would use Which event types will this apply to? and Edit under Do this. Stop before Save or applying to live event types until recurring recipients/purpose, wording and a synthetic test are approved. Expected output: Field-by-field setup specification; no account change. Use it next: Owner reviews the specification and synthetic cases before any separately authorized implementation. Check: A No-show marked Automation is available; ordinary post-meeting follow-ups exclude marked no-shows. Do not assume every cancellation race is covered without observing the test. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://calendly.com/help/how-to-create-an-automation https://calendly.com/help/automations-overview STEP 5: Human review and final handoff Tool: Responsible staff reviewer and lawyer/process owner Open: Local reviewed report beside the frozen source set Access needed: See recipe prerequisites; exact account entitlement and permissions not observed. Owner approves messages, recipient/consent scope, timing and tests. A later authorized pilot must inspect Calendar > selected test meeting > Timeline and actual recipient test inbox for the expected events before activation. Expected output: Approved plan or a blocked configuration question list. Use it next: This recipe ends before live configuration or communication. Check: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output. Documentation limit: Sources support named component capabilities. Capture fields, prompts and review requirements are the proposed adaptation, not promised native export columns. Source documentation: https://calendly.com/help/how-to-view-your-automations ACCOUNT AND SOURCE CHECKS STILL NEEDED - Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.