Docs
DashboardRelease Notes
  • What is DeepConverse?
  • Chatbots
    • Basics
      • Building chatbot intents
      • Intent action responses
      • Chatbot Persistence mode
      • Publishing changes
    • Advanced Functionality
      • Connection Override
      • User Identity Verification
      • Announcements
      • Channel Specific Functionality
        • Zendesk Sunshine Conversations
          • How to handle image and file uploads in Zendesk Sunshine Conversations?
        • Zendesk Chat (Classic)
          • How to handoff conversations to Zendesk Chat (Classic) ?
        • Calendly
    • Branding
    • Deploy
      • Chatbot Versioning
      • iOS SDK
        • iOS (Custom Webview)
      • Android SDK
      • Adding widget to your Zendesk Help Center
      • Adding widget to your website
      • Custom Initialization and Passing Metadata
      • Open chatbot via Javascript
      • Adding widget to your Shopify Store
        • Adding the widget to Shopify via the Theme editor embed block
    • Localization
    • Customizations
      • Adding a link to your Privacy Policy in Chatbot window
  • Voice Bot
    • Getting Started with Voice Bots
    • Voice Bot Architecture
    • Supported use cases for Voice Bot
    • Setup and Configuration
  • Ticket Automation
    • Setup Zendesk email and ticket automation
  • Guides
    • Building Guides
    • Guide Theme Customization
    • Embedding Guides on your website
    • Embedding Guides in Chatbots
    • How to copy Guides across sites
  • Conversational Flow Builder
    • What is the Conversation Flow Builder?
    • Assign Parameters in Conversations
      • Predefined Parameters
    • How to use Rules in Conversations
    • Conversation Blocks
      • Question
      • Salesforce Blocks
        • Agent Availability Block
        • Live Agent Handover
      • Guide Blocks
        • Guide Step (Guide Flow)
        • Solved Block
        • Unsolved Block
        • Guide (Chatbot)
      • HTTP Request
      • Client Events
      • Policy
      • Zendesk Sunshine Conversations Handoff (In Widget)
    • Data Tables
      • How to read or search data from Data Tables?
  • Analytics
    • Chatbot Analytics
    • Viewing Chat Conversations
    • Message Viewer
    • Integrating with Google Analytics
    • Export API
      • Conversations Endpoint
      • Messages Endpoint
  • Integrations
    • Supported Integrations
      • Zendesk
      • Zendesk Sunshine Conversations
      • Salesforce
      • Gorgias
  • Account
    • Adding Users
    • Permissions and Roles
    • Multiple Sites
  • Security
    • DeepConverse Public IPs
    • Subprocessors
    • Data Request Policy
    • Technical and Organizational Security Measures
    • Reporting Security Vulnerabilities
      • Log4Shell Vulnerability
    • Generative AI - Technical Security Measures
  • Support
    • Contacting Support
    • Service Levels and Response Times
    • Platform Stability
Powered by GitBook
On this page
  • Using the Policy Node
  • Configuration Options for Policy Node
  • Policy Node in Action

Was this helpful?

  1. Conversational Flow Builder
  2. Conversation Blocks

Policy

Make use of Large Language models to provide Conversational reasoning and task execution

PreviousClient EventsNextZendesk Sunshine Conversations Handoff (In Widget)

Last updated 1 year ago

Was this helpful?

The Policy node allows you to specify a task that the chatbot can perform to assist the users. The instructions for the task can be written in plain text and the chatbot will walk the user through it making decisions based on the user messages. The Policy node makes use of Large Language models such as GPT-4 to execute the instructions.

Using the Policy Node

The Policy Node comprises of the following core pieces along with optional configurations.

  1. Name - A meaningful name for the Policy

  2. Policy - Instructions describing the approach for the chatbot. This can be as detailed as needed. The policy should clearly define the task to do and the exit criteria for completion of the policy

  3. Actions - Actions are API calls that the Policy can execute.

Example Policy for 'Checking Order Status'

Give a nice greeting to the customer and then tell them you will be helping them check the order status.

In order to check their order status, ask the customer for the order ID and email, if not provided.

Once they have provided all the needed information, let them know that you are pulling up the order.

If you are able to find the order provide them with the status, shipping address and the tracking url.

If you are not able to find the order ask them to check the information they provided and provide it again.

Configuration Options for Policy Node

In addition to the core components you have control on the type of model, failure criteria and context provided to the Policy Node.

Language Model

This specifies the LLM to use for executing the Policy. You can use DeepConverse account or bring your own LLM from (Azure, OpenAI, Anthropic).

You also have an option to specify which model you would like to use.

Context Parameters

To help the policy execution you have the option of specifying which context data the policy has access to. For example, if you already have the name and email captured you can provide it to the node. In this way it can skip asking for the same data again.

  1. Parameters to Include - This property is used to list out the parameters from the context to provide to the policy node.

  2. Parameters to Capture - This property is used to specify the parameters along with a detailed description that the chatbot should capture via the policy.

Failure Settings

To ensure that the chatbot does not get stuck in the Policy node you have the option of specifying maximum number of turns that should happen for the policy.

Policy Node in Action

Here is a demo of the Policy Node in action. You can see it walking the customer through the order status check.