Exstream interactive and on demand channel counts

Interactive and on demand output is the part of an Exstream estate that produces communications one at a time, in response to a user action or a system request, rather than in a scheduled batch. A service representative composes a letter while a customer is on the line, a self service portal generates a statement when the account holder asks for it, an API returns a document the moment a downstream system calls for one. This output is real and licensable, but it is also where channel counting goes wrong most often, because a single interactive request can touch several delivery paths and a measurement taken at the request level can read each path as a separate channel. Understanding Exstream interactive and on demand channel counts lets a buyer scope this output to the channels the authorization actually defines, rather than to the number of times a user pressed a button.

This article explains what interactive and on demand output is, why its channel counts inflate, and how a buyer scopes them correctly. It supports our Exstream and customer communications audit defense practice and links up to the complete OpenText audit defense playbook for 2026.

What interactive and on demand output actually is

Batch composition runs on a schedule against a data file. Interactive and on demand composition runs in response to a trigger: a user editing a document in an interactive editor, a portal request, an API call, or a real time event from another application. The output is the same kind of communication a batch run produces, a composed document, but the trigger and the timing are different. That difference matters for counting because interactive output does not arrive in clean, countable cycles. It arrives continuously, in small increments, and each increment may be logged in several systems at once. When a finding sums those logs without reconciling them, the same composed communication can appear more than once and across more than one apparent channel. The composition versus delivery distinction at the heart of this is the same one set out in Exstream multichannel output and the metric definition.

Why interactive channel counts inflate

The inflation comes from counting the request rather than the delivered communication, and from reading every delivery path as a distinct channel. A representative who previews a document, edits it, and then sends it has generated several logged events for one communication. A portal that renders a statement on screen and also offers a download has produced one composed document delivered through what the metric should treat as a single digital path, not two. An API that returns a document to a calling system, which then itself emails the document, can be counted once by Exstream and again by the downstream mailer if the audit reaches both logs. The decision about whether delivery paths are separable at all is the subject of can OpenText count all output channels separately, and the broader pattern of path level overcounting is covered in Exstream output channel counting traps.

There is a second source of inflation specific to on demand output. Because it is triggered by external systems, on demand composition is often instrumented for monitoring rather than for licensing, and the monitoring counters tally calls, retries, and health checks alongside genuine production requests. A retry after a timeout is not a new communication. A health check that exercises the composition path produces no delivered document at all. A measurement that takes the monitoring counter as the volume figure inherits all of that noise. Separating production requests from operational traffic is the same discipline applied to scheduled work in Exstream non production and test volume scope.

Scoping interactive and on demand counts correctly

Scoping reduces the raw request and event totals to composed communications delivered through defined channels. The categories that need separating are these:

• Composed and delivered communications. The interactive or on demand requests that produced a document delivered to a recipient, the figure the metric intends.
• Previews, edits, and reissues. The intermediate events that belong to a single communication and must not each count as output.
• Retries, health checks, and monitoring calls. Operational traffic on the on demand path that delivers no communication.
• Multipath deliveries. A single communication offered through more than one path, scoped to the channels the authorization actually distinguishes rather than to every logged path.

Each category is matched to the metric the authorization defines. The print versus digital distinction that governs whether two paths are even separate channels is treated in Exstream print versus digital channel licensing, and the role of the interactive editing clients in this output is set out in Exstream Empower and Dialogue licensing.

The evidence that supports the scope

The buyer proves the scope from interactive and on demand operational records. Composition engine logs show which requests produced a delivered document and which were previews, edits, or reissues of an existing one. API gateway and integration logs distinguish production calls from retries, health checks, and monitoring traffic. Output management and delivery records show which paths a single communication actually used. Editor session logs show the difference between a representative working on one document and producing several. Assembled before any vendor measurement, this record converts a raw event total into a count of composed communications delivered through defined channels. Gathering it is part of reconciling Exstream entitlements before an audit.

A representative outcome

In a recent engagement, an Exstream finding had counted a self service portal's interactive output by request event rather than by delivered communication, so previews and on screen renders that were never delivered as separate documents had each added to the channel total, and a layer of API retries from a flaky downstream system had been swept in as production volume. By rebuilding the count from the composition and delivery logs, and by showing which events were previews, retries, and health checks, we reduced the interactive total to its delivered figure across the defined channels. The matter settled well below the opening claim, consistent with the firm reductions, where the average finding has come down 68 percent across more than 200 defended audits since 2020.

Holding the interactive scope forward

Interactive and on demand scope is worth carrying into the forward agreement, because this output keeps growing as more customer interaction moves to portals and APIs. When the resolution records that a composed communication delivered through a defined channel is the chargeable unit, and that previews, retries, and monitoring calls are excluded, the next review starts from an agreed definition rather than from a raw event log. For the cost framing buyers ask about first, see how much does an Exstream volume finding usually cost, and for the line by line method that produces these reductions, see defending an Exstream volume overclaim line by line.

Why interactive output rewards early instrumentation

Interactive and on demand output deserves attention before an audit notice arrives, because its evidence is the most perishable in the estate. Batch scheduler logs at least tend to be retained for operational reasons, but the request level detail that distinguishes a preview from a delivery, or a retry from a fresh call, is often held only briefly and then discarded as monitoring data ages out. A buyer that waits until the seven day notice lands to reconstruct its interactive channel counts may find that the events for the earlier part of the audit window are gone, leaving only a summary counter that cannot be decomposed. The disciplined approach is to instrument the composition and delivery paths so that delivered communications can always be separated from previews, retries, and monitoring traffic, and to retain that detail across the period the audit might reach. This is inexpensive relative to the exposure it prevents, and it means the channel count can be defended from records rather than argued from inference. When the instrumentation is in place, an interactive finding stops being a guess about what a portal or an API really produced and becomes a reconciled number that the buyer can stand behind line by line. To plan that work, open a case and we will map your interactive and on demand paths before the vendor measures them, and you can reach us through the contact form on this site.