Skip to content

Commit

Permalink
fix hierarchy
Browse files Browse the repository at this point in the history
  • Loading branch information
amn41 committed Sep 28, 2023
1 parent ccd53a9 commit d1183d5
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/docs/concepts/policies.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ policies:
- name: DocSearchPolicy
```

### Action Selection
## Action Selection

At every turn, each policy defined in your configuration gets a chance to
predict a next [action](./actions.mdx) with a certain confidence level.
Expand Down Expand Up @@ -348,7 +348,7 @@ are not part of a flow.
This can be helpful for handling chitchat, contextual questions,
and high-stakes topics.

#### Chitchat
### Chitchat
In an enterprise setting it may not be appropriate to use
a purely generative model to handle chitchat.
Teams want to ensure that the assistant is always on-brand and on-message.
Expand All @@ -358,7 +358,7 @@ Because the Intentless Policy leverages LLMs and considers the whole context of
when selecting an appropriate `response`, it is much more powerful
than simply predicting an intent and triggering a fixed response to it.

#### High-stakes Topics
### High-stakes Topics
In addition to chitchat, another common use case for the Intentless Policy is
providing answers on high-stakes topics.
For example, if users have questions about policies, legal terms, or guarantees,
Expand All @@ -373,7 +373,7 @@ For high-stakes topics, it is safest to send a self-contained, vetted answer
rather than relying on a generative model.
The Intentless Policy provides that capability in a CALM assistant.

#### Interjections
### Interjections
When a flow reaches a `collect` step and your assistant asks the user for information,
your user might ask a clarifying question, refuse to answer, or otherwise interject in
the continuation of the flow.
Expand Down

0 comments on commit d1183d5

Please sign in to comment.