# Service desk & customer portal

Source: https://iskue.com/docs/service-desk-portal/

> Run a service desk on Iskue: request types, the customer portal and help centre, customers and organizations, queues, knowledge base, email channel, approvals, CSAT and customer notifications.

Iskue's service desk lets customers raise and follow requests without an Iskue account, while agents work the same tickets from queues inside the project. Start a project from the **Service desk** template and you get request types, queues and two SLAs out of the box. This page covers the customer side, the agent side and the channels; **SLAs** and **ITSM** (incidents, changes, problems) have their own pages.

> **Note:** The customer portal and the help centre need the **Professional** edition (the `PORTAL` licence feature). Queues, SLAs, approvals, the email channel and the agent side work on every edition.

## Request types

A **request type** is what a customer picks: "Get IT help", "Request a laptop", "Report an outage". Each one maps onto a ticket type and carries its own form and description. Changing a ticket's request type is recorded and fires the `REQUEST_TYPE_CHANGED` automation trigger. TQL filters on it: `requestType = "Get IT help"`.

## Request forms

A request form holds **sections** and **questions**. A question can be bound to a custom field, so the answer lands as a validated field value, or stay free-form. Conditional logic shows or hides questions and sections depending on earlier answers. Customers can attach up to 3 files (2 MB each) while raising a request. Agents can fill the same form internally, and the submitted answers stay visible on the ticket. Request-type names and form texts can be **translated**; customers see the version for their language.

## The customer portal

Customers reach the portal with a link that carries an opaque **capability token** (`X-Portal-Token`), not a password. A link is valid for 14 days and a contact may hold up to **5** live links: issuing a new one adds a link and prunes expired or surplus ones, and revoking cuts them all. Customers see only their own requests, plus requests shared with them as participants or with their organization, and only **public** comments; agents appear by display name only. Any ticket that is not theirs answers a uniform 404.

- **Access.** Per project, choose **Restricted** (agents invite customers; unknown people land in an access-request queue an agent approves or declines) or **Open** (anyone can sign up, optionally only from approved email domains). Anonymous raising can be allowed too.
- **Branding.** Display name, logo, accent colour, an intro and a footer in English and French, plus scheduled **announcements**.
- **Help centre.** One site-wide landing page (name, logo, accent, intro) grouping portals into **topics**, so a customer with several portals finds the right one.
- **Widget.** An embeddable script puts a request form and knowledge-base search on your own website. It is allowed only on the origins you list (`frame-ancestors`).
- **On the portal, a customer can** raise and follow requests, reply, add participants, approve or decline when they are an approver, rate the resolution, and search published articles.

## Customers, participants and organizations

**Contacts** are per-project customer identities. **Participants** are the other customers on a request: they follow and reply, and email CC addresses become participants automatically. **Customer organizations** are site-level groups with email domains: every new contact whose address matches is grouped into the organization automatically, and a request can be **shared with the whole organization**. A restricted ticket is never served through organization sharing. **Products and entitlements** (see [ITSM](https://iskue.com/docs/itsm/)) attach to a contact or an organization.

## Queues

Queues are named, ordered, project-shared views over a TQL filter, always evaluated inside the project, so a queue can never leak another project's tickets. Each queue chooses its **columns** (system fields, custom fields, SLA timers) and its **sort** (`priority DESC`, `sla`, `remaining("Time to resolution") ASC`), and sits in the **Team** or **Other** group. Users star the queues they live in. From a queue, agents select tickets and act in **bulk**. Agents can also **merge** duplicates (the source closes as "Duplicate" and its comments, attachments, links, watchers and worklogs move to the target), see **similar requests**, and set an **out-of-office** delegate who receives automation assignments while they are away.

## Replies, notes and canned responses

Every comment is either **public** (customers see it, and it is emailed to the requester and participants) or **internal** (agents only). Posting a public reply needs the `REPLY_TO_CUSTOMER` permission: remove it from a role to make **collaborators** who can only write internal notes. **Canned responses** are shared or personal, and each agent can set a signature.

> **Warning:** `internal` defaults to **false** on the comment API: an agent comment without the flag is a public reply. Send `"internal": true` explicitly for notes the customer must not see.

## Knowledge base

Each project has a knowledge base of draft and published articles with categories. **Nothing reaches customers by itself**: an article shows on the portal only when it is published **and** marked portal-visible, its category is allowed, and the project's KB-on-portal switch is on. Customers can then search articles, vote on whether one helped, and see suggestions while they type a request. A **deflection report** counts searches, suggestions shown, articles viewed and requests raised after a suggestion.

## Email channel

Inbound mail is posted by your mail-parsing service to `POST /api/v1/email/webhook/{projectKey}`, authenticated by the project's secret header. A project can have up to **10 intake addresses**, each optionally mapped to a request type, one of them primary. Attachments are kept and CC addresses become participants; participants may reply by email too.

- **Loop and noise protection.** Mail over 25 MB, auto-replies, bulk mail and bounces, mail from the desk's own addresses, contentless replies to our notifications, and more than 20 mails per sender per hour are dropped and logged.
- **Allow and block lists** per project, and a per-sender hourly cap.
- **Restricted access respected.** On a project whose portal access is Restricted, an unknown sender no longer opens a ticket: the mail lands in the access-request queue.
- **Outbound mail** carries `Auto-Submitted: auto-generated`, the project's sender name, and a Reply-To on the primary intake address plus-addressed with the ticket key, so replies thread back to the right ticket.
- **Email log.** Every authenticated inbound delivery is logged with its outcome (created, commented, ignored as a loop or auto-reply, blocked, access requested, rejected for size) and kept for 30 days.

> **Note:** Outbound mail sends only when `MAIL_ENABLED=true`; otherwise it is logged. Set `PORTAL_BASE_URL` wherever mail is on: customer notifications carry each contact's own portal link, and the link is empty without it.

## Customer notifications

Customers are emailed when a request is created, gets a public reply, changes status, is resolved or is reopened, in their own language (English or French). Each event can be switched off, and its subject and body customised in English and French, per project. Mails go to the requester and every participant, once each, skipping anyone who unsubscribed.

## Approvals

Attach an **approval step** to a workflow status: when a ticket enters the status, the step opens and asks its approvers. Approvers can be named users, user groups, the users in a ticket field, or **customers** (contacts). The step's rule is **all**, **any**, a **quorum** (N approvers) or a **percentage**. When the step is decided, the ticket moves by itself through the Approve or Decline transition you configured; leaving the status by hand cancels the open step. Agents approve in the app, customers on the portal or **by email** through signed, single-use links that expire after 14 days. Automation can react with `APPROVAL_REQUESTED` and `APPROVAL_COMPLETED`.

## CSAT

When a request is resolved, the customer receives a single-use rating link and rates it 1–5 with an optional comment. Each project can switch CSAT on or off and set its question in English and French. Internal reporters can still rate their own tickets from the ticket page. Ratings feed the project's average, its distribution and the reports.

## AI and chat

With an AI provider configured, the portal can answer a question from published articles before the customer raises a request, and agents get summaries, reply drafts and writing help. Slack can raise and follow requests too, and Microsoft Teams gets notifications. Both are opt-in: see [Chat & AI](https://iskue.com/docs/chat-and-ai/).
