Run deductions through one operational system instead of scattered inboxes, files, and status calls.

ChargebackOps centralizes intake, evidence, dispute workflow, root-cause tracking, and recovery reporting for guided retailer chargeback pilots. The current repo is positioned for hands-on deployments, not broad self-serve claims.

Start pilot workspace See shipped proof

Multi-tenant dashboard, work queue, inbox, evidence, RCA, and reports

First-run tenant bootstrap from /login for fresh environments

Health checks, smoke tests, and setup docs for pilot delivery

Signed sessions, upload controls, and ingress rate limits on high-risk routes

Why now

Operational visibility

Dashboard KPIs, deadline radar, work queues, and top-driver views are already present for guided chargeback operations.

Pilot controls

Health checks, smoke tests, bootstrap docs, and security hardening now provide a defensible pilot baseline.

Credible scope

The message is deliberately narrow: guided deployment for vendor teams, not a finished public SaaS rollout.

Repo-backed capabilities

What the current product can honestly sell

This surface is aligned to the routes, docs, smoke coverage, and security baseline already present in the repo.

Control Tower

Track at-risk deadlines, recovery opportunities, work queues, and top drivers from a single tenant dashboard.

Inbox and Intake

Capture inbound claim traffic, normalize intake data, and route teams into a single operational flow.

Evidence and Disputes

Centralize file uploads, dispute records, and supporting documentation for analyst review.

Settings and Governance

Bootstrap the first admin, configure modules, roles, departments, and workflow defaults for a live tenant.

Pilot structure

A practical first deployment, not a promise-heavy launch.

The clean handoff for sales is a guided pilot with a small user group, defined success metrics, and a narrow set of live deductions.

Environment and tenant setup

Week 1

Stand up the app, configure database and Blob storage, create the first owner, and validate health plus smoke coverage.

Workflow and inbox alignment

Week 2

Tune roles, modules, workflow steps, mailbox handling, and evidence expectations around the customer operating model.

Operational validation

Weeks 3-4

Run a focused set of live deductions through intake, dispute prep, and reporting to prove the workflow with the pilot team.

Repo-backed today: dashboard, inbox, evidence, disputes, RCA, reports, tenant bootstrap, health checks, smoke tests, and security hardening.

Not a public self-serve claim yet: distributed rate limiting, malware scanning, and private-object storage controls are still documented gaps.

Next move

Use the current build for pilot conversations, onboarding, and controlled evaluation.

Start from the tenant bootstrap path on a clean environment, validate `/api/health`, and run the smoke suite before customer-facing demos.

Launch workspace