QuantSentry is now generally available — AI-native risk infrastructure.Read the announcement
TECHNICAL SUPPORTOperator-Grade L2 · L3. Engineering On-Call, Not a Help-Desk.

Engineering on the other end of every Sev-1.

QTG operates an L2/L3 desk staffed by trading-platform engineers — cTrader, DXtrade, Match-Trader, TradeLocker — and the infra, PSP, and bridge specialists behind them. We answer the pager, run the incident, and close it with a written RCA.

Sev-1 ack15 min
MTTR · 90d1h 12m
Sev-1 closed · 90d27 / 27
Coveragefollow-the-sun
technical-support / incident-room · liveS1 · OPEN
PAGER · LIVE QUEUE05 OPEN
S1CTRADER BRIDGE · EU-2OPEN
Order ack p99 spike
on-call · K. Aoki00:48
S2PSP · WORLDPAYMITIGATING
Payout webhook 502s
pmts · L. Fischer03:04
S3CTRADER · APACTRIAGE
Symbol mapping mismatch
plat · S. Okafor06:52
S2KYC · SUMSUBMITIGATING
Verification queue backlog
plat · D. Park05:01
S3DASHBOARD · OPSTRIAGE
Stale equity column
web · M. Adler09:00
RUNBOOK · S1 · CTRADER-EU-2STEP 5 / 6
00:00Pager fired · S1 ack by K. Aoki
00:02Symptom captured · ack p99 1.4s → 6.8s
00:04Bridge metrics pulled · CPU 91% on EU-2
00:06Failover EU-2 → EU-3 initiated
00:09p99 returning to baseline · monitoring
00:12RCA template opened · evidence collected
MTTR · LAST 30 INCIDENTS
30 AGONOW
P50 · MTTR
1h 12m
p90 · 2h 48m · p99 · 4h 06m
ON-CALL · NOW
EUK. Aoki · L3
MEAS. Okafor · L3
APACD. Park · L2
THE PROBLEM

Trading-platform incidents are not a help-desk problem.

When a platform bridge spikes, a PSP webhook drops, or a KYC provider 502s, you do not need a polite reply. You need an engineer at the keyboard, with the runbook open, before the next bar closes.

Generic help-desks

L1 ticket-pushers can not debug a platform bridge, a PSP webhook, or a corrupted symbol map. Tickets bounce; nothing closes.

CTX · GENERIC

Vendor finger-pointing

Trading platform, PSP, KYC, hosting, market-data — five vendors, one outage, no owner. The firm runs the war-room itself.

OWNERSHIP · UNCLEAR

No real on-call

Sev-1 at 03:00 hits an inbox, not a pager. Acks slip past 30 min, MTTR balloons, payouts and trader trust go with it.

PAGER · NONE

No written RCA

Incidents close with a chat thread and a shrug. Recurring root causes never get fixed. The same Sev-1 lands again next month.

RCA · MISSING
TIER MODEL

Three tiers. Two of them are ours.

Technical Support runs L2 and L3 — the operator desk and the engineering on-call behind it. L1 trader-facing support is a separate service line; here we focus on the people running the firm.

TIER · L1CUSTOMER SUPPORT SERVICE
Trader-side support
Reply
< 60s
Coverage
24 / 7
Owner
Trader
Account questions
Onboarding · KYC steps
Payout requests
Bridge or PSP outage
Code-level diagnosis
Written RCA
For trader-facing volume — handled by QTG’s 24/7 desk under your brand. · See L1 Desk
TIER · L2TECHNICAL SUPPORT · THIS PAGE
Operator desk
Sev-1 ack
15 min
Coverage
24 / 7
Owner
Operator
Bridge & gateway issues
PSP / KYC integration faults
Config & rule debugging
Runbook execution
Failover & rollback
Escalation to L3 + RCA
The desk that runs the incident. Engineers — not ticket pushers.
TIER · L3TECHNICAL SUPPORT · THIS PAGE
Engineering on-call
Pager
< 5 min
Coverage
follow-the-sun
Owner
QTG eng
Code-level forensics
Hotfix & patch delivery
Architectural change
Cross-vendor war-room
Written RCA · 5 BD
Post-incident hardening
Platform engineers from the same team that ships Quant Suite.
WHAT THE DESK OWNS

