Gorgias Not Creating Tickets From Emails: Causes & Fixes

The first thing to rule out is a platform-wide outage, which is rare but real: if colleagues also see nothing arriving across every channel, check is Gorgias down before you touch a single setting. Assuming Gorgias is up, the problem is almost always in how your email reaches it.

Start where the evidence is: the Email channel status

Open Settings → Channels → Email and look at the connection you expect tickets to arrive on. This panel lists each support address and a status column. A healthy connection reads Verified (or Connected). If the address you're missing tickets for is absent, greyed out, showing an error, or reads as unverified, you've found your problem before reading any further — the pipe simply isn't open. This is the surface every fix below either confirms or repairs, so it's the honest first stop.

A quick symptom → likely cause table

The common causes, in order

1. The email was flagged as spam by your provider

This is the single most common cause, and the most misleading, because the message looks like it should have arrived. Gorgias imports each email using the classification your email provider already gave it. Per the Gorgias email integration FAQ, if a message was marked as spam in your provider at any point — even if someone later unmarked it — it will be imported as spam in Gorgias. It never lands in your main ticket view, so an agent watching the inbox sees nothing.

Fix: In Gorgias, open the Spam view and look for the message. If it's there, open the ticket, click the three dots in the upper-right corner, and select Unmark as spam to move it into your normal queue. Also check the spam/junk folder in your underlying email provider (Gmail, Outlook) to confirm whether the flag originated there — because a single historical spam flag sticks, adding the sender to a safe-senders list at the provider level prevents a repeat.

2. You're on email forwarding, which drops spam entirely

This is the trap that makes the first cause worse. Gorgias supports two ways to connect email: a direct integration (the native Gmail or Outlook/Microsoft 365 connection) and automatic forwarding from any provider. The behaviour differs in a way that quietly loses tickets. With a direct Gmail or Outlook integration, spam-flagged emails still get imported — they just land in the Spam view where you can recover them. With automatic forwarding, the FAQ is explicit: emails your provider marked as spam won't be imported into Gorgias at all. There's no Spam view to rescue them from because they never crossed over.

Fix: Check which method the address uses in Settings → Channels → Email. If you're forwarding and legitimate emails keep vanishing, the durable fix is to move to a direct integration where spam is at least recoverable — Gorgias documents a switch from an email integration to email forwarding path (and the reverse). Tightening the spam rules in your forwarding provider so fewer real emails get flagged is the interim mitigation. Honest caveat: the native Gmail/Outlook integration requires connecting that specific mailbox with admin permissions, so this isn't something you can validate on a bare trial workspace with no mailbox attached.

3. The integration was deleted, disconnected, or reconnected

If email was arriving fine and then abruptly stopped for one address, someone likely changed the connection. The FAQ is blunt about the consequence: when an email integration is deleted or becomes disconnected, subsequent emails received at that address will not appear as tickets in Gorgias. Existing tickets are unaffected, which is exactly why this is easy to miss — your history looks intact while new mail silently falls on the floor. A common trigger is an admin reconnecting or re-authenticating the mailbox (an OAuth token expiring, a password change, a security review revoking access), which drops the live connection.

Fix: In Settings → Channels → Email, confirm the address is present and its status is healthy. If it's gone, re-add it. If it shows disconnected or an authentication error, reconnect it — this requires admin permissions and re-authenticating against Gmail or Microsoft 365. After reconnecting, send a test email from an outside, non-agent address and confirm a ticket is created.

4. The domain isn't verified (new addresses especially)

If a newly added address has never produced a ticket, the connection likely isn't fully set up. Gorgias' connect-your-email guide describes three steps: add the address, set up forwarding in your provider so incoming mail is forwarded to Gorgias, and verify your domain by adding the DNS records (SPF/DKIM) Gorgias supplies. Domain verification isn't only cosmetic — it reduces bounce rates and prevents your outbound replies from landing in customers' spam. Until forwarding is correctly pointed at the Gorgias address and the domain checks out, mail won't flow reliably.

