Priority Support

24/7 Support that never sleeps

We respond in minutes, not hours. Chat with an engineer, open a ticket, or call our on‑call line — any time.

SLA 99.99% First reply < 30m Follow‑the‑sun
Start live chatOpen a ticket
4.9/5
CSAT
<30m
Avg. reply
1.2k+
Incidents/mo
✓

Live status & SLA

All systems operational. Priority incidents receive first response under 30 minutes.

99.99%
Uptime
<30m
P1 reply
24/7
Coverage
View status pageSLA details

Live chat

Recommended

Instant help from engineers.

Email support

Tracked

Tickets with attachments.

Emergency line

On‑call

P1 outages only.

Incident updates

Status

Subscribe for alerts.

Help Center

Docs

Guides & tutorials.

Community

Peers

Best practices.

Knowledge Base

Search guides and troubleshooting.

First response ETA ~ 4 hours

Tickets are triaged 24/7. We’ll reply to your email.

Recent updates

  • 10:04
    Auto‑scaling eventInfo

    Traffic spike handled by autoscaler.

  • 08:27
    P2 – Elevated errorsResolved

    Checkout retries increased. Rollback deployed.

  • Yesterday
    Planned maintenanceCompleted

    DB minor upgrade completed without downtime.

Global coverage

Follow‑the‑sun
Americas
Timezones: PT / CT / ET
Languages: EN, ES
EMEA
Timezones: GMT / CET
Languages: EN, FR, DE
APAC
Timezones: SGT / JST / AEST
Languages: EN, BN
Fast triage

Engineers on the first line, not bots.

Clear comms

Status page, email and chat updates at every step.

Post‑mortems

We share root causes and prevention steps for P1/P2.

Support FAQ

What counts as P1 vs P2?›

P1: full outage or severe revenue impact. P2: major function impaired with workaround. P3/P4: minor issues or questions.

How do I escalate?›

Mark the ticket P1/P2, include pager number if needed, and use the emergency line for critical incidents.

Do you support WooCommerce / Shopify?›

Yes — WooCommerce, Shopify, Dokan multivendor and custom stacks via API.

Do you provide post‑incident reports?›

Yes. P1/P2 incidents include a written RCA with remediation actions.