Poke vs. Deck: Messaging Assistant or Email Teammate?

Poke and Deck both put an assistant in a channel you already use. Poke lives in Apple Messages, WhatsApp, Telegram, and RCS. It can connect to email, calendars, reminders, and other services. Deck lives at its own email address and works from the threads, files, Projects, and read-only sources you choose.

The decision comes down to where you want to delegate and how much connected action you want your assistant to take.

We make Deck. Poke's details below come from its current documentation, release notes, and pricing page, checked July 15, 2026.

The short answer

Choose Poke when messaging is your natural command line. You can ask it to search or draft email, work with calendars, set reminders, use integrations, and run automations while staying in a text conversation.

Choose Deck when email is the shared surface for your work. Forward the source material, describe the deliverable, and receive it privately. Deck can create attached PowerPoint, Excel, Word, PDF, and CSV files as part of that handoff.

Poke vs. Deck at a glance

Question	Poke	Deck
Main channel	Apple Messages, WhatsApp, Telegram, and RCS	Any email provider or email app
Email access	Connects Google or Microsoft accounts to search, draft, and use supported email actions	Reads the threads and files you CC or forward
Calendar behavior	Can create and manage supported calendar events	Reads connected calendar context for approved tasks
Automations	Recipes, background automations, integrations, and an API	Plain-language scheduled tasks with one emailed result
Output	Messages, actions, and supported files such as PDFs	Email plus PowerPoint, Excel, Word, PDF, or CSV attachments
Best fit	Mobile messaging and connected actions	Review-first delegation and recurring deliverables

Where Poke is stronger

Poke is easier to reach when your phone is already in your hand. Its docs describe natural-language access through several messaging networks, with connected tools for email, calendars, reminders, web search, and integrations.

It also supports a wider action surface. Poke's release notes document Google and Microsoft email support, calendar-event management, recurring automations, integrations, and an API that can send programmatic messages to your assistant. That API can be useful for scripts, webhooks, and event-driven work.

Current pricing lists a free plan, Pro at $19 per month, and Ultra at $199 per month. All plans include the core product, with higher tiers adding more capable models, background automation headroom, and support. Check Poke pricing for the latest details.

Sources: Poke documentation, Poke release notes, and Poke API documentation.

Where Deck is stronger

Deck fits work whose context is already carried by email. A client thread, vendor request, candidate conversation, long attachment chain, or internal recap can be handed over by adding one address. You do not need to translate that context into a separate message conversation.

Deck's privacy boundary is also straightforward. It sees the emails and files you choose to send, plus optional Projects and read-only connections you enable, such as your Gmail inbox. Its response returns only to you, so you review every draft and deliverable before anyone else receives it.

The file workflow is broader. Deck can create an actual presentation, spreadsheet, document, PDF, or CSV and attach it to the response. This suits recurring management reports, client reporting, QBRs, board preparation, research, and analysis that needs a portable artifact.

Connected action or deliberate handoff

Poke connects to the services it manages. That connected reach enables direct email and calendar behavior, plus automations triggered through its recipes and API. Review the permissions and confirmation behavior for the services you enable.

Deck takes the material you share and completes the requested work around it. Its optional scheduled-task integrations are read-only. A run sends one email to you and does not write back to HubSpot, Notion, Slack, Granola, your calendar, or your inbox.

Both approaches can feel natural. Messaging works well for quick commands from a phone. Email works well when the source material and final artifact belong in the same thread-based workflow.

Which one should you choose?

Poke is likely the better fit if you want:

• An assistant in Apple Messages, WhatsApp, Telegram, or RCS.
• Connected email and calendar actions.
• Recipes, integrations, and an API for automated triggers.
• Fast conversational commands from your phone.

Deck is likely the better fit if you want:

• A dedicated assistant address that works with any email provider.
• Explicit control over the threads and files your assistant sees.
• Private responses that come only to you.
• Recurring reports and portable office files.
• A simple path from a real email thread to a finished deliverable.

Try the Deck version of the workflow

Forward a client thread and write:

Prepare me for the next call. Summarize the client's goals, the decisions already made, every open question, and anything we promised. Draft a short agenda and a follow-up email for my review. Put the brief in a PDF and reply only to me.

See client reporting automation for a recurring version of the workflow.

Get your Deck address when you want to test the email-first handoff on the work already in your inbox.