VOKO · How it works

Draw it. Launch it. See the numbers.

Product and retention build the journey on one canvas, test it in shadow mode on real players and see the numbers on every step. Nothing reaches a player until you say so.

Schedule a Call

Your stack executes. VOKO decides.

Your tools execute

  • →Send the email or push
  • →Credit the bonus or start the mission
  • →Show a game mechanic
  • →Send a reminder or an agent task
  • →Call any of your services by webhook

VOKO decides

  • →Which stage every player is in right now
  • →What happens next, and when
  • →Which branch they take, including A/B
  • →When to wait for a click, a deposit or a timeout

The path to live.

  1. 1

    Draft

    Product and retention build stages and steps on one canvas.
  2. 2

    Simulate

    Run a test player through it: events, time shifts, effects.
  3. 3

    Shadow

    Real players, real events, real funnel. Nothing sent.

  4. Live

    Publish an immutable version and go live stage by stage.

  • Two switches, both off by default

    One for the organisation, one for the journey. An action runs only when both are live.

  • Effect caps

    Effects are capped per minute for each organisation. Anything above the cap is delayed, not dropped.

  • One event, one bonus

    Each action is identified uniquely, so a replayed event never pays twice.

  • Inside your perimeter

    For large operators we discuss installing VOKO on their own infrastructure.

A player card your support team can read.

Opened from the Players section. Built for the agent on the other end of a chat, not for the analyst.
  • Every journey the player is in, welcome to win-back, with their current stage.
  • Timers you can read, so you can tell the player when the next thing happens.
  • Click a transition to open the full path: which stage, when, and where next.
  • The effects list: bonuses, mechanics and webhooks the journey produced for this player.