One customer, every channel

Support tools still organise the world by channel. Email in one tab. Chat in another. A marketplace inbox that only the intern can find. The customer does not experience themselves as nine threads. The tool does.

FluxDM is a unified inbox for that mess. One customer, every channel. The live product is at app.fluxdm.app.

The customer is the entity. The thread is just how they happened to write this time.

What it is

FluxDM is an omnichannel inbox. It is for a team that already talks to people in more than one place and is tired of answering the same person as if they were strangers. The house line is nine channels. The product’s job is to keep the customer in view when the channel changes.

It is not a replacement for every tool a company owns. It is the inbox those conversations should land in.

What this note will not do

This is a house note, not a changelog. We will not list unshipped features, quote an SLA, or describe a workflow that is not in the product you can open today. If you want the product, open it. If you want the legal that applies to FluxDM accounts and data, use FluxDM’s own notices:

• FluxDM privacy policy
• FluxDM terms of service

The house privacy and terms pages are for braidlabs.dev. They will keep pointing here.

Why a house, not a suite

FluxDM does not become better because Reprobox sits in the same brand grid. A captured frontend session and a customer conversation are different jobs. Braid’s job is to keep that distinction, and to put a name on the company that ships both.

Open the inbox

FluxDM is live at app.fluxdm.app. That is the room. This page is the hallway.