---
digest: >
  v0.26.2 is an emergency web maintenance patch. It brings selected bulk
  conversation actions to the main Conversations view, so users can assign many
  conversations to a journey or delete many conversations in one operation
  without going through one conversation at a time.
---

# v0.26.2 — Web Conversation Bulk Actions

**Date:** 2026-06-14

## Highlights

- Adds selected bulk assignment to the main web Conversations view.
- Adds selected bulk deletion to the main web Conversations view.
- Reuses the existing safe bulk APIs for journey assignment and conversation deletion.
- Keeps the existing Unassigned conversations maintenance flow working with the same controls.

## Where We Started

The web app already had server support for selected conversation assignment and deletion, and the Unassigned conversations maintenance view exposed those controls. The main Conversations view still forced users to handle conversations one at a time, which made emergency cleanup and reclassification slow when many conversations needed the same action.

## What Changed

The main Conversations view now renders a bulk action panel above the grouped conversation list. Each conversation row includes a checkbox. After selecting one or more conversations, the user can choose a journey and assign the selected conversations in one click, or delete the selected conversations after an explicit browser confirmation.

After either operation, the current conversation surface reloads in place. The same shared behavior preserves the existing Unassigned conversations workflow while making the broader Conversations view useful for bulk maintenance.

## Conscious Exclusions

- No inline journey creation inside the bulk assignment panel.
- No new backend mutation path beyond the existing bulk assignment and deletion APIs.
- No undo flow for deleted conversations.
- No change to conversation metadata extraction, repair, or journey inference.

## What We Learned

The maintenance affordance belonged at the place where the user sees the full field, not only at the filtered edge. The safe API already existed; the missing product behavior was exposing that capability where operational pressure actually appears.

## Next Horizon

Future web maintenance work can add richer selection affordances such as select-all by day, filter-aware selection, or inline creation-and-assign flows. This patch stays deliberately small for emergency release.
