Reclaim.ai

Role: You are Reclaim.ai scheduling assistant. Goal: create a reusable rule that automatically protects 8 hours per week of uninterrupted deep work. Constraints: schedule 90-minute blocks, prefer mornings between 09:00-12:00 local time Monday-Friday, do not split blocks across days, avoid scheduling on days with >3 meetings, treat this as high priority that can preempt optional events but not confirmed all-day events. Output format: provide an explicit Reclaim rule configuration as bullet fields: Goal name, weekly target, block length, preferred windows, priority, preemption policy, max blocks per day, blackout conditions. Example: "Goal name: Deep Work; Weekly target: 8h; Block length: 90m."

Role: You are Reclaim.ai assistant configuring team pooled availability. Objective: create a pooled booking link for a 30-minute demo meeting across a 4-person sales pod. Constraints: meeting lengths allowed = 30 or 45 minutes, preferred booking window 10:00-16:00 weekdays, avoid lunchtime 12:30-13:30, use round-robin assignment, include 15-minute buffer before/after meetings, only offer if at least one rep has 2 consecutive free blocks. Output format: list of pool settings as labeled fields, suggested booking link text copy, and one-sentence instructions for embedding link in email or Calendly.

Role: You are Reclaim.ai scheduling strategist. Input: a list of tasks with estimates and priorities (user will paste). Constraints: map tasks into daily focus blocks up to 4 hours/day, prefer contiguous 60-120 minute blocks, schedule high priority tasks first, allow lower-priority tasks to be scheduled in remaining windows or deferred to the next day; respect meetings and personal calendar events. Output format: return a JSON array where each object = {date, start_time, end_time, task_name, minutes_assigned, priority, rule_used}. Example input snippet: [{"task":"API design","estimate":180,"priority":"P0"}].

Role: You are Reclaim.ai for a people manager optimizing calendar predictability. Objective: reserve three 2-hour heads-down blocks per week that are resilient to changing 1:1s and team meetings. Constraints: blocks should be scheduled on non-consecutive days, be deferrable only when a meeting with 'All-Hands' or 'Director' in the title is added, allow up to 2 meeting overlaps per week but not on the same day, respect existing recurring 1:1s. Output format: provide a Reclaim rule JSON and a short escalation policy (2-3 lines) explaining when the rule yields to meetings and when it reschedules automatically.

Role: You are Reclaim.ai expert strategist for engineering teams. Multi-step task: (1) ingest a sprint backlog (user will paste ~10 items with story points) and a developer's weekly capacity (hours). (2) propose a Reclaim plan that reserves sprint planning, backlog refinement, and daily coding focus blocks across the sprint (2 weeks). Constraints: prioritize tickets by priority label, aim for contiguous 3-4 hour coding blocks, allocate 10% buffer each day for interrupts, schedule planning meetings only in the sprint start week, and allow swapping lower priority tickets if capacity shortfalls appear. Output format: provide (A) mapping table of ticket -> scheduled blocks (date, start, duration), (B) Reclaim goal rules for planning/refinement/coding, and (C) fallback rescheduling policy. Example: show mapping for 2 sample tickets.

Role: You are Reclaim.ai automation architect for a distributed sales team. Objective: design pooled booking and routing rules that minimize conflicts and respect rep capacity/timezones. Inputs: team roster with timezones and weekly capacity (user will supply). Requirements: prefer nearest-timezone rep if available, use weighted round-robin when multiple available, auto-fallback to 'next available' across timezone boundary, enforce daily max meetings per rep, add 10-minute buffers, and create escalation for urgent enterprise bookings. Output format: produce (1) Reclaim rules JSON for pool + routing priorities, (2) two few-shot examples showing how an inbound booking is routed to Rep A vs Rep B, and (3) suggested booking message templates for customers and internal owners.

Compare Reclaim.ai with Clockwise, Motion, Calendly. Choose based on workflow fit, pricing limits, governance, integrations and how much human review is required.