A customer success manager with 80 accounts cannot record a personal video for every kickoff, milestone and renewal. So the messages go out as plain text, or they do not go out at all. Accounts that would have responded to a familiar face get a templated email instead.
If you build a customer success platform, a CRM add-on or an onboarding tool, AI avatar video lets each CSM record once and then send personal video messages triggered by account events. This post covers which moments to automate, how to wire it up, and the guardrails that keep it from feeling like spam.
Moments worth a video
Video is worth it when the message benefits from a human face and is predictable enough to template. Good candidates:
- Kickoff welcome. The CSM introduces themselves after the contract is signed, names the account and sets up the first call.
- Milestone follow-up. "Your team just sent its first 1,000 invoices through the platform." Triggered by a product event.
- Feature adoption nudge. When an account has not tried a feature that matches their plan, a 30-second explanation from their CSM.
- QBR preview. A short recap of what will be covered, sent a few days before the meeting.
- Renewal heads-up. A friendly note 60 days before renewal with the name of the person to contact.
- Support follow-up. After a long ticket is resolved, a quick thank-you from the account owner.
Avoid video for anything negative or sensitive, such as billing disputes, outages or price increases. Those deserve a real conversation, and an automated video can make a hard message worse.
Why the avatar has to look like the CSM
The whole point is that the customer sees their CSM. They will meet the same person on the next call, so the avatar has to match. PitchTwin builds the avatar from real video of the person and keeps that footage, so it looks 1:1 like them: their skin, hair, lighting and their own expressions. An avatar that looks smoothed or generic undermines trust in exactly the relationship you are trying to strengthen. Our post on why AI avatars look plastic goes into the difference.
The CSM records a 10–120 second clip once. If it contains at least 10 seconds of speech, the voice is cloned from the clip itself; a separate 1–2 minute voice sample gives the best clone. Every person in an avatar must have agreed to it under PitchTwin's Terms, so capture that consent in your own onboarding flow. When a CSM leaves or an account is reassigned, DELETE /avatars/:id removes the avatar and the cloned voice.
Architecture
A CS video feature is an event-driven pipeline. The pieces:
- Trigger. A CRM or product event fires: contract signed, milestone reached, renewal window opened.
- Eligibility check. Is video enabled for this account? Has this contact received a video in the last N days? Is the CSM's avatar ready?
- Script. Fill a template with account data, then queue it for CSM approval or send it directly, depending on the workspace setting.
- Generation.
POST /generationswith the CSM's avatar and awebhook_url. - Delivery. On
generation.succeeded, copy the MP4 to your storage, build a landing page or email with a thumbnail, and send.
Generation is asynchronous, so never block a CRM workflow waiting for a video. The request returns 202 with a queued ID right away, and the result arrives by webhook. The pattern is covered in async video generation with webhooks.
Creating the generation
async function createCsVideo(msg: CsMessage) {
const res = await fetch("https://pitchtwin.ai/api/v1/generations", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.PITCHTWIN_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
avatar_id: msg.csm.pitchtwinAvatarId,
script: [
{ text: `Hi ${msg.contact.firstName}, it's ${msg.csm.firstName}.`, pause_after_ms: 400 },
{ text: `Your team at ${msg.account.name} just ${msg.milestone}. That's a big step.`, pause_after_ms: 500 },
{ text: "I've put two ideas for what to try next right below this video." },
],
webhook_url: "https://app.example.com/webhooks/pitchtwin",
}),
});
if (res.status !== 202) throw new Error(`PitchTwin error ${res.status}`);
const { id } = await res.json();
await db.csMessages.update(msg.id, { generationId: id, status: "queued" });
}
Handling the webhook
PitchTwin signs each webhook with a PitchTwin-Signature header in the form t=<unix>,v1=<hex>. The v1 value is a hex HMAC-SHA256 of ${t}.${raw_body} using the webhook secret from Dashboard, API keys. Verify against the raw request body, before parsing JSON:
import crypto from "node:crypto";
import express from "express";
const app = express();
app.post("/webhooks/pitchtwin", express.raw({ type: "application/json" }), async (req, res) => {
const header = req.get("PitchTwin-Signature") ?? "";
const parts = Object.fromEntries(header.split(",").map((p) => p.split("=", 2)));
const raw = req.body.toString("utf8");
const expected = crypto
.createHmac("sha256", process.env.PITCHTWIN_WEBHOOK_SECRET!)
.update(`${parts.t}.${raw}`)
.digest("hex");
const ok =
typeof parts.v1 === "string" &&
parts.v1.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(parts.v1), Buffer.from(expected));
if (!ok) return res.status(400).send("bad signature");
const event = JSON.parse(raw);
if (event.type === "generation.succeeded") {
await storeAndSend(event.data.id, event.data.video_url);
} else if (event.type === "generation.failed") {
await markFailed(event.data.id);
}
res.sendStatus(200);
});
Also reject timestamps that are too old to limit replays. More detail, including a Python version, is in how to verify HMAC webhook signatures.
Two operational details matter here. Webhooks are delivered once, so run a periodic job that polls GET /generations/:id for messages still marked queued. And video_url is a signed link that expires after 24 hours, so storeAndSend should copy the file to your own storage before anything is emailed. Never put the PitchTwin link itself in a customer email.
Guardrails for CS teams
Automation can damage relationships faster than it builds them. Build these in from the start:
- Approval by default. Let CSMs review and edit scripts before generation. Make auto-send an explicit opt-in per template.
- Frequency caps. Limit how many videos a single contact receives per month, across all templates.
- No sensitive data on screen or in speech. Keep contract values, health scores and internal notes out of scripts. Videos get forwarded.
- Be clear it is AI-generated. A short line under the video ("Made with AI from a recording of Priya") is honest and avoids an awkward moment on the next call. In the EU, the AI Act also requires deployers to disclose AI-generated video that resembles real people, with transparency obligations applying from 2 August 2026 (Regulation (EU) 2024/1689, Article 50). This is not legal advice.
- Captions. Each generation returns
wordswith word-level timings. Use them for captions, since many people open these emails on a phone with sound off.
Cost per message
A 35-second milestone video in the CSM's cloned voice uses 52.5 tokens (1.5 tokens per second). On the Growth pack, $39 for 3,000 tokens, that is roughly $0.68 per video, or about 57 messages per pack. Tokens are prepaid and never expire, there are no seats, and failed generations are refunded automatically. That makes it straightforward to include a video allowance in a CS platform plan. See pricing for all packs.
Output is white-label, with no watermark and no PitchTwin branding, so the video carries your product's or your customer's brand only.
Try it
Sign up at /signup for 60 free tokens with no card, upload a CSM clip in the dashboard and generate a test milestone message in the Playground. The Playground shows the equivalent cURL and Node request, so you can move it straight into your codebase.