Poke is a consumer AI assistant designed to live inside messaging rather than a separate chatbot workspace. Its official documentation currently lists Apple Messages, Telegram, WhatsApp and RCS. A user can send text or voice messages, request reminders, connect services and install “Recipes” that package repeatable tasks. The product’s central advantage is low interaction cost: delegating something feels like texting a contact.
That convenience is also the main evaluation risk. A friendly conversation can obscure the difference between drafting a suggestion, reading connected data and taking an external action. Poke should be judged task by task: what information it receives, which account can be changed, whether confirmation is required, how failure is surfaced and whether the user can reverse the result.
What the messaging-first design changes
| Design choice | Practical benefit | Hidden cost to check |
|---|---|---|
| Lives in messaging | No new interface to learn; easy follow-up | Important permissions can feel as casual as ordinary chat |
| Proactive reminders | Information arrives at the useful moment | Notification fatigue, incorrect timing and sensitive previews |
| Connected accounts | Can act with personal context | Broader data exposure and external side effects |
| Recipes | Reusable automation without building a workflow | Recipe behavior, publisher and permissions may change |
| Text and voice input | Fast capture while mobile | Ambiguity, transcription errors and bystander privacy |
| Model routing | Service can select a model for the task | Users may not know which provider receives particular content |
A hand-drawn trust map
you | | text / voice / photo v [messaging network] ---> notification preview | v [Poke service + memory] ---> [selected AI model] | | | '--------> logs / support / safety systems v [Recipe or integration] | +--> calendar / email / health / smart home / other account Read context ≠ permission to write Draft action ≠ confirmed action
This map is a useful pre-connection checklist. Data can cross the messaging provider, Poke, an underlying model provider and the destination integration. The exact path can vary by feature and region. Review the current privacy notice and the permission screen shown during connection instead of assuming one policy covers every participant.
Recipes are installable authority
Official and launch materials describe Recipes across productivity, scheduling, travel, health, finance, home, school and developer use. Treat a Recipe like a small application, not merely a prompt. Before enabling one, identify its author, inputs, connected services, schedule, destinations, write permissions and stop condition.
| Recipe type | Low-risk trial | Escalation boundary |
|---|---|---|
| Weather or commute | Send a morning summary for one city | Do not expose precise location unless needed |
| Calendar | Read today’s events and draft a plan | Confirm before creating, moving or inviting |
| Summarize messages from an allowlist | Review recipient and body before sending | |
| Health reminder | Non-clinical habit prompt | Never rely on it for diagnosis or time-critical medication safety |
| Travel | Research options and constraints | Confirm traveler data, cancellation terms and payment |
| Smart home | Read device status | Exclude locks, alarms, ovens and safety-critical controls initially |
| Finance | Summarize public market or budget information | No transfer, trade, filing or binding purchase without independent review |
The confirmation ladder
A trustworthy assistant should increase friction as consequence rises. “Tell me tomorrow’s weather” may run immediately. “Move my meeting” should show the event and new time. “Buy this flight” should show traveler, itinerary, total price, refund rules and payment source, then require a fresh confirmation that expires if anything changes.
- Inform: answer or summarize without changing an external system.
- Draft: prepare a message, event or plan but keep it private.
- Preview: resolve exact arguments and show the intended action.
- Confirm: obtain an explicit approval bound to those arguments.
- Execute: perform the operation once with duplicate prevention.
- Receipt: report the authoritative result and reversal path.
Do not accept “go ahead with whatever works” for high-consequence work. If a price, recipient, location, time or scope changes, the approval should be invalidated. A message saying “done” is not evidence; the calendar, merchant or other system of record is.
Privacy and training terms deserve a deliberate choice
Poke’s Terms of Service, last modified March 17, 2026 when reviewed, grant broad rights needed to operate and improve the service and explicitly mention business purposes that can include training third-party AI and large language models underlying the service. Legal language and privacy choices can change, so read the current terms and privacy notice in full before sending confidential, regulated or third-party data.
Use data minimization even when a feature is convenient. Redact account numbers, medical details, private addresses, authentication codes and confidential work material. Do not paste passwords or API keys. Consider whether a message participant has consented before asking Poke to analyze their email, image, recording or personal information. Review account deletion and integration revocation from settings, then verify that connected providers also show the authorization as removed.
| Data class | Safer handling | Why |
|---|---|---|
| One-time codes/passwords | Never send | They can directly authorize account access |
| Government/financial IDs | Keep outside ordinary assistant chat | Identity theft and compliance impact |
| Health information | Use only when necessary and verify policy/feature scope | Highly sensitive and easy to misinterpret |
| Work documents | Follow employer policy; remove customer and secret data | Personal account terms may not satisfy enterprise obligations |
| Calendar/email | Connect least-privilege account or limited scope | Both reveal relationships, location and behavior |
| Photos/voice | Check background and bystander content | Uploads can expose people who did not choose the service |
Reliability tests that reveal more than a demo
Create a small benchmark of repeated tasks. Run each ten times with variations in date phrasing, time zone, names and partial information. Record whether Poke asks a clarifying question, uses the right account, avoids duplicate actions, cites current data and reports uncertainty. Repeat after major product changes because model routing and integrations can change without a new messaging interface.
- “Remind me next Friday at 8” while travelling across time zones.
- Two contacts with similar names and different organizations.
- A calendar request whose proposed time conflicts with another event.
- A follow-up such as “move it one hour” after several topics intervene.
- A duplicate inbound message or delayed network delivery.
- An instruction copied from a web page that tries to override the user.
- An integration that returns a partial failure after the action happened.
Where proactive behavior helps—and where it becomes noise
Proactivity is valuable when timing is predictable, the signal is specific and the action is reversible: a weather-based clothing reminder, a departure alert based on a known event, or a weekly summary. It is less useful when the assistant guesses emotional needs, repeatedly surfaces weak recommendations, or acts on stale context.
Every recurring Recipe should have an understandable trigger, quiet hours, frequency limit and one-message disable path. Review active automations monthly. Delete obsolete memories and connections, especially after travel, a job change or completion of a temporary project.
Channel availability is not uniform
The official docs currently name Apple Messages, Telegram, WhatsApp and RCS. Launch reporting also discussed SMS and regional constraints on WhatsApp access. Availability, business-messaging rules and feature depth can differ by country, carrier and platform. Verify the channel offered to your actual phone number; do not infer worldwide availability from a screenshot or another user’s setup.
Messaging delivery has its own failure modes: delayed messages, preview leakage on a lock screen, shared devices, recycled phone numbers and account takeover. Protect the messaging account with the strongest available authentication, hide sensitive previews, and establish how Poke handles a changed number or lost device.
Independent comparison matrix
| Option | Best fit | Advantage | Tradeoff |
|---|---|---|---|
| Poke | Consumers wanting proactive delegation inside messaging | Low-friction channel plus Recipes | Hosted service sees personal context and integration authority |
| ChatGPT tasks/agent features | Users already working in ChatGPT | Broad research and creation surface | Different channel and feature availability |
| Gemini / Gemini Spark | Users centered on Google services | Potentially deeper first-party ecosystem context | Google ecosystem and regional rollout dependence |
| Siri + Shortcuts | Apple-device automation with explicit workflows | Operating-system integration and deterministic shortcuts | Less flexible open-ended delegation |
| OpenClaw | Technical users prioritizing self-hosting and extensibility | More infrastructure control | Installation, security and maintenance burden |
| Calendar/task automation | Stable recurring rules | Predictable, auditable and often cheaper | Limited natural-language flexibility |
A safe two-week trial
Days 1–3: use only public-information questions, reminders and drafts. Test corrections, time zones and message deletion. Days 4–7: connect one low-sensitivity service with the narrowest available permission; keep all writes confirmation-gated. Week 2: enable one recurring Recipe and compare it with the manual workflow.
Track successful outcomes, false or mistimed notifications, clarifying questions, manual correction minutes, actions requiring reversal and information you regretted sharing. Continue only if it saves net time without encouraging broader permissions than the task deserves.
Frequently asked questions
Do I need to install an app?
The core experience is delivered through supported messaging channels. Current setup and any companion-app requirements should be checked on the official site for your device and region.
Which messaging services are supported?
Poke’s documentation currently lists Apple Messages, Telegram, WhatsApp and RCS. Regional and account availability can vary.
What is a Recipe?
It is a reusable Poke capability or automation. Evaluate it like an installed app: inspect inputs, accounts, schedule, outputs and permissions.
Should I connect email and calendar immediately?
No. Begin with read-only or low-sensitivity tasks, connect one service at a time and test confirmation and revocation behavior.
Can Poke make medical or financial decisions?
Do not use a general-purpose assistant as an accountable medical, legal or financial professional. Verify important information with authoritative sources and qualified people.
How do I delete my account?
The current FAQ directs users to the privacy section of Poke settings and a Delete Account control. Also revoke connected services and check their authorization pages.
Is Poke the same as OpenClaw?
No. Both can use messaging as an interface, but Poke is a hosted consumer service, while OpenClaw is an open-source system requiring technical setup and operational ownership.
Sources reviewed
- Poke official site
- Poke official documentation
- Poke official FAQ and account guidance
- Poke Privacy Notice
- Poke Terms of Service
- TechCrunch launch reporting and company interview
- Apple guidance for controlling app access to personal information
- FTC text-message safety guidance
Last reviewed July 25, 2026. Channel support, Recipes, integrations, pricing and policies can change quickly; confirm the live product and terms before connecting accounts or relying on an automation.
