> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tracklysms.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Discord Alerts

> Configure real-time alerts for delivery, billing, and more

Trackly SMS can send real-time alerts to your Discord channels when important events occur, like delivery failures, opt-outs, or billing thresholds.

## Alert Types

<CardGroup cols={2}>
  <Card title="Delivery Failures" icon="triangle-exclamation">
    When messages fail to deliver due to invalid numbers, carrier issues, or spam filtering
  </Card>

  <Card title="Opt-Outs" icon="user-minus">
    When contacts reply STOP or unsubscribe from your messages
  </Card>

  <Card title="Billing Events" icon="credit-card">
    Payment success, payment failures, and usage threshold alerts
  </Card>

  <Card title="Spam Complaints" icon="flag">
    When messages are flagged as spam by carriers
  </Card>
</CardGroup>

## Default Settings

When you link your account, these alert types are enabled by default:

| Alert Type               | Default                                  | Severity |
| ------------------------ | ---------------------------------------- | -------- |
| Delivery Failures        | ❌ Disabled (summary at 1,000+ threshold) | Medium   |
| Opt-Outs                 | ❌ Disabled                               | Low      |
| Billing Alerts           | ✅ Enabled                                | High     |
| Billing Blocked Sends    | ✅ Enabled                                | High     |
| Inbound SMS              | ❌ Disabled                               | Low      |
| Spam Complaints          | ❌ Disabled                               | Critical |
| Account Error Spike      | ✅ Enabled                                | Critical |
| Delivery Failure Summary | ❌ Disabled                               | Medium   |

## Configuring Alerts

Use the `/alerts configure` command to customize your preferences:

```
/alerts configure delivery_failures:true opt_outs:false billing:true minimum_severity:high
```

### Parameters

| Parameter           | Type    | Description                             |
| ------------------- | ------- | --------------------------------------- |
| `delivery_failures` | Boolean | Enable/disable delivery failure alerts  |
| `opt_outs`          | Boolean | Enable/disable opt-out notifications    |
| `billing`           | Boolean | Enable/disable billing alerts           |
| `inbound_sms`       | Boolean | Enable/disable inbound message alerts   |
| `minimum_severity`  | Choice  | Only show alerts at or above this level |

### Severity Levels

Alerts are categorized by severity:

| Level        | Examples                            |
| ------------ | ----------------------------------- |
| **Low**      | Opt-outs, inbound SMS               |
| **Medium**   | Delivery failures, usage thresholds |
| **High**     | Payment issues, high error rates    |
| **Critical** | Spam complaints, service outages    |

Set `minimum_severity` to filter out lower-priority alerts:

```
/alerts configure minimum_severity:high
```

This shows only High and Critical alerts.

## Muting Alerts

Need a break from notifications? Temporarily mute all alerts:

```
/alerts mute 2h
```

Duration format:

* `30m` - 30 minutes
* `2h` - 2 hours
* `1d` - 1 day

To unmute early:

```
/alerts unmute
```

## Viewing Current Settings

Check your current alert configuration:

```
/alerts status
```

Example response:

```
Alert Preferences
─────────────────
Delivery Failures: Enabled
Opt-Outs: Enabled
Billing: Enabled
Inbound SMS: Disabled
Minimum Severity: Medium
```

## Alert Examples

### Delivery Failure

<Frame>
  ```
  🔴 Delivery Failure

  Message ID: msg_abc123
  To: +1***1234
  Error: REJECTED_ABSENT_SUBSCRIBER
  Segments: 1

  The recipient is not available or the number is invalid.
  ```
</Frame>

### Opt-Out

<Frame>
  ```
  🟡 Contact Opted Out

  Phone: +1***5678
  Reason: STOP
  Source: Inbound SMS

  Contact has been unsubscribed from all lists.
  ```
</Frame>

### Payment Failed

<Frame>
  ```
  🔴 Payment Failed

  Amount: $127.50
  Error: Card declined
  Billing Record: bill_xyz789

  Please update your payment method to avoid service interruption.
  ```
</Frame>

### Spam Complaint

<Frame>
  ```
  🔴 Spam Complaint

  Phone: +1***9012
  Error Code: REJECTED_SPAM
  Message ID: msg_def456

  This number reported your message as spam. Review your content and sending practices.
  ```
</Frame>

## Operational Alert Channels

For critical alerts, notifications are also sent to Trackly's own monitoring channels:

| Channel           | Receives                                |
| ----------------- | --------------------------------------- |
| `#all-alerts`     | All critical alerts across all accounts |
| `#billing-alerts` | Payment failures, spam complaints       |

These channels are for Trackly staff monitoring. You receive alerts in your private account channels.

## Best Practices

<AccordionGroup>
  <Accordion title="Set appropriate severity thresholds">
    If you're getting too many alerts, increase `minimum_severity` to `high`. You'll still see critical issues without noise from routine opt-outs.
  </Accordion>

  <Accordion title="Review delivery failures regularly">
    High delivery failure rates can affect your sender reputation. Address patterns like invalid numbers or carrier rejections.
  </Accordion>

  <Accordion title="Act on spam complaints immediately">
    Spam complaints are serious. Review the flagged message content and remove non-consenting contacts.
  </Accordion>

  <Accordion title="Use muting during known maintenance">
    If you're doing testing or maintenance, mute alerts temporarily to avoid notification fatigue.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup cols={2}>
  <Card title="Discord Commands" icon="terminal" href="/integrations/discord-commands">
    Full command reference
  </Card>

  <Card title="Support Tickets" icon="ticket" href="/integrations/discord-support">
    Get help via Discord
  </Card>
</CardGroup>