Inkpilots

Digests and Review

Workflow

In Inkpilots, digests are about audience subscription and broadcast communication, not editorial review dashboards. The digest system gives a workspace a lightweight way to collect subscriber emails from its public surface, monitor subscriber growth over time, and prepare for outbound digest broadcasts.

This page explains the current digest behavior as it exists in the product today, including what visitors experience, what workspace users can track, and what parts of the broadcast flow are still emerging.


What the digest system is for

Use digests when your workspace needs to:

  • let public visitors subscribe with their email address,
  • build an audience around the workspace,
  • track how subscriber counts are changing,
  • prepare to send broadcast-style communications to that audience.

This makes digests part of the public engagement layer of Inkpilots. They help a workspace move beyond one-time visits and build an ongoing relationship with readers, followers, or prospective customers.


How visitors subscribe

On the public workspace side, Inkpilots provides a digest subscription modal that invites visitors to join by email.

The current public digest flow includes:

  • an email input and subscribe action,
  • validation through the public digest endpoint,
  • rate limiting for public submissions,
  • duplicate protection for already subscribed emails,
  • local preference storage so dismissed or subscribed visitors are not prompted repeatedly.

From the visitor perspective, the experience is intentionally simple. The goal is to remove friction from subscription while still protecting the workspace from spam or repeated submissions.


What happens after a subscription

When a visitor subscribes, the email is stored against the workspace digest list. The system currently supports:

  • creating a new digest subscription for a workspace,
  • recognizing when an address is already subscribed,
  • associating the subscription with the correct workspace,
  • exposing subscriber counts through the workspace digest analytics view.

This is important because the digest feature is workspace-scoped. Subscribers are not joining a global product-wide list. They are joining the digest audience for a specific public workspace.

Since May 2026, digest broadcasting is not enabled, We hope to enable it by December 2026.


What workspace users see in the digest tab

Inside the dashboard, the Digest tab is currently an analytics and management entry point for subscriber growth.

The existing digest surface shows:

  • total joined subscribers,
  • subscribers joined in the current time window,
  • subscribers joined in the previous time window,
  • numeric change between periods,
  • percentage change between periods,
  • the most recent join timestamp when available.

These metrics can be viewed across three time windows:

  • day,
  • week,
  • month.

This makes the digest tab useful for understanding whether audience acquisition is growing, flattening, or slowing over time.


How to interpret the digest metrics

The digest metrics should be read as audience growth signals.

Total joined

This is the current size of the subscriber base for the workspace.

Current window

This shows how many subscribers were added during the selected active period.

Previous window

This gives a baseline for comparison so the team can understand whether the current period is stronger or weaker than the one before it.

Change and percentage change

These values show whether subscriber growth is moving up or down. A positive change suggests stronger acquisition in the current period. A negative change suggests slower acquisition and may indicate that the public surface, content cadence, or calls to action need attention.

Last joined

This helps operators confirm that subscriptions are still arriving and gives a quick sense of recency.


What the create broadcast action means today

The Digest tab already includes a create action for broadcast workflows. In the current product, that broadcast flow is presented in the UI but is still marked as coming soon.

That means the correct way to understand the current state is:

  • subscriber collection is implemented,
  • subscriber analytics are implemented,
  • the workspace-facing broadcast authoring flow is staged in the product direction,
  • full digest broadcasting is not yet the mature part of the feature.

This distinction matters for documentation. Teams can already grow and monitor an audience. They should treat broadcast authoring as an emerging workflow rather than an already complete delivery channel.


Use digests as an audience layer

Digest subscriptions are most valuable when the workspace has a clear public identity and a reason for visitors to return.

Track growth by time window

Use day, week, and month views for different questions:

  • day for immediate response to campaigns or visibility changes,
  • week for short-term trend monitoring,
  • month for broader audience growth patterns.

Align subscription prompts with real value

Do not ask visitors to subscribe unless the workspace can give them a reason to care, such as recurring updates, new published content, or useful broadcast communication.

Treat future broadcasts as governed communication

When broadcast sending becomes part of the workflow, it should be treated as a deliberate communication layer, not as a generic email blast tool.


Common mistakes to avoid

  • Treating digests as an editorial review feature instead of a subscriber and broadcast feature.
  • Measuring only total subscribers and ignoring period-over-period growth.
  • Using subscription prompts on a public workspace that does not yet communicate a clear value proposition.
  • Assuming the visible broadcast entry point means the full outbound workflow is already complete.

How digests connect to the rest of the product

Digests work best when paired with:

These areas together shape whether visitors trust the workspace enough to subscribe and remain interested in future communication.