Can I tune how sensitive the alert is?

Adjust the score threshold in the filter. Raise it for only the clearest risks, lower it to catch more early.

enrich.entity attaches the CSM and renewal date, so the warning reaches the person who can actually save the account.

Can I combine several signals?

Emit each signal as it happens and dedupe by customer in a window, so one at-risk account is one alert, not three.

Catch churn-risk signals in Telegram

Turn the small signals — a downgrade, a usage drop, a support spike — into one scored alert that reaches the account owner while there's still time to act.

01source

sourcesdk.eventTypeScript SDK

matchchurn.signal

02pipeline · 2 steps

01ENRenrich.entitycustomer → CSM · renewal · MRR
02CTLfilter.matchscore ≥ 0.7 only

03destinations · 1

totelegramTelegram
chat@oncall

the event

You emit churn.signal with this shape. The TypeScript SDK keeps the call type-safe, and the event is stored whole — so every field below is available to the pipeline by name.

customer_idstring
signalstringdowngrade | usage-drop | support-spike
scorenumber0–1 risk
mrrnumberminor units at risk

emit it

From your code with the TypeScript SDK — or any language over the REST endpoint and signed webhook ingress.

emit churn.signal

import { ingest } from "@ingestlayer/sdk";

await ingest("churn.signal", {
  customer_id: account.id,
  signal:      "usage-drop",
  score:       risk,
  mrr:         account.mrr,
});

route it to Telegram

Message a person, group, or channel through a connected bot.

01
connect a bot
Create a bot with @BotFather and paste its token. We register the webhook and verify it in-region.
02
start a chat
Send /start to the bot from the target chat — or add it to the group/channel — then pick the chat from the list.
03
format the text
Messages use MarkdownV2; the default template bolds the event name and lists fields. Reserved characters in field values are escaped for you.

in telegramdelivered

oncall
*support.ticket.created*
ticket    T-4821
subject   API returning 500s
tier      enterprise
urgency   critical

notes

Telegram caps a bot at roughly 30 messages per second overall, and one per second to a single chat.
The bot must be added to a group — and promoted to admin for a channel — before it can post.
MarkdownV2 requires escaping characters like _ * [ ] ( ); ingestlayer escapes field values, but custom templates are your responsibility.

questions

Can I tune how sensitive the alert is?: Adjust the score threshold in the filter. Raise it for only the clearest risks, lower it to catch more early.
Who gets the alert?: enrich.entity attaches the CSM and renewal date, so the warning reaches the person who can actually save the account.
Can I combine several signals?: Emit each signal as it happens and dedupe by customer in a window, so one at-risk account is one alert, not three.

build this pipeline or read the quickstart →