> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/channels/add-a-channel/amazon-connect.md).

# Amazon Connect

Connect Amazon Connect to Syntphony Conversational AI with Amazon Lex V2 and AWS Lambda. Lambda securely passes requests between Lex and Syntphony Conversational AI.

## Create a Lambda function

Start by creating the Lambda function that bridges Lex and Syntphony Conversational AI.

1. Sign in to the [**AWS console**](https://console.aws.amazon.com/) with the required permissions
2. Open [**AWS Lambda**](https://console.aws.amazon.com/lambda) and create a function
3. Configure the credentials and connection values for Syntphony Conversational AI
4. Update the function's execution role with these Amazon Lex permissions:
   * `lex:ListIntents`
   * `lex:ListSlots`
5. Alternatively, use `AmazonLexReadOnly` when it meets your access requirements
6. Save the function.

<figure><img src="https://4008706377-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fn6zS4HeuuVpRHZEvDiFU%2Fuploads%2F15Tvcy91gFim1UG4Os61%2Fimage.png?alt=media&amp;token=e75590c5-54ce-4d14-b9d9-45d1cd602fca" alt=""><figcaption></figcaption></figure>

### Connect the Lambda function to Amazon Lex V2

Now connect the function to every Lex intent and language you support.

1. Open your bot in the [**Amazon Lex V2 console**](https://console.aws.amazon.com/lexv2)
2. Open an intent and expand **Fulfillment**
3. Enable the **Fulfillment Lambda code hook** under **Advanced options**

<figure><img src="https://docs.eva.bot/voice-gateway/~gitbook/image?url=https%3A%2F%2F47336899-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fp0SUdPEICXSM7gLqSIa9%252Fuploads%252FQx6gEkoIqV6Cs8NTWJpN%252Fimage.png%3Falt%3Dmedia%26token%3D59b2e81c-91d3-422a-8d7f-8ed5708c89ea&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=ed1e33b0&#x26;sv=2" alt=""><figcaption></figcaption></figure>

4. Save the intent
5. Repeat steps 2–4 for every intent, including `FallbackIntent`
6. Build the language. Repeat these steps for each additional language
7. Create a new bot version
8. Create an alias, or update an existing alias with the new version
9. In the alias, open each supported language
10. Select the deployed Lambda function and its version
11. Save the configuration.

<figure><img src="https://docs.eva.bot/voice-gateway/~gitbook/image?url=https%3A%2F%2F47336899-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252Fp0SUdPEICXSM7gLqSIa9%252Fuploads%252Fku2BiydgKXybIGtrP1x6%252Fimage.png%3Falt%3Dmedia%26token%3D00284b6c-7ce3-4a77-812e-9cfc454b597d&#x26;width=768&#x26;dpr=4&#x26;quality=100&#x26;sign=d9234870&#x26;sv=2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/channels/add-a-channel/amazon-connect.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
