English draft awaiting review. This translation is complete but has not yet been reviewed by a Winerim language owner. Product screenshots remain in Spanish.

EditorPending validationIntermediate

Separate incidence, product demand and billing consultation

Send each case with the minimum context to the right person.

Pending validation. Pending validation. This guide identifies the required gate and evidence; it does not authorise an unverified operation.

When to use it

When there's a bug, an upgrade requested or a contractual / invoice doubt.

Requirements and permissions

  • A confirmed account / restaurant and interponer.
  • Capture, module, action and expected result for incidents.
  • Filling / period / contract for administrative consultations.

Steps

  1. Classifies the case: incidence, functionality or billing.
  2. For incidence, play without textures and write module, steps and readback.
  3. For functionality, explain necessity and result, not an invented solution.
  4. For billing, select period and document without posting sensitive data.
  5. Use the visible / authorized channel.
  6. Record reference and monitoring officer.

Expected result and readback

Result: The case gets to the right tail with sufficient evidence and with no unnecessary information.

Check: Retirement or reference of receipt with correct category, account and liability are available.

Common errors

  • Treat billing as a technical impact.
  • Sending secrets or personal information to a capture.
  • Promise date or functionality unapproved.

Recovery or rollback

If misclassified, do not double applications: reference the original case and request reassignment.

Evidence

Support and functionality request
Unestablished billing flow

Related articles