On-call bot for Lark
The hard part of on-call is not the alert. It is not knowing who should respond. The on-call bot keeps rotations, handover, alert notifications and escalation rules in Lark, so the current responder is always clear and escalation does not depend on asking around.
What it solves
- When an alert fires, nobody knows who is on call.
- Handover lives in chat or a spreadsheet, so context gets lost.
- Escalation is unclear, and the incident circulates in the group.
Core capabilities
Rotation schedules
Configure on-call rotations by team and time window, so the group always knows who is responsible.
Alert @mentions
Alert notifications @mention the current responder instead of asking the group to look.
Timeout escalation
If an alert is not acknowledged in time, escalate to the next responder or owner.
Handover notes
Leave open items and context in the group when the shift changes.
How to connect
- Choose webhook or custom-app onboarding for this capability.
- Configure the event source, target group and notification rules.
- Send a test event and confirm the result in the group.
This page does not show the internal console. Configuration details and permissions are provided during onboarding, or contact sales to learn more.
Who it is for
- SRE and operations
- Engineering on-call teams
- Customer support on-call
FAQ
Can different teams have different rotations?
Yes. Rotations are configured per team and time window.
Do alerts have to come from Sentry or Grafana?
No. Other alert sources can connect through webhooks or the message push capability.
Related capabilities and solutions
Bring this capability into your Lark groups
Tell us about your team and use case. We will recommend SaaS or self-hosted deployment.