Fix: Re-walk the three setup steps. Confirm forwarding in your provider targets the exact Gorgias forwarding address, and that the SPF/DKIM records are published on your domain. Honest caveat: verifying a domain and editing DNS requires a domain you actually control — it's not a step you can complete against someone else's store or a throwaway trial domain.

5. Microsoft 365 is blocking external forwarding

A specific, common blocker for Outlook/Microsoft 365 shops: if your organization disables external forwarding, setting up forwarding to Gorgias fails and you may see the error "Access denied, Your organization does not allow external forwarding." No forwarding means no tickets.

Fix: As the Gorgias docs note, your email administrator needs to update the outbound policies in the Microsoft Defender portal to permit automatic forwarding for your organization (or for the specific mailbox). Once external forwarding is allowed, complete the forwarding step and send a test message.

The honest limits — and where an AI layer picks up

None of the above is Gorgias failing you; email is just a messy pipe with spam filters, forwarding rules, and DNS at every joint, and Gorgias inherits whatever your provider decides. Once you understand the two integration types and the spam behaviour, the failure modes are diagnosable rather than mysterious. If you're new to the platform, what is Gorgias covers how the helpdesk is meant to fit an ecommerce stack.

But there's a related pressure worth naming. A lot of the volume that makes a missed email feel catastrophic is repetitive: "where's my order," "how do I return this," "did my discount apply." Every one of those is a ticket an agent has to open, read, and answer by hand — which is exactly the work an AI agent for customer service is built to absorb. Macha is one such layer. It runs on top of the Gorgias you already use — it doesn't replace your helpdesk, it connects to it and reads and writes the same tickets your agents touch, resolving the routine questions automatically so the human queue shrinks to the messages that genuinely need a person. When the backlog is smaller, a stray spam-flagged email is far easier to catch. See the Gorgias AI agent explained for how that works in practice, or the Macha–Gorgias integration for the connector specifics.

Because an AI agent acts on meaning, you can extend what it does through a custom tool that turns any REST API into an action the agent can call — checking live order or tracking status mid-conversation, something no email rule can do. Credits are charged per AI action, not per resolution; the pricing page has the details.

FAQ

Why did one specific customer email never create a ticket in Gorgias? The most likely reason is that your email provider flagged it as spam. Gorgias imports emails with the classification the provider assigned, and a message marked as spam at any point — even if later unmarked — imports as spam. Check the Spam view in Gorgias and your provider's junk folder. If you're on email forwarding rather than a direct integration, spam-flagged emails aren't imported at all.

What's the difference between the Gmail/Outlook integration and email forwarding for spam? With a direct Gmail or Outlook integration, spam still gets imported into the Spam view in Gorgias, so it's recoverable. With automatic email forwarding, emails your provider marked as spam are not imported at all — there's nothing to recover. That difference is the single biggest reason forwarding setups appear to "lose" emails.

Emails stopped arriving at one address entirely — what happened? Almost certainly the integration was deleted, disconnected, or reconnected. Once an email integration is removed or disconnected, subsequent emails at that address won't become tickets, though existing tickets stay put. Go to Settings → Channels → Email, re-add or reconnect the address (admin permissions required), and send a test email to confirm.

My new support address has never created a ticket. Why? The connection likely isn't fully set up. Gorgias requires you to add the address, point forwarding at the Gorgias address, and verify your domain via SPF/DKIM records. If forwarding isn't targeting the right address or the domain isn't verified, mail won't flow. Microsoft 365 users should also check that external forwarding isn't blocked org-wide in Microsoft Defender.

Can an AI layer help with missed emails? Indirectly, and honestly. It won't fix a broken forwarding rule — you still have to repair the connection. But an AI agent layer like Macha resolves the repetitive tickets automatically on top of Gorgias, shrinking the human queue so genuine one-off emails are easier to spot and answer. See the Macha–Gorgias integration and pricing.

Ready to shrink the queue so nothing slips through? Start a free trial and grade a Macha agent against your own Gorgias history before it goes live.