Quick answer

Automating indoor TV content means removing the manual steps between the person who has the information and the screen that will show it. Two mechanisms do that without anyone opening a video editor: a standardized email, sent to a configured address, is converted into a video clip that enters the playlist; and a phone shortcut, connected over FTP to the platform, sends a freshly recorded clip straight into the account's media library. In both cases editing, format conversion and manual dashboard uploads simply stop existing. What stays human is deciding what to communicate and approving what goes on screen.

The real bottleneck: four steps for one notice

When an indoor TV goes stale on the wall, the usual diagnosis is "we ran out of content". It almost never is. HR has the announcement, the manager knows which product needs to move, the supervisor saw the queue grow. What is missing is a path.

The "Podcast Tv Indoor 1" episode, from Café & Tech, describes that path in the exact order it happens: grab the video, convert the video, upload the video to the dashboard, schedule the video. And it closes with the line that sums the problem up — it drags on, it turns into cost.

Notice that none of those four steps is about what to communicate. They are all transport. That is why automation pays off so well here: it does not replace judgement, it removes paperwork. The person who has the information can now put it on screen without depending on a second person with dashboard access and the patience to convert a file.

The classic symptom. If your operation keeps a folder of clips "to upload when there is time", the problem is not content production — it is delivery friction. Automating delivery empties that folder; producing more content only fills it further.

Mechanism 1: the email that becomes a video

The first mechanism starts from a simple observation: everyone at the company already knows how to send an email. Nobody has to learn a new tool.

It works directly. An email in a standardized format is sent to a configured address; the content of that email is automatically converted into a video file, which enters the indoor TV playlist. No editor, no export, no upload.

The example given in the podcast is corporate HR: instead of having someone produce a piece to announce a change in cafeteria hours, HR writes the short text itself and it shows up on screen.

A figure that needs confirming. In the conversation, a limit in the range of 50 characters was mentioned for the email text, along with the note that the format "is not that open" and follows defined patterns. That number came up in a live conversation with no technical detail, so treat it as an order of magnitude, not a specification. The exact limit and the formatting requirements should be confirmed with the technical team before you design a process around them.

It is worth understanding why a short limit exists at all, whatever its value: the resulting piece is shown on a screen seen in passing, from metres away, by someone who will not stop to read. Short text is not a tool limitation, it is a property of the medium. A long announcement on an indoor TV does not get read even when it fits.

Mechanism 2: the phone shortcut over FTP

The second mechanism handles the case where the information is not text but a scene: the product on the shelf, the window display, the message recorded by the manager.

The setup uses the iPhone Shortcuts app — the same one many people use for home automation — configured to connect to the platform's FTP. In practice:

  1. The person records a short clip on their own phone, where the thing is happening.
  2. They trigger the shortcut, which already knows the address and the credential.
  3. The file uploads to the server on its own.
  4. It shows up in the account's media library, ready to be scheduled.

The gain is about distance, not only time. As it was put in the episode, the employee does not have to walk over to whoever manages the TV, nor send the file through a second channel for someone else to forward. It goes up directly and appears in the library of the person building the playlist.

About the Android equivalent. In the episode, the host states that Android has an app doing the same thing, but explicitly says he could not recall the name at that moment. For that reason this article does not name a specific Android app: the concept — a phone automation that triggers an FTP upload — is what matters, and there are Android automation tools capable of it. Before standardizing on one across your operation, confirm that the app's current version really does support FTP uploads.

Who actually uses this

Internal communication (corporate TV)

This is the HR scenario. Companies past a few dozen employees have a chronic internal communication problem: the announcement goes out by email and disappears in the inbox, goes up on the noticeboard and nobody stops in front of it. The screen in the hallway or the cafeteria works as one more touchpoint — and it only plays that role if it is up to date. With email-to-video, updating no longer depends on someone having spare time. This use case connects directly with onboarding new hires through indoor TV, where content repeats and changes often.

Retail (the stocker at the shelf)

The second scenario belongs to whoever is on the floor. The stocker is the first to see the product whose expiry date is approaching, and the gap on the shelf. With the phone shortcut, they record a short clip right there, in front of the product, tap the button, and the file lands in the library. None of those steps requires leaving the aisle.

This path is also the cheap step before any sophisticated targeting project: while indoor TV with a camera and aisle-targeted content is a bespoke project with integration and a legal layer, the phone shortcut solves the most common bottleneck — slowness to update — at practically zero cost. And if your pain is approving content while away from the store, the natural complement is managing indoor TV from your phone.

What this is not (and what stays out)

Content automation has become an umbrella for quite different things. It is worth separating them, because each solves a distinct problem and they add up rather than compete.

MechanismWhich problem it solvesWhere the content comes from
Email to video · FTP shortcut (this article)Transport: how content reaches the screen without editingFrom someone inside the operation
AI video generation from photosProduction: how the piece is created without an editorFrom raw material, such as product photos
Automatic news from partner outletsFilling: how the screen never goes emptyFrom an external, continuous source

The three form the same cluster — content without manual effort — attacking different points of the same chain. A mature operation tends to use all three: partner news fills the base of the schedule, AI assembles the product piece, and the phone shortcut injects whatever is urgent and local.

