Dashe Chat

Description

Dashe Chat adds the hosted Dashe widget to your WordPress website. Use the same
Dashe inbox, team, appearance settings and optional booking calendar you already
manage at https://www.getdashe.com/.

An active Dashe workspace is required. The plugin is free to install; service
access and feature availability are managed separately through Dashe. Installing
or removing the plugin does not purchase, cancel or change a subscription.

  • Install once and paste your public widget key. No theme edits or script pasting.
  • Enable or disable the widget from Settings > Dashe Chat.
  • Exclude selected paths before the widget loads.
  • Exclude WooCommerce cart, checkout and customer-account pages by default.
  • Keep returning-browser recognition off, or explicitly enable it.
  • Optionally wait for your website’s consent manager before contacting Dashe.
  • Configure each site separately on WordPress multisite.

The plugin does not import WordPress users, WooCommerce orders, payment details or
customer accounts. It does not provide single sign-on: you sign in to Dashe
separately to manage the workspace and copy its public key. No private API token or
Dashe password is stored in WordPress.

External service and data use

This plugin relies on the Dashe hosted service: https://www.getdashe.com/.
Activation alone makes no Dashe network requests. After an administrator supplies
a key and enables the widget, the browser loads https://www.getdashe.com/widget.js
on eligible public pages. If the optional consent gate is enabled, the remote
widget is not requested until the site’s consent manager grants permission.

The widget connects to Dashe over HTTPS and WebSocket connections to provide chat,
presence and optional appointment booking. Dashe receives network information,
page paths/titles, URL/referrer context, chat activity and information visitors
submit, including contact and booking details. Configured AI, email, calendar,
video and calling features may involve additional service providers. Microphone
and camera access require separate visitor actions and browser permission.

The widget uses session storage to resume chats. Returning-browser recognition,
when explicitly enabled here, uses a random identifier in first-party local
storage. Disabling recognition does not delete older profiles held in Dashe.
Disabling or deleting this plugin does not delete hosted conversations, profiles
or appointments. Contact the workspace administrator to manage those records.

Configure a suitable privacy notice and consent mechanism for your site and
features. Suggested disclosure text is available in WordPress’s Privacy Policy
Guide. This plugin does not certify legal compliance or provide a consent banner.
Read the Dashe privacy policy: https://www.getdashe.com/privacy
Read the Dashe terms of service: https://www.getdashe.com/terms
Contact support@getdashe.com for support.

Optional SEO service

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.

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.

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.

PHP host security

SEO editing and publishing require a supported PHP branch meeting Dashe’s 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 .

Installation

  1. Upload the dashe-chat ZIP using Plugins > Add New > Upload Plugin, then activate.
  2. Open Settings > Dashe Chat.
  3. Sign in at https://www.getdashe.com/app and select the intended workspace.
  4. Under Settings > Install, register the website hostname. Your administrator can also do
    this in the Dashe console. The hostname must fit the workspace’s domain limit.
  5. Under Advanced: widget key, copy the public key beginning with pk_live_.
  6. Paste the key into WordPress, select Enable Dashe, review the other options,
    and save. Remove any older Dashe snippet before enabling the plugin.
  7. Clear WordPress, hosting and CDN caches. Visit a public page and use Check
    installation in Dashe. Check a product page and a phone-sized viewport too.

The website must have an allowed domain and an active workspace. A plugin setting
alone cannot grant access or confirm a working connection. Plugin installation on
WordPress.com requires a plan that allows plugins.

FAQ

Does this require WooCommerce?

No. It works on ordinary WordPress sites. When WooCommerce is active, the default
exclusions protect cart, checkout and customer-account pages, including endpoints.
Product and shop pages remain eligible. No order or checkout integration is added.

Can I sign in inside WordPress?

Open Dashe from the settings screen and sign in there. Version 1 connects through
the public widget key supplied by your workspace administrator.

What happens if I change themes?

The plugin uses WordPress’s script enqueue system and does not edit theme files.
It works with block and classic themes that render the standard WordPress hooks.
Check the widget after changing themes or script-optimization settings.

How do path exclusions work?

Enter a URL path per line. /private excludes that page (with or without a trailing
slash). /members/* excludes /members and its descendants, but not /membership.
Include a subdirectory if one appears in the website URL. Query strings do not
affect path matching. Admin, previews, feeds, searches, 404s and password-protected
pages are always excluded. Exclusions apply on page loads, not client-side route
changes after a widget has already loaded.

How do I use a consent manager?

Enable Wait for my consent manager. Configure the manager to set
window.dasheChatConsent = true and dispatch a document event named dashe:consent
only after the required visitor permission is granted. Do this on every page
where loading is permitted. Consent granted before the loader runs is supported.
On withdrawal, clear the flag and reload with consent denied. The plugin stores
no consent and cannot undo data already sent by an active chat session.

Why is the widget missing?

Check the enabled setting, public key, exclusions, consent manager and caches.
In Dashe, check the workspace’s allowed domain, access and usage status. Content
security policies, ad blockers and script-delay tools can also prevent loading.
Use the real public website, not the WordPress editor preview. Existing Dashe
snippets should be removed to avoid conflicting settings.

How do I remove it?

Deactivate the plugin and clear page caches. Deactivation keeps local settings
for reactivation. Deleting the plugin removes its settings from each multisite
site, but never deletes hosted Dashe records or cancels billing.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Dashe Chat” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Dashe Chat” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.1.1

  • Add authenticated PHP host checks, host-update guidance, and a local gate that pauses SEO writes when runtime requirements are unmet. Chat and monitoring stay available.
  • Disclose the limited PHP/WordPress version and security-configuration fields shared with Dashe.

1.1.0

  • Optional, explicitly authorized SEO connector with conditional metadata edits, article publishing and operation receipts. Existing chat installations stay unchanged; SEO stays off until connected.

1.0.0

Initial release: public-key installation, page exclusions, WooCommerce safeguards,
optional browser recognition, consent-manager gate and local-settings cleanup.