History
Cross-channel send history, search, filters, and export.
Open Logs → History for cross-channel sends, or open a channel log for one channel only.
What this page is for
Cross-channel outbound send history — log ID, device, recipient, message preview, channel, status, and timestamp — across WhatsApp, Telegram, WABA, and email in one searchable table.
Sample data shown.
Cross-channel history
Logs → History aggregates outbound activity across WhatsApp, Telegram, WABA, and email so you can trace sends without opening every channel log.
Use the Channel filter to narrow to one channel, or use the shortcuts in the page subtitle (WA log, Telegram log, WABA log, Email log) to jump to that channel’s dedicated log page.
Search and filter
Search is field-based: click the search area first, pick which column to search, then type your query.
| Filter / control | What it does |
|---|---|
| Search | Recipient, Log ID, or Message — see search fields below |
| Channel | All channels, WhatsApp, Telegram, WABA, or Email |
| Device | Filter by sending device — pick a Channel first (WhatsApp number, Telegram bot, WABA device, or email sender) |
| Status | All statuses, Sent, or Failed |
| Export CSV | Download matching rows (includes ID and Device) |
Search fields
| Search field | Matches | Minimum length |
|---|---|---|
| Recipient | Phone numbers or email addresses that contain your query | 3 characters |
| Log ID | The full, exact numeric ID from the ID column | Full ID only |
| Message | Message body or subject text that contains your query | 3 characters |
Recipient and Message search scan the most recent 1,000 sends per step (respecting Channel, Device, and Status). When older sends may still match, Kirisan shows Continue search below the table — same behavior as per-channel logs.
Log ID returns results immediately and does not use Continue search. Enter the full numeric ID from the ID column (exact match only).
History table
Each row is one outbound send:
| Column | Meaning |
|---|---|
| ID | Unique send row ID — copy the full number for Log ID search (exact match only) |
| Device | Sending device for that channel — see below |
| Recipient | Primary destination (phone, chat id, or email) |
| Target | Raw target value from the send payload (when different from Recipient) |
| Message | Truncated preview with a channel icon |
| Channel | WhatsApp, Telegram, WABA, or Email |
| Status | sent or failed |
| Sent | When the send was recorded |
Rows are clickable — Kirisan opens a channel-appropriate message preview (WhatsApp-style bubble, Telegram bubble, or email HTML preview).
When Recipient or Message search scans a batch with no matches but older sends remain, use Continue search:
Device column by channel
| Channel | Device shows |
|---|---|
| Device name + Fonnte number (from Devices) | |
| Telegram | Bot username or name (from Devices) |
| WABA | Display name + Cloud API phone (from Devices) |
| Sender name + from address (from Emails) |
When device tracking was not stored for an older send, Device shows — — use Recipient, Message, or Log ID instead.
Tips
- Filter Channel first, then Device when you need one WhatsApp number, bot, WABA device, or email sender.
- Search Recipient or Message after narrowing Channel (and optionally Device).
- Use Log ID when support or an API response gives you the exact row ID from the ID column.
- Per-channel logs also offer a Device (or Sender) filter if you work in one channel only.
Per-channel logs
Each channel exposes its own searchable, paginated log with the same ID, Device (or Sender for email), search fields, and Continue search behavior:
| Channel | Sidebar menu |
|---|---|
| Channel → WhatsApp → Logs | |
| Telegram | Channel → Telegram → Logs |
| WABA | Channel → WABA → Logs |
| Channel → Email → Logs |
Rows typically include status, recipient, content preview, and timestamp. Failed rows show error detail for support.
Email log previews show plain text extracted from the HTML body (no markup). The home dashboard Recent sends list uses the same style for email rows.
Webhook logs
Webhooks → Logs lists delivery attempts to your endpoints — HTTP code, duration, and error messages.
Email-specific logs
Beyond send logs, review:
- Email → Bounce — addresses that failed permanently or temporarily
- Email → Suppression — blocked recipients
Related
- Statistics — cross-channel volume and delivery trends (Logs → Statistics)
- Read cross-channel statistics — compare time windows and read the daily chart
- WhatsApp logs
- Telegram logs
- WABA logs
- Email logs