Six surfaces. One pager. One owner.

The desk owns the full operator surface — execution bridges, money rails, identity, the platforms your team actually clicks, and the infra under all of it. One number to call, one team to call you back.

SURFACE

Trading platform bridges

Order acknowledgement, fill latency, symbol mapping, execution drift, gateway flaps — across cTrader, DXtrade, Match-Trader, TradeLocker, Rithmic.

cTraderDXtradeMatch-TraderTradeLockerRithmic
SURFACE

Payment & payout rails

PSP webhook failures, retry storms, stuck approvals, broken reconciliation, region-specific rail outages — pin the cause, switch the rail, drain the queue.

StripeRapydWorldpayCrypto railsTradoPay
SURFACE

KYC / identity providers

Backlog draining, failover between providers, signature mismatches, document-flow regressions — without freezing onboarding.

SumsubOnfidoVeriffFenergo
SURFACE

Operator platform

YourPropFirm, Broker Infrastructure, QuantSentry, QuantCX — config, rule, integration, and data-pipeline issues on the surfaces your team operates.

YourPropFirmBrokerInfraQuantSentryQuantCX
SURFACE

Infra & data plane

Cloud capacity, rolling deploys, queue depth, replica lag, DNS, certificate rotations, market-data feed drift — the plumbing that breaks at 3 a.m.

AWS · GCPKafkaPostgresRedisMarket data
SURFACE

Custom integrations

CRMs, BI warehouses, comms (Slack, email, SMS), and bespoke webhooks built for you. If we shipped it, we own its pager.

CRMsWarehousesWebhooksComms
INCIDENT LIFECYCLE

From pager to RCA — six stages, one timeline.

Every Sev-1 follows the same six stages. The desk does not close the ticket until the corrective actions are tracked. We track them ourselves, and you can see them.

STAGE

Detect

Monitors, customer report, or platform alert lands on the QTG pager.

< 60 s
STAGE

Acknowledge

On-call engineer paged and acknowledged. Incident channel opened, sev assigned.

< 15 m · S1
STAGE

Mitigate

Runbook executed — failover, rollback, throttling, or feature flag — to restore SLA.

p50 · 1h 12m
STAGE

Resolve

Fix verified, monitors green for one full window. Customer comms posted to status.

CONFIRMED
STAGE

RCA

Written root-cause analysis with timeline, evidence, and corrective actions.

5 BD
STAGE

Harden

Corrective actions delivered as code, runbooks, alerts, or vendor changes. Tracked.

30 D
SLA

The numbers we sign on to.

Baseline SLA across the desk. Enterprise contracts tighten Sev-1 ack to 5 min and add named on-call rotations.

SEVERITY
DEFINITION
ACK
RESOLVE TARGET
UPDATES
SEV-1
Production down · trading or payouts impacted
15 min · 24/7
Continuous · until clear
Every 30 min
SEV-2
Degraded · workaround exists or partial impact
30 min · 24/7
< 4 hours
Every 60 min
SEV-3
Single-feature fault · no business impact
2 h · business hours
< 2 business days
Daily
SEV-4
Question · request · enhancement
4 h · business hours
Next sprint window
On change
* BASELINE · ENTERPRISE CONTRACTS UPGRADE TO TIGHTER WINDOWSRequest a Custom SLA
CHANNELS

Four ways in. One desk on the other end.

Pick the channel that matches the severity. The desk is the same; the pager is calibrated.

Pager · phone

Direct line into the on-call rotation. Sev-1 only. Routed by region, follow-the-sun.

< 5 min · 24/7

Slack Connect

Shared incident channel between your operators and our desk. Audit-logged, retained.

PRIMARY · 24/7

Ticket portal

Sev-2/3/4 routing with structured fields and evidence upload. SLA timer visible.

TRACKED · SLA-BOUND

Email

Email-in works for Sev-3/4. Auto-routed to the right pod by parser & rules.

< 2 h · BIZ HOURS
WHY QTG

A support desk that ships code.

QTG’s technical support desk is run by the same engineering organisation that builds and operates Quant Suite — so the people answering your pager already know your stack.

PILLAR

