# Plan consultation reminders and rebooking Canonical page: https://agents.paretoid.com/workflows/plan-consultation-reminders-and-rebooking/ Category: Intake & Booking Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use. Jurisdiction/provider scope: Draft a reminder plan that respects consent, rescheduling, cancellations, and staff-confirmed no-shows. Status: Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified. Verification: Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result. ## The problem Draft a reminder plan that respects consent, rescheduling, cancellations, and staff-confirmed no-shows. Why it matters: Missed consultations leave time unused, while stale reminders can confuse people who cancelled or rescheduled. A reviewed reminder plan makes the consent, timing, and stop conditions explicit. ## Sources and evidence - pain: [Pain evidence: Public discussion](https://www.reddit.com/r/LawFirm/comments/1ic7okg/no_shows_for_initial_consultations/) original post 2025-01-28. A solo reports four of the last five free 15-minute Zoom consultations did not attend despite confirmation and a 24-hour reminder. Older first-person evidence. - method: [Method: Calendly reminder workflows](https://calendly.com/learn/calendly-workflows) Calendly describes reminder and no-show rebooking templates. Verify the account plan and current cancellation, rescheduling, and trigger behavior before configuration. - method: [Method: Calendly reminder workflows · supporting guide 2](https://community.calendly.com/featured-tips-tricks-32/new-for-workflows-follow-up-with-no-shows-4149) Additional official capability reference. The complete adapted recipe has not been tested. Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. ## Suggested approach Start when: Approved consultation booking / staff marks no-show 1. schedule neutral reminders, suppress obsolete messages after cancel/reschedule, and prepare one rebooking invitation 2. Keep source references and report unknowns instead of filling gaps. 3. The responsible reviewer checks the report before any separately approved action. ## What you need - 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. - Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details. ## How to use Documentation-verified component path; proposed adaptation, not tested - 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. Access and setup: - Actual account access, source versions/completeness, privacy approval and reviewer sign-off were not observed. ### 1. Read the real booking and Automation settings Tool: Calendly Location: Scheduling > select Event Type > More options > Notifications and automations; Calendar > select meeting > Timeline 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. Next step: Copy only the approved non-sensitive configuration and alias-based examples into a review-input TXT. Check before continuing: 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. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step 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 ### 2. Load only the approved AI input Tool: Acrobat PDF Spaces Location: Acrobat homepage > PDF Spaces > Create a PDF Space > upload files or Paste copied text > Add to PDF Space 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. Next step: Use the AI Assistant message field in this same space for the next prompt. Check before continuing: 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. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step 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 ### 3. Run the bounded prompt and inspect citations Tool: Acrobat AI Assistant Location: The PDF Space AI Assistant message field 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. Prompt: ```text 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. Next step: Save the checked draft as consult-reminder-plan.docx; carry source IDs, versions and reviewer corrections into the next review step. Check before continuing: Confirm every trigger exists and all timing/channel decisions were approved; no implicit recurring outreach. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://helpx.adobe.com/acrobat/desktop/use-acrobat-ai/generative-ai-features/ai-get-answers.html ### 4. Prepare the exact native setup handoff Tool: Human Calendly owner Location: Automations > Create your own automation > When this happens / Do this; or approved template > Use automation 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. Next step: Owner reviews the specification and synthetic cases before any separately authorized implementation. Check before continuing: 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. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://calendly.com/help/how-to-create-an-automation https://calendly.com/help/automations-overview ### 5. Human review and final handoff Tool: Responsible staff reviewer and lawyer/process owner Location: Local reviewed report beside the frozen source set 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. Next step: This recipe ends before live configuration or communication. Check before continuing: All unresolved or unreadable evidence stays open. No inferred approval or external action follows from AI output. Execution status: Official public documentation checked 2026-10-15; no account, source-data acquisition, prompt run or end-to-end workflow was tested. Step documentation: https://calendly.com/help/how-to-view-your-automations ## What you will get reminder-plan.csv: booking_alias, trigger, channel, planned_time, suppression_condition, staff_gate, template_id; separate neutral draft messages ## Human review and limits No automatic no-show inference from silence, no sensitive matter descriptions in texts/calendar titles, no unapproved repeated marketing or fee changes. The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included. What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed. ## Original prepared-input schema appointments.csv: booking_alias, appointment_type, start_datetime, timezone, status, no_show_confirmed_by_staff contact-rules.csv: channel, consent_status, allowed_hours, max_followups; templates.txt: approved neutral wording and cancellation/rebooking rules Synthetic example input: ```text B1: future appointment with approved email consent B2: cancelled before reminder B3: staff-confirmed no-show with approved rebooking channel ``` Expected synthetic output: ```text B1: planned reminder B2: suppress reminder B3: one proposed rebooking invitation, no send ``` Failure check: No automatic no-show inference from silence, no sensitive matter descriptions in texts/calendar titles, no unapproved repeated marketing or fee changes. ## Starter files Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation. - [Download starter kit](https://agents.paretoid.com/assets/starter-kits/g04-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed. - [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/g04/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits - [Input template: appointments.csv](https://agents.paretoid.com/assets/starter-kits/g04/appointments.csv) — Header-only input template; preserve exact names and order - [Synthetic input: appointments.csv](https://agents.paretoid.com/assets/starter-kits/g04/appointments-example.csv) — Fabricated sample rows for an offline manual trial - [Input template: contact-rules.csv](https://agents.paretoid.com/assets/starter-kits/g04/contact-rules.csv) — Header-only input template; preserve exact names and order - [Synthetic input: contact-rules.csv](https://agents.paretoid.com/assets/starter-kits/g04/contact-rules-example.csv) — Fabricated sample rows for an offline manual trial - [Output template: reminder-plan.csv](https://agents.paretoid.com/assets/starter-kits/g04/reminder-plan.csv) — Header-only output template; preserve exact names and order - [Expected output: reminder-plan.csv](https://agents.paretoid.com/assets/starter-kits/g04/reminder-plan-example.csv) — Hand-authored synthetic expected result; not an executed workflow result - [Policy/input template: templates.txt](https://agents.paretoid.com/assets/starter-kits/g04/templates.txt) — Required source/policy preparation scaffold; not populated with firm instructions - [Synthetic policy/input: templates.txt](https://agents.paretoid.com/assets/starter-kits/g04/templates-example.txt) — Fixture-only context; not an approved production policy - [Draft scaffold: draft-messages.txt](https://agents.paretoid.com/assets/starter-kits/g04/draft-messages.txt) — Blank output scaffold; no message, form or appeal is sent - [Synthetic expected draft: draft-messages.txt](https://agents.paretoid.com/assets/starter-kits/g04/draft-messages-example.txt) — Hand-authored draft or blocked-output example for fixture review - [Synthetic fixture expectations](https://agents.paretoid.com/assets/starter-kits/g04/fixture-expectations.txt) — Acceptance targets and failure checks; no claim of workflow execution - [Review prompt](https://agents.paretoid.com/assets/starter-kits/g04/starter-prompt.txt) — Copyable offline review prompt; no executable automation - [Setup and prerequisites](https://agents.paretoid.com/assets/starter-kits/g04/README.txt) — Recipe-specific setup, evidence sources and usage boundaries ## Optional original prepared-input prompt Destination: Your firm-approved AI assistant · prepared files This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping. ```text Design a reminder and one-time no-show recovery workflow for this consultation type using our approved contact channels, times and wording. Include cancel/reschedule suppression, timezone handling and a manual no-show confirmation. Draft neutral messages containing only time, location/link and rebooking instructions. Do not imply representation or penalize the prospect. INPUTS appointments.csv: booking_alias, appointment_type, start_datetime, timezone, status, no_show_confirmed_by_staff contact-rules.csv: channel, consent_status, allowed_hours, max_followups; templates.txt: approved neutral wording and cancellation/rebooking rules OUTPUT reminder-plan.csv: booking_alias, trigger, channel, planned_time, suppression_condition, staff_gate, template_id; separate neutral draft messages Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. ``` Proposed / not tested · editorial prompt Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.