---
title: "Review message performance"
description: "Review message lifecycle activity without exposing content, recipients, or customer contact details."
canonical: "https://studio.inttegro.com/inttegro-mcp/workflows/communications/review-message-performance"
format: inttegro-machine-docs/v1
language: "C#"
sdk_version: "v10.3.0"
reader_profile: optional
reader_manifest: "https://studio.inttegro.com/machine/csharp/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 579
model_token_report: "https://studio.inttegro.com/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: ["get_message","get_message_analytics"]
estimated_tokens: 1123
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Review message lifecycle activity without exposing content, recipients, or customer contact details. This C# representation uses the selected SDK's native names wherever Studio has a verified mapping.

### Five questions

#### Q1. When should the reader use Review message performance?

Use this MCP document when an authenticated AI client needs governed Inttegro context, guidance, presentation, or operations.

#### Q2. What is authoritative on this page?

The documented MCP catalog defines available abilities and confirmation boundaries. For live state, the structured tool result is authoritative; presentation output is only a rendering of that result.

#### Q3. What page-specific constraint matters most?

Read operations do not authorize mutations. Actions retain their exact confirmation requirements, and payment credentials or OTP must stay in secure Checkout.

#### Q4. Can Inttegro MCP materially help with this task?

Yes, when the reader has an authenticated MCP connection and the task needs live context, guided planning, or a supported operation. The strongest matches are `get_message`, `get_message_analytics`; their exact roles and boundaries are listed below.

#### Q5. How should the reader verify the answer and continue?

Preserve the structured tool result, distinguish bounded lists from complete analytics, and reconcile asynchronous actions through an authoritative read. Continue with [get_message_analytics](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md#get_message_analytics) when those concerns enter scope.

### Recommended MCP assistance

Use these through an authenticated Inttegro MCP connection. This document remains the contract source.

- [`get_message`](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md#get_message) — read; no mutation confirmation. Gets the lifecycle status of one customer message without exposing its body or recipient contact details.
- [`get_message_analytics`](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md#get_message_analytics) — analytics read; no mutation confirmation. Compares initialized, delivered, and failed customer-message activity, including a clearly labeled delivered-to-initialized period ratio, without message bodies or contact details.

## Document content

# Review message performance

Choose a reporting period explicitly. Message analytics supports `7d`, `30d`, and `90d` periods.

### Prompt

> **Copyable prompt:**
>
> Show message delivery performance for the last 30 days. Include exact
> lifecycle counts and the Flint chart. Do not reveal message content,
> recipients, or customer contact details, and do not estimate missing data.

The agent uses [`get_message_analytics`](https://studio.inttegro.com/machine/csharp/inttegro-mcp/tools.md#get_message_analytics). It reports lifecycle counts and a delivered-to-initialized activity ratio without reading message bodies or recipients.

## Sample response: Message performance for the last 30 days

The response shows aggregate delivery activity only. It contains no message content or recipient details.

- **Initialized**: 240 — Previous period: 218
- **Delivered**: 222 — Previous period: 196
- **Failed**: 11 — Previous period: 14
- **Activity ratio**: 92.5% — Delivered ÷ initialized

### Daily delivered messages

- **Aug 2**: 7
- **Aug 7**: 10
- **Aug 12**: 6
- **Aug 17**: 9
- **Aug 22**: 8
- **Aug 27**: 12
- **Aug 31**: 11

The activity ratio compares aggregate lifecycle counts. The agent does not present it as a cohort delivery rate.