Loading...
Loading...
This video is about IT ticketing platforms and mentions Zammad, OurLocalHost.com, TrueNAS, Proxmox, Helm, Git, Unraid, Peppermint, UVdesk, Docker, Docker-compose, Linux server, Ubuntu, Debian, Docker-compose, Pangolin, Cloudflare, Twilio, Ollama, LM Studio, GitHub, GitLab, Gitea, IMAP, Facebook, Telegram, WhatsApp.
Full guide in Patreon. If you are considering running a #helpdesk or you need something to manage tickets internally for your business or even just your own little household projects, take a look at #Zammad , a very powerful and easy to install, helpdesk and #ticketing manager that'll take contact from multiple sources, has a accessible #knowledgebase and much more. @geekcubano
Performance Category
Average
Score
2.6/5
Shares: 3/5
Comments: 2/5
Retention: 2/5
Views: 3/5
Likes: 3/5
Followers: 2/5
Script: 3.1/5
Total Views
4447
Likes
174
Shares
5
Comments
6
Duration
6m 31s
For You
4,300
96.7% of views
Search
53
1.2% of views
Personal Profile
49
1.1% of views
Others
27
0.6% of views
Direct Message
9
0.2% of views
Follow
9
0.2% of views
Sound
0
0.0% of views
Views
Likes
Shares
Comments
For You Traffic
Profile Traffic
Search Traffic
Non-Followers
43.0%
1,912 views
Followers
57.0%
2,535 views
9.0% of followers reached
New Followers
3
Performance vs Median
Transcript Available
Perceived Value
63/100
Compared to Average
Average
"One of my TikTok followers, Danny, asked for a recommendation on an IT ticketing platform, and there are a few, but I've got one that I wanna recommend."
"Let me show you what it is, what it does, and then how to install it."
"The one I wanna talk about today is Zammad."
"I'll give you the steps and the guides in my Patreon, of course, but very straightforward."
"For everyone that cares, there is a dark mode."
The opening does identify the topic, but it does not make the benefit urgent or outcome-driven. After ignoring the natural swipe loss in the first 1-2 seconds as instructed, retention still declines from 63% at 2s to 46% at 5s and 38% at 6s, which is an anomalous early drop relative to the surrounding later pace. That suggests viewers understood the subject but were not strongly compelled by the framing. The first-15-second retention is still far above the video's average at every point (+58.1% vs avg at 2s, +41.1% at 5s, +33.1% at 6s), so the hook is not a total miss, but it is only moderately effective.
Lead with the decision and viewer outcome in the first sentence. Example: "If you need a self-hosted IT ticketing platform, this is the one I'd install today, and I'll show you setup in under 7 minutes." That gives audience, recommendation, and payoff immediately.
"One of my TikTok followers, Danny, asked for a recommendation on an IT ticketing platform"
The script quickly filters for the right viewer by naming an exact use case: IT ticketing, self-hosting, Docker, Linux server, Unraid, Proxmox, and Helm. That specificity likely helped retention remain well above the video's average in the first 15 seconds, including 24% at 14s (+19.1% vs avg), which is a positive sign for fit with a niche audience. However, because the opening starts with "one of my followers" before directly naming the viewer, the audience signal could still be tighter.
Address the target viewer directly in line one: "If you self-host and need an open-source IT ticketing system..." This keeps the niche filter while removing the indirect setup.
"asked for a recommendation on an IT ticketing platform"
The topic is specific, but the problem is not framed as a concrete pain. The script says someone asked for a recommendation, but it does not establish a real tension like cost, vendor lock-in, poor open-source options, or deployment friction. Retention from 10s to 14s only eases from 28% to 24%, which is a normal decline and not a collapse, so viewers are tolerating the setup. Still, the lack of a sharply defined problem likely contributes to the broader early fall from 63% at 2s to 25% at 12s, even though those points remain above average (+58.1% to +20.1% vs avg).
State one concrete pain early: "Most ticketing tools are expensive, closed, or annoying to self-host. This one is open source and deploys fast with Docker." One main tension makes the recommendation feel necessary rather than arbitrary.
"there are a few, but I've got one that I wanna recommend"
The viewer does get a broad roadmap: what it is, what it does, and how to install it. That clarity likely helped stabilize retention around 12s-13s at 25% to 25%, which is a positive plateau rather than an anomalous drop. However, the payoff is still generic; it does not promise a concrete end state such as "you'll have a working ticketing system on Docker" or "you'll know whether Zammad beats other options."
Make the outcome explicit and practical: "By the end of this video, you'll know why I recommend Zammad and how to launch it on Docker and access the web UI."
"Let me show you what it is, what it does, and then how to install it."
There is real informational value throughout, especially in the middle and later sections where the script names deployment steps, channels, SMTP, Twilio, AI, and integrations. However, the delivery includes filler, repetitions, and meandering phrasing that dilute the density. The early retention pattern shows a steady normal decline from 7s to 14s (33% to 24%) rather than repeated anomalous drops, which suggests the content is useful enough to keep the right viewer watching. Still, the length of 391 seconds with only 174 likes and 6 comments indicates moderate perceived value rather than standout value concentration.
Compress repeated phrases and remove side comments. Group value into tighter chunks: recommendation reason, install steps, key features, best-fit use case. Cut lines like repeated reminders and platform caveats unless they change the decision.
"like, like, uh... pretty good... not so bad... very straightforward"
This is the strongest part of the script. It uses dense, concrete nouns and operational details: Zammad, Docker Compose, TrueNAS, Proxmox, Helm, Unraid, SMTP, Twilio, Ollama, LM Studio, GitHub, GitLab, Facebook, Telegram, WhatsApp, API, port 8080. That depth strongly supports niche usefulness, and retention staying above average throughout the first 15 seconds is a positive sign that the technical specificity matched viewer expectations. The script sounds grounded in an actual workflow rather than generic software talk.
Keep this strength, but front-load the most important specifics earlier. Mention "open-source, self-hosted, Docker-based" in the first sentence to combine specificity with stronger hook performance.
"The one I wanna talk about today is Zammad... it's got a Docker... supported by TrueNAS, Proxmox, Helm"
The script sounds experienced because it compares alternatives, mentions installation choices, flags limitations, and demonstrates actual navigation through setup. Lines like noting it is not on Unraid "as far as I can see" increase trust because they show judgment instead of hype. The steady above-average retention in the first 15 seconds, plus a like concentration at 0s (53% of first-15s likes clustered at the opening), is a positive signal that existing viewers trusted the creator's recommendation framing. It is not a 5 because the recommendation criteria could be more evidence-based.
Add one or two concrete selection criteria: "I picked Zammad because it is open source, mature, supports Docker cleanly, and has the broadest channel integrations of the self-hosted options I tested."
"Zammad's been around for a long time, and they're very committed to open source"
The transcript feels human because it includes self-corrections, uncertainty markers, and practical caveats rather than polished sales language. Examples include fixing a previous directory, saying "as far as I can see," and acknowledging paid features. Those traits support authenticity. The retention curve from 12s to 14s is flat-to-gently declining (25% to 24%), a normal decline that suggests viewers were not repelled by the natural speaking style. It is not a 5 because the Patreon mentions introduce a slight promotional layer that interrupts the flow.
Keep the conversational honesty but reduce off-topic monetization interruptions. Move Patreon mentions to the end or a brief on-screen note so the recommendation feels fully viewer-first.
"Oh, I didn't delete the one before, so let me just remove"
The script is often hard to parse in real time because sentences stack clauses, tool names, caveats, and repeated qualifiers. Spoken filler like "uh," repeated phrasing, and long explanation chains increase processing effort. The gradual decline from 6s to 11s (38% to 26%) is a normal decline rather than a single anomalous cliff, which suggests the issue is sustained complexity more than one bad line. Given the long runtime and technical density, viewers likely had to work to follow the flow.
Break explanations into short commands and short reasons. Example: "Create a Zammad folder. Paste in the Docker Compose file. Start the container. Then open port 8080." Use one concept per sentence and save edge-case caveats for later.
"You can create a form, you can have it web hosted, publicly web hosted. You would add the HTML with, uh, that form, and you would need to insert the, this JS."
The video does move from recommendation to install to feature tour, but the progression is loose and often drifts into side branches. It spends time on directory cleanup, domain setup, forms, chat, AI, social channels, and checklists without a strong hierarchy of what matters most. The retention line does show a positive mini-plateau at 12s-13s (25% to 25%), but there is no evidence in the available first-15-second data of a sharp progression payoff kicking in. The overall long duration combined with only modest engagement (174 likes, 6 comments, 5 shares on 4447 views) suggests the structure delivered useful information but not a highly compelling narrative arc.
Use a clearer sequence: 1) why this tool wins, 2) 3-step install, 3) top 5 features, 4) who should use it, 5) one setup gotcha. That would create visible forward motion every 20-30 seconds.
"I'm gonna set up a new system... I'm gonna make a domain for this... we'll get back to in a second... There are integrations..."
S6yxpaywalling guides lol
I know, it's a shit thing to do, but I have no other way to make anything from this, belive me, if I could drain corporate entities of their ad money, I'd be doing that rather than charging for education but, tiktok doesn't have a creator program where I live, and YouTube requires 4000 hours of watch time before I can even start to get ad revenue. I also don't get any "brand deals", so I'm kinda out of options.
fenicican you look at AliasVault please. I love it so much but it's so small.
on it.
Dany GonzalezYou are the GOAT!
lol. I do what I can.
Total viewers and likes aligned with spoken words.