Integration

EchoPilot and WhatsApp

The message you said you would send, written for you and opened in WhatsApp, with the chat already chosen when EchoPilot can find the contact. You press send; EchoPilot never does.

  • Creates prefilled messages
  • Nothing sent without approval
WhatsApp
What one approved card becomes there
Message card
Packaging options are going to the board Monday morning.
Waiting for your approval
WhatsApp
RecipientThe contact named, or you choose
StatePrefilled, you press send
HandoffOnly after you approve the card

Creates prefilled messages

Drafted from the commitment as it was said, with the fields WhatsApp accepts, and the moment in the recording it came from.

On iPhone, Android

A meeting recorded on any device produces the same cards; you approve them on your phone.

Before anything is created

You approve the card. There is no automatic send, and no setting that turns the review off.

Nothing to connect

EchoPilot opens WhatsApp on your phone with the content ready. There is no account to sign in to, and you finish it there.

In depth

WhatsApp, in depth.

For a great many people, the follow-up to a meeting is not an email. It is a WhatsApp message to the person who was not in the room, the supplier, the client, the family group. EchoPilot writes it for you and opens WhatsApp. The sending stays yours.

When a card goes to WhatsApp

When WhatsApp is named. “WhatsApp Sarah the new address.” “Send the team the summary on WhatsApp.” Said in a meeting or in a voice note, that becomes a card with the message written in full and WhatsApp as the destination. Follow-ups that do not name WhatsApp go to the places they belong, such as an email draft or your task list.

What happens when you approve it

WhatsApp opens with the message already typed. If the card names someone and exactly one contact on your phone matches that name, their chat opens directly. Otherwise WhatsApp opens with the message ready and you choose the chat. Read it, change it if you want, and press send in WhatsApp.

EchoPilot never sends a WhatsApp message itself, and there is no setting that makes it.

Your contacts stay on your phone

To open the right chat, EchoPilot asks once for access to your contacts, and only when a card names someone. The name is matched on your phone. If you would rather not allow it, WhatsApp still opens with the message and you pick the chat yourself.

The whole meeting, too

A card carries one message. To send someone the whole write-up, export the Meeting Minutes as plain text or a PDF and choose WhatsApp in your phone’s share sheet.

After WhatsApp opens

Once the message is in WhatsApp, it is WhatsApp’s, and EchoPilot cannot edit or unsend it. If you change the card before you have sent the message, open WhatsApp again from the card and the new version is ready.

Nothing to connect

There is no account and no sign-in. The handoff works on iPhone and Android wherever WhatsApp is installed; if it is not, the message opens through WhatsApp’s own web link instead.

FAQ

Questions worth answering.

Does EchoPilot create tasks automatically?
No. EchoPilot drafts a card for each commitment it finds and shows you the destination it picked. Nothing is created, updated, or sent outside EchoPilot until you tap the confirmation on that card.
Which apps can EchoPilot send actions to?
EchoPilot's built-in Tasks, Reminders and Notes; Todoist; Google Tasks, Google Calendar and Google Drive; Slack; Notion; Microsoft To Do, Outlook Calendar, Outlook Mail, OneNote, OneDrive and Teams; Apple Reminders, the device calendar and Apple Notes; a prefilled WhatsApp handoff; and Mail drafts. Availability varies by platform and account. Gmail and Google Chat are not supported yet.
iPhone, Android, Mac, Windows and web

Record one meeting and send a card to WhatsApp.

Record a real conversation and read what lands in the review queue, with the destination already chosen and nothing created until you approve it.

Questions? support@echopilotapp.com