Statamic Inbox Laravel Package

Product Decisions This Supports

• Support ops prioritization: inbox:summary exposes per-mailbox and per-brand counts for new, open, unread, waiting longer than --wartet days, snoozed, and snoozed-until-today conversations. A PM can quantify backlog aging, SLA risk, and triage load before deciding whether to invest in staffing, automation, or mailbox cleanup.
• Build vs. buy for lightweight reporting: If the need is an operational summary for agents over SSH, this package now covers it instead of requiring custom queries or a bespoke dashboard. --json provides a fixed shape for external dashboards, cron reports, and alerting with minimal glue.
• Incident and mailbox-health visibility: Fetch problems (last_error, folder errors, messages given up on) are surfaced in the same summary, supporting on-call handoff and rapid diagnosis of broken mailbox ingestion.
• Privacy-safe triage: --details returns only the first five conversations behind each number with subject, other side, and age—never message bodies—so teams can prioritize without expanding access to content.
• Low-risk production use: The command is read-only: no writes, no events, no log lines, and unread remains unchanged. This makes it safer to give support engineers and agents access over SSH.
• Metric consistency: Moving tab logic into Support\ConversationQuery means listing tabs, the nav unread badge, and inbox:summary share one query path. PMs can trust that reported counts are consistent across UI and CLI, reducing “which number is right?” reporting disputes.
• Brand and rollout validation: --brand narrows the summary to one brand, useful for multi-brand support operations, pilot rollouts, and post-launch health checks.

When to Consider This Package

Consider adoption when:

• You run a Laravel/PHP application with shared inboxes, conversations, and multiple mailboxes or brands.
• Support agents, ops engineers, or on-call staff have SSH access and need quick operational visibility without opening the UI.
• You need SLA-style visibility into conversations waiting longer than a threshold, unread backlog, snoozed work, and mailbox fetch failures.
• You want JSON output for automation—daily standup reports, dashboards, alerting, or smoke tests—without building custom reporting queries.
• You value read-only operational tooling with limited exposure of conversation content.
• You want UI tab counts, nav badges, and CLI summaries to stay aligned through shared query logic.

Look elsewhere or plan for extension when:

• You need full BI/warehouse analytics, historical trend reporting, or real-time streaming dashboards.
• Non-technical users without SSH access are the primary audience.
• You need write actions, workflow automation, or conversation mutations from the CLI.
• You require fine-grained per-agent permissions, audit logging, or compliance controls beyond this command’s read-only scope.
• You need message-body search, customer-level reporting, or multi-channel support beyond the package’s inbox model.
• You need built-in alerting rather than JSON output that you wire into your own monitoring stack.

How to Pitch It (Stakeholders)

Executives: The new inbox:summary command gives read-only operational visibility into support inbox health—aging conversations, unread backlog, snoozed items, and fetch failures—by mailbox and brand. It includes JSON output for dashboards and automation, carries low risk because it performs no writes, and reduces the need for custom reporting. It supports SLA monitoring, faster triage, and more confident staffing and roadmap decisions.

Engineering: One CLI command, backed by the shared ConversationQuery, now powers summaries alongside the listing tabs and nav badge, so counts stay consistent. --json provides a fixed shape for automation; --details is deliberately limited to subject, other side, and age; --brand supports segmentation. The command is read-only by design, and the refactor removes duplicated tab logic from ConversationsController.

Product and support: Use it for daily standups, on-call handoffs, brand health checks, and incident debugging without building a dashboard. It helps prioritize backlog based on waiting time and snoozed work, validates mailbox or brand rollouts, and gives agents a safe, privacy-conscious way to inspect inbox state over SSH.