> For the complete documentation index, see [llms.txt](https://docs.wrangle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wrangle.io/tickets/setting-up-your-inbox/ticket-lifecycle/auto-responder.md).
# Auto-Responder
Auto-Responder automatically sends a reply when tickets are created outside of your workspace or users' working hours, letting requesters know their message was received and when to expect a response.
### How it works
When enabled, Auto-Responder posts an automatic message to new ticket threads created after hours. This helps set expectations with requesters and reduces follow-up questions about response times.
Auto-Responder uses your organization's working hours configuration to determine when to send automatic replies. Account admins can [configure working hours](https://docs.wrangle.io/account-administration/working-hours) for your entire organization, which can also be customized at a [user or team-specific level](/account-administration/working-hours.md#working-hours-by-team-user-schedules).
### Setting up Auto-Responder
**To enable Auto-Responder:**
1. Go to **Inboxes** in the left sidebar.
2. On the **Inboxes** page, select the inbox you want to configure
3. Go to **Ticket Lifecycle** in the left sidebar of the Inboxes page
4. Click **Auto-Responder**
5. Toggle **Enable Auto-Responder** on
6. Customize the auto-responder message (optional)
7. Click **Save Changes**
### Customizing your message
The default auto-responder message is:
You can customize this message to match your team's voice and provide specific information like:
* Expected response times
* Links to self-service resources
* Escalation instructions for urgent issues
* Team availability details
**Formatting tip:** Use Slack markdown formatting and links in your message. [Learn more about Slack markdown](https://www.wrangle.io/post/slack-markdown-a-comprehensive-guide-to-formatting-messages).
### Best practices
**Be specific about timing:** Instead of "we'll get back to you soon," mention your typical response time: "We'll respond within one business day" or "Our team is back online at 9 AM EST."
**Include self-service options:** Link to your help center or FAQ if requesters might find immediate answers there.
**Set the right expectations:** Make sure your auto-responder message aligns with your actual SLA and working hours configuration.
**Test it:** After enabling, create a test ticket outside [working hours](https://docs.wrangle.io/account-administration/working-hours) to confirm the message appears as expected.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.wrangle.io/tickets/setting-up-your-inbox/ticket-lifecycle/auto-responder.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.