Skip to content

Automation · Sales and quoting

Confirm on WhatsApp what was agreed in a sales meeting recorded with tl;dv

An AI agent finds the customer's sales meeting in tl;dv and confirms on WhatsApp the price, terms and agreements, quoting what was said.

How do I confirm on WhatsApp the price and timelines we gave the customer in the meeting?

A Met connected to tl;dv, when the customer writes on WhatsApp to pick up what was discussed in the sales meeting, finds that meeting by their name and the date, checks the attendees to confirm that person was there, reads the notes by topic and confirms the price, timelines and agreements. If the customer is unsure about a detail, the Met looks it up in the transcript and tells them exactly what was said and who said it. Everything comes from what tl;dv recorded; the Met changes nothing in your account.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp after a sales meeting to ask about the price, the timeline or what was left pending. 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 picks up meeting agreements

Sales team

This is not a named, seeded Met. It is the Met that already runs the sales conversation on WhatsApp, with tl;dv connected. Its work ends when the customer has in writing what was agreed in the meeting and the sale can move on without repeating the call.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

5 steps · 5 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 which account it reads from

    The Met checks the profile of the tl;dv account that authorized the connection. That tells it whose meetings it will search and, if someone else recorded the meeting, it says so instead of answering that it does not exist.

  2. 2

    Find the customer's meeting

    The Met searches for the meeting by the customer's or their company's name, the approximate date and a keyword from the topic, such as the proposal or the product. If several show up, it asks the customer which one.

  3. 3

    Check the customer attended

    Before sharing anything, the Met gets that meeting's details, with the date, duration and attendees, and checks that the person writing is among them.

  4. 4

    Read the agreements in the notes

    The Met reads the notes tl;dv generated, organized by topic, and replies to the customer with the price, the timelines and what each side still has pending.

  5. 5

    Quote the exact sentence if in doubt

    If the customer says they were given another price or timeline, the Met opens the transcript, finds the moment it was discussed and quotes the sentence with the name of who said it.

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 checks the attendees before sharing. If the person writing is not listed, it does not share what was discussed and alerts your team.

Yes, if tl;dv recorded them. The connector reads the Google Meet, Zoom and Teams meetings in the connected tl;dv account.

No. The five tools on the tl;dv server are read only, so this procedure has no write actions to turn on or off.

Yes. tl;dv requires the Pro plan or higher to connect its MCP server; on the free plan the option does not appear.

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.