- A well-built OpenClaw personal assistant saves 90–120 minutes per day by handling email drafting, scheduling, document summarisation, and research on demand
- Telegram is the recommended channel — fast, supports file uploads, and available on every device you already carry
- The morning briefing workflow runs automatically each day, delivering your calendar, priority emails, and task list before you've had coffee
- Shared memory stores your preferences, writing style, and project context — so the assistant never needs re-briefing
- Voice note transcription lets you capture ideas hands-free and have them processed, summarised, and filed automatically
The average knowledge worker loses 2.5 hours per day to tasks an AI agent could handle — email triage, meeting prep, document summarisation, and scheduling back-and-forths. That's 12+ hours per week. An OpenClaw personal assistant running on Telegram gets that time back without hiring anyone, paying a SaaS subscription, or switching tools. Here's exactly how to build one that you'll actually rely on.
What a Real Personal Assistant Actually Does
The mistake most people make when building a personal AI assistant is building a chatbot. A chatbot waits for questions. A personal assistant anticipates needs, takes initiative, and handles routine tasks without being asked each time.
The difference is architecture. A chatbot is a single agent with no memory, no scheduled tasks, and no integrations. A proper OpenClaw personal assistant is a small system: a conversational agent for on-demand requests, a scheduler for proactive tasks, and shared memory that keeps context across every interaction.
Here's what the difference looks like in practice. A chatbot requires you to type "summarise my emails." A personal assistant delivers a summary of your priority emails every morning at 8 AM without being asked. That's the bar to aim for.
Don't build every feature at once. Identify the single task that costs you the most time each day — usually email drafting or meeting prep — and perfect the assistant for that task first. Once it's reliable, add the next capability. Incremental builds produce assistants people actually use.
Core Skills to Install
A personal assistant needs integrations. Install these skills from the ClaWHub Marketplace in order of priority:
- openclaw-google-calendar — reads and creates calendar events, checks availability, sends invites
- openclaw-gmail — reads, drafts, and sends emails in your Gmail account
- openclaw-web-search — researches topics on demand using your configured search API
- openclaw-document-reader — summarises PDFs, Google Docs, and uploaded files
- openclaw-voice-transcription — converts voice notes to text for processing
- openclaw-reminders — sets time-based reminders that ping you in your messaging channel
Install each skill and verify it appears in your skill list before configuring the next one. A failed skill installation produces no error by default — always confirm with openclaw skill list.
# Install all personal assistant skills
openclaw skill install google-calendar gmail web-search \
document-reader voice-transcription reminders
# Authenticate Google integrations
openclaw skill auth google-calendar
openclaw skill auth gmailGoogle OAuth tokens expire after 7 days if not refreshed. Set up token auto-refresh in your skill config with auto_refresh: true. Without this, your assistant will silently fail to access calendar and email after a week — a confusing failure mode that trips up most first-time builders.
Prompt Engineering for a Personal Assistant
The system prompt for a personal assistant needs to capture your identity, preferences, and working style. Generic prompts produce generic assistance. Specific prompts produce a genuinely useful assistant.
Here's a proven prompt structure:
You are my personal AI assistant. You know me well:
- My name is [Name], I work in [Role] at [Company]
- My timezone is [TZ], working hours are 8 AM to 6 PM
- Writing style: direct, concise, no filler phrases
- Email tone: professional but warm, not corporate-formal
- Current priorities: [Project A], [Project B], [Project C]
When drafting emails:
- Match my writing style exactly
- Keep replies under 150 words unless complexity demands more
- Never start with "I hope this email finds you well"
When scheduling:
- Block 90-minute deep work windows in the morning
- Avoid meetings before 10 AM when possible
- Leave 15-minute buffers between back-to-back meetings
Always confirm before sending emails or creating calendar events.
Ask clarifying questions if the request is ambiguous.The last two lines are critical. A personal assistant that acts without confirmation is a liability. Always require explicit approval before sending anything or making calendar changes — especially in early deployment when you're still calibrating the prompt.
The Morning Briefing Workflow
This is the highest-value workflow for any personal assistant. It runs automatically every morning and delivers a structured briefing to your Telegram channel before you start work.
workflow:
name: morning-briefing
trigger:
type: cron
expression: "0 7 * * 1-5" # 7 AM, weekdays
steps:
- id: fetch-calendar
agent: pa-agent
input:
task: "List today's calendar events with times and attendees"
output:
memory_key: today_calendar
- id: fetch-emails
agent: pa-agent
input:
task: "Summarise the 5 most important unread emails from the last 12 hours"
output:
memory_key: priority_emails
- id: compile-briefing
agent: pa-agent
depends_on: [fetch-calendar, fetch-emails]
input:
calendar: "{{memory.today_calendar}}"
emails: "{{memory.priority_emails}}"
task: "Create a concise morning briefing covering today's schedule and priority emails"
channel: telegram-personalThe fetch-calendar and fetch-emails steps run in parallel — no depends_on means they start simultaneously. The compile step waits for both, then delivers the briefing. Total workflow time is about 45 seconds from trigger to your Telegram channel.
Memory and Context Management
This is where most personal assistant builds fall short. Without persistent memory, your assistant forgets everything the moment the conversation ends. With it, the assistant accumulates context that makes it genuinely more useful over time.
OpenClaw shared memory is the mechanism. Store these categories of information as named memory keys:
- preferences — your writing style, scheduling rules, communication preferences
- active_projects — current project names, goals, key stakeholders, deadlines
- contacts — important contact details and relationship context ("Sarah Chen = VP at Acme, warm relationship")
- ongoing_tasks — tasks that persist across sessions, updated as you complete them
- decisions_log — recent decisions and their rationale, useful for consistency in long-running projects
Update memory keys through conversation. Say "Remember that the Q1 deadline moved to March 15" and the assistant writes that to the active_projects memory key immediately. You never need to re-brief.
Common Personal Assistant Mistakes
- No confirmation gates on actions — an assistant that sends emails without asking first will eventually send something embarrassing. Always require confirmation before any external action in the first 30 days of deployment.
- Vague system prompt — "be helpful" is not a system prompt. The more specific your prompt, the more useful the assistant. Include your actual writing style, scheduling preferences, and current priorities — not generic instructions.
- No memory update workflow — if you don't actively update shared memory when priorities change, the assistant operates on stale context. Build a habit of telling the assistant about major changes, or set a weekly memory review reminder.
- Using GPT-4 for all tasks — most personal assistant tasks (email drafting, scheduling, summarisation) don't need a frontier model. GPT-4o-mini or Claude Haiku is faster and costs 20x less. Save the expensive model for complex research or analysis tasks.
- One agent for everything — a single agent handling email, calendar, research, and task management becomes unfocused. Split into specialised agents: one for communication, one for scheduling, one for research. Each performs its specialty better.
Frequently Asked Questions
What can an OpenClaw personal assistant actually do?
An OpenClaw personal assistant can draft and send emails, manage calendar events, summarise documents and meeting notes, research topics on demand, set reminders, track tasks, answer questions from your personal knowledge base, and coordinate with other agents — all through a conversational interface on Telegram or WhatsApp.
Which messaging channel works best for a personal assistant?
Telegram is the most popular channel for personal assistant deployments — it's fast, supports rich formatting, and allows file uploads for document processing. WhatsApp works well if you prefer a channel you already use daily. Both support the full feature set. Use whichever app you already have on your phone.
Can the personal assistant access my Google Calendar?
Yes. Install the openclaw-google-calendar skill and authenticate with your Google account. The assistant can then read upcoming events, create new events, reschedule meetings, and send invitations — all through natural language commands in your messaging channel of choice.
How do I keep my personal assistant's context fresh?
Use OpenClaw's shared memory to store your preferences, ongoing projects, and important context. Update these memory keys whenever your situation changes. A morning briefing workflow that runs daily can also refresh memory with your current calendar, unread messages, and priority tasks each morning.
Is my data private when using an OpenClaw personal assistant?
Your data stays on your own infrastructure — OpenClaw is self-hosted. Messages pass through your gateway to your chosen LLM provider. If privacy is a priority, use a local model like Ollama so data never leaves your machine. Gateway logs can be disabled entirely in gateway.yaml for maximum privacy.
Can the personal assistant handle voice notes from my phone?
Yes. Send a voice note to your assistant's Telegram channel and the voice transcription skill automatically converts it to text before the agent processes it. This is useful for capturing ideas while commuting — send a voice note, and the assistant transcribes, summarises, and adds action items to your task list.
M. Kim has designed personal AI assistant systems for founders, executives, and high-output individual contributors across technology and finance. Focuses on the intersection of productivity workflows and AI agent design within the OpenClaw ecosystem.