Automation · Sales and quoting

Send a Gamma proposal on WhatsApp built from what the customer asked for

An AI agent builds a Gamma proposal from your template and the customer's request, exports it to PDF, sends it on WhatsApp and sees if it was opened.

Show me this with my own operation See every automation

How do I send a customer on WhatsApp a Gamma proposal built from what they asked for?

A Met connected to Gamma finds the proposal template in your workspace and creates a new gamma with what came out of the conversation: the service the customer asked for, the scope, the timeline and the prices your team left in the skill. It waits for the generation to finish, exports it to PDF and sends on WhatsApp the link to view it online and the PDF to download it. Days later it checks the gamma's analytics to know whether it was opened and which card they reached, so your team follows up with data. Each proposal spends credits from your Gamma plan.

What starts it

When the customer writes

It starts when a customer asks on WhatsApp for a proposal or a formal quote and has already given what is needed to build it. There is no trigger to configure: the Met assigned to the line runs the procedure inside 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 builds proposals in Gamma

Sales team

This is not a named, seeded Met. It is the presentations Met from the catalog, with Gamma connected and assigned to the sales line. Its work ends when the customer has the proposal in the chat and your team knows whether they opened it.

Channels: WhatsApp

What you need connected

Gamma Create and promote

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
Find the proposal template

The Met searches your Gamma workspace templates for the one the skill names, for example "Sales proposal". It uses a workspace template, because Gamma's sample templates cannot be used to generate.
- search_templates Gamma
2
Create the proposal from the customer's request

With the template and the details from the conversation, the Met asks for a new gamma that keeps the template's structure and adapts the content to that customer. It gives view access to anyone with the link and saves it in the proposals folder if the skill says so.
- generate_from_template Gamma
3
Wait for the generation to finish

Generating is not instant. The Met checks the generation status until it finishes and takes the link to the new gamma. If it fails for credits or a plan limit, it tells the customer the proposal will arrive later and leaves a note for your team.
- get_generation_status Gamma
4
Export to PDF and send it on WhatsApp

The Met exports the proposal to PDF and checks the export until it has the download link. In the conversation it shares the gamma link to view it online and the PDF link to download it. The PDF link expires in about a week and anyone who has it can download the file.
- export_gamma Gamma
- get_export_status Gamma
5
Check whether it was opened before following up

Days later, the Met checks the gamma's analytics using its link: how many views it has, when the last one was and which card they reached. With that your team knows whether to call or wait. The data can take up to an hour to show up.
- get_gamma_analytics Gamma

Before you start

What you need ready

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

Gamma connected with a proposal template

In Met, open Connections → Gamma → Connect and authorize with the account of the workspace that holds the template. Your team designs the proposal template in that workspace and the admin leaves create and export switched on.
Credits on your Gamma plan

Each generated proposal spends credits from your Gamma plan. If they run out, Gamma rejects the generation and the Met says which limit was hit; more can be bought in Gamma billing.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that sells. The proposal is delivered in that conversation; the gamma stays saved in your Gamma workspace.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not make up prices or scope: it builds the proposal from what the customer said and what your team left in the skill. If a detail is missing, it asks before generating.
It does not measure who read the downloaded PDF: analytics count opens of the online gamma, and visitors who did not sign in are not identified by name.
It does not fix the proposal after sending it: editing starts switched off and this procedure does not use it. If the admin turns it on, each edit changes a single page.
It does not ask for confirmation in the chat before creating or exporting the gamma: if the action is on, it runs. The admin decides which actions stay on.
It does not charge or sign: the proposal supports the sale, but acceptance, the contract and payment still follow another integration or your process.

FAQ

Questions about this automation

It comes from your template, so it keeps its structure and theme. Gamma adapts the content to the customer, which is why your team should review the template before putting it to use.

As long as Gamma takes to generate and export it. It is not instant: the Met checks the status until it finishes and then sends the links in the conversation.

Whatever Gamma deducts in credits from your plan for that generation. Meteor does not resell Gamma: the spend runs on your company's account.

No, it expires in about a week. The online gamma link stays available as long as the gamma exists and has view access for anyone with the link.

Keep going