CampusCloud Helpdesk › Knowledge Base › Agent Formatting

Article: Link Formatting Reference

Examples of how hyperlinks should appear in agent replies across our markdown editor, the rich-text composer, and the email channel. Use the copy buttons next to each entry to paste the exact form into a draft reply for verification.

Audience: Support agents, QA Last reviewed: 2026-05 Owner: Helpdesk Enablement

Baseline examples

Plain links agents can paste directly into replies.

Display text vs destination

When the visible label and the destination differ, agents should always paste the destination URL alongside the label.

Markdown formatting reference

Examples of how the same link should render across markdown variants used in agent replies.

Image embedding and link previews

Inline images, banner thumbnails, and preview cards used in articles. The reference rendering fetches assets on display so agents can confirm they show up in the reply pane.

HTML anchor formatting

Rich-text articles sometimes need raw anchors. Confirm the rendered version shows the destination on hover.

Redirect and forward examples

Short links commonly used for tracking. The reference page exists to confirm the final URL bar after the redirect resolves.

International and accented domains

Customers occasionally include domains with non-ASCII characters. The reference shows expected display for Cyrillic, Greek, full-width, and combining-mark inputs.

Plain-text URL detection

Examples of bare URLs in prose. Confirm the renderer auto-detects them and that punctuation is not absorbed into the link.

Username-style URLs

Some legacy systems include credentials in the URL. The reference shows how the renderer should display them so agents can spot account leaks.

Supported link schemes

Reference renderings for non-HTTP schemes that agents may encounter in tickets (calendar invites, calls, document handlers).

Numeric host examples

Hosts written as IPv4/IPv6 literals. Reference shows expected presentation.

Custom port examples

Internal services and staging environments often use non-standard ports.

Percent-encoded characters

Encoded path/query characters as they appear in tracking links.

Path formatting

Path normalization examples (relative segments, encoded slashes).

Query and anchor formatting

Query strings and fragments commonly used in deep links.

Long URL handling

Reference for how the article view truncates long URLs.

Repeated link behavior

Same destination cited multiple times in one article. Confirm the renderer resolves each consistently.