7 EasyDesk Helpdesk Features That Boost Support Efficiency

How to Resolve Common Issues with EasyDesk Helpdesk

1. Tickets not created from incoming emails

• Check email forwarding: Verify your support address forwards to EasyDesk’s intake address.
• Validate mailbox settings: Ensure IMAP/POP or connector credentials are correct and not rate-limited.
• Review spam/quarantine: Confirm messages aren’t blocked by spam filters or company gateway.
• Test with a raw email: Send a simple test message and check EasyDesk logs for receipt and parsing errors.

2. Agents not receiving notification or assignment alerts

• Notification settings: Confirm agent notification preferences (email, push) are enabled.
• SLA/automation conflicts: Check automations/rules that may reassign or silence notifications.
• Device push permissions: On mobile, ensure app notifications are permitted and battery/Do Not Disturb modes aren’t blocking them.
• Audit recent changes: Look for recent role/permission updates that removed notify rights.

3. Slow dashboard or search performance

• Browser checks: Clear cache, disable extensions, or try a different browser/incognito.
• Large dataset filters: Narrow date ranges, statuses, or tags—heavy queries can slow UI.
• Attachment-heavy tickets: Large file loads can reduce performance; consider storage limits/archiving.
• Status page / outage: Check EasyDesk status or support announcements for service issues.

4. Missing ticket history or customer messages

• Conversation threading rules: Confirm inbound messages match ticket identifiers (subject or thread ID).
• Email-to-ticket mapping: Check parsing rules that may create new tickets instead of appending replies.
• Time-zone and timestamp differences: Verify server/client time settings when searching by date.
• Retention/archival policies: Ensure items weren’t auto-archived or purged by retention rules.

5. Automations and macros not running as expected

• Trigger conditions: Verify triggers (status change, tag added, incoming message) exactly match ticket events.
• Execution order: Check for conflicting automations where one rule overrides another.
• Permission scope: Ensure the automation runs under a user/role with required permissions.
• Audit logs: Review automation run logs for errors or failed actions.

6. Integration failures (CRM, Slack, WhatsApp, etc.)

• API keys / OAuth: Revoke and re-authorize integrations if tokens expired.
• Webhook delivery: Check webhook endpoints and response codes; retry failed deliveries.
• Field mapping: Confirm mapped fields align between systems (email, contact ID, custom fields).
• Rate limits: Ensure external APIs aren’t being throttled.

7. Incorrect reporting or metrics

• Report filters: Confirm date ranges, statuses, and agent filters are correct.
• SLA / business hours config: Ensure business hours and SLA definitions are accurate for calculations.
• Data sync delays: Some reports update on schedules—allow time or trigger a manual refresh.
• Duplicate tickets: Identify and merge duplicates that skew counts.

8. Access, SSO, or permission issues

• SSO logs: Check your identity provider logs for authentication errors and SAML/OAuth responses.
• Role assignments: Confirm user roles include required capabilities (view, reply, edit).
• Provisioning sync: Re-sync users if using SCIM/automated provisioning.
• Account lockouts: Verify account status and reset passwords or re-invite users if needed.

Quick troubleshooting checklist (use in order)

1. Reproduce the issue and capture exact steps, screenshots, timestamps.
2. Check system status / incident page.
3. Review EasyDesk logs (email ingestion, automation, webhook, auth).
4. Test with a controlled example (single test ticket/message).
5. Revoke/recreate integration credentials if applicable.
6. Escalate to EasyDesk support with logs, affected ticket IDs, and reproduction steps.

If you want, I can produce a step-by-step runbook for your team tailored to your EasyDesk plan and integrations — tell me which integrations and a typical support flow.