# Email to Ticket Guide

If you want to automatically turn incoming emails (e.g., <support@wrangle.io>) into Wrangle tickets in Slack, follow these steps:

***

{% hint style="info" %}
Emails can be turned into Wrangle tickets *only* if the sender of the email is an email associated with a Slack user in your workspace.&#x20;
{% endhint %}

### Step 1: Set Up Your Inbox Settings in Wrangle

1. Open the Wrangle dashboard and navigate to **Inboxes**. Then select the specific inbox you'd like to connect.
2. Select the inbox you want to use for email-to-ticket conversion.
3. Under **Ticket Lifecycle > Ticket Creation** there are two settings you'll want turned on:&#x20;

   1. Toggle on the option **"Create tickets for messages sent by bots"** to enable automatic ticket creation for forwarded emails.
   2. Make sure the first setting for how you'll turn messages into tickets is set to Turn new channel messages into tickets automatically&#x20;

   <figure><img src="/files/SgolpC7exMAsVPoJo941" alt="" width="375"><figcaption></figcaption></figure>

***

### Step 2: Retrieve Your Slack Channel Email Address

* Go to the Slack channel where you want Wrangle tickets to appear.
* Click the channel name at the top of the Slack interface to open the channel details.

<figure><img src="/files/g6BWQkiLlgR4OZUF0Ywk" alt=""><figcaption></figcaption></figure>

* Under the **Integrations** tab, scroll down to find the option **"Send emails to this channel"** (you may need to enable email integration for the channel if it’s not already set up).

<figure><img src="/files/bekGUw1s0rYYeUQLLQYX" alt=""><figcaption></figcaption></figure>

* Copy the provided email address for the Slack channel.

<figure><img src="/files/4YLYAz3M0wupsi7LzgSZ" alt=""><figcaption></figcaption></figure>

***

### Step 3: Configure Your Email Provider to Forward Emails

1. Log in to your email provider (e.g., Gmail, Outlook) and open the settings for the email address you want to use (e.g., <support@wrangle.io>).
2. Set up **email forwarding** to automatically forward all incoming emails to the Slack channel email address you retrieved in Step 2.
   * In Gmail: Navigate to Settings > Forwarding and POP/IMAP > Add a Forwarding Address.
   * In Outlook: Navigate to Settings > Mail > Forwarding.
3. Test the forwarding rule to ensure emails are correctly routed to the Slack channel.

***

### Additional Notes:

* Emails forwarded to the Slack channel will appear as messages. With the **"Turn bot messages into tickets"** option enabled in Wrangle, these messages will automatically be converted into tickets.

<div><figure><img src="/files/d0oEs35d4TImo5XhYcig" alt=""><figcaption><p>Forwarded email in the slack channel</p></figcaption></figure> <figure><img src="/files/EZ1sKFqqj26vrY8lznLa" alt=""><figcaption><p>Forwarded email turned into a Wrangle ticket</p></figcaption></figure></div>

* Ensure the forwarded emails contain clear and actionable information to make ticket creation more effective.
* If you’re using a shared inbox (e.g., <support@wrangle.io>), ensure everyone on your team knows that emails sent to this address will create tickets in Slack.
* The details and fuctionality are seamless in both Slack and the Wrangle Web App

<figure><img src="/files/GRQUQOUxzPFdtfc52bnV" alt=""><figcaption></figcaption></figure>

***

With this setup, your team can manage incoming email requests seamlessly in Slack, thanks to Wrangle’s ticket automation!


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.wrangle.io/~/revisions/xm0jayw05byBY8bJjjVs/tickets/email-to-ticket-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.