Skip to content
  1. Home
  2. Help center
  3. Account & billing
  4. Settings → Notifications

Settings → Notifications

Last updated:

The Notifications screen answers “who does KO write to, and about what”. A recipient here is an address, not a KO user: messages also go to people without an account.

What you see here

A single table of recipients:

  • Recipient — the name and the address, with the channel next to it: Telegram, E-mail or SMS.
  • State — Awaiting confirmation, Confirmed, Unsubscribed, Disabled or Blocked.
  • One column per notification type — a tick means this recipient is subscribed.
  • Last sent — when the last message went out and how many errors there were.

There are four types today:

  • Leads — a new enquiry, for whoever sells.
  • Integration failures — a connector is down or returning errors, for whoever fixes it.
  • Service balances — a connected service is running out of money or time.
  • Data gaps — tracking is silent, forms are not submitting, tagging is broken.

There is no separate “type is on” switch. A type works exactly when someone is subscribed to it. Two ways to switch the same thing off breed the permanent question “why is nothing arriving, the box is ticked”.

Set it up for your question

Add a recipient

  1. Click Add recipient… in the section header.
  2. Choose where to send — the channel. An unavailable channel carries its reason.
  3. Enter the address and the name. Or take a project member’s address with From project team.
  4. Confirm the address:
    • for Telegram — copy the link and hand it to the person; they open it and confirm themselves;
    • for email — a confirmation link is emailed to the address.

Subscribe to types

The type ticks are set right in the table. Subscribing is switching on: while nobody is subscribed to a type, it does not work.

Check that messages arrive

Test in the More actions menu sends a test message to that address on that channel. It is the fastest answer to “is this actually set up”.

Remove a recipient

Delete — they stop receiving notifications. Block is stronger: re-inviting that address will require a manual action.

How to read it

A Telegram group is a recipient too, and its membership lives in Telegram: KO does not manage it. Adding a person to the group gives them every notification the group is subscribed to.

“Awaiting confirmation” is not a fault, it is the normal first step. Until the address is confirmed nothing goes to it: confirmation protects people who did not ask to be written to.

“Unsubscribed” is set by the recipient, not by you: in Telegram by a command to the bot, in email by the unsubscribe link. Only a new confirmation from their side brings them back.

The “Last sent” column answers “is this working” faster than any test: if it says “Nothing sent”, either there have been no matching events yet or nobody is subscribed to the type.

Notifications used to be configured inside a connector. If the project was set up before August 2026, the settings have already been migrated here; adding the first recipient on this screen completes the switch.

If there are no numbers

  • “No recipients — notifications go nowhere” — that is the reason. Start with Add recipient….
  • There is a recipient but no messages — check three things in order: the state (Confirmed), the tick on the type you expect, and the Last sent column.
  • A channel is unavailable when adding — the reason is right there: either the engine does not raise such events yet, or a connected sending service is required.
  • Errors in Last sent keep growing — the address stopped accepting messages: the person may have blocked the bot, or the mail server is bouncing.

What’s next to it