How to Set Up Email Ticketing in NeuraDesk
Learn what you need before you start, follow numbered steps to connect your support inbox, set conversion rules, and avoid common pitfalls.
NNeuraDesk TeamNovember 19 20264 min read
On this page
You can turn any support email address into a fully tracked ticket queue that your whole team can manage together. Before you begin, make sure you have an account, admin access to the email address you want to use, and permission to set up forwarding or SMTP settings in your mail provider.
1. Create Your Account
- Visit the registration page and sign up with your work email. No credit card is required and the process takes about a minute.
- Verify your email address by clicking the link sent to your inbox.
- Log in and complete the brief onboarding wizard: choose a workspace name and invite any teammates who will handle tickets. Why it matters: the account is the container for all tickets, shared inbox views, and AI reply suggestions. Without it there is nowhere for email‑to‑ticket conversion to land.
2. Connect Your Support Email Address
- In the workspace settings, open the Email Channels section and click Add Email Channel.
- Enter the full support address (for example, support@yourcompany.com).
- Choose the connection method:
- Forwarding – set up an automatic forward from your mail provider to the unique address shown on screen.
- SMTP/IMAP – enter the server details if you prefer to pull messages directly.
- Send a test message to the support address and confirm it appears as a new ticket in the dashboard. Why it matters: this step creates the pipeline that turns every incoming message into a trackable ticket. If forwarding rules are mis‑configured, messages will never reach the queue. For detailed forwarding instructions for Gmail, see How to Set Up Email to Ticket Conversion in Gmail. For Outlook, see How to Set Up Email to Ticket Conversion in Outlook.
3. Configure Automatic Email‑to‑Ticket Conversion Rules
- Open the Automation tab and select Conversion Rules.
- Create a rule that matches all incoming mail to the connected address, or add conditions such as specific subjects, sender domains, or keywords.
- Choose the default ticket status (e.g., Open) and assign a default assignee or leave it unassigned for triage.
- Enable the option to apply AI reply suggestions automatically so agents see draft responses right away. Why it matters: rules prevent manual triage for every message and ensure consistent status assignment from the moment a ticket is created. For more advanced rule examples, refer to How to Configure Automatic Email to Ticket Conversion Rules.
4. Set Up Shared Inbox and Team Collaboration
- In the Inbox view, verify that all agents see the same ticket list — this is the shared inbox.
- Use internal notes to discuss a ticket without the customer seeing the conversation.
- Apply tags to categorize tickets by product, urgency, or region. Tags make filtering and reporting straightforward.
- Assign tickets manually or let the automatic assignment rule you created in step 3 handle distribution. Why it matters: a shared inbox eliminates duplicate replies and gives visibility into workload across the team. For guidance on building a useful tag taxonomy, see How to Set Up Internal Tags for Better Ticket Organization.
5. Define Ticket Statuses and Workflow
- Review the default statuses: Open, Pending, Resolved, Closed.
- Add custom statuses if your process includes stages such as Waiting on Customer or Escalated.
- Set up status transition rules — for example, automatically move a ticket to Pending when an agent adds an internal note requesting more information. Why it matters: clear statuses let managers track progress at a glance and help agents know what action is expected next.
6. Test the End‑to‑End Flow
- Send a real email from an external address to your support address.
- Confirm the ticket appears in the shared inbox with the correct status and assignee.
- Open the ticket, review the AI reply suggestion, edit if needed, and send a response.
- Verify the customer receives the reply and that the ticket status updates automatically. Why it matters: a full test catches forwarding loops, rule mismatches, or permission issues before real customers are affected.
Common Mistakes to Avoid
- Skipping email verification – an unverified address will not create tickets.
- Using a personal email alias instead of a dedicated support address – this mixes personal mail with support traffic.
- Forgetting to enable forwarding in the mail provider – the forward rule must be active and point to the exact address.
- Over‑complicating conversion rules – start with a catch‑all rule, then add filters only when you have volume that justifies them.
- Neglecting to train agents on internal notes – without a convention, internal discussions can leak to customers.
- Leaving default statuses unchanged when your workflow needs more granularity – custom statuses prevent tickets from stalling in a generic bucket.
Once the pipeline is live, your team can handle every support request from a single view, with AI suggestions speeding up replies. Try it free to start handling tickets in minutes: try NeuraDesk free.
Found this useful? Share it with your team.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free