The email channel end-to-end

Ref: B07 · Track: Channels · Time to complete: ~10 min

Why this matters

Email is the channel you'll handle most of. Understanding the full lifecycle — what happens before the ticket lands with you and after you reply — prevents a lot of weird customer escalations.

The lifecycle at a glance

Customer sends email
      │
      ▼
Zendesk receives at support@yourcompany.com
      │
      ▼
Triggers fire (autoreply, tagging, routing, assignment)
      │
      ▼
Ticket created, status = New, then Open when assigned
      │
      ▼
Agent replies publicly
      │
      ▼
Status → Pending (awaiting customer)
      │
      ▼
Customer replies → ticket reopens (status = Open)
      │
      ▼
Agent solves → Status = Solved
      │
      ▼
4 days later → Status = Closed (read-only)

Step 1 — Receipt

Customer sends to a support address (e.g. support@yourcompany.com). Zendesk receives the email and creates a ticket. The subject becomes the ticket subject; the body becomes the first ticket comment.

Attachments (PDFs, screenshots, etc.) come across and are visible in the ticket timeline.

If the customer's email address isn't recognised, a new user profile is created automatically.

Step 2 — Autoreply (optional)

Most teams configure an autoreply trigger: - Customer gets an immediate "Thanks — we've got your email, ticket #1234, we'll be in touch within X hours" reply. - The ticket ID goes in the subject. This is how replies route back to the same ticket.

If your team has disabled autoreplies, the customer just hears nothing until an agent replies.

Step 3 — Routing and assignment

Triggers and (if enabled) omnichannel routing decide: - Which group the ticket goes to (e.g. Billing vs Tech based on subject keywords). - Whether it gets assigned to a specific agent or stays in the group's unassigned pool. - What tags, priority, and custom fields to apply.

If you see a ticket land on your desk that shouldn't be there, don't just reassign — flag it to your admin so the routing trigger can be fixed.

Step 4 — Your reply

Open the ticket. Write in the white (public) composer. Either: - Type from scratch. - Apply a macro (A11). - Quote and respond to a specific part of the customer's message.

Submit as Pending if you're waiting on them; Solved if you've resolved it; Open if you're passing it to someone else.

Step 5 — Threading

When the customer replies to your email: - The ticket ID in the subject (e.g. [#1234]) tells Zendesk to route the reply back to the same ticket, not create a new one. - Status flips back to Open. - Your NRT clock starts (see A10).

⚠️ If a customer strips the ticket ID out of the subject (some corporate email systems do), Zendesk can't match the reply and creates a new ticket. You'll need to merge (see A14).

Step 6 — Solve

When you believe it's done: - Submit as Solved. - The customer may get a survey (CSAT) asking them to rate the interaction. - After 4 days with no further reply, the ticket closes automatically.

If the customer replies within 4 days, the ticket reopens and you handle their follow-up.

If they reply after 4 days, a follow-up ticket is created (see A12).

CCs and forwarded emails

• CCs on the original email → become CCs on the ticket. They see every public reply you send.
• Customer forwarded from another address → the forwarder becomes the requester unless admin rules fix it. If this is a common pattern in your org, work with admin to set up forwarder-recognition rules.
• Customer replies with CCs added → the new CCs are added to the ticket.

Watch CCs carefully — they can include people the original customer didn't want in the conversation.

Common email issues

• "The customer didn't get my reply" — check spam folders, check the ticket's "reply to" address, check that no trigger is blocking outbound.
• "New ticket every time they reply" — the subject line probably lost the ticket ID. Merge the tickets and educate the customer (if internal) or their IT team.
• "Weird HTML in the reply" — Zendesk renders what the customer sent. If an Outlook user sent it, it's full of quote-chevrons. Reply in plain text if it matters.

Quick check — have you got this?

• A customer's original email had her manager on CC. Do you need to CC the manager on your reply?
• The customer replies but the subject is now "RE: RE: RE: RE:" and the ticket ID has been stripped. What happens?
• You solve a ticket. Four days pass. Customer replies. New ticket or reopen?

Related articles

• A07 — Public reply vs internal note
• A09 — Ticket statuses explained
• A12 — Follow-up tickets vs reopens
• D01 — Omnichannel routing and capacity rules