Roadmap

• Alerts by text, phone call and email, with escalation until someone acknowledges, and reply-to-acknowledge by text.
• On-call schedules, overrides, escalation policies and routing by source and severity.
• Alerts from anything that can send an email or a webhook, with a list of allowed senders on each email inbox.
• Team logins, plans, prepaid credits and billing, and in-app support.
• Moving from Opsgenie: import your schedules, escalations and routing.
• Documentation inside the dashboard, and an independent check that tells us if Tocsin itself stops answering.

Trust

• A public status page for Tocsin.
• Download your organisation's data yourself, and see an audit log of changes made in your organisation.
• Notice when an escalation runs out and nobody acknowledged.
• Delivery receipts for texts and calls shown on each alert, and warnings for email addresses that bounce.

Money

• A low-credit warning, and optional automatic top-up, so you never run out in the middle of an incident.

Responding

• Acknowledge with one tap from a link in the text or email, with no login.

Running a rota

• Calendar feed of on-call shifts for Outlook and Google Calendar.
• Shift swaps and leave requests.
• Quiet hours and personal preferences, such as a text rather than a call before 7am for low severity.
• Handover notes for the next person on call.

Getting alerts in

• A voicemail phone line: leave a message and it raises an alert.
• Ready-made setups for popular tools, and detecting "resolved" emails.
• Slack and Microsoft Teams notifications.

Proving it works

• Fire drills: a scheduled test page that checks each person answers and how long it takes.
• A weekly digest of alerts and response times, and response-time targets.

Bigger teams and partners

• A partner programme for IT support firms: a separate organisation per client under one login.
• Single sign-on, and outbound webhooks so your own systems hear about alert changes.
• WhatsApp alerts.