> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Magic Title Rule Creation Guide

> Write effective Magic Title rules with prompt examples, prefix patterns, runtime variables, and best practices for concise, consistent ticket titles.

## Purpose of Title Rules

The purpose of title rules is to generate clear, consistent, and actionable ticket titles using simple prompt-based instructions. These rules tell Magic Title what to include, exclude, or emphasize when summarizing a request.

You can also use runtime variables to dynamically insert context into the title, ensuring every ticket is easy to scan, sort, and understand.

View Available Runtime Variables

## **Objectives of Title Rules**

1. Ensure concise and clear ticket titles.
2. Avoid unnecessary or redundant information (e.g., greetings, filler words).
3. Maintain consistency across all categories of requests.
4. Align titles with predefined categories or formats when applicable.

## **Guidelines for Writing Title Rules**

* Keep titles concise (3-4 words maximum).
* Avoid greetings, pleasantries, or generic terms (e.g., "Hi," "Help").
* Focus on the specific issue or action required.
* Use clear, descriptive language to ensure quick understanding.

## **Example Templates for Rules**

Use these templates as a foundation for crafting effective prompts:

1. **Default Prompt Example**"Provide a short and concise title for the ticket, including the initial problem. Ignore words like greetings or help."
2. **Format-Specific Prompt**"Write a concise, three-word title summarizing the issue. Use action-oriented language and avoid filler words."
3. **Keyword Extraction Prompt**"Analyze the request details and extract the most relevant keywords to form a clear and concise title."
4. **Role-Based Prompt**"Imagine you’re a technician receiving this request. Summarize the issue in a title that is actionable and clear, using 3-4 words."
5. **Prefix-Based Prompt**“Generate a title with the correct prefix based on the request type: **ACC:** Access requests (e.g., ‘ACC - Permissions Needed’); **SFWI:** Software issues (e.g., ‘SFWI - Installation Error’); **HWI:** Hardware problems (e.g., ‘HWI - Printer Offline’); **PSWR:** Password resets (e.g., ‘PSWR - Reset Password’); **ACCI:** Account issues (e.g., ‘ACCI - Locked Account’); **CONN:** Connectivity issues (e.g., ‘CONN - VPN Failure’). Use the prefix and summarize the issue in 3-4 words. Example: ‘SFWI - App Crash.’”

## **Categories of Titles**

When applicable, categorize titles into predefined groups for clarity and standardization. Example categories include:

1. **Access Requests**: e.g., "Access Permissions Needed"
2. **Software Issues**: e.g., "Software Installation Error"
3. **Hardware Issues**: e.g., "Printer Connection Failed"

## **Best Practices**

1. **Be Consistent**: Use the same structure and tone across all prompts.
2. **Iterate Based on Feedback**: Regularly refine prompts based on user input.
3. **Test for Clarity**: Ensure prompts are easy to understand and follow.
4. **Consider Automation**: Align prompts with AI systems to automate title generation effectively.


## Related topics

- [Configure Magic Title in Thread](/assistive-ai/setting-up-magic-title.md)
- [Thread Partner Change Management Guide](/get-started/thread-partner-change-management-guide.md)
- [Configure Auto Categorization in Thread](/assistive-ai/getting-started-with-auto-categorization.md)