Back to Play 1 Resources
Play 1: Hands-Free CRM

Calendar Logging Prompt Library

Tested prompts for past-event logging and future-event task creation.

Calendar Logging Prompt Library

Your billable hours depend on accurate time records. Your client relationships depend on documented interactions. Your malpractice insurance depends on proof of what was discussed and when.

Manual calendar logging fails because it happens after the fact, when details are fuzzy and you're already on to the next thing. AI-powered logging works because it captures context in real-time, structures it consistently, and pushes it directly into your CRM

or practice management system.

This library contains copy-paste-ready prompts for two critical workflows: logging past interactions and creating future tasks. Each prompt is designed for voice input (via mobile) or text input (via desktop), and assumes integration with tools like Zapier, Make, or native AI assistants (ChatGPT, Claude, Gemini).

System Prompt for Calendar Logging Assistant

Before using the individual prompts below, configure your AI assistant with this system prompt. This ensures consistent output formatting and proper data capture.

You are a calendar logging assistant for a professional services firm. Your job is to extract structured data from voice or text input and format it for CRM entry.

When the user describes a past event, output:
- Event Type (Meeting, Call, Email)
- Client Name
- Date and Time
- Duration
- Participants (comma-separated)
- Key Discussion Points (bullet list, 3-5 items)
- Action Items (bullet list, with owner names)
- Next Steps (bullet list)

When the user describes a future task, output:
- Task Type (Follow-up, Delegation, Time Block)
- Assignee Name
- Due Date and Time
- Task Description (1-2 sentences)
- Priority (High, Medium, Low)
- Context (any relevant background)

Always ask clarifying questions if critical fields are missing. Default to today's date if no date is specified. Use 24-hour time format.

Logging Past Events

Logging a Client Meeting

Use this prompt immediately after a client meeting, while details are fresh. Speak it into your phone or type it into your AI assistant.

Basic Version (Voice-Friendly):

Log meeting with [Client Name]. Attendees were [Name 1], [Name 2], and me. We discussed [Topic 1], [Topic 2], and [Topic 3]. I need to follow up on [Action 1] by [Date]. They're handling [Action 2].

Example:

Log meeting with Acme Corp. Attendees were Sarah Chen, Mike Rodriguez, and me. We discussed Q1 audit timeline, new revenue recognition standard implementation, and staffing for the March close. I need to send them the updated engagement letter by Friday. They're handling the preliminary journal entry review.

Detailed Version (Desktop Entry):

Log client meeting:
Client: [Client Name]
Date: [Date]
Location: [Office/Virtual/Client Site]
Duration: [X hours]
Attendees: [Name 1, Title], [Name 2, Title], [Your Name]

Discussion:
- [Specific topic with outcome]
- [Specific topic with outcome]
- [Specific topic with outcome]

Decisions Made:
- [Decision 1]
- [Decision 2]

Action Items:
- [Task] - Owner: [Name] - Due: [Date]
- [Task] - Owner: [Name] - Due: [Date]

Concerns Raised:
- [Concern 1]
- [Concern 2]

Next Meeting: [Date and purpose]

Example:

Log client meeting:
Client: Acme Corp
Date: January 15, 2024
Location: Client site, downtown office
Duration: 90 minutes
Attendees: Sarah Chen (CFO), Mike Rodriguez (Controller), Jane Smith (Partner)

Discussion:
- Q1 audit will start March 1, fieldwork complete by March 22
- New ASC 606 implementation requires restatement of 2023 comparatives
- Client is short-staffed in accounting, may need our advisory team for close support

Decisions Made:
- Approved budget increase for advisory work (8 additional hours)
- Agreed to weekly status calls during fieldwork

Action Items:
- Send updated engagement letter with revised scope - Owner: Jane Smith - Due: January 19
- Provide ASC 606 restatement template - Owner: Mike Rodriguez - Due: January 22
- Schedule kickoff call with audit team - Owner: Sarah Chen - Due: January 26

Concerns Raised:
- Turnover in client's accounting department may delay PBC list delivery
- New ERP system went live in December, data extraction issues possible

Next Meeting: February 1, pre-audit planning call

Logging a Phone Call

Phone calls are harder to reconstruct later because there's no email trail. Log them immediately.

Voice-Optimized Prompt:

Log call with [Client Name] about [Topic]. Call lasted [X minutes]. Main points: [Point 1], [Point 2], [Point 3]. I'm following up with [Action].

Example:

Log call with David Park at Northstar LLC about their 2023 K-1 deadline. Call lasted 15 minutes. Main points: they need K-1s by February 10 for a partner's mortgage application, two partners have complex passive activity loss carryforwards, one partner sold their interest mid-year. I'm following up with a draft timeline tomorrow.

Structured Version:

Log phone call:
Client: [Client Name]
Contact: [Specific person]
Date: [Date]
Time: [Start time] to [End time]
Initiated by: [Client/Us]

Call Purpose: [One sentence]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Client Requests:
- [Request 1]
- [Request 2]

