Social media on autopilot|INEMA.CLUB-PRO

Lesson 6 · 17 min

One topic, different audiences: promoavatar and promoavatar3

The same topic won’t persuade a young person and a retiree in the same way. promoavatar writes a script for each of 12 audiences; promoavatar3 writes three for the same audience: reach, authority, and promotional. In both, the bot writes and stops. You approve before spending on the avatar and rendering.

Start the lesson
A grid of twelve vertical screens, each showing a different audience, on an editing desk.

In this lesson, you will

  1. 1The 12 audiences and what motivates each one
  2. 2Reach, authority, and promotional
  3. 3The two gates: before the avatar and before rendering
  4. 4Why the video title is a contract

Goal: plan 3 videos for the same audience (reach, authority, promotional) with the two gates and each avatar’s contract title.

01The promoavatar cycle

Four phases and two gates. The pipeline stops at the gates and only moves forward when you approve.

Click each block in the diagram to see what it does.

Approving first is better than retrying later: avatar and render cost money and can’t be undone. The first gate protects your avatar spend; the second protects your render spend.

02Three videos for the same audience (promoavatar3)

Publish in this order: reach → authority → promotional.

1. Reach

Goal: stop the scroll and get shared.

CTA: comment or share. Never promotional.

Studio titleC7-jovens-alc-v1

03Commands and contract

Bot commands (inemaccbot). For your channel, the key pattern is: filter, review the plan, approve.

bot chat
# review the plan without spending anything (does not add to the queue)
/promoavatar3 <assunto> | alvos=jovens-alc,jovens-aut,jovens-pro | sombra

# run for just one audience, across all three types
/promoavatar3 <assunto> | alvos=jovens-alc,jovens-aut,jovens-pro

# after reviewing the text
/aprovar C#7
titulo-contrato.txt
promoavatar:   A<N>-<publico>-v1        ex.: A8-mulheres-v1
promoavatar3:  C<N>-<publico>-<tipo>-v1 ex.: C7-jovens-pro-v1

The download matches by exact equality. Short suffixes (alc, aut, pro):
a long title was already truncated in the studio and broke the match.
meus-3-videos.md
# Same topic, same audience: <público>

Topic: 
Audience trigger: 

| Type | Length | Goal | CTA | Studio title |
|---|---|---|---|---|
| reach | 25–40 s | get shared | comment or share | |
| authority | 35–60 s | get saved | save, follow, or try it | |
| promotional | 30–45 s | connect a pain point to a solution | one only, for your site | |

Result (comments in 7 days): reach __ · auth __ · promo __
Repository example
  • promoavatar: one video per audience, 12 audiences. Reference A#N.
  • promoavatar3: three videos per audience (reach, authority, promo), 36 possible targets. Reference C#N. The usual way to filter is | alvos=.
  • They are separate systems: changing one does not affect the other.

04Find the download by title

The avatars are in the studio. The download looks for each one by its exact title.

in studio

downloading

reel delivered

not found

Illustrative browser simulation. The failure is intentional: a title typed from memory, with the longer suffix.

05Practice: the extra challenge for sequence 4

Do this after E4. Use an avatar, your camera, or just the scripts.

Challenge · 3 videos for the same audience

1 week

Write meus-3-videos.md for an audience in your niche, publish in this order: reach → authority → promotional, and note the comments on each one.

Done when: all three were published with titles that match the contract, and you know which one got the most comments.

Extra challenge from jornada-agentes/exercicios/04-redes.md.

06Test what you learned

The explanation appears after you answer.

Question 1 of 4

When does changing a reel's cover image cost nothing?competency

To learn more

Previous lessonNext lesson