custom prompt
# support
a
I would like to include commands and instructions in the prompt for the assistant. And I want to know how to write them, because apparently it’s different on Vapi compared to other platforms. Commands or instructions like “check the available times” or “wait until the customer has responded.” The assistant should not speak these commands but simply follow them.
v
@AiCallYu_JuanS. Absolutely, I can help with that! On VAPI, when you're crafting prompts for the assistant, you should use sectional organization to separate commands and instructions from the spoken text. Here's a brief guide on how to do it: 1. **Building Blocks of Effective Prompts**: Structure your prompts with clear sections. Use comments or a specific syntax to denote instructions that the assistant should follow but not speak. 2. **Task Breakdown**: Break down the tasks into step-by-step instructions. For example, "check the available times" would be a step that the assistant performs without verbalizing it. 3. **Controlling Response Timing**: For instructions like "wait until the customer has responded," you would use the tools provided by VAPI to control the timing of the assistant's responses. 4. **Explicit Tool Integration**: If there are specific tools or commands that the assistant needs to execute, integrate them explicitly in the prompt structure, ensuring that they are not part of the spoken output. Remember to keep the commands and instructions concise and clear, so the assistant can understand and execute them effectively. If you need more detailed information or examples, please let me know, and I can provide further assistance!
You can continue this conversation by mentioning me in the message.
a
No, I don’t want to build blocks because this is still in a beta version. I want you to give me instructions how to manage this in the system prompt that I am writing for the Assistant on the dashboard.
v
@AiCallYu_JuanS. Certainly! When writing system prompts for the Assistant on the VAPI dashboard, you can manage commands and instructions by using a specific notation or convention that separates executable actions from spoken dialogue. Here's how you can do it: 1. **Non-verbal Commands**: For actions like "check the available times," you can include these as part of the system prompt in a way that indicates they are instructions for the Assistant. For example, you might write:
Copy code
[Action: Check available times]
2. **Waiting Instructions**: For instructions such as "wait until the customer has responded," you can use a similar notation:
Copy code
[Instruction: Wait for customer response]
3. **System Prompt Structure**: When writing the system prompt, structure it so that any spoken dialogue is clearly separated from these non-verbal commands and instructions. For example:
Copy code
[Action: Check available times]
   "I'm now checking for available times. One moment, please."
   [Instruction: Wait for customer response]
4. **Execution of Commands**: Ensure that the Assistant's programming is set up to recognize these notations and execute the corresponding actions without verbalizing the instructions themselves. By using a clear and consistent notation within your system prompts, you can effectively communicate to the Assistant which parts of the prompt are instructions to be executed and which parts are to be spoken aloud. If you need further assistance or have any more questions, feel free to ask!
a
What’s the difference if I write action or instruction?
v
@AiCallYu_JuanS. In the context of writing system prompts for VAPI, the terms "action" and "instruction" could be used to differentiate between two types of non-verbal commands: 1. **Action**: This typically refers to a command that prompts the Assistant to perform a specific task or function, such as retrieving information, executing a process, or interacting with an API. For example:
Copy code
[Action: Check available times]
This tells the Assistant to perform the action of checking for available times without verbalizing the command. 2. **Instruction**: This might be used to denote a directive for the Assistant's behavior or how it should handle a situation. For example:
Copy code
[Instruction: Wait for customer response]
This instructs the Assistant to pause and wait for the customer to respond before proceeding, rather than performing an immediate action. The distinction between "action" and "instruction" helps to clarify the intent behind each command, ensuring that the Assistant follows the prompts accurately. However, the specific implementation and interpretation of these terms can vary depending on the system's design. If VAPI has a defined convention for these terms, you should follow that. Otherwise, you can establish your own convention as long as it is consistent and clear to anyone else who might be working with the prompts.
a
Right I did this, and the agent is still speaking out loud what I’m putting into the instructions not every instructions but every other instruction like “Action: checking the availability” Although its written in the prompt like this: [Action: you check the availability]
v
@AiCallYu_JuanS. It seems there might be a misunderstanding in how the Assistant is interpreting the system prompts. If the Assistant is verbalizing the instructions, it's possible that the system is not recognizing the intended notation for non-verbal commands. To resolve this, you should ensure that: 1. The Assistant's programming or configuration is set up to recognize and differentiate between spoken dialogue and non-verbal commands. This might involve adjusting the Assistant's script or settings to properly parse and execute instructions within brackets or using a specific keyword. 2. The notation you're using for non-verbal commands is consistent and distinct from the spoken text. If the Assistant is still speaking out the instructions, you might need to use a different notation or confirm that the current notation is supported by VAPI. 3. The Assistant's training data includes examples of these non-verbal commands so that it can learn to process them correctly. If you've confirmed all of the above and the issue persists, it may be necessary to reach out to VAPI support for further assistance. They can provide more detailed guidance on the platform's specific requirements for writing system prompts that include non-verbal commands and instructions.
s
@AiCallYu_JuanS. check vapi prompting guide: https://docs.vapi.ai/prompting-guide
34 Views