Dashe Chat adds the hosted Dashe widget to your WordPress website. Use the same\nDashe inbox, team, appearance settings and optional booking calendar you already\nmanage at https:\/\/www.getdashe.com\/.<\/p>\n\n
An active Dashe workspace is required. The plugin is free to install; service\naccess and feature availability are managed separately through Dashe. Installing\nor removing the plugin does not purchase, cancel or change a subscription.<\/p>\n\n
The plugin does not import WordPress users, WooCommerce orders, payment details or\ncustomer accounts. It does not provide single sign-on: you sign in to Dashe\nseparately to manage the workspace and copy its public key. No private API token or\nDashe password is stored in WordPress.<\/p>\n\n
This plugin relies on the Dashe hosted service: https:\/\/www.getdashe.com\/.\nActivation alone makes no Dashe network requests. After an administrator supplies\na key and enables the widget, the browser loads https:\/\/www.getdashe.com\/widget.js\non eligible public pages. If the optional consent gate is enabled, the remote\nwidget is not requested until the site's consent manager grants permission.<\/p>\n\n
The widget connects to Dashe over HTTPS and WebSocket connections to provide chat,\npresence and optional appointment booking. Dashe receives network information,\npage paths\/titles, URL\/referrer context, chat activity and information visitors\nsubmit, including contact and booking details. Configured AI, email, calendar,\nvideo and calling features may involve additional service providers. Microphone\nand camera access require separate visitor actions and browser permission.<\/p>\n\n
The widget uses session storage to resume chats. Returning-browser recognition,\nwhen explicitly enabled here, uses a random identifier in first-party local\nstorage. Disabling recognition does not delete older profiles held in Dashe.\nDisabling or deleting this plugin does not delete hosted conversations, profiles\nor appointments. Contact the workspace administrator to manage those records.<\/p>\n\n
Configure a suitable privacy notice and consent mechanism for your site and\nfeatures. Suggested disclosure text is available in WordPress's Privacy Policy\nGuide. This plugin does not certify legal compliance or provide a consent banner.\nRead the Dashe privacy policy: https:\/\/www.getdashe.com\/privacy\nRead the Dashe terms of service: https:\/\/www.getdashe.com\/terms\nContact support@getdashe.com for support.<\/p>\n\n
SEO is off by default and independent of chat. Connect through Settings > Dashe SEO using a ten-minute code from your Dashe workspace. A public widget key never grants editing access. You can grant metadata editing, supported paragraph editing and article publishing independently, and revoke access locally at any time. Optionally approve image attachment IDs that your business has permission to publish. Deactivation prevents further requests; disconnect\/uninstall preserves published content and operation receipts.<\/p>\n\n
When enabled, public page content and metadata, selected WordPress author\/category names, approved image titles\/alt text\/URLs and publication receipts are exchanged over HTTPS with https:\/\/www.getdashe.com\/. The configured AI provider (OpenAI or Anthropic) processes public content and approved business facts for editorial work. DataForSEO supplies search\/AI observations; optional Google Search Console authorization supplies first-party performance data. No private customer conversations are sent by this connector. See https:\/\/www.getdashe.com\/privacy and https:\/\/www.getdashe.com\/terms before enabling. The hosted service requires an active plan and provider configuration. Rankings are not guaranteed.<\/p>\n\n
Changes to URLs, indexing rules, checkout, prices, inventory, legal pages and theme files are excluded. Unsupported page-builder bodies are protected. Each write checks the current page fingerprint and records an idempotent receipt. An edit made outside Dashe may require review instead of automatic rollback.<\/p>\n\n
SEO editing and publishing require a supported PHP branch meeting Dashe\u2019s documented patch requirements. Dashe checks PHP\/WordPress versions, OS family, server-level session upload progress, and cURL Brotli support\/version over the authenticated SEO connection. No phpinfo or environment secrets are sent. Checks run at connection, on scans and before writes. Old or unverified hosts keep chat and monitoring but cannot receive SEO writes. These checks do not replace host patching or a security audit; vendor backports cannot be automatically verified. See https:\/\/www.getdashe.com\/privacy and https:\/\/www.php.net\/archive\/2026.php .<\/p>\n\n\n
The website must have an allowed domain and an active workspace. A plugin setting\nalone cannot grant access or confirm a working connection. Plugin installation on\nWordPress.com requires a plan that allows plugins.<\/p>\n\n\n
No. It works on ordinary WordPress sites. When WooCommerce is active, the default\nexclusions protect cart, checkout and customer-account pages, including endpoints.\nProduct and shop pages remain eligible. No order or checkout integration is added.<\/p><\/dd>\n
Open Dashe from the settings screen and sign in there. Version 1 connects through\nthe public widget key supplied by your workspace administrator.<\/p><\/dd>\n
The plugin uses WordPress's script enqueue system and does not edit theme files.\nIt works with block and classic themes that render the standard WordPress hooks.\nCheck the widget after changing themes or script-optimization settings.<\/p><\/dd>\n
Enter a URL path per line. \/private excludes that page (with or without a trailing\nslash). \/members\/* excludes \/members and its descendants, but not \/membership.\nInclude a subdirectory if one appears in the website URL. Query strings do not\naffect path matching. Admin, previews, feeds, searches, 404s and password-protected\npages are always excluded. Exclusions apply on page loads, not client-side route\nchanges after a widget has already loaded.<\/p><\/dd>\n
Enable Wait for my consent manager. Configure the manager to set\nwindow.dasheChatConsent = true and dispatch a document event named dashe:consent\nonly after the required visitor permission is granted. Do this on every page\nwhere loading is permitted. Consent granted before the loader runs is supported.\nOn withdrawal, clear the flag and reload with consent denied. The plugin stores\nno consent and cannot undo data already sent by an active chat session.<\/p><\/dd>\n
Check the enabled setting, public key, exclusions, consent manager and caches.\nIn Dashe, check the workspace's allowed domain, access and usage status. Content\nsecurity policies, ad blockers and script-delay tools can also prevent loading.\nUse the real public website, not the WordPress editor preview. Existing Dashe\nsnippets should be removed to avoid conflicting settings.<\/p><\/dd>\n
Deactivate the plugin and clear page caches. Deactivation keeps local settings\nfor reactivation. Deleting the plugin removes its settings from each multisite\nsite, but never deletes hosted Dashe records or cancels billing.<\/p><\/dd>\n\n<\/dl>\n\n\n
Initial release: public-key installation, page exclusions, WooCommerce safeguards,\noptional browser recognition, consent-manager gate and local-settings cleanup.<\/p>","raw_excerpt":"Add Dashe to your website without editing theme code. Connect an existing workspace for live chat, AI assistance and appointment booking.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/392822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=392822"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/getdashe"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=392822"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=392822"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=392822"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=392822"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=392822"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=392822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}