Getting started
Set up a complete paging path and confirm that it works.
Create an account or accept an organization invitation at app.acked.dev. The mobile apps are notification clients.
1. Sign in on the web
- Open app.acked.dev.
- Enter your email address.
- Continue with the social provider linked to that address.
A new user creates an organization. An invited user enters the organization that sent the invitation.
Success: The Alerts page shows your active organization.
2. Create your first service
- Open Services.
- Select New service.
- Name the system that you monitor.
- Select the starter schedule and create the service.
Acked creates a default source for the new service.
Success: The service page shows its schedule and a default source.
3. Invite a teammate when needed
This step is optional. You can test the paging path by yourself.
- Open Organization → Team.
- Enter the person’s name and email address.
- Select Add member.
The member becomes active after the first sign-in. Add active members to schedule rotations.
4. Set up phone notifications
- Install Acked for iPhone or Android.
- Sign in with the same email address that you use on the web.
- Allow notifications.
- Allow Critical Alerts on iPhone or Do Not Disturb access on Android.
The web setup does not wait for the phone. Select Keep going when you have the app link that you need.
Success: Account → My devices shows the phone with push enabled.
5. Send and acknowledge a test alert
- Open Alerts.
- Select Trigger alert.
- Select the service and use high urgency.
- Trigger the alert.
- Acknowledge the notification on the phone.
Acknowledgement stops reminders and escalation. Resolve the alert after you finish the test.
Success: The alert timeline shows the alert, notification, and acknowledgement.
6. Connect a monitoring source
- Open Services and select the service.
- Find Sources and select Add source.
- Choose the service and source type.
- Create the source and copy its one-time credential.
- Configure the monitoring tool and send a test signal.
Use a stable event_key for each monitored condition. Send a recovery signal with the same key when the condition clears.
Success: A signal from the monitoring tool opens an alert for the expected service.
7. Review the routing path
- Open the service and follow its schedule link.
- Confirm the schedule timezone.
- Confirm the current on-call user and next handoff.
- Confirm the escalation delay and backup levels.