Published April 6, 2026 - Koeppel Operations Platform Team

Contact & support guidance

Ops Hub support is routed through the operational channel that matches the issue you are trying to solve. That keeps access requests, workflow questions, and production incidents moving to the right team instead of stalling in a generic inbox.

Access and password issues Start with your regional administrator or owner-level administrator. They manage account activation, role scope, and first-login password workflows.

Workflow or data mismatch Report the store, business date, and workflow area affected. Include whether the issue involves cash variances, tip reviews, or safe counts so the operations platform team can reproduce it quickly.

Urgent day-of-close escalation Escalate through your district or regional operating lead first, then attach the impacted case or review ID so the platform team can verify the queue state without slowing the store.

When reporting an issue, include the store name, the relevant week-ending or business date, and the visible case identifier when one is present. That shortens triage time and reduces the chance of support following the wrong operational thread.

If the problem is reproducible, note the exact dashboard page, filter state, and whether the count mismatch is visible only in the hub, only in the table, or in both places. Those details are often the difference between a same-day fix and a long back-and-forth with incomplete reproduction notes.

Support requests are most effective when they describe the operator impact plainly: what decision was blocked, what deadline was at risk, and whether the issue affected cash reconciliation, tip review completion, or safe count compliance. That context helps the team prioritize correctly.

If you are escalating a production issue, include screenshots only when they help clarify the state mismatch and remove any unrelated store information first. Clear, minimal evidence is better than a long thread of partial notes, and it helps the platform team act without introducing unnecessary privacy exposure.