Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recreate Journeys on new platform #137

Open
1 of 3 tasks
Tracked by #127
dennyabrain opened this issue Sep 2, 2024 · 1 comment
Open
1 of 3 tasks
Tracked by #127

Recreate Journeys on new platform #137

dennyabrain opened this issue Sep 2, 2024 · 1 comment
Assignees
Labels
level:feature An issue that describes a feature (initiative>feature>ticket)

Comments

@dennyabrain
Copy link
Contributor

dennyabrain commented Sep 2, 2024

Overview

We want to recreate the existing Journeys onto the new platform. Once we have linked the platform with our test number, Maanas and Areeba can re-create the existing journeys and also prepare to add new journeys in 3 new languages. Maanas will be responsible for technical implementation. Areeba will take calls on quality and ensuring its matches the requirements set by DAU. Maanas will also be responsible for training Areeba on the platform so she can add/edit content of the Journey.

Scope

  • Recreate Journes for the 3 existing languages
  • Put placeholder content for the 3 new planned languages
  • Integrate Webhook with test smee endpoints
@dennyabrain dennyabrain added the level:feature An issue that describes a feature (initiative>feature>ticket) label Sep 2, 2024
@maanasb01
Copy link
Collaborator

Updates on Recreating Existing Journey on Turn

  • The old Journey on Gupshup has been recreated on Turn.
  • I have implemented the journey with English and Hindi to test out the multi-language support in a single journey.
  • I have created a variable to store a JSON in a code block to keep all the messages in one place, with a Hindi and English translation for each message.
    • For example:
      "follow_whatsapp": {
      "eng": "📣Click on the link below to join our Whatsapp channel for regular updates \n\nhttp://bit.ly/3IyE8HL",
      "hin": "📣रेगुलर अपडेट्स पाने के लिए निचे दिए गए लिंक पर क्लिक कर हमारा WhatsApp चैनल फॉलो करें\n\nhttp://bit.ly/3IyE8HL"
    },
  • Throughout the journey, the text is displayed with the help of this JSON. For example, @x.follow_whatsapp["contact.language"] will display the message based on the language selected by the user.
  • All the media and URLs are being handled properly. If an image is received, it will not be processed, and if it is an Audio, Video, or URL, the link of the hosted media is sent to a smee server.
  • I have used code blocks to display the menu as with the normal "text" elements, it was not possible to do it with multi-language.
  • NOTE: I have noticed that they have a limit of characters to display the menu items. So for example, the option "🎓What are deepfakes. What we mean by synthetic media" will be displayed as "🎓What are deepfakes. Wha" on mobile phones.

Regarding the Fallback

  • I have tried implementing the Fallback functionality such that if a user sends any media item anywhere in between the conversation, the media would be processed.

What is working?

  • I created a new journey whose trigger point is any media item. So if any media is received, the journey would get triggered and process that media.
  • This is useful when a user enters the chat and without writing something like "hi"/"hello", just sends the media.

What is not working?

  • The URLs are not working the same way. Like the media items, the URL is not able to trigger the Fallback journey. I have tried using their inbuilt regex methods, but on applying them, every text would trigger the fallback journey and not just the URL (the same function is working when we are checking for the URLs in the main journey). We can ask about this in the support chat.
  • The fallback journey does not get triggered when the main journey is expecting input from the user. So for instance, if the message that displays the menu comes, or when the message to select the language comes, and the user just sends the media instead of interacting with the bot, nothing will happen. (it would work if the user sends the media again or if the user sends the media after some time when the message is displayed).
  • So for the fallback functionality, we might need to contact the Turn's support team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level:feature An issue that describes a feature (initiative>feature>ticket)
Projects
Status: Todo
Development

No branches or pull requests

3 participants