Support Desk & SLAs

A support desk with email-to-ticket, ITSM priorities and SLA clocks that cannot be gamed

Email-to-ticket, Impact × Urgency priority, SLA warn and breach flags with auto-escalation.

Module availability by plan is shown on the pricing page; our sales team can confirm it for your workspace.

Last updated:

What is the Inno Message Support Desk?

The Platform Support Desk is the helpdesk inside Inno Message. Tickets move New → Open → Resolved → Closed (and can be reopened), and are created from email through an IMAP mailbox per partner. Replies go only to the original thread, and every staff reply is emailed to the requester. Priority follows the ITSM model (Impact × Urgency), each partner has response and resolution benchmarks, and the SLA clock is anchored to ticket creation, so re-triaging a ticket cannot buy back time.

Who it's for: Support teams that serve partners and customers under agreed response and resolution times.

Illustrative view of Support Desk & SLAs in Inno Message.

Service levels you can prove

An SLA only means something if the clock is honest. Anchoring it to creation, flagging warnings before breaches and escalating automatically gives partners a service level they can trust, and gives managers the list of every breaching ticket in one popup.

Email-to-ticket

An IMAP mailbox per partner; replies go only to the original thread (From + Cc).

ITSM priority

Priority from Impact × Urgency, with response and resolution benchmarks per partner.

Honest SLA clock

Anchored to ticket creation, with warn and breach flags and automatic escalation.

Notes, assignees and history

Public replies and internal notes with attachments, an assignee picker and an event log per ticket.

How it works

  1. Connect the support mailbox

    Add an IMAP mailbox per partner; incoming email becomes a ticket.

  2. Set SLA benchmarks

    Define response and resolution targets per partner in hours and minutes.

  3. Work and escalate

    The SLA monitor flags warnings, escalates breaches and shows an alert popup listing every breaching ticket.

Technical details

Statuses
New → Open → Resolved → Closed, plus reopen. Archive instead of delete.
Email
Staff replies are emailed to the requester through the support mailbox SMTP.
SLA
Impact × Urgency priority; per-partner benchmarks; clock from creation; warn, breach and auto-escalation.
Mobile
The InnoMessage Inbox app includes the Support Desk.

Questions about Support Desk & SLAs

How is ticket priority set?
By the ITSM model: Impact × Urgency.
Can changing a ticket's priority reset its SLA?
No. The SLA clock is anchored to ticket creation, so a re-triage cannot buy back time.
Who receives staff replies?
Only the original thread (From and Cc), emailed through the support mailbox SMTP.

More answers in the Inno Message FAQ.

See Support Desk & SLAs with your own channels