AI clone sales videos for personal outreach from the rep

A prospect's inbox is full of text that looks the same. A short video from the actual rep, saying the prospect's name and referring to something specific, stands out because it shows that a real person took notice. It also carries tone in a way text cannot: a friendly face explaining a next step feels easier to answer than a paragraph of copy.

The catch has always been time. Recording a personal video for every prospect means retakes, uploads and a camera that never seems to be ready. Most reps manage a handful a week and then stop. A clone of the rep removes that bottleneck while keeping the part that makes video work, which is that the person on screen is the person who will take the call.

Every rep builds their own clone. They record a 2 minute training video and a 60 second voice sample, pass a live selfie check and read a spoken consent statement with a one time phrase that is matched to their footage. Teammates are added by invite and each person records their own consent; a manager cannot build a clone of a rep, and nobody can build a clone of a prospect, a customer's executive or any public figure. No identity documents are uploaded or processed.

That rule is what makes the approach safe to scale. The prospect sees the rep who will actually answer the reply, and the rep has agreed to every video sent in their name. When a rep leaves, the clone is deleted and the model files are removed.

• First touch after an inbound request. A 40 second video from the assigned rep that names the company and the topic of the request.
• Follow-up after a call. A recap of the two things discussed and one clear next step, sent the same day.
• Re-engagement. A short check-in that mentions what changed in the product since the last conversation.
• Proposal walkthrough. The rep explains the structure of the offer while the prospect reads it.
• Onboarding handover. The account executive introduces the customer success manager, both from their own clones.

Keep each video short. Under a minute is the target for most sales touches; the aim is to start a conversation, not to replace it.

On Business and Enterprise, the AI avatar API creates videos from templates with variables. A template is a script written by the rep or the team with variable fields such as first name and company, plus any other fields you pass in, for example the topic of the request or the city of the next event. Your CRM or outreach tool calls the API with the values for each prospect, IdClone renders the video in the rep's clone and voice, and a webhook tells your system when it is ready to attach to the email or sequence step.

• Write the template as one natural script and mark the variables, so that, for example, a prospect named Dana at a company called Northfield hears "Hi Dana, I took a look at what the Northfield team is doing" in the rep's own voice.
• Keep variables to the parts that change. Two or three personal details are enough; a script that is mostly variables sounds stitched together.
• Add every company name and unusual first name you can to the pronunciation dictionary. A mispronounced name undoes the point of a personal video.
• Set a fallback for missing fields. If the company is unknown, the script should still read naturally without it.
• Use the brand kit for intro, outro and captions so every rep's video looks like the same company.

API renders draw from the same pool of avatar video minutes as videos made in the editor. Business includes 90 minutes a month and Enterprise 300, with higher API rate limits.

Sales videos are short, so minutes stretch further than in training. A 30 second personal video uses half a minute, so the 90 minutes on Business cover about 180 such videos a month for the whole workspace, and the 300 minutes on Enterprise about 600. If your reps also send translated versions to prospects in other markets, those versions count their length too. For larger teams that need SSO, SCIM and audit log export, Enterprise also adds a 99.9 percent uptime SLA. Plans and limits are on pricing.

A sales video is a commercial message, and a prospect who later discovers that a video was generated without being told may feel misled, which is the opposite of what personal outreach is meant to achieve. Consumer protection rules against deceptive practices also apply to sales communication, whatever technology is used. The is voice cloning legal article explains the general landscape.

The simple fix is to be open about it. Every IdClone export can carry a visible AI-generated label and content credentials metadata. Many teams add one line to the email as well, for example a note that the video was created with the rep's AI clone and that the rep reads every reply. Honest framing tends to land well: the prospect sees a rep who uses modern tools and still speaks to them personally.

• Never let the video claim something the rep did not do, such as "I just watched your webinar" when nobody did.
• Never imply a relationship, endorsement or result that is not real.
• Do not use a clone in outbound phone calls without the consent that rules on artificial voices require.

When many reps send many videos, a single bad template can go out hundreds of times before anyone notices. On Business, roles and approvals solve this. Reps work as editors, a sales lead or enablement manager works as reviewer, and a template is approved by the reviewer before the team uses it in sequences. The owner controls who holds which role, and every clone keeps a consent record and an audit log.

• Review templates, not individual sends. Once a template is approved, variables only change the personal details.
• Re-approve after any edit to the script, including small wording changes.
• Keep a short list of claims that are allowed, such as product facts and current offers, and reject templates that go beyond it.
• Spot check a few rendered videos each week for pronunciation and fallbacks.

• Week one. Two or three reps record their clones and write one follow-up template each. The team lead reviews and approves.
• Week two. Connect the API to the outreach tool, map the variables and test the webhook with internal addresses.
• Week three. Send to a small segment, read the replies and fix the scripts that sound stiff.
• After that. Add the remaining reps, build a small library of approved templates per stage and review them monthly.