• LOGS
  • DATA
  • STATUS
  • HUMAN

How to troubleshoot notification delivery failures with your AI

Connect Courier to your agent to stop digging through dashboards. You just ask why a message didn't land, and your agent finds the error.

Ask AI about this page

Short answer

Why didn't my user get that notification?

Your agent pulls the specific message logs and provider error codes to find the bottleneck. It identifies if the issue was a bad recipient address, an expired token, or a provider rejection. You get a clear explanation of the failure point.

Where every issue lands.

Troubleshooting outcomes.

The agent categorizes failures so you know whether to fix your code or contact a provider.

LOGS

Error identification

The agent looks at message history to find the exact error code returned by the provider. You get the specific reason for the bounce.

DATA

Payload validation

It checks message details to see if the recipient's contact info was missing or malformed. This catches issues before they hit the provider.

STATUS

Delivery state

The agent maps the lifecycle of a message to see if it's stuck in a pending state or was outright rejected. You see exactly where the chain broke.

HUMAN

Manual intervention

If the logs show a provider outage or a blocked user, the agent tells you. You then decide whether to retry the send or update your database.

The workflow

What your AI does when a delivery fails.

The agent moves from broad message lists to specific error details to isolate the problem.

  1. Locate the message

    The agent finds the specific failed alert by looking through your recent message activity.

    list_messages

  2. Inspect the failure

    It pulls the full technical breakdown of the specific message to see the error payload.

    get_message_details

  3. Trace the pattern

    The agent looks at previous attempts for that user to see if this is a recurring issue.

    get_message_history

  4. Report the cause

    The agent summarizes whether the issue was a bad payload, a provider rejection, or a user setting.

    get_message_details

Try it

Copy these to start.

Use these prompts to kick off a troubleshooting session.

Starting points

Replace the bracketed info with your specific message IDs or user emails.

Courier Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_hncOJsHhxey2h41jZqElueYbnMXqfsh2X92gJEYa/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Courier capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "courier-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_hncOJsHhxey2h41jZqElueYbnMXqfsh2X92gJEYa/mcp"
    }
  }
}
Copy into chat04

  • Find the last failed push notification for user user_9921.

  • Check the delivery history for the 'password_reset' template sent to bob@example.com.

  • Why did the SMS sent to +15550102 fail according to the logs?

  • List all messages sent via the Twilio provider that resulted in an error today.

  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Start here

Connect Courier once, then ask.

Link your Courier account in one click. Your credentials stay encrypted, and your agent gets immediate access to your message logs.

Connect Courier to your AI

FAQ

How this task behaves.

  • 01

    Can the AI resend the failed notification?

    No. The agent can only read logs and message details. You must trigger a resend through your own application or the Courier dashboard.

  • 02

    Can the AI change user notification preferences?

    No. The agent only has read access to message history and details. It cannot modify user settings or contact information.

  • 03

    Does the AI see the actual content of the messages?

    Yes, if the message details are included in the payload, the agent can read the content to help you debug formatting issues.

  • 04

    Can the AI fix a broken provider integration?

    No. The agent identifies that a provider is returning errors, but it cannot change your API keys or provider configurations.

  • 05

    How does the agent know which message to look at?

    You provide the context, such as a user email, a specific message ID, or a timestamp, and the agent uses that to filter the logs.

  • More questions about Courier? The Connector page answers them. See everything the Courier Connector can do

Connect Courier to Claude, Cursor, ChatGPT & more