Set Up Email¶
This guide takes you from an empty Daktela instance to answering emails as tickets. It builds the pieces in the order they depend on each other.
If you haven't yet, read How Email Works first β emails become tickets, so the setup runs through categories and views rather than a routing chain.
The whole setup:
- Prepare the ticket category
- Create the email queue and connect your mailbox
- Add agents to the queue
- Add email routing rules (optional)
- Test
1. Prepare the Ticket Category¶
Incoming emails become tickets in a category, and category rights decide who sees them.
- Go to Settings β Tickets β Categories and create (or pick) the category for this mailbox's tickets β see Categories.
- Make sure the agents who should work these tickets have rights to the category.
2. Create the Email Queue and Connect Your Mailbox¶
- Go to Settings β Routings β Queues and click Add new, then select Email.
- Fill out the Unique queue number and the Title (e.g. "support@example.com").
-
Under Incoming mail server, select the protocol and connect the mailbox:
- Gmail β use Google OAuth2 and authorise with the G button: How to Authorise Gmail.
- Microsoft 365 β prefer a Graph API protocol; see which protocol to use and How to Authorise Microsoft Office 365.
- Other providers β enter the IMAP/POP3 server, name and password.
Warning
Connect a direct mailbox, not an alias. For your email queue to send and receive email, you need to set up both Incoming mail server and Outgoing mail SMTP server β with OAuth protocols you can instead enable Use same method for Outgoing.
-
Set the Sender info and Sender address (the mail server must be allowed to send from this address).
- Under Tickets, select the Category from step 1.
- Optionally set an Auto response template and Working hours (a time group β the auto response is only sent during them), a Signature template and a Default template.
- Click Save.
Every field is described in the Email Queue reference.
3. Add Agents to the Queue¶
- In the queue list (Settings β Routings β Queues), find your new queue and click Change in the Agents column.
- Check (tick) the user rights that should have access to the queue and select a Login type β Automatic is a good default.
Tickets are automatically distributed only to agents that are logged in to the queue, and agents only see tickets whose category they have rights to. See Queue Basics β Assign Agents to a Queue for all the options.
4. Add Email Routing Rules (Optional)¶
Email routings refine tickets before they reach agents β e.g. send "noreply" senders to a Do not reply category, give VIP domains a high priority, or sort "complaint" subjects into a special category.
- Go to Settings β Routings β Emails and click Add new.
- Set the Direction, the filtering conditions and the action (category, priority, status, custom fieldsβ¦).
- Mind the Order (rules are evaluated in order) and Stop (stop evaluating further rules on match).
The rule editor, ordering and import/export are described in Email Routings.
5. Test¶
- With an agent logged in to the queue and in the Ready state, send a test email to the mailbox.
- Check a ticket is created in the right category, your routing rules applied, and the ticket reaches the agent.
- Reply from the ticket and check the outgoing email arrives with the right sender address and signature.
Go Further¶
- Ticket views β give agents filtered work lists (by category, status, ageβ¦).
- SLA β response-time targets per category.
- Macros β one-click ticket actions for agents.
- Scheduled sending β agents can schedule outbound emails unless disabled in the queue settings.
- For agents β working with email is described in Email and Tickets.