Avatars

Avatar sources

• A rep can upload an image from Profile.
• A Stand-in can use generated candidates, select an existing organization avatar, or upload where the appearance flow permits.
• The organization avatar pool allows reuse of stored Stand-in visuals without regenerating the same concept.
• A fallback mascot appears when no usable avatar has been configured.

Static-image processing

Common static formats enter the crop workflow, are normalized to a square presentation, resized, and stored in an optimized web format. The preview shows the area visitors will see before the upload is committed.

Animated GIF and WebP rules

• Valid animated GIF and WebP avatars keep their animation and original bytes.
• They must be square, between 64×64 and 256×256 pixels, at most 256 KiB, at most 300 frames, and at most 10 seconds per loop. A 128×128 file below 100 KiB is recommended for normal widget use.
• Each animation frame must last at least 30 milliseconds.
• Animated images bypass cropping and optimization, so the confirmation preview is exactly what visitors download.
• A single-frame GIF uses the static-image path. WebP files with an animation container are validated as animations even when they contain one frame; ordinary non-animated WebP uses the static path.

Prepare an animation

• Animated avatar preparation and command-line examplesOptimize a source file before uploading; Stand preserves accepted animations without resizing or re-encoding them.

Set or change an avatar

• Open the rep Profile or the Stand-in’s Looks tab.
• Choose an upload or generated candidate.
• For a static image, position the crop and confirm it.
• For an animated image, review dimensions, file size, frame count, and duration in the confirmation dialog.
• Save the profile or Stand-in changes and verify the visitor-facing preview.

Reuse and safety boundaries

• Rep and Stand-in avatar choices are separate; updating one does not silently replace the other.
• Malformed, oversized, undersized, non-square, excessively fast, or structurally unsafe animations are rejected with guidance.
• Generated candidates can be reported from the appearance workflow; reporting does not automatically select a replacement.
• An active circle lapel-pin policy can be used as a Stand-in avatar where that option is enabled.

Example

The screen below shows the feature in its normal Stand context. Labels and surrounding controls may vary with account state and plan.

Related features

• Chat identity — Chat identity tells visitors who is answering and whether that responder is a person or an AI Stand-in, while preserving the organization’s chosen brand presentation.
• Lapel pins and team pin policy — Lapel pins add a compact badge or brand mark to responder identity, with an owner-controlled team policy that can override individual choices.
• Stand-in management and version history — The AI Stand-ins list is the control surface for creating, opening, cloning, enabling, disabling, and deleting Stand-ins. When a Stand-in already has conversation history, replacement-on-edit preserves the old configuration as part of those historical records.