Editor

Sayless uses a rich text editor in the places where your team writes meaningful content: conversation replies, ticket descriptions, ticket comments, broadcasts, notes, and reports. The editor is designed for quick writing first, with formatting and attachments available when the message needs more structure.

​

Overview

Use the editor when you need to write customer-facing replies, internal context, broadcast messages, or record notes. The editor supports formatted text, links, lists, mentions, file uploads, inline images, and common keyboard shortcuts. Some editor behavior depends on where you are writing. For example, a conversation reply can include recipients and attachments, while a ticket description is saved as part of the ticket.

⌘ then K or Ctrl then K opens the Sayless command menu. Inside the editor, ⌘/Ctrl + K is also used for link insertion, so shortcut behavior depends on whether the editor has focus.

​

Writing content

Start typing directly in the editor. Use plain language for the main message, then add formatting only where it helps the reader.

​

Formatting

The editor supports common formatting such as bold, italic, underline, headings, quotes, code blocks, and lists. Common shortcuts include:

• ⌘ or Ctrl + B for bold.
• ⌘ or Ctrl + I for italic.
• ⌘ or Ctrl + U for underline.
• ⌘ or Ctrl + K to insert a link while writing.
• ⌘ or Ctrl + Z to undo.

​

Lists and structure

Use bullet lists, numbered lists, or checklists when a message includes steps, requirements, or decisions. Longer ticket descriptions and notes are easier to scan when you break them into headings and lists instead of writing one long paragraph.

​

Mentions

Mentions help pull people into the context of a message or internal note. Use them when someone needs to review, answer, or take action. Mentions are most useful in team-facing writing such as comments, ticket context, and notes.

​

Adding media

Use files and images when text alone is not enough.

​

Attachments

Conversation replies can include attachments. Attach files when the recipient needs a document, image, export, or other supporting material.

Attachment support depends on the editor surface and channel. A ticket description can store uploaded files for ticket context; a channel reply can only send what the destination channel supports.

​

Inline images

The editor supports inline image handling in rich text areas. Use inline images when the image is part of the explanation rather than a separate file the reader should download.

​

Links

Use links for external references, customer resources, internal tools, or follow-up material. In ticket workflows, prefer the Linear or Jira sections when the link is specifically an external issue.

​

Drafts and saving

Sayless saves or preserves writing differently depending on the page.

​

Conversation drafts

Conversation replies keep draft state while you are working so you can move around without immediately losing what you typed.

​

Ticket autosave

Ticket titles and descriptions are edited directly from the ticket detail page. Changes are saved as part of the ticket editing flow, and the page tracks unsaved editor changes while you work.

​

Broadcast drafts

Broadcasts can be created and edited before they are sent. Use drafts when a broadcast needs review, a destination change, or more editing before delivery.