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

# Surfaces

> Where customers, agents, and Dubot meet

## One action layer, multiple surfaces

The same approved capability can appear differently depending on where the customer needs help. Dubot is being designed around two product surfaces and connections to support AI.

<CardGroup cols={3}>
  <Card title="Browserbot" icon="bot">
    Works with the live product interface to guide a customer through a reviewed step.
  </Card>

  <Card title="Contextual sidepanel" icon="panel-right">
    Shows context, progress, confirmation, and recovery alongside the product.
  </Card>

  <Card title="Support AI" icon="sparkles">
    Recognizes an eligible request and offers the appropriate approved capability.
  </Card>
</CardGroup>

## Browserbot

Browserbot works with the existing product interface. In its first version it is descriptive and human-scripted: guided by an intent, it can take the customer to the right place, highlight the relevant control, prompt a click, and explain the step. It is the "show" half of Dubot's runtime, used when a direct action is not available or when a step benefits from being done in context.

Browserbot is useful when:

* the task already exists in the product interface;
* the journey spans several screens or UI states;
* the customer benefits from help in context;
* rebuilding the workflow as a separate integration would add unnecessary work.

<Info>
  **Available for evaluation:** Browserbot is the primary surface for testing reviewed journeys and agreed controls with customers.
</Info>

## Contextual sidepanel

The sidepanel is intended to make the journey legible. It can explain what Dubot is doing, show progress, request confirmation, and give the customer or agent a clear place to pause or recover.

The sidepanel should not become a second version of the product. Its job is to provide context and control while the work happens in the real interface.

<Note>
  **Coming next:** The sidepanel experience is in active development. Final behavior and availability should not be assumed from this description.
</Note>

## Support AI

A support system can remain the conversational entry point. When an answer is not enough, it can offer an eligible Dubot capability and pass the customer into the appropriate product surface.

This keeps responsibilities clear:

| Layer      | Responsibility                                     |
| ---------- | -------------------------------------------------- |
| Support AI | Understand the conversation and explain the option |
| Dubot      | Select and govern the approved capability          |
| Browserbot | Work with the live product interface               |
| Sidepanel  | Show context, progress, and control                |
| Product    | Remain the source of truth for the resulting state |