Release 5.18.4
This release includes all changes of 5.18.2 and adds changes to the AI Assistant, a new persistent keyboard for Telegram bots, and a more convenient period selection in the "Quality assessment" section.
AI Assistant
New
- The "Stop" button really stops the assistant. Previously, pressing "Stop" only stopped showing the reply in the chat. Now the stop request reaches the assistant and the current run is ended. The chat shows "Execution stopped." If no confirmation came back, the chat says the request was sent but the assistant may still be finishing in the background.
- Reloading the page during a reply does not stop it. To stop, press "Stop" after the reload.
- A second Enter interrupts the current request and starts the new one. If the assistant is still replying and you send the next message, press Enter once more: the current processing is interrupted, the chat shows "Previous processing interrupted — running the new request.", and your newest request starts right away.
Fixed
- Instead of an empty bubble, the assistant explains what happened. Previously, if the assistant did not finish within the allowed time or ended without a final text, you could see an empty message or "(no response)", and the text it had already written was lost.
- Before: an empty bubble, "(no response)" or a technical error code.
- Now: the part of the reply the assistant managed to write is kept, and below it a clear explanation appears in the interface language: time ran out, or the assistant performed actions but did not summarize the result, or there was no reply.
- The AI Assistant conversation context is not lost on a restart. Previously, after the assistant service was restarted or when it ran as several copies, the conversation could start over as if there were no previous context. Now the context state is stored separately, and a cleared context does not come back after a failure. The change applies on instances where the ConnectiveOne team has connected a separate state store for the assistant; no action is needed on your side.
Channels
New
- Persistent Telegram keyboard. Under the input field of a Telegram bot you can show buttons at every scenario step, including steps with an inline menu: for example, "Main menu", "☎ the client's phone number" and "Start". Inline buttons under messages stay as they were.
- The buttons are built in the process settings, in the "Persistent Telegram keyboard" card: up to 4 rows of 3 buttons, buttons can include variables (for example, the client's phone), and each button gets an action: go to a scenario step, start over, or only send the text to the chat. There is a "How the client will see it" preview. No JSON is needed.
- Anyone who can change the process settings can edit the card.
- Works only in private Telegram chats. A button whose variable is still empty is not shown.
- After a broadcast, the keyboard comes back on the next bot step.
Quality assessment
Improved
- Assessments for today and for custom dates. In Quality control → Assessments, the "Period" block has a new "Today" option, and under the list there is an "Or pick dates" field with a calendar: pick one date (assessments for that day) or a range (both days included). When the calendar has a date, the period list shows "Custom dates". Choosing an item from the list clears the calendar.
- Filters are applied with the "Apply filters" button; "Reset" returns the period to "7 days".
- The CSV export uses the same dates as the list.
- A day is counted in your browser's time.
Please note
- The persistent Telegram keyboard is turned on per instance. Until it is turned on, the card is not in the process settings and the bot behaves as before. To turn it on, contact your ConnectiveOne manager.
- The "Main menu" button needs a scenario node. The button leads to a node with an alias (the "Connect To" node). If the scenario has no such node, the button will not work — see the guide below for details.