On-Call Handover
On-call handovers are where context goes to die. The outgoing engineer has critical information about ongoing issues, monitoring quirks, and pending actions — but the incoming engineer gets a two-line Slack message at best. Tellagen provides a structured shift workspace that makes handovers reliable.
Shift notes that persist
Each shift has a dedicated notes space where on-call engineers document ongoing issues, things to watch, and actions pending. Notes carry forward between shifts until explicitly resolved, so nothing falls through the cracks during handovers. The incoming engineer sees exactly what the outgoing engineer wanted them to know.
Recurring links and dashboards
Every on-call shift needs the same set of dashboards, runbooks, and monitoring pages. Tellagen lets teams configure recurring links that appear on every shift view. No more hunting through bookmarks or asking in Slack for the Grafana URL.
Handover checklists
Configurable checklists ensure outgoing engineers cover critical handover items: active incidents, pending deploys, known monitoring gaps, escalation notes. The checklist is visible to the incoming engineer so they can verify the handover is complete before the outgoing engineer signs off.
Incident context in shift view
Active and recently closed incidents are surfaced in the shift workspace with timeline summaries. The incoming on-call engineer can review incident status and recent decisions without switching to separate incident pages.
Capabilities
Frequently asked questions
Does Tellagen integrate with PagerDuty schedules?
Tellagen manages its own shift workspace. It complements PagerDuty by providing the handover structure that PagerDuty's on-call scheduling does not cover — shift notes, context preservation, and handover checklists.
Can multiple teams have separate shift configurations?
Yes. Each team has its own shift workspace with independent notes, recurring links, and checklists. Teams can configure handover templates that match their specific processes.
What happens to notes when an issue is resolved?
Notes carry forward between shifts until an on-call engineer explicitly marks them resolved. Resolved notes are archived but remain searchable for reference.