It helps, but it is not a blocker. The module expects a catalog with images, categories, variants and prices — most businesses prepare that content first and configure it in 2-4 hours.

Yes. The catalog supports simple products and products with variants, add-ons and recurring promotions — all managed from the same business dashboard.

Yes. Ecommerce plugs into Referral, Loyalty Card, Multichannel Notifications, Form Builder and Promo & Coupon — discounts and rewards run inside the same ecosystem.

Yes. Add as many branches and operators as you need — each with its own services, price list, working hours and availability — and manage every location from one business dashboard.

Yes — reminders are the fastest win. Set confirmations and reminders before you launch and you cut no-shows from day one. You can fine-tune timing and messages later.

Absolutely. Any appointment-based service works — clinics, coaches, tattoo studios, repair shops, consultants. If you sell it in time slots, Salon Booking handles it.

No — that is the whole point of the module. You edit the content in the dashboard and it updates in the app instantly: no app-store release, no developer, no waiting.

Yes. Link it from the homepage, a push notification or another module and use it as the landing page for a campaign, an event or an onboarding flow — fully inside your app.

For most pages, yes. Custom Page is block-based and mobile-optimized out of the box, so anyone on the team can build with it. Choose Custom HTML only when you need fully bespoke markup.

Points are faster to launch and easier for customers to understand — start there. Tiers shine when you want to reward long-term loyalty with status and perks. Many businesses run both: points for everyday actions, tiers for the customers who stick around longest.

Yes — and it is one of the smartest combos. Award points for a successful referral, a first purchase or a review, and your customers start doing the marketing for you. Loyalty plugs straight into Referral, Ecommerce and Multichannel Notifications.

No. Three to five relevant, reachable rewards beat a catalog full of options nobody can unlock. Start small, watch which rewards get redeemed most, and expand from there.

Yes — that is exactly how it is designed. Run confirmations, reminders and alerts on one side, promos and re-engagement on the other, all from the same template system. Keep the two streams visually distinct so customers always know when it is about their order… and when it is an offer.

They do — and the module makes that easy. Panel, app and message copy share the same language structure with fallback logic, so a missing translation never turns into a broken notification. Align them once and every channel stays coherent.

Start with the 3-4 messages with the biggest operational impact: order and booking confirmations, the reminder before an appointment and one follow-up. Those alone cut support questions and no-shows — then add promos once the basics run clean.

Yes — and you should. Build a dedicated form for each goal: a quote request on your landing page, a short survey after purchase, an onboarding questionnaire on a custom page. Each form keeps its own fields, confirmation and notifications, and every submission stays organized in the dashboard.

Almost always. Every extra field costs you completions — ask only for what you truly need to act on the request. If a longer form is unavoidable, split it into logical sections so the user always knows how much is left. You can collect the rest later in the conversation.

Every submission lands in the business dashboard with full details, timestamp, consent status and handling status — so your team reviews and handles leads in one place instead of digging through WhatsApp and email threads.

They solve different problems. Webview is for content that already lives on a website — a booking portal, a policy page, a campaign landing — and you want it inside the app today. Custom Page is for content you build natively in Klikko with blocks. Rule of thumb: if it already exists on the web and stays updated there, use Webview; if you want it to feel like a real app screen, build a Custom Page.

We don't recommend it. Simple, mobile-tested flows usually work, but complex checkouts depend on scripts, redirects and 3D-secure handshakes that behave differently inside an embedded view. For anything payment-critical, open it externally in the browser or use Klikko's built-in ecommerce and payments — you keep conversion high and support tickets low.

Yes. The same webview item runs on iOS, Android and PWA, with per-channel opening rules — inside the app where the content works well, externally where the browser is safer. Test once on Web and PWA before release and you're covered everywhere.

Conversion — every time. Rewarding shares floods you with signups that never buy; rewarding the invited friend's first real action ties every euro of reward to actual revenue. Keep a small perk for the invite itself if you want volume, but put the real budget behind conversions and your acquisition cost stays under control.

Perfectly. Pay referral rewards in loyalty points or benefits instead of cash and the two modules feed each other: the invite earns points, the points drive the next purchase, and the next purchase triggers another invite. It is the cheapest retention loop you can build in Klikko.

Yes — the panel shows generated invites, registered referrals, conversions, rewards issued and acquisition cost per channel. You see which codes perform, which rewards actually convert and what each new customer really costs you — instead of guessing from word of mouth.

Not always — modern browsers block autoplay with sound, so on Web and PWA the stream usually starts after a user tap. The module handles this gracefully: a clear "tap to start" state, no broken player, no confusion. Inside the iOS and Android app, playback starts from the in-app play control with background playback and media notifications — so your listeners hear the channel, not a silent bug.

Yes. When your stream carries now-playing metadata, the player shows the current show or track live — artwork and title included. When metadata is missing, the module falls back to your curated artwork, station title and schedule, so the screen always looks intentional instead of empty.

Yes — it is the one test that separates a real radio channel from a toy. Give it 20 minutes on real devices: lock the screen, take a call, switch apps, drop the signal and come back. If the stream resumes and media controls respond, your listeners get a broadcast-grade experience; if not, you would rather find out before they do.

Not at all — generic chat is exactly the problem this module removes. Every thread is anchored to a real business event: an order, a booking or a form submission. The operator opens the conversation already seeing the amount, the date and the request, so nobody wastes the first three messages asking "can you send your order number again?". It is operational support, not small talk.