Engineers, not gatekeepers

Every desk seat is held by an engineer who can read platform bridge logs, trace a webhook, or roll a hotfix. No “I will escalate” wall.

PILLAR

Same team that ships Quant Suite

L3 on-call comes from the engineering org behind YourPropFirm, QuantSentry, and TradoPay. Forensics happen at the source.

PILLAR

Multi-vendor war-room ownership

When the platform, the PSP, and the KYC provider all blame each other, we run the call. One owner, one shared log.

PILLAR

Written RCAs, tracked actions

Every Sev-1 closes with a documented RCA inside 5 business days, and corrective actions are tracked to delivery.

BENEFITS AT A GLANCE

What you get.

One pager · one team · one accountability layer
Sev-1 ack in 15 min · 24/7
L3 staffed by Quant Suite engineers
Multi-vendor war-room ownership
Written RCA on every Sev-1
Corrective actions tracked to delivery
Runbooks built and version-controlled
Status page · Slack Connect · email · portal
Follow-the-sun coverage across EU · MEA · APAC
Tighter SLAs available on enterprise contracts
USE CASES

Where the desk earns its keep.

Five archetypes pulled from active engagements. Each one is a real combination of surfaces, severity profile, and outcome the desk owns.

UC3 SURFACES

Prop firm · payout-day pager

You run challenges and pay funded traders weekly. We answer the Sev-1 when the PSP webhook flaps and the queue stalls.

SURFACES
PSP railsPayout queueRecon
OUTCOME
No missed payout windows
UC3 SURFACES

Broker · platform bridge ownership

You run a brokerage on cTrader and need an engineer who reads the bridge logs without three escalation hops.

SURFACES
cTrader · DXGatewaySymbol map
OUTCOME
L2/L3 on the same desk
UC3 SURFACES

Multi-platform operator

cTrader, DXtrade, and TradeLocker all in production. One desk, one set of runbooks, one MTTR target.

SURFACES
cTraderDXtradeTradeLocker
OUTCOME
Single owner across stacks
UC3 SURFACES

Compliance-grade incident trail

Regulator, auditor, or PI insurer wants the full incident history. Status page, RCAs, and corrective actions on file.

SURFACES
StatusRCAAudit log
OUTCOME
Audit-ready evidence pack
UC

Fintech platform · post-launch ops

You shipped a custom platform with QTG. Technical Support takes the pager and the runbooks at go-live — same engineers.

SURFACES
Custom platformInfraWebhooksBI
OUTCOME
Build → operate handover
PACKAGES

Three desks. One backbone.

Pick the response profile that matches your stack. Move up at any time — the runbooks and on-call rotation scale without re-onboarding.

PKG · STANDARD
Standard desk
Sev-2+
SCOPE
RESPONSE PROFILE
Sev-1 ack30 min
CoverageBiz hours · 5×8
ChannelsPortal · email
RCAOn request
BEST FOR
  • Single-platform operators
  • Lower-volume desks
  • Pre-production stacks
Scope this desk
PKG · 24/7
24/7 operator desk
Sev-1+
SCOPE
RESPONSE PROFILE
Sev-1 ack15 min · 24/7
CoverageFollow-the-sun
ChannelsPager · Slack · portal · email
RCA5 BD · written
BEST FOR
  • Live prop firms · brokers
  • Multi-platform stacks
  • Money-rail dependent ops
Scope this desk
PKG · ENTERPRISE
Enterprise · named pod
Sev-1+
SCOPE
RESPONSE PROFILE
Sev-1 ack5 min · 24/7
CoverageNamed on-call
ChannelsAll · plus war-room
RCA3 BD · with hardening plan
BEST FOR
  • Regulated entities
  • Multi-region operators
  • Audit-heavy stacks
Scope this desk
FAQ

Common questions.

Everything we get asked in scoping. If yours isn’t here, ping us directly.

No. Technical Support is for the operator — the people running the firm. Trader-facing L1 support is a separate service line called Customer Support Service.
PARTNER WITH QTG

Hand the pager to engineers.

Tell us about your stack and incident profile, and we will scope the right desk — Standard, 24/7, or Enterprise — with the right SLA, the right rotation, and the right runbooks.