Frequently Asked Questions

How it behaves when something fails, and what you can see when something is slow. Those questions distinguish platforms far better than which provider is named, and they are the ones that matter at three in the morning.

It depends on the apps you run. The website needs a favicon and logos, the mobile apps need app icons, notification icons and splash screens, and each TV platform has its own icon or tile. Vodlix lists every slot per app and marks the ones required before that app can be published.

No. The brand kit holds your shared logo, colours and default splash, and every app reuses it until you override an asset for that app. Copy from app starts one app from another app's set.

Each app shows a readiness percentage and a Before you can publish panel naming the required assets that are still missing. When they are all in place it changes to Ready to publish and shows how many optional assets are still empty.

Tickets raised inside a Vodlix service arrive attached to the subscriber's account, with device, plan and history already visible, so your team skips the identity questions and addresses the actual problem first.

When you have a rota, service level commitments or multiple channels to manage. Deciding that before you commit is worth the thought, because moving support tooling later is more disruptive than choosing correctly at the outset.

Whoever runs your programming. Building and reordering lists happens in the admin area, so merchandising your home screen is an editorial task rather than something that waits on a release.

Fill in your metadata properly. Complete synopses and useful tags, including genre and mood words, are what search reads, so a catalogue that has been described carefully is far easier to search than one where only the titles were filled in.

You change the date. Because nothing is published until the moment arrives, moving a launch forwards or backwards is editing a field rather than unpicking something that has already gone out. That is the practical advantage of scheduling over publishing manually and hoping the plan holds.

Yes. Every Vodlix plan lets you connect your own domain, such as watch.yourbrand.com or yourbrand.com. You set it up in the admin under Vodlix Settings with Configure Custom Domain, add one DNS record at your domain provider, and verify it.

Use a CNAME record where you can; the admin marks it as recommended. It works for subdomains, and for a root domain when your DNS provider supports ALIAS or ANAME records. Use an A record only when your provider cannot add a CNAME.

Yes. Tick Enable www when you configure the domain and add the record for the www address as well. Verification then checks both addresses.

Yes, with one rule. A CNAME record works with Cloudflare. An A record must be set to DNS only (grey cloud); an A record behind the Cloudflare proxy (orange cloud) fails verification, so switch to a CNAME if you need the proxy.

Ask whether it describes how something needs to work or how it used to work in a system you are replacing. A surprising share of bespoke requests are habits carried over rather than genuine constraints, and that is worth twenty minutes before it is worth a proposal.

With the configuration you already have. Branding, pricing, languages, territories, quality and screen limits are all settings, and a meaningful number of requirements that arrive described as development turn out to be one of those that nobody had found yet.

Yes. Vodlix lets you preview and customise a new template separately from your live site, which stays untouched until you choose to activate the new one.

You can search by username, email, address or session ID, and filter by date range and by app on top of that. In practice that means whatever the customer tells you is enough to find the session, including the case where they only remember roughly when it happened and which device they were using.

Yes. Vodlix dynamic menus are lists you build and reorder in the admin area, with changes going live the moment you save, so a new link never needs a developer ticket or a release.

No. Navigation is configuration rather than code, so a change is live when you save it and reaches the web and the apps together.

Turn on the opt-in checkbox on your signup form and write its wording. Each viewer's choice is saved on their account and shown on the Email Subscribers screen, where you can also change it for one viewer or for a selected group.