Contact support
Email us at support@opsping.com. Standard support coverage is Monday–Friday, 9 AM–5 PM Eastern (America/New_York, following daylight saving time), excluding observed U.S. federal holidays.
To get a useful answer on the first reply, include:
- The email address you sign in with and your organization name.
- The alert ID or tiny ID, incident, schedule, or integration involved.
- When it happened, with your time zone.
- For app issues: phone model, iOS or Android version, and the OpsPing app version.
- What you expected to happen and what happened instead. Never send API keys or passwords.
Support policy and response targets
Effective update: November 6, 2026; not retroactive. Existing customer commitments and signed terms remain in effect. These published targets do not replace or reduce them; any reduction for an existing customer requires the applicable notice and/or agreement before taking effect, including the material-change communications required by our Terms and at least 30 days' notice for material reductions under our SLA.
- Team: first-human-response target within 8 support hours (one support business day).
- Business: first-human-response target within 4 support hours.
- Free and trial, evaluation, or proof-of-concept (PoC) use: documentation and best-effort email support, with no guaranteed response or resolution time, unless applicable written terms expressly override this policy.
These are first-human-response targets, not guaranteed response or resolution times. An automated receipt does not count as a human response. Resolution depends on the issue and may require further investigation or information from you.
A support hour is an hour within the coverage window above. The response clock starts when a request arrives during coverage; outside coverage it begins or resumes when coverage next opens. Evenings, weekends, and observed U.S. federal holidays do not count. For example, a Business request received Friday at 4 PM Eastern has a first-human-response target of Monday at noon Eastern, assuming neither day is an observed holiday.
Paging availability is separate from staffed support
Continuous paging availability does not mean 24/7 human support. The standard paid-plan availability SLA remains 99.5% monthly; its measurement, exclusions, service credits, and claim process are unchanged. See the availability SLA for details. These support targets do not create service credits for missed response targets.
A custom or stronger SLA requires a separate written agreement and is not automatically included with Business. Free and trial/evaluation/PoC use has no contractual availability SLA unless applicable written terms expressly extend coverage.
See also the support provisions in our SLA.
Fix common problems
- Mobile app setup. Connecting the iOS/Android app to your OpsPing account, enabling push notifications and critical alerts. See the mobile setup guide.
- Signing in on a new phone. Generate a one-time QR code in the admin console and scan it from the app instead of typing a password. See pair your phone.
- Notifications not arriving. Check notification permissions, critical-alert settings, and any mute or P1-only preference. See notifications & channels.
- Apple Watch pings but iPhone stays silent. iOS sends each alert to one device. See Apple Watch & critical alerts for the fix.
- On-call schedules and escalations. An alert pages whoever its escalation policy or schedule responder selects. See schedules & escalations.
- Too many low-priority pages. Suppress, delay, or reprioritize noisy alerts with alert policies, and preview the effect before saving.
- Company sign-in. Connect Okta, Azure AD, or Google Workspace over OIDC. See single sign-on (SSO).
- On-call pay reports. Export the business vs after-hours split as CSV from the on-call hours report.
- Customer-facing status page. Visibility, incident updates, and subscriptions are covered in the status pages guide.
- Account and billing. Email support@opsping.com from your account email.
- Security issues. Report vulnerabilities to security@opsping.com — see our security page.
Integrations and the API
- First alert. Create an integration API key and send a test alert with curl in the getting started guide.
- Alerts not showing up from a monitoring tool. Check the mapper and payload format for Grafana, CloudWatch/SNS, Alertmanager, Datadog, and email in inbound integrations, or the Prometheus Alertmanager integration page.
- API errors. Every endpoint, auth scheme, and payload limit is in the API reference.
- Calls written for Opsgenie. The Opsgenie-compatible alerts API page lists which Opsgenie v2 alert endpoints and fields OpsPing accepts and what to change.
Migration help
Moving from Opsgenie or another end-of-life on-call tool? Start with how to switch from Opsgenie and the migration guide. Stuck on a step? Email migration@opsping.com with your setup. Migration help is async by email; calls are by appointment.
Self-serve resources
- Documentation — full product guides
- FAQ — quick answers on alerts, notifications, plans, and migration
- API reference — REST API for integrations
- Status page — current service health
- Contact — sales, security, and migration addresses
- Privacy policy — data collection and your rights