Yes — that is its core job. Threads get assigned to a specific operator, picked up, put in progress and closed, and the whole team sees the status at a glance, so nobody answers the same customer twice. Internal notes let operators and backoffice collaborate on a case without the customer reading the debate, and the full history stays attached to the thread — handovers between shifts take seconds, not ten minutes of retyping.

No — they solve opposite problems, so you can comfortably run both. Community Hub is a social space where your customers and members talk to each other; Communications Hub is an internal operational inbox where your team handles orders, bookings, forms and support. One is your audience's living room, the other is your back office. Keeping them separate is exactly what keeps both clean.

Yes — and when prizes have real value, you should. Tie the campaign to your login flow and every play, claim code and redemption lands on a real profile instead of an anonymous device, which means no duplicate wins, no code resellers and no "my cousin already used it" disputes at the till. Guest play is still possible when you simply want reach — you choose the trade-off per campaign.

Absolutely — that is what makes it a premium campaign tool instead of a coin flip. Build a full prize pool where each prize carries its own draw weight, stock and claim instructions: a hundred small coupons, thirty freebies and exactly three VIP bundles, with the odds exactly as you set them. When a prize runs out it simply stops dropping, so you never promise what you cannot deliver.

Yes — and during a live promo that little tile is prime real estate. Drop the Scratch & Win tile on your app's home layout and the campaign becomes the first thing users see when they open the app, which is exactly what pulls return visits during the promo window. When the campaign ends, the tile goes quiet and your home goes back to normal — no rebuild, no new release.

Yes — and running both is where the retention comes from. Public rooms give your community a buzzing square, private rooms keep VIPs or ambassadors in a quieter space, and 1:1 direct threads handle the conversations that should never be public. Users move between all three in the same messenger-style UX, so it feels like one living app instead of three bolted-on features — and the smart unread badge always points them back to the one thread with something new.

Yes — you decide what the community is allowed to drop into a conversation. Keep attachments on and threads come alive with photos and inline image previews; restrict them when you want a clean, text-only space with almost no moderation overhead. Moderators can delete anything that breaks the rules straight from the control room, so a lively chat never turns into an unmoderated file dump.

Less is more. Fire push only on the first unread message — a direct mention, a 1:1 thread, or the first message after a user went quiet — and let the in-app unread badge handle the rest. That way a notification stays a reason to open the app instead of a reason to mute it. Communities that push on every single message train their best users to turn notifications off completely.

Opposite directions. Community Hub is your audience's living room — customers and members talking to each other in rooms and direct chats. Communications Hub is your back office — an internal inbox where your staff handles orders, bookings, forms and support. One grows engagement and retention, the other keeps operations fast. Plenty of businesses run both: the community keeps people inside the app, the inbox keeps the team sane.

No — the games are original and shipped inside the module, so there is literally nothing to source, license or upload. Your only creative decisions are the fun ones: pick a card back, pick a table color, set draw mode and undo, and the whole thing looks like it was built for your brand. That is why setup takes 10-15 minutes instead of the usual content marathon.

Yes — anyone can sit down and play a round, which keeps the feature friction-free. What requires login is saving the score: only logged-in results reach the leaderboard, and that is the default setup for a good reason. It keeps the rankings clean and real, and it quietly nudges anonymous players to create an account the moment they land a score worth bragging about.

That is exactly how the module is built — Solitaire, FreeCell and Memory today, with new titles landing in the same Games module as they ship. No new activation, no new configuration marathon, no second tile to redesign: your appearance settings, rules and leaderboard keep working exactly as they are. You get a games shelf that grows while your setup time stays flat.

No — the app or PWA you already use is enough, so there is no extra player to buy, install or maintain. Pairing takes a minute: open the Profile tab on the device, scroll to the bottom, tap the version number for hidden kiosk access and scan the display's pairing code. From that moment the device boots straight into the playlist, every restart included.

The loop follows along — you never walk over to the screen with a USB stick. Reorder items, change a duration, rewrite a text card or swap a widget from the panel and the display picks it up in the running loop. That also means a flash offer can go live on the shop-window screen in the same minute you decide to run it.

Yes — every widget keeps its own configuration dialog. Reopen the same item later in the playlist, fix what you need and save: the item stays exactly where it is in the order, with its duration untouched. Pair that with the Preview popup before going live and a typo never reaches the shop window.

Absolutely — that is what displays are for. Create one display per physical screen, each with its own name, orientation and playlist: the shop window runs the promo video and menu, the waiting room shows packages, the counter shows loyalty rewards. And if a screen goes away, unpair it right away so your "active displays" numbers stay honest.

It opens automatically, and that is exactly the point. The popup is not a tile your users have to find and tap — it appears the moment the app opens, so your message meets them before anything else on the screen competes for attention. Behind the scenes it runs as a system runtime component: the business configures creative, timing and rules in the panel, and the app simply shows the right campaign in the right moment. You still decide the entrance (a short delay after open) and the exit (automatic close or an explicit close), so it reads like a well-mannered announcement, never a trap.

Yes — audience is one of the core settings of every campaign. Publish to everyone, or only to logged-in users, so you can split the message: a public promo for the world, a private notice for your registered customers. Combined with per-user limits and a clear time window, a single popup becomes a precise instrument — a welcome-back reward that only returning users ever see, instead of the same banner blasted at everybody.

Yes, and you never have to worry about them colliding. Each popup carries its own time window and priority, and at every app open the module shows the highest-priority campaign still valid for that context — the others simply wait their turn or retire when their window closes. That means a flash promo, a welcome message and an operational notice can all live in the same week: the flash promo takes the screen while it matters, and everything else runs quietly in the background.