Building Interactive Experiences with Widgets

Sometimes a Peer response needs more than text. A sales summary is easier to read as a chart, an approval is easier to review as a card, and a multi-step intake is easier to complete as a guided form.

Widgets give Peers and Flows a way to present structured, interactive content inside the conversation.

What widgets are

Widgets are reusable visual experiences that can appear in Peer conversations, Flows, and Webchat. They help users understand, review, or act on information without leaving the Cognipeer experience.

Common widget uses include:

• KPI summaries.
• Charts and trend views.
• Tables and lists.
• Review cards.
• Guided forms.
• Status summaries.
• Action prompts.

Why widgets matter

Text is flexible, but it can become hard to scan when the response includes numbers, options, records, or decisions. Widgets make that information easier to use.

They help teams:

• Make complex results easier to understand.
• Keep repeated outputs consistent.
• Give users clearer next steps.
• Reduce copy-and-paste between systems.
• Present business context in a more professional format.

Good widget use cases

Sales performance

A Peer can summarize revenue, pipeline movement, and top risks with a short explanation plus a chart or metric card.

Support triage

A Flow can show customer details, ticket priority, and suggested next action in a review card before an agent approves the response.

Approval workflows

An approval widget can show the requested action, risk level, owner, and business context before the approver chooses approve or reject.

Guided intake

A form widget can collect structured information before a Peer continues, which is cleaner than asking the user to type every detail in a message.

Planning a widget experience

Before enabling or requesting a widget, answer these questions:

• Who will use it?
• What decision or task should it support?
• What information must be visible?
• What information should be hidden?
• What should happen when data is missing?
• Which Peer or Flow owns the experience?
• Who will maintain it over time?

The best widgets are narrow and task-focused. A widget that tries to show everything usually becomes harder to use than a clear text answer.

Where widgets fit in Cognipeer

Peer conversations

Use widgets when a Peer needs to present a result that users will review repeatedly, such as a customer summary or performance snapshot.

Flows

Use widgets in Flows when a step needs to show structured context, collect input, or make an approval easier to evaluate.

Webchat

Use widgets in Webchat when the embedded experience should feel guided and consistent for customers or external users.

Admin guidance

Admins should review widget access and usage regularly.

Check:

• Which widgets are enabled.
• Which Peers and Flows use each widget.
• Whether the widget shows sensitive data.
• Whether the user experience is clear on desktop and mobile.
• Whether the owning team still maintains it.

Rollout checklist

Before sharing a widget broadly:

1. Preview it with realistic data.
2. Test empty and partial data states.
3. Confirm the labels are understandable.
4. Check permissions for sensitive information.
5. Test the Peer or Flow path that displays it.
6. Ask a real user to review whether it helps them act faster.

When to use the Developer Hub

Use the Developer Hub for custom widget development, component code, data schemas, validation rules, embed behavior, and SDK details.

Product users and admins should start with the Widgets guide.