Skip to content
TruthVouch Docs

Notification Channels

Configure how Shield sends alerts to your team. Choose from email, Slack, Teams, PagerDuty, webhooks, and in-app notifications. Route alerts by severity, category, or custom rules.

Supported Channels

1. Email

Send alerts via email to individuals or distribution lists.

Setup:

  1. Go to Shield → Settings → Notification Channels
  2. Click Add Channel → Email
  3. Enter recipient email (individual or group)
  4. Test delivery: Click Send Test Email
  5. Save

Features:

  • HTML-formatted email with full alert details
  • Unsubscribe link (for individual recipients)
  • Includes suggested correction (if available)
  • Clickable link to open alert in dashboard

Best for: Formal notifications, audit trail, non-urgent alerts

Example email:

Subject: Shield Alert: Hallucination Detected (Medium Severity)
From: alerts@truthvouch.com


Alert Details
─────────────
Severity:    Medium
Type:        Hallucination
Fact:        "TruthVouch Series A funding was $50M"
AI Engine:   ChatGPT
Detected:    2024-03-15 14:32 UTC


What AI Said
"TruthVouch raised $50M in Series A funding from Sequoia Capital"


Your Truth
"TruthVouch raised $40M in Series A (Sequoia, others)"


Suggested Correction: [View & Approve] [Edit Truth Nugget] [Dismiss]


Review full alert: [Open in Dashboard]

2. Slack

Send alerts to Slack channels or direct messages.

