> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Conversation side panel

> Read the panel top to bottom: AI output and tags, contact details, booking data from your PMS, and custom fields.

Every conversation has a side panel that collects what you would otherwise go hunting for across your PMS, your channels, and your own notes. Open it with the side panel icon on the top left of the conversation.

The panel is split into two tabs. **General** holds everything described below. **Calls** holds the call history for this contact, with transcripts and summaries. You will also find this in [The Calls view](/inbox/calls/calls-view).

The sections appear in a fixed order, working from what is happening right now down to reference detail.

## At a glance

The top block is the fastest read on the conversation, and it is where most of the AI output lives.

| Field | What it tells you |
| - | - |
| **Agent** | Which agent is handling the conversation, for example `Guest`. See [Agents](/build-your-agent/agents) |
| **Agent Mode** | Whether the agent is active on this conversation or not |
| **Sentiment** | How the guest appears to be feeling, for example `Very happy`. Expand it for the reasoning behind the reading |
| **AI Summary** | A short account of what the conversation is about. Expand it for the full summary |
| **Tags** | Conversation tags currently applied, each removable |
| **Labels** | Labels currently applied to the contact |

Sentiment and the AI summary are most useful on handover. If you assign a long thread to a teammate, or come back to it yourself days later, the summary saves reading the whole history. See [Assigning conversations](/inbox/team/assigning-conversations) and [Proposed replies](/inbox/agent/proposed-replies).

<Tip>
  Read the summary before you reply to anything long, then skim the last few messages to confirm it. Two seconds of checking is cheaper than answering the wrong question confidently.
</Tip>

### Tags

Tags reach a conversation in more than one way, which is worth knowing when you are wondering why one appeared:

* **The agent applies it automatically**, based on the description written for that tag
* **Your team applies it by hand**, using **Add tag** in this panel
* **Agent instructions apply it**, where a skill tells the agent to tag a particular situation
* **A workflow applies it**, as a step triggered by something happening

Removing a tag is the `x` on the tag itself.

The escalation level on a tag decides whether the agent keeps replying or stops and escalates. See [Conversation Tags](/inbox/setup/conversation-tags) for creating and configuring them, [Writing tag descriptions](/inbox/setup/conversation-tags#writing-tag-descriptions) for making them fire accurately, [Skills](/build-your-agent/skills) for instruction-driven tagging, and [Workflows](/workflows/getting-started) for tagging as a workflow step.

### Labels

Labels sit on the contact rather than on the message, and never affect what the agent does. Use **Add label** to apply one by hand. The picker only offers labels configured for the contact's current inbox. See [Labels](/inbox/setup/labels).

## Contact Info

Who you are talking to and how they are reachable: first name, last name, phone, WhatsApp, email, and any other channel address on file, plus the **Inbox** the contact belongs to.

**Add info** lets you record details the contact did not arrive with. See [General Inbox Settings](/inbox/setup/general-settings) for how contacts are organized, and [Inbox Routing](/inbox/setup/routing) for how a contact ends up in a given inbox.

## Booking Info

The reservation behind the conversation, pulled from your PMS. The refresh control at the top of the section re-pulls it if something changed in the PMS moments ago.

Typical fields:

| Field | Notes |
| - | - |
| **Listing** | The property, with its thumbnail |
| **Check-in** and **Check-out** | Dates with times, so you can answer arrival questions without opening anything else |
| **Status** | Where the stay sits in time, for example `Current`, `Future`, or `Past` |
| **Guests**, **Adults**, **Nights** | Party size and length of stay |
| **Channel** | Where the booking came from |
| **Reservation ID** and **Confirmation** | Identifiers for looking the booking up elsewhere |
| **Created** | When the booking was made |
| **Total** and **Payment** | Value of the stay and whether it is paid |
| **PMS link** | Straight through to the reservation in your PMS |
| **Guest portal** | The guest-facing view of the booking, if your PMS provides one |

Status is the field to check before you reply. The same question means different things depending on whether the guest is mid-stay, arriving next month, or already checked out.

<Note>
  Which fields appear depends on your PMS and what it sends. If something you expect is missing, the gap is usually upstream rather than in Conduit.
</Note>

## Listing Details

Standing facts about the property itself, such as max guests, minimum nights, and maximum nights. These come from the listing record rather than the booking, so they stay the same across every reservation at that property.

## Custom fields from your PMS

Custom fields configured in your PMS appear at two levels, populated independently:

* **Reservation level**, for anything true of this specific booking
* **Listing level**, for anything true of the property

If a level shows nothing, either your PMS has none configured at that level or none are set on this particular record. See [PMS Knowledge](/build-your-agent/knowledge-base/pms-knowledge).

## Custom fields created in Conduit

Below the PMS data sit collapsible sections holding custom fields you have defined in Conduit itself, for example **Next Clean** or **Late Checkout**. Each section groups related fields and expands on click.

These are for the things your operation tracks that your PMS has no field for. You choose what they are called, what they hold, and which contact type they attach to. See [Custom Fields](/inbox/setup/custom-fields).

<Tip>
  Before creating a custom field in Conduit, check whether the value already exists in your PMS. Anything synced from the PMS stays current on its own, whereas a Conduit field is only as accurate as the last person who updated it.
</Tip>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why is there no booking information on this conversation?">
    The contact is not linked to a reservation. This happens with inbound enquiries from someone who has never booked, or where the address they contacted you from does not match a synced reservation.
  </Accordion>

  <Accordion title="Why are there no reservation custom fields?">
    Either your PMS has none configured at the reservation level, or none are set on this particular booking. Listing level and reservation level are populated independently.
  </Accordion>

  <Accordion title="A tag appeared and nobody on my team added it. Where did it come from?">
    Either the agent applied it from the tag description, a skill instructed it to, or a workflow step did. Check the tag's description first, since an over-broad description is the most common cause.
  </Accordion>

  <Accordion title="What is the difference between a tag and a label here?">
    A tag describes what the conversation is about and can stop the agent from replying if it is marked urgent. A label sits on the contact, is inbox-scoped, and never changes agent behaviour. See [Labels](/inbox/setup/labels).
  </Accordion>

  <Accordion title="Is the sentiment or summary ever shown to the guest?">
    No. Both are internal and visible only to your team.
  </Accordion>

  <Accordion title="The booking data looks out of date. Can I force a refresh?">
    Yes. Use the refresh control on the Booking Info section header to re-pull from your PMS.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.