?

 

© 2026 KokoroLinks · A Jinova Systems product · Operated by GoShizen Enterprises

The sample wedding

Priya and James are not real.
Their wedding invitation is.

This is a published invitation on a real link, with a real guest list and real replies behind it. Nothing on this page is a screenshot or a mock-up. Every link runs the same code a paying customer's wedding runs on, which is the only way you can judge it and the only way we find our own bugs.

Walk it in order. It takes about four minutes.

As a guest

  1. 01

    Open the invitation

    The wax seal breaks, the card rises. Four functions across Bengaluru and London, a countdown, the story, travel and visa notes.

    Open the invitation
  2. 02

    Open it as a named guest

    The same link carrying a guest token. The host sees the moment it is opened, and the reply form arrives already filled in.

    Open as Shreya
  3. 03

    Reply, for real

    Answer for the mehndi, the sangeet and the ceremony separately, pick a meal, leave a note. It is written to the real database through the real endpoint.

    Send a reply

As the couple

These are the actual dashboards, not pictures of them. They open read only: you can look at everything and change nothing.

  1. 04

    The guest list

    Forty guests, households kept together, tagged by side. The funnel from invited to opened to replied, with a nudge for whoever has gone quiet.

    Open it
  2. 05

    The replies

    Counts, a reply trend, meal totals for the caterer, per-function headcounts, and a one-page catering summary with no names on it.

    Open it
  3. 06

    The door

    The check-in list as it looks on the day, built to work on bad venue wifi.

    Open it

If you reply, where does it go?

Into the real database, through the real endpoint, exactly as a guest's reply would. Then it appears on the replies dashboard above, and the counts move by your party size.

Only for you. Everyone else sees the seeded guest list and none of your details. We did it that way so you can watch a reply land without a stranger's words ending up on a page we show to someone else. It is remembered by a cookie on this device, so clearing your cookies loses sight of it.