SolutionDeskDocs

Create a ticket

File work for a company, set type, priority, visibility, and fields.

From the tickets board, open New ticket (or the equivalent create action).

Steps

  1. Title — short, customer-safe summary when the ticket may become public.
  2. Type — e.g. bug, feature, question (configured per workspace).
  3. Priority and initial status (defaults come from workspace config).
  4. Company — which end-customer this concerns (e.g. Acme). Often pre-selects the first company.
  5. Visibilityinternal (default when unsure), public, or restricted.
  6. Custom fields — type-specific fields (often a rich-text description).
  7. Assignees / labels — optional at create time; editable later.
  8. Submit.

Create ticket form

Visibility checklist

IntentVisibility
Team-only planning / triageinternal
Share progress with the whole company on the ticketpublic
Share only with matching end-user attributesrestricted + access rules

After create

You land on ticket detail. Attach files, leave an internal note for the team, or write the first customer-visible reply if the portal should already show conversation.

On this page