docs: split Structure into six linked department pages
This commit is contained in:
1 parent
88a4375776
commit
5c5809d349
13 files changed
+254
-89
No files matched your search
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: Operations
|
||||
pagination_prev: structure/technology
|
||||
pagination_next: structure/marketing
|
||||
description: Operations purpose, teams and responsibilities in Eldorado’s operating model.
|
||||
---
|
||||
|
||||
**Purpose:** keep marketplace trading dependable and resolve customer issues fairly and efficiently.
|
||||
|
||||
**Operations Squad** delivers the department’s responsibilities across the following workstreams.
|
||||
|
||||
| Workstream | Responsibilities |
|
||||
| --- | --- |
|
||||
| Customer Support | Buyer and seller assistance, knowledge management, self-service and support workflow automation. |
|
||||
| Trust & Resolution | Disputes, appeals, refunds, warranties, chargebacks and complex customer cases. |
|
||||
| Risk & Fraud | Transaction and account risk, fraud prevention, investigations and operational controls. |
|
||||
| Operational Quality | Independent case reviews, quality standards, calibration, service accuracy and improvement tracking across operational teams. |
|
||||
|
||||
The COO coordinates Operations. Team leads manage specialists and daily service delivery. Operational Quality reports directly to the COO and reviews quality across teams.
|
||||
|
||||
[Return to Structure overview](../structure.mdx)
|
||||
Reference in new issue
Block a user