> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/release-notes/june-2023.md).

# June 2023

Smartico release notes for June 2023 - covering CRM Automation and Gamification improvements done since the previous release.

### Restriction on pop-up and inbox for Scheduled Campaigns

Since pop-up and inbox are ‘online’ communication activities (they require the user to be online) we have restricted adding them to the flow builder **at the beginning** of a scheduled campaign. There are cases, where it is allowed to add a pop-up or inbox in Scheduled campaigns but first, you need to add some offline activity like email/SMS/push/WhatsApp/IVR call.

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-c803e4e5d5bf112a2cf6c40197b1116e14eaab97%2FScreenshot_55.png?alt=media" alt=""><figcaption><p>Example of the error message</p></figcaption></figure>

For example, if you want to use a pop-up in a scheduled campaign you can do the following in the flow builder:

1. Send an Email with a link for the user to go online
2. On the ‘Sent’ connection from mail put ‘Wait for event’ and type: ‘Core: user went online’
3. Show the popup when the user comes online

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-bf9ae5fcb83d171d17ce8e314342fa4f1108d6fa%2FScreenshot_54.png?alt=media" alt=""><figcaption></figcaption></figure>

You can add inbox or pop-up communication activities without using offline activity like email/SMS/ etc. when building a Journey campaign. For instance, you can build a Journey that starts on the ‘Core: user went online’ event and show the popup. You can also react to events like Deposit, Login, etc.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/release-notes/june-2023.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.