# AI Analyst — evidence-backed telecom investigations

> Last updated: 2026-06-12. Admin panel: https://admin.trustrouting.com/ai-analyst

## Summary

**TrustRouting AI Analyst** is a chat interface in the web admin panel that answers operational questions about your captured delivery data — SMS, OTP, calls, RCS, and optional chat-notification traffic from real Android handsets.

It is part of the **AI Evidence Engine**: answers cite fields from your TrustRouting records (SMSC, operator, delay, channel, platform match). AI recommends next steps; **your team decides** — nothing is auto-blocked.

## Who can use it

- Available to **admin accounts** with an active subscription (not read-only viewer accounts)
- Works on data already synced from your Android test devices
- Complements manual filters, analytics, and XLSX exports — does not replace them
- Questions work in **English or Russian** (free-text); UI labels are English-only

## Filters (sidebar)

Before you ask, narrow the dataset:

| Filter | Purpose |
| --- | --- |
| **Period** | Presets: 7 / 30 / 90 days, or custom date range |
| **Phone number** | Type MSISDN or pick from synced numbers on your devices |
| **Service name** | e.g. WhatsApp, a bank OTP service |
| **Channel** | All, SMS, Calls, RCS, WhatsApp, Viber, Telegram |

Batch Analyze uses the same filter scope (up to 100 events per run).

## Quick actions (one-click templates)

- What services were delivered to a number in the period, and are there delivery problems?
- Are there signs of grey-route or tariff-path bypass?
- Is OTP delivery stable for a service on this number?
- Which unknown or suspicious GT/SMSC should we review?
- Which services deliver via non-SMS channels (WhatsApp, Viber, RCS)?
- Classify calls: flash-call, robocall, or normal service call
- Which traffic did not go through my platform (PLATFORM_MATCH = No)?
- **Batch Analyze** — run automated analysis across the filtered dataset (async job, up to 100 events)

## You can also ask (free-text)

These question types are routed automatically when you type in the chat (no separate quick-action button):

| Topic | Example question |
| --- | --- |
| **SMSC classification** | Which GT/SMSC are normal vs suspicious for this service? |
| **Channel shift** | Is this service shifting from SMS to WhatsApp, Viber, or flash-call? |
| **Voice spikes** | Are there suspicious spikes of short or robocall-like traffic? |
| **Network / route quality** | Are there serious delivery or route-quality problems on this route? |
| **Action vs monitoring** | Do we need to act now, or is monitoring enough? |
| **Service pattern** | Which detection pattern matches this service, and how confident is it? |
| **Poor recognition** | Which services are poorly recognised (high Unknown share)? |

## Chat behaviour

- **Multiple threads** — separate conversations with persisted history per admin account
- **Streaming answers** — responses appear incrementally in the chat
- **Clarification** — if a required input is missing (e.g. phone number for “services on number”), the assistant asks before running analysis
- **Copy answer** — one-click copy for escalation notes or vendor emails
- **Deep links** — when offered, open the underlying SMS/call/RCS record in Messages for manual review
- **Analysis context** — shows the period and filters used for the answer

## Typical use cases

| Team | Question AI Analyst helps answer |
| --- | --- |
| CPaaS / SMS hub | Summarize SMSC mismatch and delay patterns before a supplier escalation |
| MNO | Flag unknown GT/SMSC candidates and off-platform traffic |
| Enterprise / banking | Check OTP stability on a test number before launch |
| Voice / flashcall | Classify short calls and robocall patterns on a handset |

## How it works

1. Install the [Android agent](https://trustrouting.com/install) and sync traffic to the admin panel
2. Open [AI Analyst](https://admin.trustrouting.com/ai-analyst)
3. Set period, optional MSISDN, service, and channel filters
4. Ask a question, use a quick action, or run Batch Analyze
5. Review the evidence-backed answer; open linked message records when offered
6. Export or escalate using existing XLSX workflows

## Guardrails

- **Evidence-first:** claims reference your captured records, not supplier DLRs alone
- **Human review:** recommendations only — no automatic blocking or route changes
- **Privacy:** OTP codes in message bodies are masked before analysis

## Related AI features (not the chat page)

These live elsewhere in the admin panel under **AI Evidence Engine**:

| Feature | Where | What it does |
| --- | --- | --- |
| **Per-event analysis** | Messages record detail | Analyze a single SMS/call/RCS row |
| **AI Reports** | Reports | Weekly / monthly summaries |
| **Dashboard widget** | Dashboard | Risk counts and distribution snapshot |
| **Cases / Firewall** | Super admin | Case management and firewall rules |

## Related pages

- [Product overview](https://trustrouting.com/product)
- [AI Analyst page](https://trustrouting.com/ai-analyst)
- [Web admin guide](https://trustrouting.com/admin-guide)
- [SMS route monitoring](https://trustrouting.com/sms-route-monitoring.md)
- [Admin panel login](https://admin.trustrouting.com)