Setup:

  1. Click Add Channel → Slack
  2. Authorize TruthVouch Slack app (OAuth)
  3. Select target channel (#security-alerts, @john, #product, etc.)
  4. Configure message format (summary vs. detailed)
  5. Test: Click Send Test Message

Features:

  • Rich message formatting with buttons
  • Quick actions: “Approve Correction”, “Dismiss”, “Investigate”
  • Threading for related alerts
  • Configurable emoji/icons per severity

Slack message example:

:warning: Medium Severity Alert
Hallucination detected in "TruthVouch funding" fact
ChatGPT claimed: $50M (your fact: $40M)


[Approve Correction] [Dismiss] [View Details]

Best for: Real-time alerts, team collaboration, quick triage

3. Microsoft Teams

Send alerts to Teams channels or direct messages.

Setup:

  1. Click Add Channel → Microsoft Teams
  2. Authorize TruthVouch Teams app
  3. Select target team/channel
  4. Configure message formatting
  5. Test delivery

Features:

  • Adaptive cards with full alert details
  • Action buttons for quick response
  • Threading and mentions (@channel, @person)
  • Integrates with Teams workflows

Best for: Organizations using Teams; enterprise communication

4. PagerDuty

Trigger PagerDuty incidents for critical alerts.

Setup:

  1. Click Add Channel → PagerDuty
  2. Enter PagerDuty API key (from PagerDuty integration settings)
  3. Select escalation policy (who gets paged)
  4. Configure trigger rules (which alert severities trigger incidents)
  5. Test: Click Send Test Incident

Features:

  • Creates incident in PagerDuty on-call dashboard
  • Responder can acknowledge/resolve from PagerDuty
  • Escalates if not acknowledged within X minutes
  • Integration with incident management workflows

Best for: Critical alerts requiring immediate response

Example config:

  • Trigger PagerDuty incident if:
    • Alert severity = Critical OR
    • Same fact hallucinated 3+ times in 1 hour
  • Escalation policy: “AI Governance On-Call”
  • Auto-resolve PagerDuty incident when Shield alert resolved

5. Webhooks

Send alerts to custom endpoints (your own system, Zapier, etc.).

Setup:

  1. Click Add Channel → Webhook
  2. Enter webhook URL (must be HTTPS)
  3. Optionally: Add custom headers (authentication)
  4. Test: Click Send Test Webhook

Features:

  • HTTP POST with JSON payload
  • Retries on failure (3 attempts with backoff)
  • Signed requests (HMAC signature for verification)
  • Customizable payload

Example webhook payload:

{
  "event": "alert.created",
  "alert_id": "alt_abc123",
  "severity": "medium",
  "type": "hallucination",
  "fact": "TruthVouch Series A funding was $50M",
  "ai_response": "TruthVouch raised $50M in Series A",
  "truth_nugget": "TruthVouch raised $40M in Series A",
  "confidence": 0.92,
  "timestamp": "2024-03-15T14:32:00Z",
  "detection_url": "https://truthvouch.com/shield/alerts/alt_abc123"
}

Best for: Custom integrations, automation, advanced workflows

Example use case: Send alerts to your internal incident management system (Jira, ServiceNow, etc.)

6. In-App Notification

Alerts visible in Shield dashboard notification center.

Features:

  • Bell icon shows unread count
  • Click to see all alerts
  • Mark as read/unread
  • Filter by severity, type, date

Always enabled (cannot disable)

Best for: Internal reference; secondary notification method

Routing Rules

Route alerts to different channels based on severity, category, or custom conditions.

Default Routing

Critical & High Severity:

  • Email to Security team
  • Slack #security-alerts
  • PagerDuty (page on-call)

Medium Severity:

  • Email to relevant team owner
  • Slack #product-alerts

Low Severity:

  • In-app notification only
  • Daily digest email

Custom Routing Rules

Create rules to override defaults:

Example Rule 1: Financial Facts Critical

  • If: Alert about financial fact (fact category = “Financial”)
  • Then: Send to Finance team email + Slack #finance-alerts + page CFO

Example Rule 2: Brand Facts High Priority

  • If: Alert about brand/product (category = “Product”)
  • Then: Send to Marketing team + Slack #marketing
  • Do NOT page (non-critical for sleep schedules)

Example Rule 3: High-Velocity Alerts

  • If: Same fact hallucinated 3+ times in 1 hour
  • Then: Escalate severity to Critical + page on-call
  • Reason: Sustained hallucination = urgent

Create Routing Rule

  1. Go to Settings → Alert Routing
  2. Click Create Rule
  3. Define condition:
    • Alert severity (Critical, High, Medium, Low)
    • Fact category (Financial, Product, Leadership, etc.)
    • AI engine (ChatGPT, Claude, Gemini)
    • Fact name (if specific)
  4. Select channels:
    • Which channels to use
    • Include suggestions? (Yes/No)
    • Urgency level (if PagerDuty)
  5. Save

Channel Priority

If multiple channels are active for same alert, they all fire unless you set priorities.

Example: Prevent duplicate notifications

Instead of:

  • Email to #security-alerts
  • Slack #security-alerts
  • PagerDuty (all firing for same alert)

Use priority order:

  1. If PagerDuty incident created → Don’t send Slack/Email
  2. If Slack notification sent → Don’t send Email
  3. Always send In-app notification

Prevents notification fatigue.

Notification Frequency

Real-Time

Alert sent immediately when detected.

Use for: Critical/High severity alerts

Batched Digest

Collect multiple alerts; send single email/Slack message with summary.

Options:

  • Hourly digest (collect alerts; send once per hour)
  • Daily digest (morning 9 AM; evening 5 PM)
  • Custom (collect until N alerts or X hours)

Example digest:

Daily Alert Summary (March 15, 2024)
────────────────────────────────────
Critical:   2 alerts
High:       5 alerts
Medium:     8 alerts
Low:       12 alerts


Top Issue: "Product pricing" hallucinated 5x
→ Approve 1 correction (fixes all 5)


[View Full Report] [Manage Alerts]

Use for: Non-critical alerts; low-severity trends

Testing Notifications

Before going live, test each channel:

  1. Click Test on the channel config
  2. System sends test alert
  3. Verify you receive it
  4. Check formatting (email layout, Slack message clarity, etc.)

Test alert format:

TEST NOTIFICATION - This is a test
Type: Hallucination
Fact: "TruthVouch was founded in 2023"
Severity: Test (no action needed)

Troubleshooting

Email Not Received

  • Check spam folder — Alerts may be marked as spam
  • Verify email address — Typo in recipient email?
  • Check company email rules — Your email system might block external senders
  • Test delivery — Click “Send Test Email” to confirm setup works

Slack Connection Fails

  • Re-authorize app — Click “Reconnect to Slack”
  • Check channel permissions — App must have write access to channel
  • Verify channel name — Use #channel-name format (not display name)

PagerDuty Incidents Not Creating

  • Verify API key — Check PagerDuty integration still valid
  • Check escalation policy — Must be active (not archived)
  • Review trigger rules — Does alert severity match rule?
  • Check PagerDuty account — Is service active? Are users on-call?

Webhook Not Firing

  • Verify URL — Must be HTTPS, publicly accessible
  • Check auth headers — If authentication required, verify credentials
  • Review payload — Does your system parse JSON correctly?
  • Check firewall — Can your system reach the webhook URL?

Next Steps

  1. Identify notification requirements — Who needs to know about alerts?
  2. Set up channels — Email for formal record, Slack for quick triage, PagerDuty for critical
  3. Configure routing rules — Route by severity and category
  4. Test all channels — Verify setup works end-to-end
  5. Establish escalation policy — Who pages who if urgent?