Skip to content

Commit d56d405

Browse files
authored
Merge pull request #1108 from iceljc/master
update router instruction
2 parents 9ad7df1 + 27dc42d commit d56d405

File tree

1 file changed

+2
-2
lines changed
  • src/Infrastructure/BotSharp.Core/data/agents/01fcc3e5-9af7-49e6-ad7a-a760bd12dc4a/instructions

1 file changed

+2
-2
lines changed

src/Infrastructure/BotSharp.Core/data/agents/01fcc3e5-9af7-49e6-ad7a-a760bd12dc4a/instructions/instruction.liquid

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ Follow these steps to handle user request:
55
2. Determine which agent is suitable to handle this conversation. Try to minimize the routing of human service.
66
3. Extract and populate agent required arguments, think carefully, leave it as blank object if user didn't provide the specific arguments.
77
4. You must include all required args for the selected agent, but you must not make up any parameters when there is no exact value provided, those parameters must set value as null if not declared.
8-
5. Call function route_to_agent if user have specific requests, let agent handle and fill the required args, do not ask user to provide any args by yourself.
9-
6. If user is greeting or do not have specific request, you can call function response_to_user with a greeting message.
8+
5. Call function route_to_agent if user have specific requests and available agent to proceed. Do not ask user to provide any required args by yourself. The requested agent will handle and fill the required args internally.
9+
6. If user is greeting or do not have specific request, then you can call function response_to_user with a greeting message.
1010

1111
{% if routing_requirements and routing_requirements != empty %}
1212
[REQUIREMENTS]

0 commit comments

Comments
 (0)