odoo-forge-bundle 0.1.0

package/payload/skills/odoo18-docs/references/docs/applications/websites/forum.md

@@ -0,0 +1,394 @@
+---
+title: "Forum"
+source_url: "https://docs.odoo.sbggai.top/applications/websites/forum.html"
+---
+
+=====
+# Forum
+
+**Odoo Forum** is a question-and-answer forum designed with providing customer support in mind.
+Adding a forum to a website enables you to build a community, encourage engagement, and share
+knowledge.
+
+.. _forum/create:
+
+# Create a forum
+
+To create or edit a forum, go to :menuselection:`Website --> Configuration --> Forum: Forums`. Click
+:guilabel:`New` or select an existing forum and configure the following elements.
+
+:guilabel:`Forum Name`: add the name of the forum.
+
+:guilabel:`Mode`: select :guilabel:`Questions` to enable marking an answer as best, meaning
+questions then appear as *solved*, or :guilabel:`Discussions` if the feature is not needed.
+
+> **note**:
+>    Regardless of the selected mode, only **one answer** per user is allowed on a single post.
+   Commenting multiple times is allowed, however.
+
+:guilabel:`Default Sort`: choose how questions are sorted by default.
+
+  - :guilabel:`Newest`: by latest question posting date
+  - :guilabel:`Last Updated`: by latest posting activity date (answers and comments included)
+  - :guilabel:`Most Voted`: by highest vote tally
+  - :guilabel:`Relevance`: by post relevancy (determined by a formula)
+  - :guilabel:`Answered`: by likelihood to be answered (determined by a formula)
+
+> **note**:
+>    Users have several sorting options (total replies, total views, last activity) on the forum
+   front end.
+
+:guilabel:`Privacy`: select :guilabel:`Public` to let anyone view the forum, :guilabel:`Signed In`
+to make it visible only for signed-in users, or :guilabel:`Some users` to make it visible only for a
+specific user access group by selecting one :guilabel:`Authorized Group`.
+
+Next, configure the :ref:`karma gains <forum/karma-gains>` and the :ref:`karma-related rights
+<forum/karma-related-rights>`.
+
+.. _forum/karma:
+
+## Karma points
+
+Karma points can be given to users based on different forum interactions. They can be used to
+determine which forum functionalities users can access, from being able to vote on posts to
+having moderator rights. They are also used to set user :ref:`ranks <forum/ranks>`.
+
+> **important**:
+>    - A user's karma points are shared across all forums, courses, etc., of a single Odoo website.
+   - eLearning users can earn karma points through different :ref:`course interactions
+     <elearning/karma>` and by :ref:`completing quizzes <elearning/quiz>`.
+
+.. _forum/karma-gains:
+
+### Karma gains
+
+Several forum interactions can give or remove karma points.
+
+.. list-table::
+   :header-rows: 1
+   :stub-columns: 1
+
+   * - Interaction
+     - Description
+     - Default karma gain
+   * - :guilabel:`Asking a question`
+     - You post a question.
+     - 2
+   * - :guilabel:`Question upvoted`
+     - Another user votes for a question you posted.
+     - 5
+   * - :guilabel:`Question downvoted`
+     - Another user votes against a question you posted.
+     - -2
+   * - :guilabel:`Answer upvoted`
+     - Another user votes for an answer you posted.
+     - 10
+   * - :guilabel:`Answer downvoted`
+     - Another user votes against an answer you posted.
+     - -2
+   * - :guilabel:`Accepting an answer`
+     - You mark an answer posted by another user as best.
+     - 2
+   * - :guilabel:`Answer accepted`
+     - Another user marks an answer you posted as best.
+     - 15
+   * - :guilabel:`Answer flagged`
+     - A question or an answer you posted is :ref:`marked as offensive <forum/moderation>`.
+     - -100
+
+> **note**:
+>    New users receive **three points** upon validating their email address.
+
+To modify the default values, go to :menuselection:`Website --> Configuration --> Forum: Forums`,
+select the forum, and go to the :guilabel:`Karma Gains` tab. Select a value to edit it.
+
+If the value is positive (e.g., `5`), the number of points will be added to the user's tally each
+time the interaction happens on the selected forum. Conversely, if the value is negative (e.g.,
+`-5`), the number of points will be deducted. Use `0` if an interaction should not impact a user's
+tally.
+
+.. _forum/karma-related-rights:
+
+### Karma-related rights
+
+To configure how many karma points are required to access the different forum functionalities, go
+to :menuselection:`Website --> Configuration --> Forum: Forums`, select the forum, and go to the
+:guilabel:`Karma Related Rights` tab. Select a value to edit it.
+
+> **warning**:
+>    Some functionalities, such as :guilabel:`Edit all posts`, :guilabel:`Close all posts`,
+   :guilabel:`Delete all posts`, :guilabel:`Moderate posts`, and :guilabel:`Unlink all comments`,
+   are rather sensitive. Make sure to understand the consequences of giving *any* user reaching the
+   set karma requirements access to such functionalities.
+
+.. list-table::
+   :header-rows: 1
+   :stub-columns: 1
+
+   * - Functionality
+     - Description
+     - Default karma requirement
+   * - :guilabel:`Ask questions`
+     - Post questions.
+     - 3
+   * - :guilabel:`Answer questions`
+     - Post answers to questions.
+     - 3
+   * - :guilabel:`Upvote`
+     - Vote for questions or answers.
+     - 5
+   * - :guilabel:`Downvote`
+     - Vote against questions or answers.
+     - 50
+   * - :guilabel:`Edit own posts`
+     - Edit questions or answers you posted.
+     - 1
+   * - :guilabel:`Edit all posts`
+     - Edit any question or answer.
+     - 300
+   * - :guilabel:`Close own posts`
+     - Close questions or answers you posted.
+     - 100
+   * - :guilabel:`Close all posts`
+     - Close any question or answer.
+     - 500
+   * - :guilabel:`Delete own posts`
+     - Delete questions or answers you posted.
+     - 500
+   * - :guilabel:`Delete all posts`
+     - Delete any question or answer.
+     - 1,000
+   * - :guilabel:`Nofollow links`
+     - If you are under the karma threshold, a *nofollow* attribute tells search engines to ignore
+       links you post.
+     - 500
+   * - :guilabel:`Accept an answer on own questions`
+     - Mark an answer as best on questions you posted.
+     - 20
+   * - :guilabel:`Accept an answer to all questions`
+     - Mark an answer as best on any question.
+     - 500
+   * - :guilabel:`Editor Features: image and links`
+     - Add links and images to your posts.
+     - 30
+   * - :guilabel:`Comment own posts`
+     - Post comments under questions or answers you created.
+     - 1
+   * - :guilabel:`Comment all posts`
+     - Post comments under any question or answer.
+     - 1
+   * - :guilabel:`Convert own answers to comments and vice versa`
+     - Convert comments you posted as answers.
+     - 50
+   * - :guilabel:`Convert all answers to comments and vice versa`
+     - Convert any comment as answer.
+     - 500
+   * - :guilabel:`Unlink own comments`
+     - Delete comments you posted.
+     - 50
+   * - :guilabel:`Unlink all comments`
+     - Delete any comment.
+     - 500
+   * - :guilabel:`Ask questions without validation`
+     - Questions you post do not require to be :ref:`validated <forum/moderation>` first.
+     - 100
+   * - :guilabel:`Flag a post as offensive`
+     - Flag a question or answer as offensive.
+     - 500
+   * - :guilabel:`Moderate posts`
+     - Access all :ref:`moderation tools <forum/moderation>`.
+     - 1,000
+   * - :guilabel:`Change question tags`
+     - Change posted questions' :ref:`tags <forum/tags>` (if you have the right to edit them).
+     - 75
+   * - :guilabel:`Create new tags`
+     - Create new :ref:`tags <forum/tags>` when posting questions.
+     - 30
+   * - :guilabel:`Display detailed user biography`
+     - When a user hovers their mouse on your avatar or username, a popover box showcases your
+       karma points, biography, and number of :ref:`badges <forum/badges>` per level.
+     - 750
+
+> **tip**:
+>    Track all karma-related activity and add or remove karma manually by :ref:`enabling developer
+   mode <developer-mode>` and going to :menuselection:`Settings --> Gamification Tools --> Karma
+   Tracking`.
+
+.. _forum/gamification:
+
+## Gamification
+
+Ranks and badges can be used to encourage participation. Ranks are based on the total :ref:`karma
+points <forum/karma>`, while badges can be granted manually or automatically by completing
+challenges.
+
+.. _forum/ranks:
+
+### Ranks
+
+To create new ranks or modify the default ones, go to :menuselection:`Website --> Configuration -->
+Forum: Ranks` and click :guilabel:`New` or select an existing rank.
+
+Add the :guilabel:`Rank Name`, the :guilabel:`Required Karma` points to reach it, its
+:guilabel:`Description`, a :guilabel:`Motivational` message to encourage users to reach it, and an
+image.
+
+.. image:: forum/ranks.png
+   :alt: Default forum ranks
+
+.. _forum/badges:
+
+### Badges
+
+To create new badges or modify the default ones, go to :menuselection:`Website --> Configuration -->
+Forum: Badges` and click :guilabel:`New` or select an existing badge.
+
+Enter the badge name and description, add an image, and configure it.
+
+Assign manually
+***************
+
+If the badge should be granted manually, select which users can grant them by selecting one of the
+following :guilabel:`Allowance to Grant` options:
+
+- :guilabel:`Everyone`: all non-portal users (since badges are granted from the backend).
+- :guilabel:`A selected list of users`: users selected under :guilabel:`Authorized Users`.
+- :guilabel:`People having some badges`: users who have been granted the badges selected under
+  :guilabel:`Required Badges`.
+
+It is possible to restrict how many times per month each user can grant the badge by enabling
+:guilabel:`Monthly Limited Sending` and entering a :guilabel:`Limitation Number`.
+
+Assign automatically
+********************
+
+If the badge should be granted **automatically** when certain conditions are met, select
+:guilabel:`No one, assigned through challenges` under :guilabel:`Allowance to Grant`.
+
+Next, determine how the badge should be granted by clicking :guilabel:`Add` under the
+:guilabel:`Rewards for challenges` section. Select a challenge to add it or create one by clicking
+:guilabel:`New`.
+
+> **tip**:
+>    It is possible to give the badge a :guilabel:`Forum Badge Level` (:guilabel:`Bronze`,
+   :guilabel:`Silver`, :guilabel:`Gold`) to give it more or less importance.
+
+.. image:: forum/badges.png
+   :alt: Default forum badges
+
+.. _forum/tags:
+
+## Tags
+
+Users can use tags to filter forum posts.
+
+To manage tags, go to :menuselection:`Website --> Configuration --> Forum: Tags`. Click
+:guilabel:`New` to create a tag and select the related :guilabel:`Forum`.
+
+> **tip**:
+>    - Use the :guilabel:`Tags` section on the forum's sidebar to filter all questions assigned to the
+     selected tag. Click :guilabel:`View all` to display all tags.
+   - New tags can be created when posting a new message, provided the user has enough :ref:`karma
+     points <forum/karma-related-rights>`.
+
+.. _forum/use:
+
+# Use a forum
+
+> **note**:
+>    Access to many functionalities depends on a user's :ref:`karma points
+   <forum/karma-related-rights>`.
+
+.. _forum/post:
+
+## Post questions
+
+To create a new post, access the forum's front end, click :guilabel:`New Post`, and fill in the
+following:
+
+- :guilabel:`Title`: add the question or the topic of the post.
+- :guilabel:`Description`: add a description for the question.
+- :guilabel:`Tags`: add up to five :ref:`tags <forum/tags>`.
+
+Click :guilabel:`Post Your Question`.
+
+.. _forum/interact:
+
+## Interact with posts
+
+Different actions are possible on a post.
+
+- Mark a question as **favorite** by clicking the star button (:guilabel:`☆`).
+- Follow a post and get **notifications** (by email or within Odoo) when it is answered by clicking
+  the bell button (:guilabel:`🔔`).
+- **Vote** *for* (up arrow :guilabel:`▲`) or *against* (down arrow :guilabel:`▼`) a question or
+  answer.
+- Mark an answer as **best** by clicking the check mark button (:guilabel:`✔`). This option is only
+  available if the :guilabel:`Forum Mode` is set to :guilabel:`Questions`.
+- :guilabel:`Answer` a question.
+- **Comment** on a question or answer by clicking the speech bubble button (:guilabel:`💬`).
+- **Share** a question on Facebook, Twitter, or LinkedIn by clicking the *share nodes* button.
+
+Click the ellipsis button (:guilabel:`...`) to:
+
+  - :guilabel:`Edit` a question or answer.
+  - :guilabel:`Close` a question.
+  - :guilabel:`Delete` a question, answer, or comment. It is possible to :guilabel:`Undelete`
+    questions afterward.
+  - :guilabel:`Flag` a question or answer as offensive.
+  - :guilabel:`Convert` a comment into an answer.
+  - :guilabel:`View` the related :ref:`Helpdesk ticket <helpdesk/forum>`, if any.
+
+.. image:: forum/post-actions.png
+   :alt: Posts actions
+
+> **note**:
+>    By default, 150 karma points are required to view another user's profile. This value can be
+   configured when creating a new website.
+
+.. _forum/moderation:
+
+# Moderate a forum
+
+On the forum's front end, the sidebar's :guilabel:`Moderation tools` section gathers the essential
+moderator functionalities.
+
+.. image:: forum/moderation-tools.png
+   :alt: Forum sidebar moderation tools
+
+:guilabel:`To Validate`: access all questions and answers waiting for validation before being
+displayed to non-moderator users.
+
+.. image:: forum/to-validate.png
+   :alt: Question to validate
+
+> **note**:
+>    A question is pending if a user does not have the required karma. The user is not able to post
+   questions or answers while awaiting validation. Only one pending question per user is allowed per
+   forum.
+
+:guilabel:`Flagged`: access all questions and answers that have been flagged as offensive. Click
+:guilabel:`Accept` to remove the offensive flag or :guilabel:`Offensive` to confirm it, then select
+a reason and click :guilabel:`Mark as offensive`. The post is then hidden from users without
+moderation rights, and 100 karma points are deducted from the offending user's tally.
+
+.. image:: forum/offensive-reason.png
+   :alt: Offensive reason selection
+
+:guilabel:`Closed`: access all questions that have been closed. It is possible to :guilabel:`Delete`
+or :guilabel:`Reopen` them. To close a question, open it, click the ellipsis button
+(:guilabel:`...`), then :guilabel:`Close`, select a :guilabel:`Close Reason`, and click
+:guilabel:`Close post`. The post is then hidden from users without moderation rights.
+
+> **note**:
+>    When selecting :guilabel:`Spam or advertising` or :guilabel:`Contains offensive or malicious
+   remarks` as the reason, 100 karma points are deducted from the poster's tally.
+
+> **tip**:
+>    - Create and edit close reasons by going to :menuselection:`Website --> Configuration --> Forum:
+     Close Reasons`. Select :guilabel:`Basic` as :guilabel:`Reason Type` if the reason should be
+     used when closing a question, and :guilabel:`Offensive` if it should be used for flagged posts.
+   - Manage all posts by going to :menuselection:`Website  --> Configuration --> Forum: Forums`,
+     selecting the forum, and clicking the :guilabel:`Posts` smart button. By clicking the
+     :guilabel:`Actions` button, it is possible to :guilabel:`Export`, :guilabel:`Archive`,
+     :guilabel:`Unarchive`, or :guilabel:`Delete` one or multiple posts.

package/payload/skills/odoo18-docs/references/docs/applications/websites/livechat/chatbots.md

@@ -0,0 +1,260 @@
+---
+title: "Chatbots"
+source_url: "https://docs.odoo.sbggai.top/applications/websites/livechat/chatbots.html"
+---
+
+========
+# Chatbots
+
+A *Chatbot* is a program designed to mimic a conversation with a live human. Chatbots are assigned a
+script of pre-written steps to follow. The scripts are designed to anticipate a visitor's potential
+response, and lead them through a series of questions and answers the same way a live team member
+would.
+
+Chatbots can be customized to fill various roles, from customer support, to creating leads, to
+collecting contact information. The goal of each chatbot can vary based on several criteria,
+including the webpage where it is located, and the information it captures.
+
+.. image:: chatbots/chatbot-visitor-view.png
+   :align: center
+   :alt: View of the chat window with a helpdesk ticket created in Odoo Live Chat.
+
+# Build a chatbot
+
+Before creating a new chatbot, the *Live Chat* application must first be installed on the database.
+This can be done directly from the :menuselection:`Apps` application, by searching for `Live Chat`
+in the :guilabel:`Search...` bar, and clicking :guilabel:`Install`.
+
+Once the *Live Chat* application has been installed on the database, go to :menuselection:`Live Chat
+app --> Configuration --> Chatbots`.
+
+> **note**:
+>    When the *Live Chat* app is installed, a sample chatbot is created, named *Welcome Bot*. This
+   chatbot has a preconfigured script that walks through a few basic steps, including asking for a
+   visitor's email address, and forwarding the conversation to an operator.
+
+   *Welcome Bot* can be used as a starting point. The existing steps can be edited or removed, and
+   new steps can be added to customize the script, as needed.
+
+   *Welcome Bot* can be deleted or archived, if necessary.
+
+   .. image:: chatbots/chatbot-welcome-bot.png
+      :align: center
+      :alt: View of the Welcome Bot script in Odoo Live Chat.
+
+To create a new chatbot, navigate to the :guilabel:`Chatbot` page (:menuselection:`Live Chat app -->
+Configuration --> Chatbots`) and click :guilabel:`New`. This opens a blank chatbot details page.
+
+On the blank chatbot details page, enter a name in the :guilabel:`Chatbot Name` field and click on
+the :guilabel:`Edit Image` icon in the upper right corner of the form to add a photo.
+
+## Chatbot scripts
+
+After the new chatbot has been created and named, the next step is to create a script. Chatbot
+conversations follow an accompanying script. These scripts are comprised of lines of dialog, each
+designed to deliver or capture information.
+
+To create a chatbot script, click :guilabel:`Add a Line` in the :guilabel:`Script` tab of the
+chatbot detail page, and a :guilabel:`Create Script Steps` modal appears.
+
+
+This form must be filled out for **each** line of text (dialog) that the chatbot could deliver
+during the conversation.
+
+First, enter the content of the message in the :guilabel:`Message` field. Then, select an option
+from the :guilabel:`Step Type` and :guilabel:`Only If` drop-down menus.
+
+### Step types
+
+The :guilabel:`Step Type` selected depends on the intended purpose of the message. The available
+options in the :guilabel:`Step Type` drop-down menu are detailed below:
+
+Text
+****
+
+This step is used for messages where no answer is expected or necessary. Text steps can be used for
+greetings, to offer resources, such as documentation, or provide links to specific web pages.
+
+> **important**:
+>    *Text* step types are only intended to deliver information, and do **not** allow for any visitor
+   input. As such, they **must** be followed by additional steps to continue the conversation.
+
+Question
+********
+
+This step asks a question and provides a set of answers. The visitor clicks on one answer, which
+either leads to a new step in the conversation, or can lead to an optional link to a new webpage.
+
+Enter the question in the :guilabel:`Message` field. Then, under the :guilabel:`Answer` heading,
+click :guilabel:`Add a Line` to create a blank answer line.
+
+Proceed to enter the answer as it should appear to the visitor. To turn the answer into a link that
+redirects the visitor when selected, add the URL to the answer line under the :guilabel:`Optional
+Link` heading.
+
+Repeat these steps for every answer to be included for the question.
+
+Click :guilabel:`Save & Close` or :guilabel:`Save & New`.
+
+> **tip**:
+>    It is helpful to add a catchall answer to question steps (e.g: `Something else`). This helps
+   visitors continue the conversation, even if their needs do not exactly fit with any of the other
+   answers.
+
+Email
+*****
+
+This step prompts visitors to provide their email address, which is stored and can be used by team
+members later to follow up with additional information.
+
+The **only** accepted inputs for this step type are email addresses that are in a valid format. If a
+visitor attempts to enter anything other than a valid email address, the chatbot responds with a
+message stating it does not recognize the information submitted.
+
+.. image:: chatbots/chatbot-invalid-email.png
+   :align: center
+   :alt: View of a chatbot responding to an invalid email.
+
+Phone
+*****
+
+Similar to email, this step type prompts the visitor to enter their phone number, which can be used
+to follow up with additional information, schedule demos, and more.
+
+> **warning**:
+>    Due to the vast number of formats used for phone numbers worldwide, responses to this step type
+   are **not** validated for formatting, and can include both numbers and special characters.
+
+Forward to Operator
+*******************
+
+This step forwards the conversation to an active live chat operator, so they can continue
+assisting the visitor. As the conversation transcript is passed on to the operator, they can pick up
+where the chatbot left off. This not only saves time for all parties involved, it can also help
+qualify conversations before they reach live operators.
+
+> **note**:
+>    If no active operator is available on the channel, the chatbot continues the conversation with
+   the visitor. Therefore, additional steps should be added after this one to ensure there is no
+   abrupt end to the conversation. The additional steps can both inform visitors about the lack of
+   available operators (e.g. `Uh-oh, it looks like none of our operators are available`) and
+   continue the conversation (e.g. `Would you like to leave your email address?`).
+
+   .. image:: chatbots/chatbot-no-operator.png
+      :align: center
+      :alt: View of a chatbot follow up messages when no live chat operator is available.
+
+Free Input/Multi-Line
+*********************
+
+The *free input* step allows visitors to respond to questions without providing pre-written
+responses. Information provided in these responses is stored in the chat transcripts.
+
+Choose between :guilabel:`Free Input` and :guilabel:`Free Input (Multi-Line)` depending on the type
+and amount of information the visitor is asked to provide.
+
+Create Lead
+***********
+
+This step creates a lead in the *CRM* application. Select an option from the :guilabel:`Sales Team`
+drop-down field that appears to assign the created lead to a specific team.
+
+> **note**:
+>    This step is **only** available if the *CRM* application is installed on the database.
+
+Create Ticket
+*************
+
+This step creates a :doc:`ticket <../../services/helpdesk/overview/receiving_tickets>` in
+the *Helpdesk* application. Select an option from the :guilabel:`Helpdesk Team` drop-down field that
+appears to assign the created ticket to a specific team.
+
+> **note**:
+>    This step is **only** available if the *Helpdesk* application is installed on the database.
+
+### Only if
+
+Chatbot scripts operate on an if/then basis, which means the next question presented to the visitor
+is determined by the answer provided to the previous question.
+
+To continue the progression of the conversation, the :guilabel:`Create Script Steps` form for a new
+step contains a field labeled :guilabel:`Only If`. This field is where the progression of questions
+is defined.
+
+If a step is intended to follow all of the previous messages, this field can be left empty. However,
+if a message should **only** be sent conditionally, based on a previous response, or several
+previous responses, those responses **must** be added to this field.
+
+> **important**:
+>    If any selections are made in the :guilabel:`Only If` field, they must **all** be selected during
+   the conversation *before* this step will be included. Only include selections in this field if
+   they are necessary for this step to be displayed.
+
+.. example::
+   In the *Welcome Bot* script, a visitor can ask about pricing information. If the visitor selects
+   this response, a step is included to forward the conversation to an operator. The chatbot first
+   sends a message informing the visitor that it is checking to see if an operator is available to
+   chat.
+
+   However, this message should **only** be delivered if the visitor requests pricing information.
+   In that situation, the conversation would proceed as below:
+
+   - Welcome Bot: "*What are you looking for?*"
+   - Visitor: "**I have a pricing question.**"
+   - Welcome Bot: "*Hmmm, let me check if I can find someone that could help you with that...*"
+
+   In the details form for the :guilabel:`Text` step, the *I have a pricing question* response has
+   been selected in the :guilabel:`Only If` field. As such, this step is **only** shown in
+   conversations where that response has been selected.
+
+   .. image:: chatbots/chatbot-only-if.png
+      :align: center
+      :alt: View of the new message form emphasizing the Only If field.
+
+## Script testing
+
+To ensure all visitors have a satisfactory experience with the chatbot, each message needs
+to lead to a natural conclusion. Chatbot scripts should be tested to confirm there are no dead-ends,
+and to understand what the visitor sees when they interact with the chatbot.
+
+> **important**:
+>    If the visitor provides an answer, or input, that is **not** assigned a corresponding follow-up
+   response, the conversation stops (*dead-ends*). Since the visitor cannot re-engage the chatbot,
+   they must restart the conversation by refreshing the chat window, or their browser.
+
+To test the performance of a chatbot, first click on the :guilabel:`Test` button at the top-left of
+the chatbot script page. Then, upon being redirected to the testing screen, answer the chatbot
+prompts the same way a potential site visitor would.
+
+When the script has reached an end-point, the message *Conversation ended...Restart* appears at the
+bottom of the chat window. To begin the conversation at the beginning of the script, click on
+:guilabel:`Restart`. To return to the script page, click :guilabel:`Back to edit mode` at the top of
+the page.
+
+# Add chatbot to a channel
+
+After a chatbot has been created and tested, it needs to be added to a live chat channel.
+
+First, open the :menuselection:`Live Chat` application, find the Kanban card for the appropriate
+live chat channel, hover over it, and click the :guilabel:`⋮ (three dots)` icon to open the
+drop-down menu. Click :guilabel:`Configure Channel` to open the channel detail form.
+
+> **note**:
+>    To create a new live chat channel, open the :menuselection:`Live Chat app` and click
+   :guilabel:`New`. See :doc:`Live Chat <../livechat>` for more information.
+
+Click on the :guilabel:`Channel Rules` tab. Then, open an existing rule, or create a new one by
+clicking :guilabel:`Add a line`.
+
+On the :guilabel:`Create Rules` modal, choose the appropriate chatbot in the :guilabel:`Chatbot`
+field.
+
+If the chatbot should **only** be active if there are no live chat operators available, check the
+box labeled :guilabel:`Enabled only if no operator`.
+
+.. image:: chatbots/chatbot-add-to-channel.png
+   :align: center
+   :alt: View of the channel rules emphasizing the chatbot field.
+
+.. seealso::
+   :doc:`Live chat channel rules </applications/websites/livechat>`