Communication · Integration

Email (SMTP) + Voicent AI

Voice workflows that actually work — not just call transfers.

Voicent sends email straight from a workflow over your own SMTP. Summaries, confirmations, and templated follow-ups go out under your domain — no third-party sender in the middle.

Communication2 actionsapi_key auth

Overview

Sometimes the right follow-up is an email, not a text — a detailed recap, a document, a formal confirmation. Voicent’s SMTP connector sends it directly from your workflow using your own mail server, so the message comes from your domain with your deliverability, not a shared third-party sender. send_email handles one-off messages and send_template_email fills a reusable template with call variables, so every recap is consistent and personalized without a human drafting it.

What your agent can do with Email (SMTP)

How it works

  1. The call produces the content — a summary, next steps, a confirmation — as workflow variables.
  2. send_template_email fills your reusable template with those variables, or send_email composes a one-off message.
  3. The email sends over your own SMTP server, under your domain and deliverability reputation.

What the agent actually says

I've emailed you a summary of everything we covered, along with the next steps.

Put it in a workflow

Combine Email (SMTP) with triggers, branches, and other connectors in a Voicent workflow.

Browse workflow templates →

In practice

Call recaps and confirmations emailed under your own domain.

A B2B team wants call recaps in the prospect’s inbox. Voicent sends a templated summary email over the company’s SMTP the moment the call ends, so follow-up lands before the rep is even free.

See Email (SMTP) + Voicent on a real call.