Skip to content

Keyword autoreply

Match incoming messages by keyword and send automatic replies.

4 min read

Open Autoreply → Autoreply.

What this page is for

Autoreply templates match incoming WhatsApp, Telegram, or WABA messages by keyword and send an automatic reply — plain text, a channel template, or a submission form.

Each device handles inbound messages in exactly one mode. For keyword rules to run, set On incoming message to Autoreply on the device (see Enable autoreply on a device below).

Autoreply — template list, search, and table

Sample data shown.

Template list

Column / controlWhat it does
Add templateOpens the editor to create a new keyword rule.
Search by name or keyword…Filters the list (minimum 3 characters).
NameOptional label for your reference — matching still uses Keywords.
KeywordsTrigger phrases (comma-separated in the table when there are several).
LogicHow the incoming message is compared to keywords.
TypeMessage, Template, or Submission.
ResponsePreview of the reply text, template name, or submission form name.
ChannelsClick N linked to see which devices or bots use this template.
UpdatedLast save time.
ActionsEdit template or Remove template.

Create or edit a template

Click Add template or edit an existing row.

New autoreply template — devices, keywords, logic, and response

Sample data shown.

1. Name (optional)

A short label such as Price list — helps you find the rule in the list. Keywords still control matching.

2. Devices

Use the channel filter (WhatsApp, Telegram, or WABA), search, and pick one or more devices or bots. Use All or All filtered to link many at once.

The same template can target multiple channels. For Template response type, switch the channel filter to configure the WhatsApp, Telegram, or WABA template separately.

3. Keywords

Add one keyword per field. Any keyword in the list can trigger the rule.

Click Add keyword for more triggers (for example price and harga).

4. Logic

LogicMatches when
Exact matchThe full message equals the keyword (trimmed, case-insensitive).
ContainsThe message includes the keyword anywhere.
Starts withThe message begins with the keyword.
Ends withThe message ends with the keyword.

Put specific rules above broad ones — Kirisan evaluates templates in list order and the first match wins.

5. Response type

TypeWhat Kirisan sends
MessagePlain text, with an optional image attachment from upload or Files. Same text goes to all linked devices.
TemplateA saved template from Channel → channel → Templates. Pick the template per channel when devices span WhatsApp, Telegram, and WABA.
SubmissionStarts a submission form — questions run as a chat session on the sender’s side.

Click Add template (or Save changes) to apply.

Enable autoreply on a device

Keyword templates only run when the device is in Autoreply mode:

  1. Open Channel → WhatsApp → Devices, Channel → Telegram → Devices, or Channel → WABA → Devices.
  2. Edit the device.
  3. Under On incoming message, choose Autoreply (not Flow, Spreadsheet, or Webhook).
  4. Save.
ModeBehavior
AutoreplyMatch keyword templates on this page.
FlowRun a linked conversation flow.
SpreadsheetMatch rows from a linked Google Sheet.
WebhookForward to your webhook only — no autoreply, flow, or spreadsheet.

Only one mode is active per device at a time.

Supported channels

Autoreply templates support WhatsApp, Telegram, and WABA. Email inbound is not handled here — use email logs and your mail workflow.

Tips

  • Test with a second phone or account before linking production lines.
  • Use Template for WABA when Meta requires approved template messages outside the 24-hour window.
  • Pair Submission response type with forms on Autoreply → Submission, then review sessions on Answer (Submissions).
  • For sheet-driven FAQs without dashboard rules, use Spreadsheet mode instead.
  • Submissions — multi-question forms triggered by keywords
  • Flow — multi-step conversation trees
  • Spreadsheet — Google Sheet keyword lookups
  • Webhooks — forward inbound events to your server
Last updated: June 22, 2026
Was this page helpful?