> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/core-concepts/mediation-feature.md).

# Mediation feature

Allows users and the super administrator/administrators to resolve disagreements arising from an automated processes on the platform

* [Why](#id-1.14.x-disputebundle-businessrules-why)
* [Which context](#id-1.14.x-disputebundle-businessrules-whichcontext)
* [Interfaces](#id-1.14.x-disputebundle-businessrules-interfaces)
* [Configurations](#id-1.14.x-disputebundle-businessrules-configurations)
* [Access rights](#id-1.14.x-disputebundle-businessrules-accessrights)
* [Workflows](#id-1.14.x-disputebundle-businessrules-workflows)
* [Special rules](#id-1.14.x-disputebundle-businessrules-specialrules)

## Why <a href="#id-1.14.x-disputebundle-businessrules-why" id="id-1.14.x-disputebundle-businessrules-why"></a>

The mediation bundle or mediation management sets up a system where users and the super administrator/administrator can manage a disagreement situation from the platform with automated processes.

The bundle reinforces the administrators' role on the Marketplace as a trusted and objective third party.

Their role is to guarantee a good relationship between the two unsatisfied parties and to provide additional security because of an indirect transaction.

It also adds credibility to the platform with its ability to accompany 2 parties in a disputed transaction, thanks to the management online of such situations.

Moreover, administrators don’t have to implement off-platform systems for such circumstances.

This reinforces customer trust rather than having them send an email to <dispute@xxx.xxx>.

## Which context <a href="#id-1.14.x-disputebundle-businessrules-whichcontext" id="id-1.14.x-disputebundle-businessrules-whichcontext"></a>

Mostly for BtoC marketplaces.

Can be used by all marketplaces should disagreements occur.

## Interfaces <a href="#id-1.14.x-disputebundle-businessrules-interfaces" id="id-1.14.x-disputebundle-businessrules-interfaces"></a>

You can find here all interface documentation related to the Mediation bundle.

**SBO:**

* [Mediation management (Mediation feature)](https://features.scnd.com/v2.0/superadmin/mediation.md)

**Dashboard:**

* [Mediation management dashboard (Mediation feature)](https://features.scnd.com/v2.0/dashboards/bookings-dashboard/mediation-management-dashboard-mediation-feature.md)

## Configurations <a href="#id-1.14.x-disputebundle-businessrules-configurations" id="id-1.14.x-disputebundle-businessrules-configurations"></a>

SBO > Other > Feature > Boooking > Mediation

### Access rights <a href="#id-1.14.x-disputebundle-businessrules-accessrights" id="id-1.14.x-disputebundle-businessrules-accessrights"></a>

Dashboard > Booking > Mediation

## Workflows <a href="#id-1.14.x-disputebundle-businessrules-workflows" id="id-1.14.x-disputebundle-businessrules-workflows"></a>

Booking accepted => Mediation opened => Super-administrator manage it => Refund is done => Dispute closed.

## Special rules <a href="#id-1.14.x-disputebundle-businessrules-specialrules" id="id-1.14.x-disputebundle-businessrules-specialrules"></a>

There are no special rules for the Mediation feature


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://features.scnd.com/v2.0/core-concepts/mediation-feature.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
