Continental · TCP 3.0 · Demo Scenario 2

The retailer engages
his own members.

A retailer builds a store-scoped campaign targeting his own active members — not a head-office blast. The member gets a push, books, and the retailer sees it convert to sell-out. Open the apps side by side and watch the campaign flow live.

START HERE
🏪
Retailer · TyreCare Bangsar

Retailer App

Open Campaigns → Create store campaign: a "Store Anniversary" offer to members recruited in your store, active ≤ 12 months. Execute → it pushes to the member. Then watch bookings land and View results.

Open retailer demo →
📱
Consumer · Ahmad Rizal

Mobile App

The campaign arrives as a notification banner on Discover the moment the retailer executes. Tap Book › → pick the store → confirm. Watch the status timeline and rate the visit.

Open consumer demo →
🛠️
Continental · Operations

Admin Portal

The same appointment in the queue and a live activity feed — Continental sees the retailer's local campaign drive engagement and sell-out across the network.

Open admin demo →
Scenario 2 — the flow
  1. Retailer creates store campaign
  2. Target active members (≤12mo)
  3. Execute → push
  4. Member gets notification
  5. Member books
  6. Retailer Accepts · 360 upsell
  7. Complete →
  8. Retailer sees results

Live cause → effect (zero backend): open the Retailer App and the Mobile App side by side. In the retailer app, Campaigns → Create store campaign → Execute. A push notification appears on the consumer's Discover instantly. The member taps Book → the booking lands in the retailer's Appointments and in the campaign's results funnel, live. All three surfaces share one local store, scoped to this scenario.