Skip to content

Automation · Sales and quoting

Confirm on WhatsApp what was agreed in a meeting recorded in Avoma and record its outcome

An AI agent finds your customer meeting in Avoma, confirms on WhatsApp what was agreed and records the outcome of the meeting.

How do I confirm to a customer on WhatsApp what we agreed in the meeting recorded with Avoma?

A Met connected to Avoma gets today's date, searches for the meeting with the customer in the right range and opens it to confirm it is the right one by its attendees. Then it pulls the Avoma notes, with key points, decisions and action items, and writes the customer a WhatsApp summary of what was agreed with that data. Finally it lists your organization's outcome options and sets the right one on the meeting, so your team sees it in Avoma without loading it by hand.

What starts it

When the customer writes

It starts when the customer writes on WhatsApp after the meeting, for example to ask what comes next or for what was left pending. There is no trigger to set up: the Met assigned to the line handles it 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 follow up Met

Sales team

It is the Met that looks after customers after a sales meeting, with Avoma connected. Its work ends when the customer has the agreements in writing and the meeting has its outcome in Avoma.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

6 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. 1

    Know what day it is

    The Met asks Avoma for the current date and time in UTC, to work out the search range correctly when the customer says yesterday or last week.

  2. 2

    Find the meeting with the customer

    With that range, the Met lists the meetings and uses the attendee filter to find the customer meeting they mean.

  3. 3

    Confirm it is the right one

    The Met opens the meeting details to check the title, time and attendees before using its content. If two look alike, it asks the customer which one it was.

  4. 4

    Pull what was agreed

    The Met pulls the structured Avoma notes, with key points, decisions and action items, and writes the customer a summary with that data, not with what it remembers of the conversation.

  5. 5

    See the outcome options

    The Met lists the meeting outcome options your organization defined in Avoma, so it uses one that exists and does not invent another.

  6. 6

    Record the meeting outcome

    With what the customer says, the Met sets the right outcome on the meeting, following its instructions. This step needs the set outcome action to be on.

Before you start

What you need ready

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

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

The Met can open the meeting transcript, which the Avoma page also includes, and quote what each person said and when.

The Met lists them and checks the details of each one. If it cannot tell which one it is, it asks the customer before summarizing.

The Avoma page includes that action. This automation does not use it: it only records the meeting outcome.

The Met replies in the language its instructions set, with the data from the Avoma notes. The notes are not changed in Avoma.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.