Production unavailable
Use when a communication-dependent workflow is blocked across a location, department, or high-priority service path.
- On-call escalation path
- Impact and workaround review
- Ticket updates retained for follow-up
Support
Every submission creates a private support ticket with the operational details the technical team needs: affected service area, priority, organization context, and a clear description of the issue. Standard requests are triaged through our support team in California, Texas, and New York, with 24/7/365 on-call escalation for production-impacting issues.
Support model
Med Pulse uses online ticketing so every request starts with the context needed for assignment, escalation, and follow-up. Production-impacting issues can route to 24/7/365 on-call coverage.
Use when a communication-dependent workflow is blocked across a location, department, or high-priority service path.
Use when monitoring, delivery evidence, archive retrieval, email continuity, or routing support is degraded but not fully unavailable.
Use for setup questions, archive searches, API context, planned changes, compliance documentation, or general account support.
Ticket lifecycle
Customers receive confirmation after submitting a ticket. The support team reviews service area, business impact, technical notes, and contact details before assigning the request to the right path.