|
8 | 8 |
|
9 | 9 | Sign-up for an account (or log-in to your existing account) — you will then find yourself inside the web dashboard. It will look something like this: |
10 | 10 |
|
11 | | - <Frame caption="Your dashboard may look a bit different if you already have an account with assistants in it. The main idea is that we’re in the dashboard now."> |
| 11 | + <Frame caption="Your dashboard may look a bit different if you already have an account with assistants in it. The main idea is that we're in the dashboard now."> |
12 | 12 | <img src="../static/images/quickstart/dashboard/vapi-dashboard-post-signup.png" /> |
13 | 13 | </Frame> |
14 | 14 |
|
|
30 | 30 | <img src="../static/images/quickstart/dashboard/choose-blank-template.png" /> |
31 | 31 | </Frame> |
32 | 32 |
|
33 | | - You will then be able to name your assistant — you can name it whatever you'd like (`Vapi’s Pizza Front Desk`, for example): |
| 33 | + You will then be able to name your assistant — you can name it whatever you'd like (`Vapi's Pizza Front Desk`, for example): |
34 | 34 |
|
35 | 35 | <Info> |
36 | 36 | This name is only for internal labeling use. It is not an identifier, nor will the assistant be |
|
43 | 43 |
|
44 | 44 | Once you have named your assistant, you can hit "Create" to create it. You will then see something like this: |
45 | 45 |
|
46 | | - <Frame caption="The assistant overview. You can edit your assistant’s transcriber, model, & voice — and edit other advanced configuration."> |
| 46 | + <Frame caption="The assistant overview. You can edit your assistant's transcriber, model, & voice — and edit other advanced configuration."> |
47 | 47 | <img src="../static/images/quickstart/dashboard/assistant-created.png" /> |
48 | 48 | </Frame> |
49 | 49 |
|
50 | | - This is the assistant overview view — it gives you the ability to edit different attributes about your assistant, as well as see **cost** & **latency** projection information for each portion of it’s voice pipeline (this is very important data to have handy when building out your assistants). |
| 50 | + This is the assistant overview view — it gives you the ability to edit different attributes about your assistant, as well as see **cost** & **latency** projection information for each portion of it's voice pipeline (this is very important data to have handy when building out your assistants). |
51 | 51 |
|
52 | 52 | </Accordion> |
53 | 53 | <Accordion title="Model Setup" icon="microchip" iconType="solid"> |
54 | | - Now we’re going to set the "brains" of the assistant, the large language model. We're going to be using `GPT-4` (from [OpenAI](https://openai.com/)) for this demo (though you're free to use `GPT-3.5`, or any one of your favorite LLMs). |
| 54 | + Now we're going to set the "brains" of the assistant, the large language model. We're going to be using `GPT-4` (from [OpenAI](https://openai.com/)) for this demo (though you're free to use `GPT-3.5`, or any one of your favorite LLMs). |
55 | 55 |
|
56 | 56 | <AccordionGroup> |
57 | 57 | <Accordion title="Set Your OpenAI Provider Key (optional)" icon="key" iconType="solid"> |
58 | | - Before we proceed, we can set our [provider key](https://docs.vapi.ai/customization/provider-keys) for OpenAI (this is just your OpenAI secret key). |
| 58 | + Before we proceed, we can set our [provider key](/customization/provider-keys) for OpenAI (this is just your OpenAI secret key). |
59 | 59 |
|
60 | 60 | <Note> |
61 | 61 | You can see all of your provider keys in the "Provider Keys" dashboard tab. You can also go |
62 | 62 | directly to [dashboard.vapi.ai/keys](https://dashboard.vapi.ai/keys). |
63 | 63 | </Note> |
64 | 64 |
|
65 | | - Vapi uses [provider keys](https://docs.vapi.ai/customization/provider-keys) you provide to communicate with LLM, TTS, & STT vendors on your behalf. It is most ideal that we set keys for the vendors we intend to use ahead of time. |
| 65 | + Vapi uses [provider keys](/customization/provider-keys) you provide to communicate with LLM, TTS, & STT vendors on your behalf. It is most ideal that we set keys for the vendors we intend to use ahead of time. |
66 | 66 |
|
67 | 67 | <Frame caption="We set our provider key for OpenAI so Vapi can make requests to their API."> |
68 | 68 | <img src="../static/images/quickstart/dashboard/model-provider-keys.png" /> |
|
85 | 85 | For our use case, we will want a first message. It would be ideal for us to have a first message like this: |
86 | 86 |
|
87 | 87 | ```text |
88 | | - Vappy’s Pizzeria speaking, how can I help you? |
| 88 | + Vappy's Pizzeria speaking, how can I help you? |
89 | 89 | ``` |
90 | 90 |
|
91 | 91 | <Info> |
|
105 | 105 | The system prompt can be used to configure the context, role, personality, instructions and so on for the assistant. In our case, a system prompt like this will give us the behavior we want: |
106 | 106 |
|
107 | 107 | ```text |
108 | | - You are a voice assistant for Vappy’s Pizzeria, |
| 108 | + You are a voice assistant for Vappy's Pizzeria, |
109 | 109 | a pizza shop located on the Internet. |
110 | 110 |
|
111 | 111 | Your job is to take the order of customers calling in. The menu has only 3 types |
|
0 commit comments