dydu documentation
FrenchEnglish
  • A Single Software, various applications
  • First use guide
    • Getting started
    • Create your bot
    • Create your first knowledge
    • Create and publish your chatbot
    • Frequent use cases
    • Best practices
    • Glossary
  • Contents
    • Knowledge
      • Knowledge management
      • Tags management
      • Knowledge types
        • Answer to a question
        • Complementary answer
        • Predefined answer
        • Event-triggered knowledge
        • Slot filling
      • Answers elements
      • Accessibility for bot answers
      • Decision tree
      • Comments
      • Test the bot
      • Qualities alerts
    • Knowledge map
    • Matching groups
    • Global sentences
    • Language / Spaces
    • Context conditions
    • External Contents
    • Gallery
    • Web services
      • Web Services
      • Configuration examples (REST)
      • Configure OIDC on Keycloak for a Web Service
      • Frequently asked questions
    • Advanced
      • Server scripts
      • Predefined answer templates
      • Variables
      • Web services triggers
      • Top knowledge
    • Tools
    • Import/Export of knowledge
  • Learning
    • Dialogs
    • Suggestions
    • Misundestood sentences
  • Analytics
    • Exploitation
      • Important
      • Dialogs
      • Visitors
      • Themes
      • Knowledge
      • Qualification
      • Users feedbacks
      • Clicked links
      • Rewords
      • Performance
      • Other
    • Livechat
      • Dialogs
      • Knowledge
      • Operators
      • Satisfaction
      • Waiting queues
    • Knowledge base
      • Formulations
      • Users
      • Matches
    • Export
    • Configuration
  • Custom analytics
    • Reports
    • Alerts
    • Configuration
      • Reports
      • Exports
      • Predefined sources
      • Alerts
      • Preferences
      • Annex: List of indicators
  • Livechat
    • Enable livechat
    • Knowledge base setup
    • DYDU Livechat
      • Overview of interfaces
        • Operator Interface
        • Manager interface
      • Dydu livechat setup
        • General
        • Competencies
        • Waiting queues
          • General
            • Setting up the waiting queue
          • Competency
            • Setting up the waiting queue by competency
            • Setting up a knowledge base with the waiting queue by competency
        • Operator capactiy
        • Account parameters
    • Genesys Livechat connector
  • Integration
    • FAQ
      • Static FAQ
      • Dynamic FAQ
    • MetaBot
    • Customisation
    • Javascript actions
    • Custom event-triggered rules
    • Channels
      • Dydubox
      • Dydubox advanced
        • Css editor
          • Teaser
            • CSS Teaser Modification
          • Header
            • CSS Header Modification
          • Body
            • CSS Body Modification
        • Custom JS Editor
        • Label management
        • Possible integrations
      • Connector
        • Teams
        • META
          • Messenger
          • Instagram
          • WhatsApp
          • Compatibility of DYDU bot features with META
          • Meta application control
    • LLM - Generative AI (Artificial Intelligence)
    • Integration of a chatbox into a webview
  • Preferences
    • SAML 2
    • OpenID Connect (OIDC)
    • Users and rights
    • Bot
      • General
      • Dialogs
      • Survey
      • URLs
      • Search field
  • Other
    • How does your bot work?
    • Data protection
      • Cookie management policy
    • Console logs
    • Special keywords
    • Technical aspects
      • Hosting
      • Infrastructure
    • Security
      • General information
      • Server usage
      • Open source tools
      • User session expiration
  • Developers
    • API reference
      • Authentication
      • Dialog API
      • Dialogs Export
      • Search field
      • Import Export Bot
      • Import/Export Knowledge Base
      • Server Status API
      • Access to APIS
      • User Management in the BMS
    • Chatbox V5
      • Setup and integration
Powered by GitBook

Tous droits réservés @ 2023 dydu.

On this page
  • Introduction: what are anwser templates and what are they used for?
  • How to create anwser templates in the BMS?
  • Best practices

Was this helpful?

  1. Contents
  2. Advanced

Predefined answer templates

PreviousServer scriptsNextVariables

Last updated 15 days ago

Was this helpful?

Introduction: what are anwser templates and what are they used for?

You can make your content more attractive by using the appropriate answer template.

According to the message you want to deliver to your audience, you can choose between:

  • Quick reply

  • Product card

  • Carousel

Quick reply

Quick replies are pre-defined responses that chatbots offer to their users. They offer users simple, guided ways to reply to a message.

These buttons can be used to redirect the audience to a new piece of knowledge or an external URL.

Product card

A product card allows you to show off a product or a service in a visual way.

It allows to include:

  • an image or a gif

  • a title

  • an integer

  • a subtitle that can be used as a description

  • up to 3 buttons

Note: when there is more than 1 button, the first one will always have a different color (the same one as the chatbot's primary color).

Carousel

A product card template displays only one card, while a carousel template consists of as many product cards as you want.

How to create anwser templates in the BMS?

  1. Go to Content > Advanced > Templates

  2. Click on Import

  3. Choose the template you want to use in your answer

The imported model offers 9 buttons by default, but you can manually add more depending on your needs.

  • Go back to the answer edition page and click "more options"

  • In the "Template" section, choose the template you want to use

For Quick Reply template, fill out the button box you want to show by creating a personalized text that must contain a redirection link (to an external URL or a piece of knowledge).

For Product card / Carousel template, fill out the fields you want to show in the edition box of each card (title, description, buttons...).

Buttons should always contain a redirection link (to an external URL or a piece of knowledge).

Empty fields will not show in your card(s).

Best practices

Quick reply

  • Use quick replies to prompt for specific next steps.

  • Be brief — long quick replies will be truncated.

  • If you want to add an image in a button, make sure it is a square image up to 18 x 18px.

  • Each button can contain up to 15 characters.

  • Each button must contain a redirection to a URL or a piece of knowledge.

Product Card & Carousel

For this type of template, consistency of design elements is essential to deliver quality messages.

You need to pay attention to the image ratio

As one of the most eye-catching components of the carousel, images should be chosen with an appropriate aspect ratio to ensure overall aesthetics.

An aspect ratio of an image is the proportional relationship between its width and height. The first number represents the width and the second represents the height. Essentially, the ratio defines the shape of an image.

For example, a square image has a ratio of 1:1, whether its dimensions are 50 x 50px or 1500 x 1500px.

Another example, a horizontal image (landscape style) might have a ratio of 16:9. It could be 1920 x 1080px or 1280 x 720px.

In the Carousel model, since images can be scaled up or down to fit different content and chatbox widths, they may not always have the same dimensions but will always maintain the same shape. This is why you should pay attention to the shape rather than the size

In addition to the shape, you need to take into account the "safe area" when choosing an image.

A safe area of an image is the part that will always show regardless of the shape or size of the screen.

Images inside the carousel cards may have their aspect ratio modified depending on the content. That's why the most important detail must be kept in the "safe area" to avoid it being cut off.

For example, if you want to use an image with two people chatting, we recommend having them at the center of the image. Just keep in mind: the more centered the subject of your image is, the better!

General tips:

  • We recommend using up to 3 buttons per card.

  • No more than 35 characters for the text corresponding to each button.

  • Buttons must contain a redirection to a URL or a piece of knowledge.

  • The text zone only shows up to 85 characters (including spaces). Beyond that limit, the rest of the text will be reduced with "...read more".

Don't forget the "Safe Area"

Our recommendations on card elements and image ratio

​
​