Skip to content

Beginner

3 min read

Stay in the UI. Finish Start here, then learn these four ideas in order. Together they cover the daily loop: compose something reusable, send it, automate a simple reply, and verify what happened.

1. Send

Send is the one-off composer. You pick a connected device, a recipient (typed number/chat/email or a contact), and either an inline message or a saved template. Use this to prove the channel works before you automate anything.

Fallback channels, variables, and attachments (when your plan allows) are available here the same way they appear later in Campaign and the API.

Send — composer overview

2. Templates

A template is a reusable message layout — text, media, buttons, or (for WABA/email) provider-approved / HTML structures. Create templates once, then pick them from Send, campaigns, schedules, and autoreply instead of retyping.

WABA templates also go through Meta approval; email templates are HTML blocks with variables. Chat channels (WhatsApp / Telegram) are more flexible for free-form layouts.

WhatsApp templates list

ChannelDocsDashboard
WhatsAppTemplatesTemplates
TelegramTemplatesTemplates
WABATemplatesTemplates
EmailTemplatesTemplates

3. Autoreply

Keyword autoreply watches inbound text on selected devices. When a message matches a rule, Kirisan sends the configured response (text, media, template) without an agent. Start with a few clear keywords (“price”, “hours”, “help”) before you build multi-step Flow.

Autoreply keyword rules

4. Logs & inbox

Logs prove outbound attempts (status, errors, which device). Inbox holds inbound conversations so you can read and reply from the dashboard. Check both after every test send or autoreply — if Send looks fine but the customer never got the message, the log reason is usually the answer.

Message history — outbound sends

Inbox — inbound conversations

NeedWhat it showsDocsDashboard
Outbound historyCross-channel sendsHistoryHistory
Cross-channel inboxWhatsApp, Telegram, WABA togetherInboxInbox
WhatsAppDevice log + chat inboxLog · InboxLog · Inbox
TelegramBot log + inboxLog · InboxLog · Inbox
WABACloud API log + inboxLog · InboxLog · Inbox
EmailOutbound log + mailboxLog · InboxLog · Inbox

Next

Level up: Power. Prefer code? Developer path.