Rolling out Harriet with Endpoint AI

A practical sequence for enabling Harriet across chat platforms, embeds, and optionally Endpoint AI–managed desktops.

Endpoint AI complements Harriet’s normal rollout: it helps you deploy consistent endpoint configuration and govern which skills and connectors reach users after review.

Suggested rollout order

Verify identity — confirm SSO or account linking behaves as expected for pilot users.
Connect core integrations — directory and primary HRIS before advanced automations.
Upload baseline knowledge — employee handbook, IT policies, and FAQs Harriet should cite.
Pilot channel — a small Slack or Teams channel before company-wide announcement.
Train champions — short guide on how to phrase questions and when to open tickets.
Endpoint AI (if licensed) — send enrollment invites so pilot users open the secret link, install Harriet Desktop from that page when your tenant publishes builds, then link the device; use Claude Desktop only where your organization standardizes on it (see Enrol a device — Harriet Desktop first). Align review queue ownership so new connectors and package skills are approved before broad assignment.

Communication

Set expectations: Harriet answers from your documents and connected systems, not the open internet.
Provide a fallback path (ticket or email) for sensitive or novel requests.

After launch

Review ticket themes weekly for the first month.
Iterate on document coverage where questions repeat.
For Endpoint AI: monitor review queue throughput so authors are not blocked waiting for approvals.