And there is what stays out, which is worth stating plainly: delivery automation does not decide what to communicate, does not write the promotion, and does not replace the judgement of whoever publishes. It shortens the distance between the decision and the screen. The decision remains human work.

What to set up before switching it on

Neither mechanism is plug-and-play. The steps are few, but they exist:

  1. Credential and pre-authorization. FTP access has to be created and handed to whoever will use it. The podcast states this explicitly: you have to pre-authorize the person and pass along the access details. Treat that credential as system access, not as a wi-fi password.
  2. The shortcut, once per phone. The automation is built on each person's device. It takes a few minutes, but it is individual — and it is worth documenting the steps so you do not depend on whoever built the first one.
  3. A file naming convention. The library will receive material from several people. Without a simple naming pattern, someone will spend time guessing what each clip is — exactly the time the automation just saved.
  4. Agree on who publishes. A file landing in the library is not the same as it going on screen. Define who approves, and how quickly, so the process does not stall at the last metre.
  5. Format and audio. Record in the same orientation as the screen, and assume nobody will hear it: indoor TV runs without sound in the overwhelming majority of venues. Anything essential has to be visible in the image.
An honest test before scaling: pick one person, one screen and one week. If by the end of it the screen changed more often than in the previous month, the mechanism landed. If it did not, the bottleneck was somewhere else — probably in deciding what to communicate, and no delivery automation fixes that.

Want to try this flow in your operation?

JMV Indoor TV runs on an ordinary smart TV, with cloud scheduling and a 30-day free trial. To assess automated delivery in your own scenario, reach us through the contact form.

This article covers only the delivery-automation angle. The full episode covers indoor TV business models by segment — watch the complete "Podcast Tv Indoor 1" on YouTube.

To sum up: a stale screen is rarely a content problem, it is a path problem. An email that becomes a video and a shortcut that uploads the file on its own are not sophisticated features — they are operational shortcuts that give the person holding the information the ability to put it on screen the day it matters. On how we handle data on our side, see the Privacy Policy.

Frequently asked questions

Do I need to know how to edit video to keep an indoor TV up to date?
No. The two mechanisms described in this article exist precisely to remove that step: the standardized email that is automatically converted into a video clip, and the phone shortcut that sends the recorded file straight to the platform's FTP. In neither case does anyone open an editor, convert a file format or upload manually through the dashboard. What stays human is deciding what to communicate and approving when it goes on screen.
How does an email become a video automatically?
Someone sends an email in a standardized format to a configured address, and the content of that email is converted into a video file that enters the indoor TV playlist. In the Café & Tech episode behind this article, the example given was a short HR message, with a mention of a limit in the range of 50 characters. That figure came up in a live conversation with no further technical detail: the exact limit and the email formatting requirements must be confirmed with the technical team before being treated as a specification.
How does sending a video from a phone through a shortcut work?
Using the iPhone Shortcuts app, you build an automation that connects to the platform's FTP. The person records a short clip on their own phone, triggers the shortcut, and the file is sent to the server on its own, showing up in the media library ready to be scheduled. In the podcast, the host mentions that Android also has an equivalent app but could not recall its name at that moment, so this article does not name a specific Android app. If you are on Android, validate first that your chosen automation tool actually supports FTP uploads.
Is this the same as AI generating video from photos?
No, they are complementary. AI generation creates the piece from raw material such as product photos — the problem it solves is producing the content. The mechanisms in this article solve the next problem, which is transport: how content that already exists, or a request to update it, reaches the screen without editing and without a manual upload. An operation can use both: AI assembles the piece and the delivery automation gets it into the playlist.
Does a clip sent from a phone go on screen without anyone reviewing it?
It should not, and by default it does not. What the automation does is drop the file into the dashboard's media library; putting that item into the playlist is still an action taken by whoever administers the account. That separation is deliberate and it is what stops a clip recorded by mistake from ending up on the store screen. If you want to shorten that gap, agree on who has permission to publish rather than removing the review step.
What has to be configured before using the FTP shortcut?
Three things. First, the account's FTP credential has to be created and handed to whoever will use it — the podcast says this plainly: you have to pre-authorize the person and pass along the access details. Second, the shortcut has to be set up once on each person's phone, pointing at that address. Third, agree on a file naming convention, because the library will receive material from several people and someone needs to know what each file is.
Does a clip recorded on a phone look good on an indoor TV?
It works for the use case it serves: fast, time-sensitive communication such as an internal notice or a promotion on a product that needs to move. Two precautions help. The first is orientation: record in the same orientation as the screen, horizontal for horizontal screens and vertical for vertical ones, so you avoid bars. The second is audio: in the overwhelming majority of venues an indoor TV plays with no sound, so anything essential has to be visible in the image, not just spoken.
What kind of operation gets the most out of this?
Ones where content changes often and the person who knows about the change is not the person running the dashboard. The two scenarios named in the episode are exactly those: internal communication at a company with many employees, where HR needs to announce something today, and retail, where the stocker sees on the shelf which product needs to move. In operations with stable content that changes once a month, delivery automation solves little — there the gain sits in time-based scheduling instead.

Talk to the JMV Indoor team about your project →