A business is choosing a payments provider. The finance director asks what happens if something breaks on a Saturday during their busiest trading weekend.
Two providers say they offer excellent support. One says that incidents are answered within a stated time at any hour, that severity levels are defined, that there is a named escalation path, and publishes a status history showing how past incidents were handled.
The third provider costs slightly less. They choose the one that answered the question, because the difference in price is trivial against a weekend of failed payments.
Ask: what hours are actually covered
And by what. A chat widget staffed in office hours is a different product from an incident line available at any time, and both are described as support.
Ask: what the response commitment is
By severity, in writing. A single response time across all issues means the commitment is not real for the ones that matter.
Ask: how severity is defined
Who decides, and whether the customer can escalate something the provider has classified as routine. This is where support promises actually break down.
Ask: what the escalation path is
Named roles rather than a queue. A business with money stuck needs to reach somebody with authority rather than somebody with a script.
Ask: what happens overnight and at weekends
Specifically, which is the ground in support escalation questions when money is involved.
Ask: whether there is a named contact
For business accounts above a certain size, and what that person actually does, since account management varies enormously in substance.
Ask: what the status page shows
Whether incidents are published, how quickly, and what the history looks like. A provider that publishes failures honestly is a provider that handles them.
Ask: what the incident communication looks like
Whether customers are told proactively, through what channel, and how often during an incident. Silence during an outage damages more than the outage.
Ask: what support is included at each tier
And what costs extra, since a support commitment that requires an upgrade is a pricing question rather than a service one.
Ask: how onboarding support differs
The first weeks need more, which is the ground in onboarding questions that stall fintech signups.
Ask: who answers technical questions
Whether a developer can reach somebody who understands the integration, or whether every question passes through a general queue first.
Look for: published response times rather than adjectives
The difference between a commitment and a marketing claim is a number, and buyers should treat the absence of one as an answer.
Look for: a provider that handles the routine automatically
So that human attention is available for the incidents, which is the argument in 24 7 support without hiring a night shift a.
Ask: what the support looked like during the last incident
Not in principle but in practice. A provider willing to describe a specific past failure, how long it took, what was communicated and what changed afterwards is demonstrating the thing every other answer merely claims.
Ask: what the customer is expected to do
Whether there is a defined process for reporting an incident, what information is required, and what happens if it is submitted through the wrong channel at midnight by somebody who is not the account contact.
Answer the support question during the evaluation
An assistant that states the hours and channels, gives response commitments by severity, explains the escalation path and the incident communication and routes an urgent question straight to a person answers the question that decides the deal. The tier detail sits in support tier and response time questions. See features, start at try, and the sector view sits under fintech.