Our Commitments:
- [Commitment 1] by [Date]
- [Commitment 2] by [Date]

Follow-up Required: [Yes/No - specify]

Logging an Email Exchange

Use this for email threads that contain decisions, approvals, or scope changes. Don't log routine correspondence.

Quick Version:

Log email thread with [Client Name] re: [Subject]. Key outcome: [Outcome]. Action: [What you're doing next].

Example:

Log email thread with Jennifer Wu at Catalyst Partners re: audit fee dispute. Key outcome: client accepted revised fee of $47K (down from $52K) in exchange for limiting scope on subsidiary testing. Action: sending revised engagement letter today.

Detailed Version:

Log email exchange:
Client: [Client Name]
Subject: [Email subject line]
Date Range: [Start date] to [End date]
Participants: [Name 1], [Name 2], [Name 3]

Thread Summary: [2-3 sentence overview]

Key Points:
- [Point 1]
- [Point 2]
- [Point 3]

Agreements Reached:
- [Agreement 1]
- [Agreement 2]

Open Issues:
- [Issue 1]
- [Issue 2]

Next Steps:
- [Step 1] - Owner: [Name] - Due: [Date]
- [Step 2] - Owner: [Name] - Due: [Date]

Creating Future Tasks

Scheduling a Follow-Up

Use this to create calendar holds for future client interactions.

Voice Prompt:

Schedule follow-up with [Client Name] on [Date] at [Time] to discuss [Topic]. Invite [Name 1] and [Name 2].

Example:

Schedule follow-up with Acme Corp on February 1 at 10 AM to discuss audit planning. Invite Sarah Chen and Mike Rodriguez.

Detailed Prompt:

Schedule follow-up:
Client: [Client Name]
Date: [Date]
Time: [Time]
Duration: [X minutes/hours]
Format: [In-person/Video/Phone]

Purpose: [One sentence objective]

Attendees:
- [Name 1, Title]
- [Name 2, Title]
- [Your team members]

Agenda:
1. [Agenda item 1] - [X minutes]
2. [Agenda item 2] - [X minutes]
3. [Agenda item 3] - [X minutes]

Pre-work Required:
- [Task 1] - Owner: [Name]
- [Task 2] - Owner: [Name]

Materials to Prepare:
- [Material 1]
- [Material 2]

Delegating a Task

Use this to assign work to team members and create accountability.

Quick Delegation:

Assign to [Name]: [Task description]. Due [Date]. Priority: [High/Medium/Low]. Context: [One sentence background].

Example:

Assign to Marcus: Pull 2023 depreciation schedules for Acme Corp audit. Due January 25. Priority: High. Context: Client's fixed asset system crashed, we need to recreate from source documents.

Formal Delegation:

Delegate task:
Assignee: [Name]
Task: [Clear, specific description]
Due Date: [Date]
Priority: [High/Medium/Low]
Estimated Hours: [X hours]

Background:
[2-3 sentences explaining why this task exists and what it's connected to]

Deliverable:
[Exactly what you expect to receive]

Resources:
- [Resource 1]
- [Resource 2]

Questions/Blockers:
[Any known issues or dependencies]

Check-in: [Date for status update]

Blocking Time for Focused Work

Use this to protect time for deep work, proposal writing, or technical research.

Simple Block:

Block [Duration] on [Date] for [Purpose]. Mark as busy, no meetings.

Example:

Block 3 hours on January 18 for drafting Northstar LLC tax planning memo. Mark as busy, no meetings.

Structured Block:

Block focused time:
Date: [Date]
Time: [Start] to [End]
Purpose: [Specific deliverable or outcome]

What I'm Working On:
[Specific task or project]

Success Criteria:
[What "done" looks like by end of block]

Materials Needed:
- [Material 1]
- [Material 2]

Do Not Disturb: [Yes/No]
Location: [Office/Home/Off-site]

Integration Notes

These prompts work best when connected to your practice management system. Common integration paths:

Zapier: Use the "New Message in ChatGPT" trigger to parse prompts and create events in Clio, MyCase, or Practice Panther.

Make: Build a scenario that watches for calendar logging keywords in Slack or email, extracts structured data, and writes to your CRM

.

Native AI Assistants: Configure ChatGPT, Claude, or Gemini with the system prompt above, then use voice input on mobile to log events hands-free.

Microsoft Power Automate: Connect Outlook calendar to your AI assistant, auto-generate summaries of past meetings, and push them to Dynamics 365 or custom databases.

The goal is zero manual data entry. Speak the prompt, let the AI structure it, let automation push it to your system of record.

Revenue Institute

Reviewed by Revenue Institute

This guide is actively maintained and reviewed by the implementation experts at Revenue Institute. As the creators of The AI Workforce Playbook, we test and deploy these exact frameworks for professional services firms scaling without new headcount.

Revenue Institute

Need help turning this guide into reality? Revenue Institute builds and implements the AI workforce for professional services firms.

RevenueInstitute.com