Skip to content
English
Explore features

Grow your audience with clear choices.

Waitlists, referrals, newsletters and more — in one place. Give your community simple ways to join, share and stay engaged.

Try a referral example

More ways to grow. Clear rules for joining and sharing. Your brand, your choices.

A referral, from share to confirmation

Switch views to see the participant journey and example owner configuration.

Browser example only · No invitation is sent.

Browser example · Fictional records. No email, enrollment or real access is created.

Invite a friend to Kottoko

Share an example link. A referral counts only after the friend confirms their email. Sharing or clicks alone do not count.

Your example status

Interest request
Awaiting confirmation
Verified signup points
0
Effective points
0 / 3
Chronological wave after confirmation
Second wave
Projected wave
Awaiting confirmation
Example referral link

Only a confirmed request bound to a verified account can create a personal referral link. This example uses a fictional verified recipient.

Referred signups

A referral counts after a friend confirms their email. Sharing or clicks alone do not count.

A unique verified signup earns one point. Existing signups and self-referrals earn none. Four valid records demonstrate the effective cap of three.

  • Example signup 1Awaiting verification
  • Example signup 2Awaiting verification
  • Example signup 3Awaiting verification
  • Example signup 4Awaiting verification
  • Existing signupAwaiting verification
  • Self-referralAwaiting verification

Your invitation

Your reserved place
Not reserved
Your invitation
No invitation prepared
Project access
Not active
Invitation history

Steps show local actions in order; they are not delivery evidence or real timestamps.

No invitation transitions yet.

Invitation notification preferences

These local choices are separate from newsletter consent. They send no message and do not grant or withdraw access.

Rules and installed setup

A live project needs Growth and Invitations, verified Accounts, declared capacity and permitted operator actions. Its server owns allocation, recipient credentials, email delivery, retention and access. Public feature switches govern this local example only.

Confirmed signups

Counted only after email verification.

This is example configuration. No live activity or people are shown.

Reward boundary

If enabled with Commerce, a verified qualifying paid order can earn 30 days of digital access after 14 days without a full refund or dispute. This is separate from invitation priority.

Signup points cannot earn a paid-access reward. With Commerce, a server-verified qualifying order and a completed 14-day hold may earn one 30-day digital-access grant through existing entitlements. Full refunds reverse it; disputes require review. This example issues no reward.

Changes stay in this mounted browser example. Reset affects only these sample records, not saved page copy or other Growth examples.

Six ways to grow and engage

Different jobs. One coherent community experience.

WaitlistsCapture interest and manage access with clear positioning.ReferralsLet people invite friends. Verified signups can affect capped invitation priority.InvitationsSend targeted invitations when you are ready to expand.NewslettersKeep people informed with double opt-in and preferences.AffiliatesWork with partners using a separate commission program.ProgressGive members a private sense of progress and achievement.

More examples

Send only to people who confirmed.

Follow a subscription from consent to a reviewed audience. Keep preferences and opt-out within reach.

  • Confirmation is required before a subscriber joins an audience.
  • Review the content, topics, audience and schedule together.
  • Unsubscribe and suppression exclude people from delivery.
Setup and limits

Installed newsletters use Content revisions, account permissions, exact consent and mandatory double opt-in. A reviewed schedule includes its timezone and eligible audience. Delivery needs separately configured transport. When Newsletter is inactive, retained privacy access and unsubscribe remain available; new confirmation and preference changes do not.

Open technical reference
Newsletter example · Example data

Try a subscription

This fictional address stays in the example. No email is sent.

[email protected]

Email preferences
Not subscribed

Choose topics and consent, then simulate a signup.

Browser example only. Confirmation, preferences and review are local previews. No real subscription or email is created.

Follow a commission into its statement.

See how applications, confirmed attribution and commission evidence fit together. External payments stay separate.

  • An application needs authorized review before activation.
  • Commissions use eligible net revenue and stay separate by currency.
  • Disputes and external handoff preserve original evidence.
Setup and limits

Installed Affiliate needs account authority, Commerce-verified payment, explicit product eligibility and versioned terms. Customer confirmation applies at each eligible checkout. Pending commission finalizes only after the hold and applicable refund deadlines. Handoff requires threshold, readiness, permissions and expiry checks. Payment happens outside Kottoko.

Open technical reference
Affiliate example · Example data

Apply to an example program

Example terms: explicitly eligible products, 10% of eligible net revenue, a 30-day hold subject to longer refund deadlines, and a €5 handoff threshold. These are fictional terms, not an offer.

No example application submitted.

Fictional application, commissions and evidence. No enrollment, customer tracking, financial liability or payment is created.

Progress stays yours.

Follow verified milestones privately. Choose whether to share a recognition, and keep corrections understandable.

  • Understand the next step through verified project events.
  • Keep private progress separate from optional recognition sharing.
  • Ask for a correction without erasing the original history.
Setup and limits

Installed progress uses server-verified milestones in a project-defined journey. Recognition has no points, monetary value or access effect. A project may permit sharing, but only the participant chooses each share. Corrections and withdrawal preserve history and revoke an outdated public projection.

Open technical referenceExplore the member area
Progress example · Example data

Private project journey

Choose an authored sample state. These controls do not verify your own activity or create real progress.

  1. Choose a project goalVerified in this sample
  2. Review an example pageVerified in this sample
  3. Complete the project reviewVerified in this sample

All required sample milestones are verified. Recognition and its history remain separate.

Recognition

A recognition describes completion. It does not grant money, points, discounts or access.

Project review completed

Only the recognition is shared. You can stop sharing at any time; private progress is never included.

Private by default. No public recognition preview is shown.

Ask for a correction

Choose a factual issue for this sample recognition. A request waits for review and does not rewrite milestones or recognition.

Inspect private history and correction samples
  • Sample history: verified completion recorded; recognition issued privately.

Private history never enters the shared projection. Revoking a share does not erase history.

These are independent observations. Selecting one revokes the earlier sample share and does not resolve your pending correction request.

Example data only. No real progress, recognition, public link or account permission is created.

Referral outcomes

See what happens when a link is valid or expired, a signup is a duplicate, a referral point is reversed, or referrals are turned off.

The example link can be shared. A referral is counted only after a new signup is verified.