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

# Dial-in capture — a phone into a conference bridge

> Capture a conference bridge that a browser bot cannot join, by dialling into it over the phone network.

**Can Vexa dial into a conference bridge by phone?**

**Today:** No. Capture today is a browser bot joining Meet, Zoom or Teams. A bridge reachable only by phone has no route in. A spike exists and is unmerged.

**Sponsorable:** yes — A phone route into the bridge, and the plumbing to treat it as a capture platform.

***

*Reach a bridge the browser bot cannot enter, by dialling into it.*

|                 |                                                                                       |
| --------------- | ------------------------------------------------------------------------------------- |
| **Status**      | **sponsorable** — [spike exists, unmerged](https://github.com/Vexa-ai/vexa/pull/1692) |
| **Size**        | M                                                                                     |
| **North star**  | 1 · Capture anywhere, owned by you                                                    |
| **Measured by** | platforms and routes covered                                                          |

## What it does

* A phone leg into a conference bridge, treated as a capture route like any platform.
* Audio arrives from the bridge as one mixed stream.
* The transcript lands in the same meeting record as any other route.

## What exists today

Capture today is a browser bot joining Meet, Zoom or Teams. A bridge reachable only by phone has no route in.

## What this adds

A phone route into the bridge, and the plumbing to treat it as a capture platform.

## How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so "done" means done on your meetings. Your name goes on the release note. Sponsorship buys **the order of the queue** — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

## Two doors

<Columns cols={2}>
  <Card title="Sponsor this" icon="handshake" color="#0D9373" href="https://cal.com/dmitrygrankin/web?utm_source=docs&utm_medium=roadmap&utm_campaign=sponsor&utm_content=dial-in-capture" horizontal arrow cta="Book fifteen minutes">
    Fifteen minutes. Bring the constraint you are under.
  </Card>

  <Card title="Watch this" icon="envelope" color="#0D9373" href="mailto:dmitry@vexa.ai?subject=Roadmap%20update%3A%20Dial-in%20capture%20%E2%80%94%20a%20phone%20into%20a%20conference%20bridge&body=watch" horizontal arrow cta="Email me">
    One email when it ships. The mail is already written — send it as it is.
  </Card>
</Columns>

## Questions

<AccordionGroup>
  <Accordion title="Can Vexa dial into a conference bridge by phone?">
    No. Capture today is a browser bot joining Meet, Zoom or Teams. A bridge reachable only by phone has no route in. A spike exists and is unmerged.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    A phone route into the bridge, and the plumbing to treat it as a capture platform.
  </Accordion>

  <Accordion title="What happens when it ships?">
    It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
  </Accordion>
</AccordionGroup>

***

*Ships upstream Apache-2.0 when sponsored.*