# What Adragent is

Adragent turns everyday operational messages into work that is ready to review. Your team can ask in chat, forward a supplier email, paste a promotion note, send a WhatsApp screenshot, or text from the field. Adragent reads what arrived, understands what needs to happen, finds the affected records, and prepares the next step.

Adragent is built for the overhead around the decision: reading messy inputs, checking what is affected, setting up repetitive changes, and showing what still needs attention. You stay in control — every change is previewed and only runs after your *Confirm*.

{% hint style="info" %}
**No special syntax to learn.** Bring the work as it arrives — a sentence, promo email, contract PDF, WhatsApp screenshot, or SMS. Adragent turns it into a clear task you can review.
{% endhint %}

<figure><img src="/files/OKaXgZMVdna8ij65VaWy" alt="Work channels → Adragent → clear preview, one approval and result summary"><figcaption><p>Adragent reads work from your channels, prepares it with AI assistance, and gives the operator a clear preview, one approval step and the result.</p></figcaption></figure>

***

## The overhead Adragent removes

Adragent is useful when the business decision is simple, but getting the work ready takes time.

* **It reads what arrived.** Emails, contract details, screenshots and short messages become a task.
* **It prepares the work.** Adragent finds the affected properties, dates, rate plans, channels or bookings and drafts the change.
* **It keeps the loop clear.** If something is unclear, it asks. If the work changes data, it waits for confirmation and then shows the result.

## What you can ask Adragent to do

Adragent's reach spans every operator workflow in the console. It is strongest when a user knows the desired business outcome but does not want to assemble every screen, filter and batch step manually. Read operations are broad and immediate; write operations always go through preview and confirm.

### Catalog and content

***

`Operator-side`

Properties, rooms, attributes, meal plans, images, descriptions — query and bulk-update.

* *"Find all properties in Antalya without images and queue them for content review."*
* *"Update Hotel Sunrise's English description with what I'm pasting below."*
* *"List the properties waiting on a content editor's approval."*

Open the [catalog reference](/console/catalog/property.md) [→](/console/catalog/property.md)

***

### Rates, inventory and promotions

***

`Operator-side`

Rate plans, allotments, stop-sale, promotions, day-of-week rules — search the calendar and apply changes in bulk.

* *"Apply a 15% weekend discount to Hotel Sunrise rooms for May."*
* *"Stop-sale Bodrum properties on July weekends."*
* *"List properties that have a non-refundable rate plan but no BAR defined."*

Open the [rate plan guide](/console/pricing-and-availability/rate-plans.md) [→](/console/pricing-and-availability/rate-plans.md)

***

### Distribution

***

`Operator-side`

Outbound channel exposure and inbound reservation tracking.

* *"Publish Hotel Sunrise on the niche channel we onboarded last week."*
* *"Show me the channels that received zero bookings in the last seven days."*
* *"Show me when the last rate update went to channel X for Hotel Sunrise."*

Open the [distribution overview](/console/distribution/overview.md) [→](/console/distribution/overview.md)

***

### Contracts and onboarding

***

`Operator-side`

Supplier onboarding, allotment matrices, release periods, markup setup.

* *(forwarded contract email)* *"Onboard the supplier in this contract and create the allotment matrix."*
* *"List the allotments whose release period expires this week."*
* *"Draft a markup rule for the new supplier for May, ready for my approval."*

Open the [contracts guide](/console/contracts-and-onboarding/contracts.md) [→](/console/contracts-and-onboarding/contracts.md)

***

### Payments

***

`Operator-side`

Settlement, virtual card issuing, refund and chargeback status.

* *"Prepare last month's reconciliation report for virtual card transactions."*
* *"Show pending refunds for cancelled bookings."*
* *"Summarise Hotel Sunrise's March settlement by currency."*

Open the [payments overview](/console/payments/overview.md) [→](/console/payments/overview.md)

***

## How an Adragent operation runs

{% stepper %}
{% step %}

### Capture intent

You write a request in chat, paste a promo email, forward a supplier message, send a WhatsApp screenshot, or text an SMS. The channel does not change what Adragent does next.
{% endstep %}

{% step %}

### Adragent prepares the operation

Adragent reads your input, resolves scope (which properties, which dates, which rate plans), and drafts the operation. If anything is ambiguous — a date range that could mean two things, a property name that matches three records — it asks back with a clarifying question.
{% endstep %}

{% step %}

### You see the preview

Adragent shows the operation as a preview card: what changes, where (counts of affected properties, rate plans, dates), and what stays the same. The preview is bound to your request — once shown, it cannot be tampered with.
{% endstep %}

{% step %}

### You confirm; Adragent applies

Tap **Confirm**. Adragent applies the operation through the same console flow and shows the result in the relevant product view.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Read-only requests skip preview and confirm.** Listing properties, checking a rate cell, summarising bookings — anything that does not change state — returns immediately.
{% endhint %}

{% hint style="warning" %}
**No auto-execute.** Adragent never applies a state-changing operation without your *Confirm*. If you walk away from a preview, the operation expires.
{% endhint %}

***

## What Adragent does not do

* **Does not maintain a parallel system.** No separate catalog and no second source of truth. A change made through Adragent appears in the same product views as a console change.
* **Does not run scheduled rules on its own.** Adragent acts on your intent, on demand. If you want recurring automation — *"apply a markup every Monday"* — set the rule in the console; Adragent helps you set it up but does not become the schedule.
* **Does not read another organization's data.** Organization isolation extends to Adragent. Another agency's contracts stay outside your workspace.

## Where to next

* **The channels Adragent runs on** → [Channels](/console/adragent/channels.md)
* **Why every write waits for your approval** → [Confirm-before-apply](/console/adragent/confirm-before-apply.md)
* **The operations Adragent can do for you** → [Tools](/console/adragent/tools.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://adrasis.gitbook.io/console/adragent/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.