AI chat
Usage
Overview
The AI chat component provides a dedicated, multi-turn interface for insurance professionals to interact with our underlying AI model. It is engineered to facilitate complex inquiries and draft content while maintaining context across a session.
When to use
- Agentic experiences: Use when a workflow involves multiple conversational steps that rely on maintaining context throughout a session to facilitate reasoning across turns (for example, multi-step analysis).
- Natural language interaction: Use when users need to ask follow-up questions, pursue multiple lines of inquiry, or initiate actions across the solution using conversational prompts.
When not to use
- Single-turn interactions: For single-use or pre-made prompts that do not require follow-up, embed the output directly in the page instead of opening a chat.
- Changes to the page: Actions that make changes to the main page, such as filling out forms, refreshing content, or embedding visuals, generally do not need to initiate chat.
Formatting
Anatomy

The AI chat component consists of the following elements:
- AI assistant header: Displays the specific feature or product name.
- “Start new chat” button: A secondary action button that clears the current conversation history and initiates a fresh session. Guidewire recommends implementing a confirmation step for this action to prevent accidental data loss.
- User message: A right-aligned container for the user's input.
- AI response: A left-aligned text area for displaying the AI's output.
- Utility actions: Functional icons displayed below the AI response or user request (for example, Copy and Retry).
- Prompt input: A text area for user queries. This field includes placeholder text and supports multi-line input for longer prompts.
- Send button: Submits the message to the AI model.
Message actions
Utility actions enable users to interact with message history. The available actions differ depending on whether the message is from the user or the AI.

AI responses include Copy and Retry actions.

User prompts include Copy and Re-run actions.
Placement
The AI chat component is designed to be flexible and can be placed within various UI patterns. Recommended implementations include: drawer, full-page interface, and embedded.
Note: The AI chat component does not include these containers. Developers must implement the surrounding UI pattern (such as a modal or drawer) separately.




Behaviors
States

When the AI is generating a response, a status indicator appears within the chat conversation.

When an error occurs, an inline notification appears within the chat conversation.
Out-of-scope prompts
The prompt input remains active at all times to ensure the interface does not appear broken. If a user enters a query that falls outside the assistant's specific knowledge or capabilities:
-
The assistant provides a standard response indicating it cannot help with that specific request.
-
The assistant automatically displays a suggestions list as follow-up buttons to guide the user back to supported workflows.
You can configure the component to re-display the initial list of pre-defined suggestions after a task is completed, rather than generating dynamic AI follow-up questions.
Content
General writing guidelines
- En todos los aspectos del diseño de las interfaces de productos de Guidewire, utilice mayúsculas como se usan en las oraciones. No use mayúsculas en todas las palabras.
- Use verbos en tiempo presente y voz activa en la mayoría de las situaciones.
- Use contracciones comunes para darle al texto un tono más natural e informal (pauta correspondiente al inglés).
- Use un lenguaje sencillo. Evite la jerga innecesaria y el lenguaje complejo.
- Las palabras y las oraciones deben ser breves.
AI-specific guidelines
- Non-human persona: Don't attribute human qualities, gender, or personal names to the assistant. Avoid verbs that imply cognition or agency.
- Status indicators: When the system is working, use approved feedback loops like "Processing..." or "Just a moment..."
- Transparency: Clearly identify the AI chat assistant as an automated system. Establishing this boundary sets the right user expectations and maintains trust.
- Brevity: Focus on efficiency. Provide only the information required to complete the user's goal, avoiding unnecessary filler or excessive detail.
Accessibility
The AI chat component represents a complex interactive region used to perform conversational actions. It includes input fields, dynamic content areas, and action buttons.
This component is designed to meet WCAG 2.1 AA accessibility guidelines. The contrast ratio of textual elements against their background is above 4.5:1. Non-textual content that conveys meaning and keyboard focus indicators have a contrast ratio of at least 3:1 with their adjacent colors.
However, changes made by the content author or the specific implementation context can affect accessibility conformance.
Follow the guidance below and refer to the WAI-ARIA Authoring Practices when using this component in your applications:
- Labels: Ensure the prompt input field has an accessible label (for example,
aria-label="Type your message"). Action buttons represented by icons (like Copy or Retry) must have descriptivearia-labelattributes. - Focus management: When the chat opens, focus must move immediately to the chat container or input field. When a message is sent, focus must remain in the input field. When closed, focus must return to the triggering element.
- Dynamic content: The chat uses ARIA live regions to announce incoming AI responses to screen readers. Ensure these regions are not obstructed by custom implementations.
- Keyboard navigation: All chat functions must be operable through keyboard only, including typing, sending, navigating messages, opening menus, and uploading files.