Templates & blueprints
The playbook in copy-paste form — for any format: video, UGC or slideshow. Copy, fill the [brackets], post.
The content blueprint — beat by beat
The structure that sells — regardless of format. Whether you talk to camera, voice over clips, or build a slideshow: these 5 beats stay the same, only the medium changes. And whether it's a full route, a “things to do in [place]”, a hotel check or a vlog — the move is always the same: show concrete, repeatable travel info and, at the end, say you planned it all with travo.ai.
How to carry the beats into your format
Speak the beat to camera or as a voiceover over your clips.
Speak the beat, lay matching footage or a screen recording on top.
Write the beat as text across 1–3 images.
This is [destination]?! And here's how little [X days] here costs — with tips nobody tells you 🧠
Let's start with the expensive part — the flight: only [price] [show/screenshot]. My tip: [e.g. book Tue/Wed].
[Place/highlight]: [what you do] for [price], slept at [hotel] for [price]/night 🧠 [tip you'd otherwise only learn on the ground]
And what it all costs together? Coming up — you won't believe it 💸
Total: [odd number] 🤯 Planned entirely with travo.ai — route, hotels & activities in minutes. 3 days free, code [YOUR-CODE].
Checklist — for any format
- ✓Hook in the first 2–3 seconds: expectation break + promise
- ✓Concrete, odd prices instead of rounding — proof beats a claim
- ✓Show real app results (screenshot/screen recording), not rebuilt graphics
- ✓Hold the total/reveal until the very end (tension)
- ✓At the end, name the app + code clearly — spoken AND as text/caption
- ✓Keep it tight: every moment without new info is an exit point (slide or second)
Hook patterns & CTA rules
The hook decides 80 % of performance — the CTA decides whether views become a sale. With your face and voice (personal brand) the same hook converts significantly better. Works equally as a spoken line or a text overlay. Don't copy 1:1, adapt to your destination — swipe sideways for more options →
Top patterns (proven strong)
Expectation break + instant proof right at the start:
More patterns to adapt
Variation is welcome — test what fits your channel and style:
CTA rules (at the end + caption)
73 % of subs come through App Store search — the app name IS the search term. Concrete beats vague. Name the app + code in at least two places (in the content itself + in the caption). And: sell the value proposition (whole trip planned in minutes, tailored to your interests), not just the price — that decides your earnings.
Check before posting
- ✓Hook adapted (not copied 1:1)
- ✓Expectation break + number/proof right at the start (first seconds / image 1)
- ✓App's value proposition clear? (Complete planning — not just “cheap”)
- ✓App + code in 2 spots (in the content + caption)
Caption, pin comment & 🧠 tips
The second CTA after the post: a pinned comment with the app name. Plus five 🧠 aha-tips that drive saves — copyable and universal, no matter the format.
Caption template
Pin comment (pin right after posting)
Flip the objection (reply to “paywall …”)
🧠 aha-tips (universal, save-worthy)
Criteria: 100 % universal, unknown local service, concrete price contrast, solves a real problem. As a template — swap in your destination:
Comment hygiene
- ✓Pin comment with the app name set right after posting
- ✓Never delete correction comments — pin your own correction instead
- ✓No image comments with a store screenshot (spam flag)
- ✓Answer concrete questions fast (= someone is planning = a sale)