Replies / Notifications
This chapter talks about the different formats used when replying to or sending an on-demand notification to a user.
Usage
On-demand
As Reply in the Conversation
Using the @reply
instance, accessible from any action block in a context or in the callbacks from the Conversation
class.
For this case, the call to the send()
method is not necessary, since it's a reply within the conversation, therefore the framework will do it automatically.
Notification Formats
In Kogno, we try to unify as many formats as possible, in order to allow developers to write a unified code for a cross-platform conversational application.
Format | Description | Platforms |
---|---|---|
Text message | All | |
Text message with one or more buttons. | All | |
Text message with one or more buttons below. | All | |
Calls to each platform with raw params. | All | |
Multiple choice list. | ||
Carrousel images, title, description, link, among others. | Messenger | |
Url with image, title and description. | All | |
Pause for X seconds. | All | |
Sends an image. | All | |
Sends a video. | All | |
Message in HTML format. | Telegram | |
Message in Markdown format. | Telegram | |
Contact information. | WhatsApp & Telegram | |
Sends a location. | WhatsApp & Telegram | |
Request for subscription to recurring notifications in Messenger. | Messenger | |
The generic template from Messenger. | Messenger | |
WhatsApp media message template. | WhatApp |
Last updated