The mobile Messenger's appearance, flows, news, CSAT and push title

Last updated: 13 October 2026 · 8 min read

Steps

1. 1

   Appearance and publishing

   • Changes are kept in a draft, with “There are unpublished changes” at the top. Apps see only the published version.
   • “Publish” sends the draft to the apps, and open Messengers update on screen.
   • “Versions” › “Go back to this version” puts an older version back into the draft, then “Publish” again.
   • The “Preview” on the right shows each change at once: the “Home”, “Conversation”, “Messages” and “App” screens, in “Light” and “Dark”.
2. 2

   The parts of Appearance

   • “Brand”: “Name”, “Main colour” (“Fix automatically” when the colour is hard to read), “Header” (“Gradient”, “Solid”, “Image”), “Glow”, “Logo” (“Icon + name” or “Full logo”), “Logo size” and a separate logo for dark mode.
   • “Team”: “Show team photos”, “Photos” (“Automatic”: the 3 agents most recently active in this inbox, “I choose”: up to 3 photos), “Reply time” and the text for outside working hours. Working hours are in the channel's “Business Hours” section.
   • “Bot”: the bot's name and photo. Without a photo, the logo is used.
   • “Texts”: the greeting and the card texts. An empty field shows the default text, “Reset to default” brings it back. “Variables” put the user's name into the greeting.
   • “Home”: the order of the “Cards” (drag them), “Social channels” (up to 5 on, “Add channel”) and “Greeting size”.
3. 3

   Languages, theme and floating button

   • “Languages”: the languages the Messenger speaks (Azerbaijani, English, Russian) and the “Main language”. The app can pick one of the enabled languages with setLanguage("en"). Otherwise the Messenger follows the phone's language, and the main language when the phone's is not enabled.
   • “Theme”: mode (follow the phone, light, dark), sounds, “Floating button”, its position and “Distance from the bottom”.
   • A value the app sets in code wins over the dashboard: setTheme, setLauncherVisible, setSoundsEnabled.
   • “Show "Powered by Clomni" at the bottom”: hiding this label is not in every plan. If you see “Hiding this label is not part of your plan”, talk to the Clomni team.
4. 4

   Flows

   The “Flows” section groups the channel's flows:

   • “When a conversation starts”: the flow that greets a new conversation.
   • “App event”: flows the app starts with startFlow. Each shows a name like “Event: ride_problem” and the code that sends it.
   • “By hand”: flows an agent sends into a conversation.
   • “When the conversation status changes”: for example, a flow that asks for a rating when the conversation is resolved. See “A flow that starts when the conversation status changes, and CSAT”.
   • “Reusable”: flows with no trigger of their own, started by another flow's “Start another flow” step.

   The “How does it look in the app?” link at the top of the section shows, in a separate window, how choices and a form look in the SDK. “Open the builder” opens the flow builder. For an app event, choose “App event” as the trigger, enter the event name and publish the flow. In the app:

   // Android
   Clomni.startFlow("ride_problem", mapOf("ride_id" to "R-1923"), openMessenger = true, source = "ride_screen")

   // iOS
   Clomni.startFlow("ride_problem", data: ["ride_id": "R-1923"], openMessenger: true, source: "ride_screen")

   • The flow's texts use the data as {{data.ride_id}}. The data must be JSON: strings, numbers, booleans, lists, maps.
   • If no published flow is tied to the event, nothing happens.
   • For an event the user did not tap themselves (for example a failed payment), keep openMessenger = false: the user learns about it from a push or the unread count.

   The event name is not the flow's name. Pass startFlow the name on the flow's “Event: …” line. A flow with the “When a conversation starts” trigger does not start with startFlow.

   Every choice in a flow must lead to a step. A choice that leads nowhere can leave the customer stuck. From SDK 1.0.2 the flow ends at such a choice and the customer gets the text field.

5. 5

   News

   News shows on the Messenger's home: the first three published items. The “News” section has the list: “Title”, “Status” (“Draft” or “Published”, with “On Home” for the items on Home) and “Date”. Drag a row to change the order. The “How does it look in the app?” link under the title shows the news cards on the app's Home.

   “New item”, or a row of the list, opens the editor on a page of its own. “← News” above the title goes back to the list. In the editor:

   • “Cover image”: 16:9, up to 5 MB, at least 720 px wide.
   • The language buttons (AZ, EN, RU) pick the language you edit. The Azerbaijani text is required; where en or ru is empty, the az text is shown.
   • “Title” and “Short text” are on the Home card, “Full text” shows when the item is opened. The full text takes **bold**, *italic*, links and lists.
   • “Button” (optional): its text and a web address or a deep link of the app.
   • “Save” keeps your changes; a new item stays a draft. “Publish” saves the item and sends it to the apps, “Unpublish” hides it, “Delete” deletes it.
   • The “In the app” preview on the right shows the card on Home and the opened item, and follows each change.

   With unsaved changes, the dashboard asks before you leave the page.

   The button can open a web address or the app's deep link. With onLink set, the link comes to the app first:

   // Android: return true when the app opened the link itself
   Clomni.onLink { url -> url.startsWith("example://") }

6. 6

   CSAT

   In the channel's “CSAT” section, turn the survey on the same way as for the website chat: “Enable CSAT”, “Display type”, “Message”, “Update”. When a conversation is resolved, the Messenger shows the survey as a card inside the conversation: 5 stars when the display type is stars, otherwise 5 emoji. The user can add a comment. The results are on Reports › CSAT. If the channel has an active flow that asks for a rating when a conversation is resolved, the CSAT survey is not sent: the flow asks for the rating.

7. 7

   Push notification title

   Push › “Notification title” › “Style”:

   • “Agent · Brand” (the default), for example “Leyla · Example”.
   • “Brand name only”.
   • “Agent name only”. When a bot replies, the brand name is shown.
   • “Your own text”: per language, the default language is required.

   Click “Save”. The notification's text is the message itself.

8. 8

   Full guide

   • PDF: Clomni Mobile SDK guide, in English, Azerbaijani and Russian.
   • Online: Clomni dashboard.
   • In the dashboard: “Guide” in the channel's settings column.