Updated
Your agent now needs to work on customer websites with existing navigation, forms and mobile layouts. Installation settings need to produce the expected interface, and visitors need to understand what happened when a response stops halfway through.
Curiosive can develop embedded support chat widgets for AI product teams serving Sweden, Norway, Denmark and Finland. Start with your existing agent endpoint, its response contract and representative customer pages. The proposed deliverable connects installation, configurable presentation and conversation controls.
Agree the supported settings, defaults and invalid-value behaviour before designing a configuration screen. Model selection, conversation language, panel size, position and launcher appearance have different consequences. Decide which values the customer controls and how a change reaches an installed widget. A preview can be scoped, but its approved values must also be checked on the actual host page.
YouNet, recorded in Canada, is the published interface reference. Its React and Material UI widget loads through one script and mounts on a custom element. Script settings configure the model, language, size, position, button text and image. Responses stream as formatted Markdown; visitors can stop responses or change conversation language. A shadow root helps isolate widget styling from the host page. The reference establishes interface delivery; knowledge retrieval, answer evaluation and helpdesk integrations require separate scope.
Choose representative host pages with real navigation, forms, sticky controls and banners. Scope launcher placement, open-panel dimensions, scrolling and keyboard focus for supported viewports. Shadow-root styling can separate component appearance from surrounding CSS; it provides no security guarantee. Browser policies, loading restrictions and conflicts with other overlays still need their own review on the agreed host environments.
Choosing Stop should visibly stop the response stream and leave the partial answer readable. Whether the underlying request also stops depends on the endpoint’s cancellation contract. A connection failure needs its own explanation and recovery action. Define how partial Markdown stays readable, whether retry replaces or appends to the unfinished answer, and what happens to a submitted question when the request status is uncertain. The endpoint's cancellation and retry behaviour determines which controls the interface can truthfully offer.
Choose whether the widget serves anonymous visitors, signed-in customers or both. Admission, session ownership and account-linked history would be new scope. If history is retained, define what survives closing the panel, a page change or signing out, and who may reopen it. Keep credentials and account permissions in the appropriate backend flow; presentation settings must not become an authority to access private conversations.
Choose the interface languages your team can review and the languages the existing agent supports. Define whether switching language affects future answers, starts another conversation or requests a translation. Existing messages should follow an agreed rule, including partial responses. Specify the language used by retry and error controls. A country selection alone should not determine a visitor's preferred conversation language.
Combine the installation contract, representative host pages and stream events. Use the worksheet to settle decisions before adding configuration screens or retained history.
Embedded support widget discovery worksheet
Proposed acceptance: install an agreed configuration on two representative host pages and compare the model, language, size, placement and button settings with the approved values. Open and close the widget beside navigation, a form and a banner; review keyboard focus and a narrow viewport. An unsupported setting follows the agreed rejection or default rule. Stop the visible response stream, retain its readable partial answer and confirm that late stream events do not silently resume it. Check backend cancellation separately only where the endpoint supports it. Separately interrupt the connection: the failed state must differ from a visitor stop, with an explicit retry action and agreed duplicate-message treatment. Change language and verify the defined effect on existing and subsequent messages. These are proposed release checks, not historical YouNet test results.
Share a host page, current embed and the agent's response contract. Curiosive can deliver the agreed scope remotely from Ankara, Türkiye. Start with one customer installation and its interrupted-conversation behaviour.
That is the intended starting point. We review its stream format, cancellation support, error states and session contract before agreeing the interface scope.
An embed can avoid a page rebuild, subject to the host's script policy and installation access. Review representative customer environments before choosing the installation method.
Only if customers need it. An initial release can use documented embed settings. A dashboard adds decisions about ownership, validation and how changes reach existing installations.
Answer evaluation requires its own approved examples and knowledge scope. We can define that work separately; a clear stream or successful installation does not establish answer correctness.
Persistence can be scoped around session identity, expiry and permitted storage. Agree whether the conversation follows a browser session or a signed-in account before retaining history.
A short note about the product, the timeline and who it is for is enough to start. You will hear back from the engineer who would do the work, not a sales team.
Ankara / Türkiye · Working across European and US time zones