What it does
Configure a support widget with your own site key, accent color and launcher label, and embed it on your own external website with a single script tag — every submitted ticket becomes a task in your workspace, complete with a customer-visible thread.
Who needs it
Any company that wants a support inbox on their own site without standing up separate helpdesk software — the same widget IterDone itself uses on its own site.
Why use it
Tickets land exactly where the rest of your work already lives, visitors can attach a screenshot of the page they're stuck on without a single extra step, and the widget's look matches your brand instead of a generic default.
How it works
Admin > Support Sites turns this workspace into the support system for any website you run — separate from IterDone's own use of the same widget on its own Support page. Register a site, and visitors to your site get a floating support widget whose entire UI is hosted here; every ticket they submit lands as a task in the list you chose, with a customer-visible conversation thread attached.
Registering a site asks for:
- Site name — a label for the registration.
- Tickets go to list — which list new tickets are created in.
- Allowed origins — comma-separated origins allowed to embed the widget; anything else is refused.
- Widget title — the text shown in the widget's header (default: "Need help? Want a feature? Let us know!").
- Launcher label — the text on the floating button (default: "I Need...").
- Accent — the widget's accent color.
- Require visitor email — whether a visitor must give an email before submitting a ticket.
- Ticket priority — the priority assigned to every ticket this widget creates.
Embedding it is one line, pasted before </body>: <script src=".../support/widget.js" data-site-key="pksite_…" async></script>. The script also accepts optional overrides right on the tag — data-accent, data-label, and data-position ("right", "left", or "dock" into a matching slot on your page) — without touching the admin-configured defaults.
A visitor can attach a screenshot of the page they're on directly from the widget; it's captured client-side and attached to the ticket, so you see exactly what they saw. If your backend can vouch for who a visitor is, call TaskSupport.identify({ email, name, externalId, exp, sig }) with a signature computed from the site's identity secret to attach their tickets to a known identity instead of an anonymous one.