Skip to content

Automation · Customer service and scheduling

Email from your domain what the customer asked for on WhatsApp with Resend

An AI agent sends with your Resend template the catalog or instructions the customer asked for on WhatsApp and confirms whether it arrived.

How do I email, with my template and from my domain, what a customer asks for on WhatsApp?

A Met connected to Resend asks the person for their email, checks which verified sending domain you have and picks the template that matches the request: catalog, instructions or conversation summary. It reads the template's variables, fills them with the chat details and sends the email from your domain. It registers the person as a contact so they stay in your account, and if they later say it did not arrive, it looks up that email in Resend and tells them its delivery status instead of resending blindly.

What starts it

When the customer writes

It starts when a customer asks on WhatsApp to get something by email: the catalog, the usage instructions or a summary of the conversation. 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

Support Met that sends information by email

Customer service team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with Resend connected. Its work ends when the email goes out from your domain with the right template and the person knows whether it arrived.

Run by the customer support Met

Channels: WhatsApp

What you need connected

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

    Confirm the sending domain

    The Met lists the domains in your Resend account and uses the one the skill names as sender, as long as it is verified. If there is no verified one, it does not send.

  2. 2

    Pick the template and read its variables

    The Met looks through your templates for the one that matches the request and opens it to see which variables it expects, for example the name or the product.

  3. 3

    Send the email

    With the email the person gave, the Met fills the variables with the conversation details and sends the email from your domain. If an attachment is needed, such as the catalog, it goes in the same send.

  4. 4

    Register the person as a contact

    The Met creates the contact in your Resend account with their name and email, so your team has it and can add it later to a segment or a broadcast.

  5. 5

    Tell whether the email arrived

    If the person writes that it did not arrive, the Met looks up that email in Resend and tells them its delivery status. That way they know whether to check spam or whether the address was wrong.

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

Yes. It goes out from your verified domain and with your Resend template. The Met only fills the variables with the conversation details.

The email does not reach them. When they write again, the Met looks up the email in Resend, sees the status and asks for the right address.

Cancelling starts switched off and this procedure does not schedule sends: the email goes out right away. If you need it, the admin turns that action on.

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.