> ## 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.

# Name mapping — separated speakers matched to a roster you supply

> Put real names on separated speakers from a roster or calendar invite you supply — no voice enrolment, and an unnamed speaker stays unnamed rather than guessed.

**Can Vexa put real names on speakers it separated?**

**Today:** No. The participants endpoint returns who was invited and who spoke, and deliberately refuses to merge the two — matching a voice to an invitee is a guess.

**Sponsorable:** yes — An explicit mapping step you control, on top of speaker separation.

***

*Put real names on separated speakers, from a list you supply.*

|                 |                                              |
| --------------- | -------------------------------------------- |
| **Status**      | **sponsorable**                              |
| **Size**        | S                                            |
| **North star**  | 2 · Dependable capture                       |
| **Measured by** | served-transcript share and named-word share |

## What it does

* Matches separated speakers to a roster or calendar invite you provide.
* Names come from your list. Nobody enrols a voice.
* Leaves a speaker unnamed rather than guessing at one.

## What exists today

The participants endpoint returns who was *invited* (from the calendar) and who *spoke* (distinct transcript speakers), and deliberately refuses to merge the two — matching a voice to an invitee is a guess, and a wrong guess silently merges two people.

## What this adds

An explicit mapping step you control, on top of speaker separation.

<Note>
  Speaker separation **separates** speakers. Names come from a roster you supply. Nobody enrols a voice.
</Note>

## 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=name-mapping" 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%20Name%20mapping%20%E2%80%94%20separated%20speakers%20matched%20to%20a%20roster%20you%20supply&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 put real names on speakers it separated?">
    No. The participants endpoint returns who was invited and who spoke, and deliberately refuses to merge the two — matching a voice to an invitee is a guess.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    An explicit mapping step you control, on top of speaker separation.
  </Accordion>

  <Accordion title="Does this require voice enrolment?">
    No. Speaker separation separates speakers; names come from a roster you supply. Nobody enrols a voice.
  </Accordion>
</AccordionGroup>

***

*Ships upstream Apache-2.0 when sponsored.*