---
name: dobrodesk-install
description: Integrate the published DobroDesk web widget or a supported mobile SDK into an application while preserving the documented identity, lifecycle and security boundaries.
---

# DobroDesk integration

Use this skill only for a user-requested DobroDesk integration. The task prompt is the scope for the change. Read the current DobroDesk guide linked in that prompt before editing the repository. The guide is the source of truth for package versions, APIs, platform requirements and verification.

## First inspect the application

- Find the existing DobroDesk widget or SDK integration before adding files or dependencies.
- Reuse the existing client, launcher, host container, customer session and route lifecycle when they already exist.
- Do not install a second widget, create a duplicate client for one application session or add a second launcher.
- Use configuration values only after the user has saved them in DobroDesk. Ask the user to save pending setup changes before using those values. Code installation may be prepared before the integration is published or enabled.
- If a public Integration ID or allowed website origin is missing, obtain it from the published DobroDesk setup. Never guess it. Keep a clearly marked placeholder while waiting.

## Web widget

For a website, follow the current [web widget guide](https://dobrodesk.com/developers/web) and use the exact saved embed snippet or the documented programmatic SDK for the existing application shape. If the site already has a valid single-loader static HTML embed that satisfies the task, preserve it and update only the necessary saved values. Choose the programmatic SDK only when the host needs documented identity, a custom launcher or lifecycle control. Do not rewrite a working embed solely because the SDK guide contains package examples. Keep the widget's customer session and one launcher under one host integration.

If the site uses a Content Security Policy, merge the required DobroDesk sources into the existing policy. Preserve all existing restrictions. Do not use broad wildcards, add unsafe script allowances or remove directives to make the widget load. Check the guide's `script-src`, `frame-src` and `connect-src` requirements together.

For signed customer identity, follow the [secure identity guide](https://dobrodesk.com/developers/identity). Keep signing secrets, support API tokens and backend identity credentials on the server. The browser may receive only the short-lived customer identity result required by the guide. Call the documented logout and destroy lifecycle when the host account ends.

## Mobile SDK

For iOS, Android, Flutter, React Native, NativeScript or Capacitor, use the matching current guide from the [developer documentation](https://dobrodesk.com/developers). Check the [capability matrix](https://dobrodesk.com/developers/capabilities) and [release requirements](https://dobrodesk.com/developers/releases) before selecting a package or version. Use a published version that satisfies the target platform floor. Do not copy an unreleased API from another platform.

Respect the documented login, logout, account-switching, route-remount and session lifecycle. Reuse the documented client and session rather than creating duplicate clients. Keep customer identity credentials in the host backend. Enable push notifications or voice only after explicit user opt-in and only when the capability matrix marks them available for that platform.

## Verification and boundaries

- Run the smallest relevant build, type check or platform verification after the change.
- For the web widget, check loader and frame readiness, launcher behavior and the absence of duplicate widgets. For a mobile SDK, follow its platform guide's initialization, presentation and session lifecycle checks with the host's existing test tools.
- For a delivery test, use an enabled test integration or isolated test workspace and one clearly labeled synthetic message with fictional customer data. Do not create test conversations in a production inbox by default. Report accepted-message or reply evidence only when observed. Leave delivery unverified if no test environment or account access is available.
- Never use a live customer conversation as a test.
- Never approve or send an AI draft or reply to a live customer.
- Never change billing, plan access or permissions as part of an integration task.
- Do not send private exports, customer conversations, workspace data, credentials or secrets to the coding agent. Use only public setup values and files explicitly placed in scope.
- If the guide or saved setup does not provide enough evidence, stop and explain the missing value instead of inventing an API, version, identifier or permission.

Canonical entry points:

- [Developer documentation](https://dobrodesk.com/developers)
- [Web widget](https://dobrodesk.com/developers/web)
- [Secure customer identity](https://dobrodesk.com/developers/identity)
- [Capability matrix](https://dobrodesk.com/developers/capabilities)
- [SDK releases](https://dobrodesk.com/developers/releases)
