Support guide

Support Scope and Escalation Boundaries

Support is one of the easiest words to overuse in this market. Buyers need to know what support includes, what they still need to provide, and where escalation stops being a promise and starts being a process.

Portcast uses this guide to define support as an operating process with boundaries. That is a higher-trust signal than vague claims about fast internal help or guaranteed fixes.

  • Support-scope clarity
  • Escalation boundaries
  • Client responsibilities
  • No guaranteed outcomes
Support Scope and Escalation Boundaries

Trust rail

Get clear on ownership and fit before you submit.

Primary role

Make the buying boundary explicit before inquiry.

Best use

Resolve ownership, onboarding, payment, or support uncertainty.

Next step

Return to commercial or move into quote/contact with lower ambiguity.

Boundary page

Support becomes credible when the exclusions are visible too

Review these points to confirm whether the support model fits your situation.

Support becomes credible when the exclusions are visible too

Support can include

  • Ongoing account-management support
  • Appeals assistance and documentation-readiness guidance
  • Escalation support where an operational process exists
  • Coordination with optimization and reporting where relevant

Support does not imply

  • Guaranteed reinstatement, approval, or performance
  • Unsupported claims about official internal escalation channels
  • Acceptance of refused categories or casino inquiries
  • A substitute for the client's own truthful documentation and lawful use

What support usually covers

The public support story is specific enough to evaluate

Management support

Portcast can support ongoing account management and issue handling where the scope fits the engagement.

Appeals assistance

Support can include helping buyers review documentation needs and move through an appeal process with more structure.

Operational coordination

Support may also include coordination across optimization, reporting, and escalation processes when those are in scope.

Next step

If support boundaries make sense, move into a discussion with actual issue context

Support questions are best handled with platform, account status, and documentation state already on the table.