Works with:
Third-party marks are the property of their respective owners. They are shown to indicate compatibility only, with no endorsement implied.
On call built
for Australian MSPs.
Alert routing from your RMM. Ticket sync to your PSA. Built for Australian MSPs to cut on-call burnout, reduce staff turnover and get full visibility into every shift.
Already on PagerDuty or Opsgenie? Import your schedule in 60 seconds →
Integrations that work for you
Notifications to the tools your team already use
Channels you already use, alerts you can trust
Get notified when your engineers shifts start, handover summaries, schedule gap warnings, and pending-item reminders
See it in action
A clean, purpose-built UI your team will actually use.
Duration: 8h 12m
Alerts routed to whoever is on call
RMM and monitoring alerts route to the engineer on your Shiftctl schedule, escalate over SMS, voice, Slack, email and push until acknowledged. Any alert, open or closed that shift, carries into the next handover. Straight to the next engineer.
Sound familiar?
Handoffs over Slack
Critical context gets buried in team chats or an engineer's memory. The incoming engineer spends 30 minutes piecing together what's happening or scrolling through last weeks messages.
No structured sign-off
Engineers finish their rotation and walk away with everything still in their head. Open tickets, pending items, context the next engineer needs. Nothing handed over.
Zero coverage visibility
You don't know who's on call, who escalates after them, what team they're in, or how to reach them. The handover document, if it exists, is somewhere in Slack from three weeks ago.
Structured briefs replace the 30 to 60 minutes it takes to reconstruct context from chat scrollback.
Straight to your engineers slack, email, SMS and voice call.
Round-the-clock response is why clients sign and why they leave. (Barracuda, 2025) Make sure your on-call software isn't the reason.
How the handover works
Four steps. Every shift accountable. Full engineer context.
Your shift starts automatically
Shiftctl starts your shift on schedule and sends you a notification. Open the app and read the full incoming brief from the previous engineer. No surprises.
Work your shift with full context
Log tickets as you resolve them throughout the shift. Pending items are always visible so nothing slips through. Every action is timestamped and recorded for the handoff.
Complete your sign-off
When your shift ends the engineer begins the 4 step sign-off process where all reported tickets, pending actions and shift difficulty rating are logged.
Next engineer is notified
The moment sign-off completes, the next scheduled engineer gets notified. A summary is posted to them via email and Slack. Context in as little as 3 minutes.
On Enterprise, alerts run the same loop: an alert fires from your RMM or monitoring → Shiftctl routes it to the engineer on call and escalates until acknowledged → any alert still open at sign-off carries into the handover brief.
Everything your on-call team needs
From the first alert to the final handover, Shiftctl keeps every step accountable.
PSA ticket sync directly in Shiftctl
Tickets created in shiftctl are one way synced to ConnectWise Manage, Autotask PSA, or HaloPSA. Status updates however sync both ways, never losing you critical information on call again.
Alert routing (Enterprise)
RMM and monitoring alerts route to the engineer on call. Configure however you prefer: SMS, voice, Slack, email or all! Every alert, open or closed that shift, carries into the next handover.
Manager insights
Track shift difficulty trends, engineer on-call burden and handoff brief statistics, all in one place. Export a clean PDF report or schedule it to land in your inbox.
PagerDuty import & live sync
Already running on PagerDuty? Connect your iCal feed and Shiftctl syncs your schedule automatically, every hour. Or do a one-time import from any iCal source. Works with PagerDuty, Opsgenie, and any iCal feed.
Email & Slack alerts
Handoff summaries, shift start/end alerts, coverage gap warnings, and daily on-call digests, posted automatically to your Slack channel. @mention the right engineer every time.
Want the full picture? See all features in our docs
Simple, transparent pricing
Start with a 14-day free trial. Team tier when you need integrations and analytics. Enterprise tier when alerting and compliance get involved.
14-day free trial · full access · no credit card required
Start 14-day free trialFor MSPs that want to enhance their existing alerting and paging with structured handovers, roster management, and analytics.
- Unlimited members
- Shift sign-off & handover briefs
- Auto-scheduling & multiple on-call teams
- PagerDuty / Opsgenie import & live sync
- PSA integrations: ConnectWise, Autotask, HaloPSA
- Data Hub analytics & scheduled PDF reports
For MSPs who need on-call alerting RMM and PSA integrations and compliance reporting across all clients.
Startup Program: 50% off your first 12 months on annual billing. First-year Enterprise costs less per seat than Team. Applied automatically at checkout.
- Everything in Team
- Alert routing & escalation from your RMM/monitoring
- SMS, voice & push paging to the on-call engineer
- Heartbeat monitors for backups & scheduled jobs
- Per-client reporting & QBR export
- Compliance suite: Azure SCIM, audit log, custom data retention
Questions? Contact us
Start your 14-day free trial with full access and no credit card required. Pick a plan as your team grows and your ops mature.
How much is unmanaged on-call costing you?
Expand “How we calculate” below to view the sources.
After-Hours Alert Exposure
Without paging, an overnight critical waits ~30 min for a response. Shiftctl's escalating push, SMS and voice paging targets a 5-min ack, removing 25 minutes of client downtime per alert.
At 48 critical alerts/year, that's A$247,380/year of client downtime exposure, at a conservative SMB downtime cost.
Client Retention
23% of SMEs have fired an MSP over poor service, and 45% will switch without demonstrated 24/7 capability. One client at A$2,350/mo is A$84,600 over a typical 3-year tenure.
And it cuts both ways: 92% will pay up to 25% more for advanced 24/7 coverage. This is a service you can sell, not just churn you avoid. Shiftctl for your whole team: A$140/mo.
Engineer Hours Saved
52 handovers/year, each costing ~50 min in handover plus context recovery, add up to 43 hours/year lost.
Shiftctl's structured brief cuts this to ~3 min, saving 41 hours/year of senior engineer time.
How we calculate these numbers
Downtime cost: $133/min is Datto's SMB downtime figure ($8,000/hour, Global State of the MSP Report), deliberately the conservative end. Enterprise studies run $4,500 to $15,000 per minute.
Response delta: teams with escalating paging acknowledge in ~4 to 5 minutes (incident.io telemetry across 100k+ incidents); overnight response without paging tooling commonly takes 30+ minutes. We use a 30-vs-5-minute delta and count only that gap, not full resolution time.
Retention stats: 23% / 45% / 92% are from the Barracuda MSP Customer Insight Report 2025, fielded independently by Vanson Bourne (n=2,000 SME IT decision-makers). Client value assumes a 3-year tenure.
Handover time: 30-minute reconstruction baseline plus context-recovery time that scales with rotation cadence (5 to 50 min), anchored by Gloria Mark's (UC Irvine) finding that interrupted work takes ~23 minutes to fully re-enter. Shiftctl reduces the handover to ~3 minutes.
Pricing: Shiftctl cost shown for the Enterprise plan billed annually (alerting and paging live there). Prices in AUD are approximate.
Frequently asked questions
Everything you need to know before getting started.
Yes, for most teams. Shiftctl routes and escalates alerts from your RMM or monitoring to whoever is on call (Enterprise plan) SMS, voice call, Slack and email. And unlike a pure paging tool, any alert still open at shift change carries into the next engineer’s handover brief. Import your existing schedule in 60 seconds and run both in parallel while you switch.
Atlassian is retiring Opsgenie on April 5, 2027, and has already stopped new sales. Shiftctl imports your Opsgenie schedule in about 60 seconds and keeps it live-synced while you transition. So you can run the two side by side and cut over when you’re ready, with alert routing, escalation and voice/SMS paging waiting on the other side.
ConnectWise Manage, Autotask PSA, and HaloPSA. Tickets you log in Shiftctl are created automatically in your PSA, and status updates sync in both directions.
Yes. Outbound voice and SMS pages come from an Australian number, so your engineers see a local caller ID at 2am instead of an unknown overseas one they're more likely to ignore. Simply press 1 on the voice call to acknowledge the alert.
Yes. You get a 14-day free trial with full access, so you can try the whole experience. No credit card required. Upgrade when you’re ready to keep everything after your trial.
Connect your PagerDuty iCal feed and Shiftctl will sync it automatically, every hour. You don't re-enter anything, and your PagerDuty schedule stays the source of truth.
Microsoft 365 sign-in is available on all tiers. SCIM provisioning is available on the Enterprise tier only.
In Australia, our database runs in the AWS Sydney region (ap-southeast-2), so client data stays onshore to support Privacy Act and data-residency expectations. We store handover notes, shift history, ticket references, and integration metadata; we don't store your customers' end-user data from your PSA, only the ticket references needed to link Shiftctl handovers back to the PSA record.
Stop losing context between shifts.
Enforced handoffs. Automatic notifications. Structured briefs. PagerDuty schedule sync. Manager analytics. PSA ticket sync.
Set up takes under 5 minutes. Already on PagerDuty? Import your rotation schedule in seconds.
14-day free trial · No credit card required · Australian-hosted · Cancel any time