Link sharing and link cards | Stand Feature Reference

01

How links appear in a reply

An AI Stand-in can include descriptive Markdown links directly in its explanatory text. When one destination is the clear next step, the Stand-in can also emit a separate card with a title, optional description, and destination host.

The text reply is stored before the card, so the visitor receives context rather than an unexplained call to action. Clicking either the Markdown link or card follows the normalized destination.

Presentation	Use
Markdown link	Keeps a destination inline with the sentence that explains it. A useful URL may be repeated in later prose when the conversation still needs it.
Primary link card	Visually emphasizes one next step after the explanatory reply. Multiple candidate card actions in one AI turn are reduced to the first supported card.

02

URL resolution and validation

Absolute https:// and http:// destinations retain their supported URL.
A root-relative path such as /pricing resolves against the visitor conversation’s website origin.
In a dashboard test conversation without a normal page URL, Stand resolves a relative path against the assigned Site.
Equivalent same-site relative and absolute URLs are canonicalized to the same destination for card deduplication.
Unsupported schemes such as javascript: are dropped. The explanatory text reply still posts even when its proposed card URL is rejected.

03

Card limits and session scope

Stand claims a canonical destination when its first card is appended to the session. A later attempt to create a card for the same effective URL does not add another card, including when one form was relative and the other absolute.

Deduplication applies to the card presentation, not to ordinary prose. The Stand-in can mention or link the same URL again when it remains useful to the answer. Starting a new conversation creates a new card scope.

04

Where destinations come from

Stand-in, Site, or Team instructions can name an approved absolute or site-relative destination.
Attached knowledge can contain relevant links that the AI Stand-in uses when answering.
The current visitor page supplies the base origin used for relative links.
Stand does not require a separate dashboard catalog of link cards; the card is created during the AI turn from the available grounded destination.

05

Availability and prerequisites

Markdown links and AI link cards are available on every plan.
A card requires an AI Stand-in turn; human reps can still send ordinary supported Markdown links in their messages.
The destination must be a valid supported URL after relative resolution.
A meaningful title should describe the destination. Description text is optional.

06

Limits and boundaries

Only one link card is accepted from a single AI response even if several card tool calls are proposed.
The same canonical destination receives at most one card during a conversation.
A card does not verify that the external destination remains available or that its content is safe after the link was created.
Link cards are retained as conversation messages for continuity and History, but their deduplication state ends with the live session.

07

Related features

Visitor messaging and chat controls — The Stand widget gives website visitors a real-time text conversation with a matched rep or AI Stand-in. Visitors can send formatted messages, minimize or resize the window, end a conversation, and start another without leaving the website.
Conversation continuity — Stand restores an active website conversation when the visitor reloads the page or moves around the same site in the same browser. The transcript, responder, conversation language, and session boundary remain intact instead of routing the visitor into a duplicate chat.
Attaching knowledge bases to Stand-ins — An attachment makes an organization knowledge base available for private retrieval by one AI Stand-in. The Stand-in searches attached material when it is relevant and falls back to its instructions when no useful source is found.