Automation · Collections and receivables

Confirm on WhatsApp whether a customer's bank transfer came in, by checking Clay

An AI agent checks in Clay whether the transfer the customer says they made reached the bank, and which invoice is still pending.

Show me this with my own operation See every automation

How do I confirm on WhatsApp that a customer's transfer arrived, if my bank is connected to Clay?

A Met connected to Clay finds the company, checks the bank transactions for the period when the customer says they transferred and looks for a deposit for that amount. Then it checks in Clay which of that customer's documents are still pending and how much they owe by age, and it answers on WhatsApp with what the bank shows: the deposit is there, or it does not show up yet. So your team can reconcile without searching, it leaves the direct link to the transaction in Clay in the internal note. It does not record the payment or reconcile on its own.

Where it applies: Chile. Written for Chilean companies with their bank connected to Clay; the RUT identifies the customer.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp that they already made a transfer and asks whether it arrived. 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

Collections Met that confirms transfers in Clay

Customer service team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with Clay connected. Its work ends when the customer knows whether the transfer shows up at the bank and how much is still pending, or when the case goes to the team.

Run by the customer support Met

Channels: WhatsApp

What you need connected

Clay 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
Find the company that receives the payment

The Met lists the companies in the Clay account and takes the one your team named in the skill. If the account holds several companies, it does not look for the deposit in the wrong bank.
- clay_empresas_list Clay
2
Look for the deposit at the bank

The Met checks that company's bank transactions for the period the customer gives and looks for a deposit for the amount they say they sent. If several look alike, it asks the customer for one more detail instead of picking one.
- clay_bancos_movimientos Clay
3
Find the customer in Clay

The Met looks for the customer among the company's customers and suppliers, by the business name or RUT the person gives, so it checks their documents and not someone else's.
- clay_clientes_list Clay
4
Check what is still pending

The Met checks the company's pending documents and the age of what that customer owes. That way it can say which invoice the transfer covers and whether any balance is left.
- clay_obligaciones_pendientes Clay
- clay_clientes_aging Clay
5
Answer and leave the link for the team

The Met answers the customer with what the bank shows. If it found the deposit, it requests the direct link to that transaction in Clay and leaves it in the internal note, so your team reconciles it with the invoice without searching.
- clay_urls_movimiento Clay

Before you start

What you need ready

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

Clay with the bank synced

The company's bank account has to be connected in Clay, or its statement uploaded. If the transaction has not synced yet, the Met does not see it even if the money already arrived.
Clay connected in Met

In Met, open Connections → Clay → Connect and authorize with an admin or owner of the Clay account. This procedure only uses read actions.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers customers. The answer happens inside that conversation; Clay remains the data source.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not reconcile or record the payment: it leaves the transaction link for your team. Reconciling is a separate action and recording a payment starts switched off.
It does not see deposits Clay has not synced from the bank yet. If the customer transferred a few minutes ago, the transaction may not show up.
It does not accept a receipt sent as a photo: it answers with what the bank shows in Clay, not with the image the customer sent.
It does not work for companies outside Chile: Clay works with Chilean banks, the SII and the TGR.

FAQ

Questions about this automation

Not in this procedure. It leaves the direct link to the transaction so your team reconciles it. Clay has an action to create the match, and the admin decides whether it stays on.

The Met only sees what Clay already synced from the bank. If it does not show up, it tells the customer and lets them know the team will check once the transaction comes in.

It should not: the procedure finds the customer by business name or RUT and answers only about their documents. The skill should spell that out.

Keep going