Automation · Sales and quoting

Send a PandaDoc proposal for signature from WhatsApp

An AI agent creates in PandaDoc the proposal the customer accepted on WhatsApp, sends it for signature and tells them where it stands.

Show me this with my own operation See every automation

How do I send a PandaDoc proposal for signature as soon as the customer agrees on WhatsApp?

When the customer agrees on WhatsApp, a Met connected to PandaDoc first searches for an existing document in their name so it does not create a duplicate. If there is none, it creates the document in your PandaDoc account with the details the customer confirmed, checks its details and content, and sends it to its recipients from PandaDoc. When the customer asks later, the Met checks the document's status and tells them whether it is completed or still pending. Signing happens in PandaDoc, not in the chat.

What starts it

When the customer writes

It starts when the customer accepts the proposal on WhatsApp and asks for the document to sign, or when they write back to ask about it. There is no trigger to configure: the Met assigned to the line runs the procedure in that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Sales Met that closes proposals

Sales team

It is the Met that already carries the sales conversation on WhatsApp, with PandaDoc connected. Its work ends when the document went out in the right person's name and the customer knows where it stands.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

PandaDoc Collect and manage

5 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Check whether the customer already has a document

The Met searches PandaDoc for a document with the customer's or their company's name. If one is already in progress, it works on that one instead of creating another, so the customer does not get two proposals.
- pandadoc_documents_search PandaDoc
2
Create the document with the confirmed details

With the name, email and what was agreed in the conversation, the Met creates the document in PandaDoc. If your company uses a template, it names it in the Met's instructions, because the connector cannot list templates.
- pandadoc_documents_create PandaDoc
3
Review the document before sending it

The Met checks the details and content of the new document and confirms that the recipient and what was agreed match the conversation. If something is off, it alerts your team instead of sending it.
- pandadoc_documents_details_get PandaDoc
- pandadoc_documents_content_get PandaDoc
4
Send the document from PandaDoc

With the document ready, the Met sends it to its recipients from PandaDoc and tells the customer on WhatsApp that it will arrive from PandaDoc to sign.
- pandadoc_documents_send PandaDoc
5
Tell where the signature stands

When the customer asks, the Met checks the document's status in PandaDoc and answers whether it is completed or still pending, with what PandaDoc reports and not with a guess.
- pandadoc_documents_status_get PandaDoc

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

PandaDoc connected in Met

In Met, open Connections, then PandaDoc, then Connect. A PandaDoc window opens so you sign in and authorize Met. An account in the global region (app.pandadoc.com) works.
Create and send turned on

The workspace admin keeps the actions to create and send documents on in the connector. If they are off, the Met can only search and check.
Instructions with the template and content

Your team writes in the Met's instructions which template or content to use in the proposal, because the connector does not list PandaDoc templates.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not have anyone sign inside WhatsApp. PandaDoc sends the document to its recipients and signing happens in PandaDoc.
It does not negotiate prices or change terms on its own. It uses what your team left in the instructions and what the customer confirmed.
It does not serve accounts in PandaDoc's European region, which use a different server from the one Met uses.
It does not ask for confirmation in the chat before creating or sending. The control is which actions the workspace admin keeps on.

FAQ

Questions about this automation

PandaDoc sends the document to the recipients it has. The Met asks for each person's details in the conversation, but it does not invent signers the customer did not name.

The Met can update the document if that action is on, or hand the case to your team if the change touches price or terms that are not in its instructions.

Your company, under its PandaDoc plan. Meteor does not resell PandaDoc and does not charge Energy for these calls.

Keep going