Document the delay, not an assumed motive
Record when the request was sent, the intended operation, replies received and unresolved dependencies. Describe the measurable operational consequence rather than speculate about why a provider has delayed.
Build an evidence pack
Keep contract/support references, deployed release, requested API, affected outlet, intended operation, ticket history, responses and outstanding questions in one controlled record.
Exclude secrets, guest personal data and unnecessary commercial information from general escalation correspondence.
Request a specific explanation
For a generic 'integration not supported' response, ask which operation is unsupported and why. For licensing gaps, request the subscription name and price. For a contractual restriction, request the relevant term and supported alternative.
Oracle's integration programme establishes an open architecture, not unconditional access under every customer contract.
Use the proper support and partner channels
Begin with the contractual service channel. A qualified technical question may also be raised through the relevant Oracle partner/ISV route, subject to its support terms.
End each escalation with a specific requested outcome: entitlement details, an authorised account, a test schedule or an evidence-based written explanation. Begin with the provider email template.
Prepare a concise escalation record
Summarise the initial request date, venue and outlet, intended transaction, replies received and the one unresolved technical question. Use the support channel specified in the contract and ask for an actionable answer, such as the subscription or permission required to create an STS Gen2 account.
If staff must manually associate POS checks while awaiting access, measure that operational burden without presenting it as evidence of deliberate obstruction. Keep the escalation factual, dated and limited to relevant technical and contractual records.
Rezervem's contribution
As an Oracle partner with STS Gen2 integration, Rezervem can document validated transaction workflows. It does not predetermine the customer's contractual rights or a service provider's internal entitlement decisions.
Official Oracle references
Oracle Simphony integration programme · STS Gen2 API · API Accounts.
