- Docs
- Guides
Announcements: the “What’s new” widget
Announcements tell your visitors what’s new — new features, fixes, offers or opening hours — in a “What’s new” tab in the messenger, behind your own “What’s new” button anywhere on your site or app, by email to people who subscribe and, if you switch it on, on a public changelog page with an RSS feed. Visitors react with an emoji and can reply: the reply starts a chat in your inbox. Announcements are included with Starter, Pro, Lifetime and Reseller accounts.
Write a post
Go to Engage → News in the left bar and click New post (or New → News post). Workspace admins and the owner can write posts; every teammate can read them and see their numbers.
- Text: the same editor as help-center articles — headings, lists, links, callouts and images (paste or drop them). Scripts and embeds are removed when you save.
- Cover picture (optional): shown at the top of the post, on its card and in the email. 1200×630 works best.
- Video link (optional): a YouTube, Vimeo or Loom link plays inside the post. YouTube plays from youtube-nocookie.com and Vimeo with “do not track”. A YouTube post without a cover picture uses the video’s thumbnail.
- Button (optional): a label and a link, e.g. “Try it now”.
- Labels: coloured tags such as New, Improvement, Fix and Announcement. Rename, recolour or add your own (up to 12) under Widget & install → Labels; visitors see them as you write them.
Publish, schedule and hide
- Draft — only your team sees it. Publish now — visitors see it from their next page view. Schedule — it goes live at the time you pick (in the workspace’s time zone).
- Hide after (optional) — for offers and events: the post disappears on its own.
- Pin to the top keeps a post first in the list. Otherwise the newest is first.
- Show to — everyone, new or returning visitors, people you don’t have an email for yet, leads, or logged-in users of your site (identified with the JavaScript API).
- Only if… (optional) — conditions on top of “Show to”: custom attributes such as
plan is trialorseats ≥ 5, contact details, visits and tags (see Targeting with attributes). Visitors who don’t match never see the post, its pop-up or its unread badge. Included with Starter, Pro, Lifetime and Reseller accounts. A post with conditions stays in the messenger: it isn’t emailed to subscribers or shown on the public changelog. - Pop up once — a new post shows a card above the chat button, one time, to visitors who haven’t seen it, for 14 days.
- Email it to subscribers — see Email subscribers.
To take a post down, choose Unpublish in the list (it becomes a draft) or delete it.
In the messenger
Once a post is published, the messenger gets a What’s new tab next to Home and Messages, with the number of unread posts on it, and the newest post appears as a card on its Home screen. Both can be switched off under Widget & install, and you can rename “What’s new” — left empty, visitors see it in their own language.
A post counts as unread until the visitor opens the posts. Posts older than 60 days never count as unread, so a new visitor isn’t told that last year’s posts are new.
Your own “What’s new” button
Add data-talkingdot-news to any button or link on a page where the messenger is installed — a menu item, a bell icon, a footer link:
<button type="button" data-talkingdot-news>What’s new</button>
It gets a small red badge with the number of unread posts, and a click opens the posts in a popover under the button or a sidebar that slides in from the right edge (choose under Widget & install → Opens as). One button can differ from the rest: data-talkingdot-news="sidebar" or ="popover". On phones the posts always open full screen.
- Buttons you can’t edit: enter a CSS selector such as
#nav-updatesunder More buttons by CSS selector. - Buttons added later (single-page apps) are picked up on their own.
- No place for a button? Switch on the floating “What’s new” button: a small pill in the bottom corner opposite the chat button.
- Announcements without chat: add
data-launcher="hidden"to the messenger’s script tag to hide the chat button on that page. “Reply” on a post still opens a chat.
From your own code
TalkingDot('showNews'); // open the posts (right-edge panel)
TalkingDot('showNewsPost', 12); // open one post
TalkingDot('hideNews'); // close the panel
TalkingDot('showSpace', 'news'); // open the messenger on its What’s new tab
TalkingDot('onNewsCountChange', function (count) {
// the number of unread posts — show it on a badge of your own
});
All commands are listed in the JavaScript API, with the Google Analytics events for announcements.
Reactions and replies
- Reactions: 👍 ❤️ 🎉 😕 under each post — one per visitor, which they can change or take back. You see the counts in the posts list and the editor.
- Reply: starts a normal conversation in your inbox. The conversation shows “The visitor replied to the announcement …” with a link to the post, and the post counts its replies.
Both can be switched off under Widget & install → What visitors can do.
Email subscribers
- Visitors subscribe with Get updates by email at the end of the posts. They get a confirmation email first and are only added when they click its button (double opt-in), so only people who asked receive your posts.
- A post with Email it to subscribers is emailed once, when it goes live — straight away, or at its scheduled time. Editing it later doesn’t send it again, and people who subscribe afterwards don’t get older posts.
- Emails go out in each subscriber’s language and your messenger’s colour, in batches of 50 a minute. They are sent through your own mail server when your plan includes it and you set one up.
- Every email has an unsubscribe link. Email subscribers lists everyone (subscribed, not confirmed yet, unsubscribed); you can remove an address or export the list as CSV.
Public changelog
Your posts can also have a public changelog page in your help center: a page search engines can find, with an RSS feed for people who follow updates in a feed reader. It is off until you switch it on — posts are written for the messenger first, so you decide when they go public. The public changelog is included with Starter, Pro, Lifetime and Reseller accounts.
- Switch it on under Engage → News → Widget & install → Public changelog; the page’s address and its RSS feed are shown there once it is live. Your help center must be on (Help center → Settings).
- The page —
/help/your-help-center/changelog— lists the posts, pinned first and then newest, with their labels, dates, cover pictures, the whole text and the button, 10 to a page. Visitors can show one label at a time, and every post has a page of its own, where its YouTube or Vimeo video plays (a Loom video is a link). - Which posts: only published posts shown to Everyone. Drafts, scheduled posts (until their time), posts past their “Hide after” date and posts for any other audience — new or returning visitors, leads, logged-in users… — stay in the messenger.
- RSS feed:
/help/your-help-center/changelog/feed.xmlhas the newest 20 posts with their full text and cover picture. The changelog pages announce it, so feed readers find it from the page’s address too. - Links to it: a Changelog link at the top of your help center, and a small “All updates →” link under the posts in the messenger.
- Search engines: each page has its own title, description and structured data (Blog and BlogPosting), and follows your help center’s Let search engines index it setting. A list filtered by one label is never indexed.
- Your look: the changelog uses your help center’s logo, colour, dark mode and address.
Numbers
For each post: read by (people who opened it, each counted once), times opened, button clicks, reactions, replies and how many subscribers it was emailed to.
Privacy
Reactions and “read” marks belong to the visitor’s contact and are deleted with it — also when anonymous visitors are cleaned up after 30 days. Deleting a workspace deletes its posts and subscribers. Videos play from the providers’ privacy-friendly players. If you email subscribers, you are the sender: mention it in your privacy policy.
What it doesn’t do (yet)
- A post is shown as written — there are no per-language versions of a post. The messenger’s own texts (“What’s new”, “Reply”, “Get updates by email”) are translated.