> ## Documentation Index
> Fetch the complete documentation index at: https://polyai-mintlify-665e356f.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# 05.2026

> May 2026 release notes.

The **May 2026** PolyAI Agent Studio release ships a redesigned **Conversations** workspace built for high-volume review, adds a one-click **Tripleseat** integration for restaurant agents, and starts populating the **HANDOFF\_TO** response metric for voice handoffs.

Expand the items below for details:

<AccordionGroup>
  <Accordion title="Conversations workspace revamp" icon="comments" id="conversations-revamp">
    <img src="https://mintcdn.com/polyai-mintlify-665e356f/ITmGFFs_1FlEHv25/images/analytics/conv-review-side-panel.png?fit=max&auto=format&n=ITmGFFs_1FlEHv25&q=85&s=0a5d1b75cad7b1f3759e6d821724d300" alt="conv-review-side-panel" width="2490" height="1026" data-path="images/analytics/conv-review-side-panel.png" />

    The Conversations page is now organized around channel scopes, saved views, layered diagnosis, and an integrated review side panel — purpose-built for analyzing conversations at scale.

    * **Voice and Webchat as separate scopes** — each with their own saved views, column layouts, and an integrated review side panel that opens without leaving the table.
    * **Saved views** — built-in **Production** and **Test** System Views, plus your own **Custom Views** as pinned tabs. Duplicate, set as default, and share filters as a link.
    * **Diagnosis toggle group** — debugging layers (tool calls, flows, variables, latency, logs, sources) are now independent toggles that persist as you move between conversations.

    See [Conversation review](/analytics/conversations/review), [Views](/analytics/conversations/views), and [Diagnosis](/analytics/conversations/diagnosis) for the full walkthrough.
  </Accordion>

  <Accordion title="HANDOFF_TO populated on voice handoffs" icon="phone-arrow-up-right" id="handoff-to-metric">
    Voice conversations that end in a handoff now record the destination on the `HANDOFF_TO` response metric, alongside the existing `HANDOFF_REASON`. Previously only the reason was emitted, so dashboards and API consumers could not see *where* the call was being transferred to.

    * Applies to both the OpenAI Realtime and Raven Omni voice engines.
    * `HANDOFF_TO` is populated with the destination configured on the handoff (for example, `FRONT_DESK` or `SALES`) whenever the call ends with the `HANDOFF` outcome.
    * No configuration change is required if you have already enabled `HANDOFF_TO` as a response metric. To start exposing it in API responses, enable it under **API Keys > Configuration** — see [Metrics](/settings/metrics#enabling-metrics-for-api-responses).
  </Accordion>

  <Accordion title="Tripleseat integration" icon="champagne-glasses" id="tripleseat-integration">
    Connect PolyAI to **Tripleseat** to capture event and large-party leads from voice, webchat, and SMS conversations — without writing custom code. Projects on the PLG restaurant template can connect Tripleseat through one-click OAuth from the Integrations page; other projects continue to be supported through Managed Services.

    See [Tripleseat](/integrations/tripleseat) for the setup guide.
  </Accordion>
</AccordionGroup>