Skip to main content

Forwarded Address

The Forwarded Address intake mode gives each Help Desk Department its own ready-to-use inbound email address — no mailbox to provision, no IMAP server to configure. Emails sent to the address become tickets automatically.

This is the recommended option for districts that don't want to manage a dedicated mailbox per department, or who want to roll out new departments quickly.

Permission Required

To configure intake settings on a Help Desk Department, you need the Manage Settings permission assigned to your role.

When to Use Forwarded Address​

Use Forwarded Address when you want:

  • A dedicated ticket-intake address for a department without provisioning a mailbox on your district's mail server.
  • A consistent, brand-managed address that doesn't change when staff turn over.
  • The ability to roll out new departments in minutes.

Stay on Custom Mailbox (POP / IMAP) when you want:

  • All inbound mail to flow through your district's existing mail infrastructure.
  • Centralized auditing or retention through your mail provider.
  • A specific email address on your own domain that staff already publish.

Both modes can coexist in the same Manage1to1 instance — choose per department.

How It Works​

  1. You enable Forwarded Address on a department and save. Manage1to1 generates a unique inbound address for that department.
  2. You publish the generated address (or have staff forward parent / user emails to it).
  3. Manage1to1 checks for new messages on a short interval and turns each one into a ticket in the correct department.
  4. Replies sent through Manage1to1 are emailed back to the requester as normal.

The generated address follows this shape:

tickets+<department-slug>_<token>@incoming.manage1to1.com
  • <department-slug> — a short readable identifier derived from the department's name (e.g. device-support, network-wifi).
  • <token> — a 12-character random code that ensures the address is unguessable. The token is the routing key; if it changes, the address changes.

You don't need to type or remember the address — Manage1to1 displays it on the department edit page with a one-click Copy button.

Enable Forwarded Address on a Department​

  1. Navigate to Settings → Help Desk and open the department you want to edit (or click Add to create a new one).
  2. In the Inbound Mail section, set Intake Mode to Forwarded Address.
  3. Click Save Settings.

After saving, the Inbound Address field appears showing the generated address. Use the Copy button to grab it for distribution.

Default for new departments

On a fresh Manage1to1 install, new departments default to Forwarded Address when forwarded mail is available. Existing departments keep their current mode until you change it manually.

What to Publish​

The generated address is what you give to:

  • Staff who should email new tickets directly.
  • Parents and students, if you want them to be able to open tickets by email (typically published on the school site, parent portal, or in a footer).
  • Internal forms or automations that need to open tickets programmatically.

Treat it as a regular email address — anyone who knows it can send mail that creates a ticket.

Admin Forwarding — Open a Ticket on Behalf of a User​

A common workflow: a parent emails an admin directly, and the admin wants to log a ticket so the help desk team can work it. Forwarded Address mode handles this automatically.

When an administrator forwards an email to a department's inbound address:

  1. Manage1to1 recognizes the message came from an admin and that the subject begins with Fwd:, Fw:, or Forward:.

  2. It reads the original sender's name and email out of the forwarded message block (the From: line that Gmail, Outlook, and Apple Mail include when forwarding).

  3. The resulting ticket is opened on behalf of the original sender — not the admin who forwarded it.

  4. The ticket body includes a clearly labeled note at the top, showing the admin who forwarded it. For example:

    [Forwarded by Pat Lee <plee@district.org>]

  5. Replies go to the original sender's email address. The admin who forwarded the message is not added to the ticket recipients.

What this preserves:

  • The original sender is credited as the requester.
  • The forwarding admin shows up in the ticket body so anyone reviewing the ticket can see how it arrived.
  • The "Fwd:" prefix is stripped from the ticket title so it reads naturally.

When it doesn't apply:

  • If the subject doesn't look like a forward (Fwd: / Fw: / Forward: prefix), the message is rejected the same as any other direct admin email with no ticket reference.
  • If the forwarded body has no parseable From: header, the message is rejected — Manage1to1 won't guess at the original sender.
  • If the extracted original sender is also a Manage1to1 administrator, the message is rejected (this prevents admins from forwarding their own mail to themselves to bypass the normal admin-reply rule).

Regenerate the Address​

If the inbound address gets out into the wrong hands — published incorrectly, leaked in a screenshot, or simply needs to be retired and reissued — click Regenerate Address on the department edit page.

This:

  • Issues a new token immediately.
  • Re-derives the slug from the department's current name (useful if you renamed the department after the original address was generated).
  • Stops mail to the old address from being processed. Any messages still in transit to the old address will not become tickets.
One-way action

Regenerating the address invalidates the previous one. There is no rollback. Make sure you have a plan for getting the new address to anyone who publishes or uses it.

Department Rules Apply Either Way​

Every other Help Desk Department setting works identically regardless of intake mode:

  • Whitelisted Emails Only still restricts who can open tickets.
  • Whitelisted Domains still gate inbound by sender domain.
  • Admin Only still hides the department from the public portal.
  • Auto Assign Tickets still routes the new tickets to the right technician.
  • Restrict to Buildings still scopes auto-assignment.
  • Ticket ID Format still controls the ticket's display ID.
  • Custom Fields still capture extra data on creation.

In other words, Forwarded Address only changes how the mail arrives. Everything downstream behaves the way it already does.

Switching Back to Custom Mailbox​

You can switch a department to Custom Mailbox (POP / IMAP) at any time from the same Inbound Mail section. The previously generated forwarded address is retained on the department — switching back to Forwarded Address later restores the same address without regenerating.

If you want a clean break (new address on re-activation), click Regenerate Address after switching back.

Best Practices​

✅ Do:

  • Publish the forwarded address only where you actually want tickets created.
  • Use Admin Forwarding when staff receive parent emails outside the published address — it logs the ticket without anyone needing to retype the parent's address.
  • Regenerate the address if you have any reason to suspect it has been mishandled.
  • Add school district domains to Whitelisted Domains if you want only staff / parent senders to be able to create tickets.

❌ Don't:

  • Don't publish the forwarded address as the "From" address for outbound mail — it's an intake-only address.
  • Don't share the same forwarded address across multiple departments — each department has its own.
  • Don't manually edit the slug or token portion of the address. Use Regenerate Address if you need a new one.

Forwarded Address mode lets a district stand up email-to-ticket flow for any Help Desk Department in a single click — and the Admin Forwarding feature means staff can pull existing email conversations into the queue without losing attribution.

Related articles

Loading…