Contact Us

Support

A ticketed support path for urgent routing and service requests.

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.

1. Ticket createdThe request is logged with affected service, business context, priority, and technical notes.
2. Triage beginsSupport reviews operational impact and routes the ticket to the right technical path.
3. Work is assignedThe technical team works the issue and keeps the account contact aligned through resolution.

Submit a support ticket

Support model

Production issues are triaged by impact, urgency, and service area.

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.

Critical

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
Urgent

Degraded operations

Use when monitoring, delivery evidence, archive retrieval, email continuity, or routing support is degraded but not fully unavailable.

  • Priority technical triage
  • Service-area assignment
  • Account contact alignment
Standard

Service requests

Use for setup questions, archive searches, API context, planned changes, compliance documentation, or general account support.

  • Documented request intake
  • Queue-based assignment
  • Resolution notes captured

Ticket lifecycle

From intake to closeout, the support record stays attached to the work.

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.

ConfirmationThe submitted request is logged with customer, priority, service area, and message context.TriageSupport reviews urgency and routes the ticket to the right operational or account team.CloseoutResolution notes, follow-up items, and documentation needs are retained in the ticket record.