Exploring Kaizala card view scenarios

Kaizala Developer Platform team

In the Developing a custom action for Kaizala blog post, I introduced Kaizala custom actions – which has 4 views (creation view, chat card view, response view and results / summary view). In this post, I’ll explore different scenarios where each of the views can be used for a different purpose. While this post intends to give you an idea of card view customization and not an exhaustive list! Your creativity can take you way beyond.

While a Kaizala action / card has 4 views, they are not mandatory and are upto the developer to pick and choose based on the scenario at hand. Below are a few example scenarios I have picked to showcase a mix and match of the available views.

# 1 – User initiated survey requesting for details

In this kind of action  / card, there are 2 parties (at least) involved. The sender / requester who sends the survey and the responder who responds to the survey. An ideal example for this scenario would be the out-of-box survey card.

Creation View

Allows the sender to capture the title of the survey and the questions that need to be asked. On confirming, an instance of survey / action is created.

Chat Card View

As soon as the survey is created (in the creation view above), the chat card is created on the group. The chat card typically has the title of the survey, the expiry information, etc. Clicking on the chat canvas would take to the response results view and clicking on the Respond button would take to the response view.

Response View

Response view allows the user to respond to the questions in the survey.

Response Results View / Summary View

The summary view shows the responses to the survey. Either only the user’s response / all responses based on how the card is designed.

 # 2 – Survey type without summary view

This is very similar to #1 except that it would have the summary view disabled. (I don’t have an example handy – will post one soon).

# 3 – Response only form

This scenario is where the user taps on an icon and adds a response directly. It is also known as a form type action. It is like a survey with the difference that there would only be one instance of the survey and responses would be aggregated at group level. Example for this is feedback form (try this). Looking at the views involved for this kind of action:

Creation View

Opens up a form where the user can submit his input / response.

Chat Card View

As soon as the user submits the response, the chat card is created on his group view. The chat card typically has the title of the survey. Clicking on the chat canvas would take to the response results view.

Response Results View / Summary View

The summary view shows the user’s response shared in the form earlier.

#4 – Sharing a news bite / update

In this scenario the user shares a news article with the members in the group. (this is very much like the out-of-box announcement action).

Creation View

Opens up a form where the user can enter the news bite details, probably an image and a link to the news article.

Chat Card View

As soon as the user submits the card, the chat card is created on his group view. The chat card has the news summary, image, etc. Clicking on the chat canvas would take to the response results view.

Response Results View / Summary View

The summary view shows the detailed news or opens a link to the complete news article.

#5 – API initiated survey

This is very much like scenario #1, except that the survey type of card is sent programmatically using API / Flow – eliminating the need for a creation view.

Chat Card View

As soon as the survey is sent, the chat card is created on the group. The chat card typically has the title of the survey, the expiry information, etc. Clicking on the chat canvas would take to the response results view and clicking on the Respond button would take to the response view.

Response View

Response view allows the user to respond to the questions in the survey.

Response Results View / Summary View

The summary view shows the responses to the survey. Either only the user’s response / all responses based on how the card is designed.

#6 – API initiated news bite / update

This is very much like scenario #4, except that the news bite is sent using API, eliminating the need for a creation view. (or the same card in #4 could also be used here – just that creation view does not have a role while being sent using API.)

Chat Card View

When the news bite is sent using API, the chat card is created on his group view. The chat card has the news summary, image, etc. Clicking on the chat canvas would take to the response results view.

Response Results View / Summary View

The summary view shows the detailed news or opens a link to the complete news article.

 #7 – API initiated info card

Certain times, all we need is to pass a short information that fits in the chat canvas itself – not requiring an immersive view at all. In this case, we could just use the chat card view. This was demonstrated in the post, Customer ticketing solution on Kaizala – where a service ticket was sent (and updated) to the customer on Kaizala.

Chat Card View

When the information is sent using API, the card is created on the group and has the information that was sent (and designed to display).

#8 – Informational view in single screen (non-transactional)

This scenario is not much of a Kaizala scenario, but in case you don’t have any transaction / conversation involved and just want to display some information – for example, class time-table in the class group, you could design a card that is pinned / associated to the group palette that shows the time-table in the creation view. No other views are required.

Creation View

Query / fetch details required in the scenario and render it in the immersive view itself. Since no survey / form is created / submitted – an instance of action is not created. As a result of this, no chat card would be created, hence no entry points to the response view / response results view.

Hope this post was helpful in taking you through few possibilities / scenarios that you could model Kaizala action cards around. Let me know if you have any feedback / questions through the comments.

Kaizala Developer Platform team

Follow