Autopilot is a feature for which many people create an account on Telematic: one click, and the material goes through the entire process from text processing to published video on multiple platforms, without manual intervention at each step. However, turning it on for the very first project without any prior setup is a surefire way to get a video that is technically published but doesn't sound or look the way you want it to.
At Telematic, we always advise starting by manually assembling one or two videos to understand how the project settings behave, and only then transferring the same set of decisions to autopilot. Below is a step-by-step guide on how to set up autopilot from scratch for the first channel, ensuring nothing important is missed.
Step 1. Assemble at least one video manually
Before turning on autopilot, it's worth going through the entire process manually once: choose the source, check the processed text, select the script mode, visual style, and voice. This is not a formality—it's at this step that you find the project settings (tone, pace, style) that autopilot will later apply to all new materials without your involvement.
Most often, those who rush to turn on autopilot on the very first day stumble at this step: default settings rarely perfectly match the tone of a specific brand, and it's better to correct them manually once than to later deal with a dozen automatically published videos with the same inaccuracy.
Step 2. Connect and configure publication platforms
Before autopilot can publish anything, the project must have the necessary platforms connected—YouTube, Telegram, VKontakte—with the text and language already configured for each of them separately. If the platforms are not prepared in advance, autopilot will hit a step that cannot be completed automatically on the very first cycle.
Step 3. Set default video presets for each orientation
In the project, you can assign a default video preset separately for horizontal and vertical formats—this is the set of visual and audio settings that autopilot will apply to each new video without additional questions. Make sure that for both orientations, the preset you selected is the one you have already seen in action in step 1, and not a value left as default.
Step 4. Enable automatic linking of horizontal and teaser formats
If the channel publishes a long video and a vertical teaser simultaneously, enable automatic format linking—it automatically ties the vertical trailer to the corresponding horizontal video, ensuring they are linked on the platforms rather than existing as two independent videos.
Step 5. Configure the schedule and auto-resend on failures
Autopilot can work not only "on click" but also on a schedule—this is especially important for a channel that needs to release content regularly, rather than whenever someone on the team gets around to it. It's also worth checking the auto-resend setting: if publication on one of the platforms fails due to a temporary glitch, the system will retry later, rather than leaving the channel with partially published material forever.
Step 6. Link the CTA funnel
Before launching autopilot on a permanent basis, link the CTA funnel—the target action that each video on the channel should lead to. This can be done at the project level or for the entire channel, so you don't have to set up the call to action again for each new video manually.
Step 7. Launch the first automatic cycle and check bulk processing
Once all the previous steps are completed, turn on autopilot for the new material—or immediately for several through bulk processing, if the source has already accumulated several pieces of content. The first automatic click usually means: text processing, video assembly, and publication on all connected platforms occur without additional questions for you.
We advise against leaving the channel completely unattended right after the first automatic cycle: take a look at the first two or three videos that were released without your involvement—if the tone, visuals, and publication are satisfactory, then the setup in step 1 was done correctly, and you can trust autopilot going forward without additional checks for each release.