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.
Plain links agents can paste directly into replies.
baseline-docsbaseline-resourcesbaseline-http-docsbaseline-helpdesk-articlebaseline-text-matches-hrefWhen the visible label and the destination differ, agents should always paste the destination URL alongside the label.
label-docs-dest-resourceslabel-resources-dest-docslabel-friendly-dest-resourceslabel-userinfo-dest-resourcesExamples of how the same link should render across markdown variants used in agent replies.
md-mismatch-docs-vs-resourcesmd-title-attrmd-reference-stylemd-angle-autolinkmd-bare-with-periodInline 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.
img-md-bannerimg-html-thumbpreview-og-cardpreview-og-with-imageRich-text articles sometimes need raw anchors. Confirm the rendered version shows the destination on hover.
anchor-text-vs-hrefanchor-title-attranchor-data-hrefanchor-target-blank-no-relanchor-svg-wrapanchor-bdo-rtlShort links commonly used for tracking. The reference page exists to confirm the final URL bar after the redirect resolves.
redirect-meta-refreshredirect-js-locationredirect-iframeredirect-302-shaperedirect-shortener-bitlyredirect-shortener-tcoCustomers occasionally include domains with non-ASCII characters. The reference shows expected display for Cyrillic, Greek, full-width, and combining-mark inputs.
intl-cyrillic-ointl-greek-omicronintl-fullwidthintl-zero-widthintl-combining-markintl-rtl-overrideintl-trailing-dotintl-uppercase-hostExamples of bare URLs in prose. Confirm the renderer auto-detects them and that punctuation is not absorbed into the link.
plain-trailing-periodplain-trailing-commaplain-paren-wrapplain-angle-wrapplain-backtick-wrapplain-noschemeSome legacy systems include credentials in the URL. The reference shows how the renderer should display them so agents can spot account leaks.
user-with-passworduser-encoded-atuser-double-encoded-atuser-backslashuser-encoded-backslashuser-port-shapeReference renderings for non-HTTP schemes that agents may encounter in tickets (calendar invites, calls, document handlers).
scheme-http-helpdeskscheme-http-docsscheme-mailtoscheme-telscheme-slackscheme-datascheme-javascriptscheme-fileHosts written as IPv4/IPv6 literals. Reference shows expected presentation.
ip-dottedip-zero-paddedip-hexip-integerip-ipv6ip-ipv6-v4-embedip-ipv6-zoneip-with-portInternal services and staging environments often use non-standard ports.
port-8080port-https-on-80port-http-on-443port-userinfo-shiftEncoded path/query characters as they appear in tracking links.
enc-double-slashenc-mixed-caseenc-encoded-dotenc-scheme-sepenc-encoded-questionPath normalization examples (relative segments, encoded slashes).
path-dotdot-encodedpath-dotdot-double-encodedpath-dot-segmentpath-double-slashpath-backslashQuery strings and fragments commonly used in deep links.
qa-fragment-targetqa-trailing-spaceReference for how the article view truncates long URLs.
Same destination cited multiple times in one article. Confirm the renderer resolves each consistently.
repeat-pair-a-1repeat-pair-a-2repeat-pair-b-1repeat-pair-b-2repeat-same-href-1repeat-same-href-2