The SHL import now supports publication websites and notes, allowing more complete data to be brought in during import.
Draft emailSHL import now supports publication websites and notes
The SHL import now accepts two additional fields: **publication website** and **note**.
- **Publication website:** When included, the platform uses the domain to fill in domain authority data and consolidate duplicate publication entries that share the same website, even if they were imported under different names.
- **Note:** Notes are stored per list and surface in the journalist briefing panel when composing outreach, so any context you've recorded about a journalist is visible at the point of writing.
Both fields are optional. If your existing SHL files don't include them, nothing changes. To use them, add the relevant columns to your import file before uploading.
When importing journalists via the SHL import, customers can now also include a publication website and a note for each journalist. The publication website helps consolidate duplicate publication entries, and the note is stored per list and surfaces in the journalist briefing view when composing outreach.
Why we built it
The publication website field was added so the system can fill in domain authority data and consolidate publications that are written with different names but share the same website. The note field was added as a practical convenience so that context about a journalist (stored per list) also appears in the journalist briefing, tying list-level notes into the outreach workflow.
Use cases
A customer uploads a journalist list with publication websites included, allowing the platform to automatically consolidate duplicate publication entries that share the same domain.
A customer uploads a journalist list with notes (e.g. context or facts about each journalist), and those notes then appear in the journalist briefing panel when crafting outreach, giving the sender useful context at the point of writing.
The two things that we added is a note and a publication website. We want the publication website because we want to fill in the domain authority if we can. Also, we will be using the publication website to consolidate publications because if we have two publications written with different names but they have the same website, that would be our opportunity to just consolidate them.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·1d ago
journalist.salutation merge tag
A new generic `journalist.salutation` merge tag has been added to correctly handle salutations in languages where they are complex or variable.
A new `journalist.salutation` merge tag is now available in your templates. Unlike a plain first-name tag, this one generates a complete, language-appropriate salutation for each journalist — so you drop it in without adding 'Hi' in front of it.
What it produces depends on the journalist's language:
- **English (or unknown language):** 'Hi [preferred first name]'
- **German:** an informal salutation, since a correct formal one requires gender data we may not have
- **Slavic languages (e.g. Czech):** a generic formal salutation, because the name itself changes grammatically and cannot be used directly
- **Czech specifically:** a per-journalist salutation where a generic form is grammatically impossible
If you run outreach across multiple regions — or have previously worked around salutation issues by maintaining separate templates per market — this tag is worth switching to. You'll find it in the merge tag picker alongside the existing journalist fields.
A new `journalist.salutation` merge tag is available that automatically generates a correct, language-appropriate salutation for each journalist. When you use this tag in a template, you don't add a 'Hi' in front of it — the full salutation snippet is already included. For English journalists it prefills as 'Hi [preferred first name]', but for languages where that structure doesn't work (like Slavic or German), it generates the appropriate formal or informal salutation instead.
Why we built it
The team built this because templating salutations the English way (e.g., 'Hi [first name]') breaks in many other languages where the name itself changes grammatically based on context, or where generic salutations are not possible at all. A specific trigger was a client (JLR) operating across multiple regions, including markets like Czech Republic where generic salutations simply cannot be constructed and a per-person salutation is required — otherwise open and response rates would suffer.
Use cases
Sending journalist outreach emails in Czech, where a generic salutation is grammatically impossible and the salutation must be set on a per-journalist basis.
Sending outreach in German, where a formal salutation requires knowing the journalist's gender, so the tag instead pre-fills an informal salutation similar to the English style.
Sending outreach in Slavic languages, where the journalist's name cannot be used directly in the salutation, so a generic formal salutation is inserted automatically.
Multi-region PR teams (e.g., JLR) running campaigns across countries with very different salutation conventions, using a single merge tag that adapts per journalist.
It is actually language aware and pre fills to something. So if you have an English language journalist or we don't have the language that pre fills this as hi first name or in particular hi preferred first name in other languages it does other things. For example, in Slavic languages you cannot use the name, so it does a generic formal salutation... if you use this one you don't have to put a hi in front of it because whatever is in the salutation already incorporates the full snippet that you would want to use here.
Flagged uncertain
Possible duplicate of announcements-v51-personalize-at-scale: The journalist.salutation merge tag is related to personalization at scale, and the 'Announcements | v5.1 Personalize at Scale' entry could potentially include this feature. However, there is also a 'journalist-preferred-name-field' entry that relates to journalist-specific fields, and 'templates-in-inbox-with-merge-tags' relates to merge tags. Without knowing the exact contents of these entries, it is uncertain whether the journalist.salutation merge tag is already captured. The candidate is specific enough (a named merge tag for salutations) that it may be a distinct new feature not yet in the registry.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·1d ago
Web Resources (Admin Only)
A new web resources feature has been introduced, available to admin users only.
Draft emailNew: add a URL as a resource so Ivy stays current automatically
Admins can now create **web resources** in MVPR. Instead of uploading a file, you point Ivy at a URL — a company newsroom, blog, or events page — and Ivy reads the page, extracts the content, and refreshes it once a week. No manual re-uploads needed. Once an admin creates a web resource, all client users can see and use it.
A few ways teams are already putting this to use:
- Keeping a company blog or newsroom in Ivy's knowledge base so it always reflects the latest content
- Tracking events pages to catch speaker applications or calls for nominations as they open
- Checking publication sites to see whether they accept thought leadership or offer executive profile opportunities
Web resource creation is limited to admins for now. If you have questions about setting one up, reach out to the team.
Web Resources let you point Ivy at a URL (like a company blog or newsroom) instead of manually uploading files. Ivy reads the page and any sub-pages you specify, extracts the content, and refreshes automatically once a week — so customers always have up-to-date information in their resources without having to re-upload anything. Currently only admins can create web resources, but once created, clients can see and use them.
Why we built it
Two reasons: first, clients were asking for a way to keep dynamic content like websites and newsrooms in Ivy's knowledge base without constant manual uploads. Second, and more importantly for the team, it is a proof-of-concept to validate a critical piece of underlying technology they want to use in media monitoring — reading content directly from publication websites.
Use cases
Adding a company's blog or newsroom as a resource so Ivy always has current content without manual re-uploads
Tracking events pages to detect when speaker opportunities open or calls for nominations are published
Checking publication websites to determine whether they accept thought leadership pieces or offer executive profile interviews
Potentially reading a Notion knowledge hub to keep internal knowledge accessible to Ivy
Because Ivy is not allowed on the Internet, so that we are in control about everything that Ivy knows. Therefore, everything needs to feed from the resources, which then can sometimes get tedious... So clients asked if they can have like their website or their newsroom in the resources, like something that is more or less curated by them, but like something where they don't have to update it all of the time. And this is what web resources are supposed to solve.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·8d ago
Standalone coverage page
Coverage now has its own standalone page, making it easier to view and manage coverage independently.
Draft emailCoverage has its own page in the dashboard
Coverage is now on a dedicated sub-page under the dashboard, rather than sitting directly on the main screen. You can get to everything you could before — recorded coverage, clips, reporting — just from a focused home of its own.
This is the first step toward something more useful: connecting media monitoring directly to coverage recording. The longer-term goal is that when monitoring picks up a mention, it gets automatically screened, verified, and logged as a proper coverage entry on this page — without manual copy-paste. For now, it is a cleaner place to manage what you have recorded. More to follow as that workflow takes shape.
Coverage now lives on its own dedicated sub-page under the dashboard, rather than being listed directly on the main dashboard. This gives customers a focused, dedicated place to view and manage all their media coverage.
Why we built it
The team needed a home for a new 'Coverage Ivy' AI assistant they are building. The longer-term vision is to use this page to connect media monitoring with coverage recording — so that when media monitoring finds coverage, it can be automatically screened, verified, and recorded as proper coverage entries on this page. It also reflects a broader dashboard direction of having teaser sections that link through to detail pages, rather than surfacing everything on one screen.
Use cases
Viewing all recorded media coverage in one dedicated place instead of scrolling through a crowded dashboard.
Future: automatically recording organic or pitch-driven coverage found via media monitoring, with AI pre-screening to verify relevance and link it to the right thread.
We added a sub page under the dashboard which is the coverage page. Currently it is very, very boring because we just took the coverage report and put that onto their own page. The reasoning why we are doing this is because we have a coverage ivy which really can't do much as of today. But we want this ivy and we needed a home for it.
Flagged uncertain
Possible duplicate of shareable-pages-v11-all-the-pages: The candidate describes a standalone coverage page, which could relate to 'Shareable pages | v1.1 All the pages' or 'coverage-audience-and-opportunity-tier-updates'. However, neither entry clearly describes a dedicated standalone coverage page as a distinct feature. The match is not confident enough to call it a duplicate, but there is enough overlap to warrant uncertainty.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·8d ago
Expanded notifications
More notification types have been added to keep you better informed about activity within the platform.
Draft emailNew notifications: mail bounces and press page visits
Two new notification types are now available in MVPR: mail bounce alerts and press page visit events. You can receive either via email or through a connected Slack channel.
Here is what that looks like in practice:
- **Mail bounce notifications** fire when a sent email bounces, with a direct link to the relevant thread
- **Press page visit notifications** trigger when a journalist visits or downloads something from your press page
- Both types can be routed to a shared Slack channel, so your whole team sees journalist engagement as it happens
If you already have a Slack channel connected, these notification types are available to enable now. If you are using email notifications, the same types apply there too. Head to your notification settings to configure which events you want and where you want to receive them.
Customers can now receive notifications for mail bounces and press page visits (e.g. when a journalist visits or downloads from the press page) either via email or through a connected Slack channel, giving them more ways to stay informed about key platform activity.
Why we built it
The team wanted to give customers flexible transport options for notifications — so whether someone prefers email alerts or Slack messages, they can receive the same notification types in whichever channel suits them best.
Use cases
Getting an email notification when a sent email bounces, with a direct link to the relevant thread
Receiving a Slack or email notification when a journalist visits or downloads something from the press page
Funneling press page visit events into a company Slack channel so the team is immediately aware of journalist engagement
The new notifications are the mail bounce and press page visit. So mailbounce is essentially the Slack notification we get when a mail bounces — you can now get them either via your connected Slack channel if you want to, or you can get them as an email.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·8d ago
Scheduled action frequency control
You can now control how often a scheduled action runs, giving you more flexibility over automation timing.
Draft emailNew: Set a run limit on scheduled actions
Scheduled actions now support frequency control. Instead of choosing between running once or running forever, you can set an action to stop automatically after a defined number of runs.
This is useful for any automation tied to a fixed campaign window. For example:
- Schedule a coverage check to run every Monday and Tuesday for 20 iterations (10 weeks), then stop on its own
- No manual cancellation needed, no wasted tokens, no clutter on your board
To use it, open a scheduled action and set the maximum number of runs alongside your existing day and time settings. Once the limit is reached, the action stops without any further input from you.
You can now set a scheduled action to run a specific number of times before it automatically stops, rather than having to choose between running once or recurring forever. This means automations like coverage checking can be set to run on certain days for a fixed number of occurrences (e.g. 20 times = 10 weeks) and then stop on their own.
Why we built it
Users were creating recurring scheduled actions (e.g. for coverage checking) but then had to remember to manually cancel them later. This added friction, wasted tokens, and cluttered the board. The team built frequency control to let automations self-terminate after a defined number of runs.
Use cases
Coverage checking scheduled to run on Mondays and Tuesdays for 20 iterations (10 weeks), then automatically stop without manual cancellation.
Any recurring action that should run for a limited campaign period rather than indefinitely.
Now you can say actually this action should not be recurring forever. It should be recurring for a few times and then the rest just stays the same... you can now say maybe it should run on Monday, on Tuesdays, but it should only run for 20 times. So that's 10 weeks. And then it would immediately stop afterwards and not burn tokens, not annoy you, not clutter the board.
Flagged uncertain
Possible duplicate of ivy-scheduled-actions: The candidate describes 'frequency control' for scheduled actions, which could be a sub-feature or enhancement of the existing 'Ivy Scheduled Actions' entry. It's unclear whether this frequency control was part of the original scheduled actions release or is a new addition. The overlap is significant enough to warrant caution, but the candidate may represent a distinct new capability added on top of the base scheduled actions feature.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·8d ago
Task board search bar
Task boards now have a search bar, available on both company and agency boards, making it easier to find specific tasks.
Draft emailTask boards now have a search bar
You can now search across your task boards. Type any word from a task's name or description and the board will filter down to matching results instantly, no scrolling required.
The search bar is available on both company and agency boards, so whether you remember one word from a task title or a fragment of its description, you can find it without hunting through the board manually.
Task boards now have a search bar so users can quickly find a specific task by typing a word from its name or description, without having to scroll through the entire board. It's available on both company and agency boards.
Why we built it
The team built this so that users who can't remember exactly where a task is, but know a word in it, can find it quickly rather than hunting through the board manually.
Use cases
Finding a specific task when you only remember one word from its name or description
Searching across both company-level and agency-level task boards
if you have this one task that you don't remember exactly where it is, but you know, like one word in it, you can find it with the search bar.
Flagged uncertain
Possible duplicate of task-group-filter-on-company-task-board: The candidate describes a search bar added to task boards (company and agency). The existing entry 'task-group-filter-on-company-task-board' is related to task board functionality but specifically covers a filter feature on the company task board, not a search bar. There is also 'ivy-task-management-and-platform-improvements' which could potentially bundle this change. The candidate feature is distinct enough (search bar vs. group filter) to likely be new, but there's enough overlap in the domain to warrant uncertainty. Most likely this is a new entry.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·8d ago
Company ownership transfer
Company owners can now transfer ownership of a company to another user, useful if you created the company on someone else's behalf.
Draft emailYou can now transfer company ownership to another user
Company owners can now transfer ownership of a company account to another user. This is useful when you created an account on someone else's behalf and need to hand it off to the right person later.
When you transfer ownership:
- The new owner gains full ownership rights, including the ability to manage billing settings
- The previous owner becomes a regular member and stays on the account
Two common situations this covers: an agency or consultant who set up a company for a client and now needs to pass control to that client, and companies where the person who originally signed up is different from the person who handles billing.
To transfer ownership, go to your company settings and find the ownership section. From there you can select any existing member as the new owner.
Company owners can now transfer ownership of their company account to another user. The new owner gains full ownership rights (including the ability to change billing settings), while the previous owner becomes a regular member and stays on the account.
Why we built it
The team built this to handle situations where they set up companies on behalf of clients and need to hand off ownership to the right person later. It also solves the case where the person who pays the bills is different from the person who originally signed up.
Use cases
An agency or consultant who creates a company account on a client's behalf can later transfer ownership to the client.
A company where the accounts/billing department person is different from the person who signed up — ownership can be transferred to the billing person so they can manage payment settings.
It kind of helps us for a situation where we need to set up someone. And basically this makes us the owner of all of the companies. Now we can hand them off to whoever should be in charge later on.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·8d ago
Clickable Ivy policy links
When Ivy reads out a policy, you can now click on it to jump directly into editing that policy.
Draft emailIvy policy references are now clickable
When Ivy mentions a policy in a conversation, that policy name is now underlined and linked. Clicking it takes you directly to the policy so you can view or edit it without searching manually.
This is particularly useful when auditing Ivy's behaviour. If a response came out differently than expected, you can now see exactly which policy was applied and jump straight into it.
**What you can do now:**
- Click any policy name in an Ivy response to open that policy immediately
- Audit why Ivy made a particular decision by reviewing the linked policy's contents
- Edit a policy on the spot after seeing it referenced in context
When Ivy mentions a policy during a conversation, that policy name is now underlined and clickable, taking you directly to that policy so you can view or edit it.
Why we built it
To make it immediately clear which policy is being used at any given moment, especially when auditing why Ivy behaved a certain way. It helps users quickly identify and navigate to the relevant policy without having to search for it manually.
Use cases
Auditing why Ivy made a particular decision by clicking the linked policy to see its contents
Quickly jumping into a policy to edit it after seeing it referenced in an Ivy response
Whenever Iview reads the policy, we have now underlined the policy and you can immediately click into it to go to the policy and edit it... especially when you kind of want to audit why something happens then. Now it's always clear which policy is actually one that was referred to.
Flagged uncertain
Possible duplicate of multiple-ivy-and-press-page-improvements: The candidate describes a specific Ivy feature (clickable policy links in Ivy readouts). The slug 'multiple-ivy-and-press-page-improvements' could potentially include this, but without knowing its exact contents it's unclear. No other entry clearly matches this specific clickable policy link feature. It could also relate to 'ivy-task-management-and-platform-improvements' or 'multiple-new-platform-features-and-enhancements', but none are a clear duplicate.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·8d ago
Templates in inbox with merge tags
You can now use templates directly in the inbox, with merge tags automatically filled in when applying them.
Draft emailTemplates now work in the inbox, with merge tags resolved
You can now insert templates directly into inbox email threads. When you apply a template that contains merge tags, MVPR resolves them immediately using the journalist's actual details, so what you see in the editor is exactly what gets sent.
This matters because it closes the loop on templates across the platform. A few things worth knowing:
- Merge tags like `Dear [first name]` are replaced the moment you apply the template in a thread
- You can review the resolved text in the editor before sending, so it's easy to confirm the right name came through
- Templates behave consistently whether you're working in campaigns or replying to an ongoing inbox thread
Customers can now insert templates directly into inbox email threads. When a template containing merge tags (like 'Dear [first name]') is applied in the inbox, the merge tags are automatically resolved to the actual journalist's name, so what you see in the editor is exactly what will be sent — no raw tags visible.
Why we built it
The team wanted to complete the full feature story for templates. Since templates already existed for use in campaigns/cells (e.g. for JLR press releases), it would be confusing if users expected to find them in the inbox but couldn't. Even if the team considers inbox usage a minor use case, leaving it out would feel like a gap.
Use cases
A user who has set up a template with merge tags (e.g. 'Dear [first name]') can insert it into an ongoing inbox thread with a journalist, and the merge tag is instantly replaced with the journalist's real name.
Users can audit outgoing messages in the inbox editor to verify the name was filled in correctly before sending.
The template actually has a merge tag here. So it has dear first name, obviously, because the template doesn't know yet what name it is. But the moment we put it into an actual thread with an actual journalist... at this point they are essentially instantiated... it looks exactly the way it goes out and you can basically audit whether it was built in correctly.
Flagged uncertain
Possible duplicate of inbox-v100-comfort: The candidate describes templates with merge tags in the inbox. The 'Inbox | v10.0 Comfort' release likely covers inbox improvements and may include this feature, but without knowing the full contents of that release, it's uncertain. Additionally, 'email-signatures-templates-browser-plugin-and-ai-improvement' references templates but appears broader in scope. Neither is a clear confirmed duplicate without more detail.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·8d ago
Journalist Preferred Name field
Journalists now have a 'Preferred Name' field on their profile, which is used when filling in merge tags across emails and templates.
Draft emailNew: Preferred Name field for journalist profiles
Journalist profiles now have a **Preferred Name** field. Whatever you enter there is what merge tags like `{{journalist_first_name}}` will pull through in emails and templates, overriding the system's automatic name detection.
If you leave the field blank, nothing changes. But the field is useful in two situations:
- **Nicknames** - if a journalist goes by something other than their formal first name, enter it here and all your merge tags will use it automatically.
- **Functional or non-English accounts** - for contacts like an editorial desk listed in Cyrillic or another non-Latin script, automatic detection does not work. You can now type in whatever salutation you want (for example, "Team") and it will populate correctly across every email and template.
To set a preferred name, open any journalist profile and look for the Preferred Name field beneath the contact details.
Journalists now have a 'Preferred Name' field on their profile. When sending emails or using templates with merge tags (like 'journalist first name'), the system will use whatever name you type into this field instead of the automatically guessed name. If you don't fill it in, behaviour stays the same as before.
Why we built it
Two main reasons: (1) To let users store a journalist's preferred nickname or informal name rather than relying on the system's automatic first-name guess. (2) To handle functional/editorial accounts (e.g. 'news desk', 'editorial team') in non-English languages, where the automatic detection fails — users can now simply type in whatever salutation they want (e.g. 'Team') and it will work regardless of language or script.
Use cases
A journalist goes by a nickname — the user can enter that nickname in the Preferred Name field so merge tags use it automatically.
An outlet's contact is a functional account in a non-English language (e.g. Cyrillic 'editorial team') — the system can't detect 'Team' automatically, but the user can type it into the Preferred Name field and it will populate correctly in all emails and templates.
if you have a proper name of someone then you can put their nickname into this preferred name field... But it's also useful for functional accounts like our editorial team ones... in other languages you can't really use this field because it would not ever find editorial teams. But now you can just put in whatever name you want and it will work in all of the languages.
Flagged uncertain
Possible duplicate of alternative-names-for-journalists-and-publications: The candidate describes a 'Preferred Name' field for journalists used in merge tags, which is conceptually similar to 'Alternative names for journalists and publications'. However, without knowing the exact content of that registry entry, it's unclear if it covers the same specific feature (a profile field for preferred names used in email/template merge tags). The overlap is plausible but not confirmed.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·15d ago
Alternative names for journalists and publications
You can now record alternative names and websites for journalists and publications, making it possible to recognise that 'NY Times' and 'The New York Times' refer to the same outlet. This lays the groundwork for smarter deduplication and matching across your media contacts.
Draft emailRecord alternative names and websites for journalists and publications
You can now add alternative names and websites to journalist and publication records. This means variations like "NY Times", "New York Times", and "The New York Times" all map to a single authority record, so searches on any variation return the right result.
This works across a few common scenarios:
- **Publication name variants** - abbreviations, articles ("The"), and common shorthand all resolve to one record
- **Multiple websites or regional subdomains** - record them together rather than creating duplicate entries
- **Journalist name formats** - middle names spelled out or abbreviated can be stored as alternatives on the same profile
This lays the groundwork for smarter deduplication and automated matching across your media contacts database. You can start adding alternative names now from any journalist or publication record.
You can now record alternative names and alternative websites for publications and journalists, so that variations like 'NY Times' and 'New York Times' are recognised as the same outlet. This also works for journalists who may have middle names spelled out or abbreviated.
Why we built it
The team built this to make the journalist/publication database more expressive, enabling smarter search (so any variation of a name still surfaces the one authority record) and laying groundwork for future deduplication and matching. It also gives the team enough data volume to experiment with and evaluate automated systems for creating journalist and publication records.
Use cases
Recognising that 'NY Times', 'New York Times', and 'The New York Times' all refer to the same publication so search always returns the correct authority record.
Recording multiple websites or regional subdomains for a publication under one record.
Storing alternative name formats for a journalist, such as a middle name spelled out versus abbreviated.
If someone puts in the New York Times, it's the same thing as NY Times or like New York Times and all of these things, which means we can now express them. And then we can also bias our search in a way that if someone types in any of these names, still the one authority record comes up.
Flagged uncertain
Possible duplicate of mvpr-entity-protocol-v10-formalized-references: The candidate describes adding alternative names/aliases for journalists and publications to enable deduplication and matching. The 'MVPR Entity Protocol | v1.0 Formalized references' slug could potentially cover this as 'formalized references' might relate to entity resolution and alternative naming. However, the description is not specific enough to confirm a match. The candidate could also relate to 'journalist-database-v50-data-lifecycles' given it concerns journalist/publication records. Without clearer descriptions of those existing entries, a definitive duplicate call cannot be made.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·29d ago
Email signatures, templates, browser plugin, and AI improvements
Several new features have shipped: email signatures (one per company, auto-filled in drafts, with a generator), email templates in inbox settings, dedicated settings pages, a browser plugin company selector aligned with the platform, a new 'newsjacking' intent auto-set by Ivy, an improved membership invite flow, and Ivy can now read attachments to help create pitches from files.
Draft emailEmail signatures, templates, Ivy improvements, and more
Several updates have shipped across the platform this week.
**Email signatures** are now available in settings - one per company, auto-filled into every new draft and follow-up. You can type one from scratch, paste existing HTML, or use the built-in generator to produce a clean signature with your name, title, logo, and a trackable press kit link in a few minutes.
Other changes in this release:
- **Email templates** are available in inbox settings, so teams can create consistent branded starting points for announcements
- **Ivy can now read attachments** (including images and PDFs), so if your press release is uploaded as a file rather than typed into the document body, Ivy can still draft a pitch from it
- **Newsjacking intent** is now available and auto-set by Ivy on news-driven outreach threads
- The **browser plugin** has a simplified company selector
- The **membership invite flow** now shows non-admin members who the account owner is, so they can request invites directly
Customers now get email signatures (one per company) that are automatically pre-filled in every new draft and follow-up email. They can type their own, paste in existing HTML, or use a built-in generator to create a tidy-looking signature in minutes. Email templates are also available in inbox settings, letting teams create branded starting points for announcements. The browser plugin now has a single, cleaner company selector. A new 'newsjacking' intent is available and auto-set by Ivy. The membership invite flow now tells non-admin members who the account owner is. Ivy can now read attachments (including images) to help draft pitches or cover letters from uploaded files.
Why we built it
The primary motivation for signatures was to replace the old mandatory footer (which included an unsubscribe link) with something flexible and user-controlled, while still ensuring a trackable press kit link is included. Templates were built for clients like JLR who need branded, consistent email starting points. The browser plugin was simplified to reduce confusion and encourage more use of journalist data collection. Ivy reading attachments solves the problem of Ivy being unable to draft a sell-in when a press release is uploaded as an attachment rather than typed into the document body.
Use cases
A company user generates a signature in a few minutes using the built-in generator, which auto-fills their name, title, company logo, and a trackable press kit link into every new draft.
An agency user pastes their own existing HTML signature (e.g. from Superhuman) into the signature field so it appears consistently across client campaigns.
A client like JLR creates email templates in inbox settings so team members can start announcements from a pre-approved branded template.
A user attaches a press release PDF to an announcement page and asks Ivy to draft a sell-in pitch, with Ivy now able to read the attachment to do so.
A non-admin team member trying to invite a colleague is now told who the account owner is so they can request the invite themselves, reducing support burden.
Ivy automatically labels news-driven outreach threads with the 'newsjacking' intent so they can be distinguished from standard proactive pitching.
The reason really is that there are like we added already a few things to settings and we will be adding more things... our big motivation to do this is to replace our footer... you can either adjust it or replace it with your own signature... if you want to do the draft sell in, then this obviously tries to draw from a document which is now empty because you have added your press release as an attachment. But now Ivy has the ability to also read these attachments.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·2026-05-13
Browser plugin UI improvements
The browser plugin has been updated with two improvements: the company selector now matches the platform's appearance, and 'Add to list' now shows a list picker automatically instead of requiring manual selection from the top. Update your browser plugin to get these changes.
Draft emailBrowser plugin update: UI improvements to company selector and lists
Two small but useful changes are now available in the latest version of the MVPR browser plugin.
- **Company selector** now matches the look and feel of the main platform, making it easier to scan and select the right company without switching mental gears.
- **Add to list** now opens a list picker automatically. Previously you had to navigate to the top of the plugin to trigger this manually.
To get these changes, update your browser plugin now. If you have auto-updates enabled, you may already be on the latest version.
Flagged uncertain
Possible duplicate of ivy-browser-extension-v40-tighter-product-integration: The candidate describes browser plugin UI improvements (company selector styling and 'Add to list' auto-picker), which sounds like it could be related to 'Ivy Browser Extension | v4.0 Tighter Product integration'. However, the existing entry's name 'Tighter Product integration' is vague enough that it might cover these UI improvements, or it might be a different set of changes. There is also 'ivy-browser-extension-v40-audience-company-extraction' which relates to company functionality in the browser extension. Without more detail on what those v4.0 entries contain, a definitive duplicate or new verdict cannot be made with confidence.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-05-11
Agency dashboard and content page improvements
The agency dashboard now shows aggregated activity charts, and you can add attachments directly on announcement, proactive pitching, and thought leadership pages. Newsjacking and opportunities have been consolidated into a new 'News Opportunities' tab for easier access.
Draft emailAgency dashboard charts, attachments, and News Opportunities tab
Three updates are now live across the platform:
- **Agency dashboard activity charts:** The agency overview now shows aggregated message activity across all linked client companies. Decision-makers can review rolled-up metrics in one place without drilling into individual accounts - useful for monthly reporting or portfolio-level views.
- **Attachments on content pages:** You can now add file attachments directly on announcement, proactive pitching, and thought leadership pages. Files are attached at the draft stage, so a branded PDF can accompany the email body from the start rather than being added later.
- **News Opportunities tab:** Newsjacking and news tracking have moved out of the journalist tab into a dedicated 'News Opportunities' tab. The journalist list stays prominent where it belongs, and news-related features are grouped together for cleaner navigation.
The agency dashboard now shows aggregated activity charts so decision-makers can see rolled-up metrics across all their client companies in one place. You can also add attachments directly on announcement, proactive pitching, and thought leadership pages, so files are ready when you create drafts. Newsjacking and news tracking have been moved out of the journalist tabs into a consolidated 'News Opportunities' tab for cleaner navigation.
Why we built it
The agency dashboard chart was built to make the agency overview page genuinely useful for software clients' decision-makers who don't want to dig into individual inboxes or announcement pages — giving them presentable, aggregated results. The attachment feature was built as a convenience for software customers (like JLR) who need to attach PDFs with strict corporate identity requirements alongside their emails. The news opportunities consolidation was done to keep the journalist list prominent in the journalist tab and group related features together logically.
Use cases
Agency decision-makers reviewing aggregated monthly message activity across all client companies and putting the data on a slide without having to drill into individual accounts.
VC firms wanting a portfolio-level view by linking all portfolio companies to an agency account and seeing consolidated activity.
Enterprise clients like JLR attaching a branded PDF announcement to the worktop upfront (since HTML emails can't guarantee corporate identity), so they only need a small cover letter in the email body.
Users navigating to news tracking/newsjacking features more easily from the new consolidated 'News Opportunities' tab instead of hunting through the journalist tab.
The decision makers that really don't want to go into an inbox and look at threats may not even want to look into announcement page. They now get like aggregated results that they could put on the slide and that look good. So that's the reason why we put it here.
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-05-05
Multiple shipped product updates
Several customer-facing improvements have shipped: you can now resend remaining messages after 'send all' errors, copy Ivy messages, duplicate journalist lists, see error callouts for bounced announcement threads, and use a redesigned quick-action bar with clearer labels. Additional updates include a more compact calendar UI, more email-accurate message styling in the inbox, admin-only system prompts, and a dedicated flow for connecting shared inboxes.
Draft emailAnnouncement error recovery, list duplication, and more
Several improvements have shipped across the platform this week.
**Error recovery and transparency**
- If a 'send all' fails partway through, you can now resend the remaining emails without starting over or losing your work
- Bounced and failed announcement threads now surface clear error callouts directly in the announcement, along with guidance on next steps
- The quick-action bar has been redesigned with clearer labels that explain which actions are available and why others are disabled
**Other changes**
- Journalist lists can now be duplicated within a company, so you can build on an existing list without modifying the original
- Ivy messages can now be copied
- The inbox now renders message styling closer to how emails appear in an actual email client
- The calendar UI is more compact
- Admins can now set system prompts and connect shared inboxes through a dedicated flow
All changes are live in your account now.
Customers now get clearer error callouts when announcement emails bounce or fail, can resend remaining emails after a 'send all' error without losing their work, duplicate journalist lists within a company, use a redesigned quick-action bar with clearer labels explaining what actions are available and why, see a more compact calendar UI, and view emails in the inbox styled closer to how they actually appear in an email client.
Why we built it
The team wanted to eliminate frustrating dead-ends (e.g. users having to delete and redo entire announcements after a single send error), make the platform state and available actions transparent to users at all times, and support new customer requirements (like JLR's branded email templates) while also improving security around how email HTML is rendered.
Use cases
A customer sends one email manually to test it, then clicks 'send all' for the rest — the platform previously blocked the whole send because one draft was already sent (empty). Now it surfaces an error but lets them send the remaining emails without starting over.
A user with a large announcement list (e.g. thousands of journalists) who previously had to delete and recreate the entire announcement when a single error occurred can now just send the remaining ones.
A user selects a mixed set of journalists in an announcement and the quick-action bar now clearly explains which actions are available and why others are disabled (e.g. 'you can only follow up if there is something to follow up').
A user wants to start a new announcement from an existing journalist list — they can now duplicate the list within their company, rename it, and modify it without affecting the original.
A user notices their email has bad formatting in the inbox because it now displays closer to what the journalist actually sees, prompting them to clear formatting before sending.
An admin user (e.g. at JLR) pastes an HTML email template to send branded press releases with logos and elaborate headers/footers.
"Now it's like, it's very transparent. If something is up with your announcement, then the announcement tells you, and the announcement also tells you further how to mitigate."
Flagged uncertain
Possible duplicate of an existing entry: registry dedup error: Unterminated string in JSON at position 765
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-04-07·conf 85%
Task Group filter on company task board
A new 'Task Group' filter has been added to the company task board, making it easier to find and manage tasks by group. This is now live in production.
Draft emailNew: filter the task board by Task Group
The company task board now has a **Task Group** filter. You can use it to scope the board to a single group of tasks - such as those belonging to a specific task recipe - instead of viewing everything at once.
If you use task recipes as projects (for example, one recipe per campaign or announcement), you can now filter down to just that recipe and see only its tasks. This makes it easier to track progress on a specific piece of work without noise from unrelated tasks.
A few ways this is useful right now:
- Filter the task board to a single task recipe to see only tasks tied to that project
- Switch between recipes quickly to compare workloads across projects
The filter is live now. If your team organises work into task recipes, it is worth trying today.
On the company task board, users can now filter tasks by their group (e.g., a task recipe or call transcript group), making it easier to view only the tasks related to a specific project or activity rather than seeing all tasks at once.
Why we built it
The filter was built primarily to unblock a customer (Fever) who use task recipes as projects (e.g., announcing a new activity) and needed a way to see only the tasks belonging to a specific project. It also serves as a signal to that customer that their feedback is taken seriously, and as an experiment to explore how task grouping could be formalised more broadly across the platform.
Use cases
A customer running a task recipe (which maps to a project like launching a new campaign) can filter the task board to show only tasks from that recipe/project, ignoring all other tasks.
Future possibility: filtering tasks by announcement, or by task type (e.g., news-checking or opportunity responses), once those are formalised as groups.
For them a task recipe corresponds to a project which is like announcing their new activity or something. And for them it would be good to only see all tasks related to that project, which in our world is a task recipe which is now possible by filtering it down and say, actually I only want this thing and then only see the tasks which are related to this one.
Flagged uncertain
Possible duplicate of ivy-task-management-and-platform-improvements: The candidate describes a specific 'Task Group' filter added to the company task board. The registry entry 'ivy-task-management-and-platform-improvements' could potentially include this change as it broadly covers Ivy task management improvements, but without knowing the exact contents of that release it's unclear if this specific filter feature is already captured there. Several other 'multiple updates' entries could also contain this feature.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
shortcut·2026-04-06
Announcements | v5.1 Personalize at Scale
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-04-02
MCP | v1.0 PoC
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-03-30·conf 82%
Multiple Ivy and Press Page Improvements
Several customer-facing features have shipped: the press page now supports uploading non-YouTube/Vimeo videos, Ivy's UI shows when a task has been delegated to another Ivy, newsjacking can now search beyond on-screen opportunities autonomously, and Chat-Ivys can search threads/stories, retrieve journalist info, and use vector search.
Draft emailClearer inter-Ivy delegation, one-click coverage checks, and more
Several improvements have shipped across Ivy and Press Pages this week. The most significant changes are to how Ivy-to-Ivy delegation appears in the UI.
When one Ivy hands off to another, the delegated response now appears as a threaded reply directly below the handoff message, rather than surfacing further down the conversation with no clear connection to what triggered it. You can click the Ivy's name or the icon in that message to jump straight to the relevant thread. This also lays the groundwork for the one-click coverage check button on announcements, which lets all Thread Ivys check for coverage simultaneously instead of requiring you to trigger each thread individually.
Also included in this release:
- **Press page video uploads:** non-YouTube/Vimeo video files can now be uploaded directly to your press page
- **Newsjacking:** can now search beyond on-screen opportunities autonomously
- **Chat-Ivys:** can search threads and stories, retrieve journalist information, and use vector search
When one Ivy delegates a task to another Ivy (e.g. a News Ivy handing off to a Thread Ivy), the UI now shows the delegated response as a threaded reply right below the handoff message, rather than appearing randomly further down the conversation. This makes it clear which response belongs to which action, and you can click directly to jump to the other Ivy's thread.
Why we built it
The old UI made it confusing when inter-Ivy communication happened — responses would appear disconnected from the actions that triggered them. The team also made underlying technical improvements to inter-Ivy communication as part of this change, which enables future features like the one-click 'check for coverage' button on announcements.
Use cases
When Ivy checks for newsjacking opportunities and delegates a response to a Thread Ivy, the user can now clearly see the threaded reply right after the handoff message, rather than having it appear randomly lower in the conversation.
Users can now click a single button on an announcement to trigger all Thread Ivys to check for coverage simultaneously, instead of having to click a button on each of 20–30 threads individually.
Users can click on the Thread Ivy's name or an icon in the delegated message to jump directly to that thread.
When these things happen where one Ivy talks to another Ivy, then there won't be random stuff happening down here. It is still the conversation that you're having with News Ivy, but the response is coming in down here, like right after where it was handed off to the other Ivy. Pretty much how a thread works in Slack or any chat.
Flagged uncertain
Possible duplicate of an existing entry: registry dedup error: Unterminated string in JSON at position 790 (line 4 column 710)
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-03-16·conf 91%
Coverage, audience, and opportunity tier updates
You can now add coverage directly from the dots menu on announcements, top-line, and proactive pitching — including for first-time coverage. RS opportunities are now only available to Starter, Silver, and Gold tier clients, and the Chrome plugin will prompt you when it detects a page it needs for improved audience extraction.
Draft emailAdd coverage from any workup, RS access updates, Chrome plugin prompts
Three changes are now live across the platform:
- **Add coverage from any workup:** The dots menu on announcements, top-line, and proactive pitching now includes an "Add coverage" option, even before any coverage has been recorded. Previously, the button only appeared once coverage existed, making it impossible to log a first entry directly from the workup.
- **Response Source opportunities:** RS opportunities are now available to Starter, Silver, and Gold tier clients only. If your account is on a different tier, you will still see HARO and Source of Sources opportunities.
- **Chrome plugin audience prompts:** When the plugin detects a LinkedIn page that contains audience data not yet captured, it will prompt you to collect it. This is the first step toward building audience data passively as your team browses normally.
The coverage and Chrome plugin changes are available now. If you have questions about tier access to RS opportunities, contact your account manager.
You can now add coverage directly from the dots/dropdown menu on any workup (announcements, top-line, proactive pitching) — even when no coverage has been recorded yet. RS (Response Source) opportunities are now restricted to Starter, Silver, and Gold tier PR clients only. The Chrome plugin will now show a prompt when it detects a LinkedIn page that needs to be scraped for audience data.
Why we built it
The 'add coverage' button was added because the existing coverage display only appeared once coverage existed, making it impossible to record a first piece of coverage from the workup itself. RS opportunities were restricted to comply with licensing/access requirements for that data source. The Chrome plugin prompt was introduced as a first step toward passively collecting audience data without manual effort.
Use cases
A user on a workup needs to record the very first piece of coverage for a client — they can now do so directly from the dropdown menu without needing the coverage section to already exist.
A client not on a Starter, Silver, or Gold tier tries to access Response Source opportunities — they will no longer see RS opportunities but will still get HARO and Source of Sources.
A team member browsing LinkedIn for any reason encounters a profile that needs to be scraped for audience extraction — the plugin prompts them to click a button to collect the data passively.
For all of the worktops you have now an option here which is 'add coverage', which is pretty much the same button that you have in the coverage display. But this one is always there even if the coverage display is there yet because it's empty. So if you are on a workup and you need to record the first piece of coverage which is not related to a thread, now you can do it from the dropdown.
Flagged uncertain
Possible duplicate of an existing entry: registry dedup error: Expected ',' or '}' after property value in JSON at position 907 (line 4 column 834)
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-03-09·conf 92%
Ivy task management and platform improvements
Ivy can now create, complete, and display tasks inline with checkboxes, and the company task board has new collaborator filters. Proactive pitching pages now show outreach statistics and coverage, opportunity ingestion is faster with improved text formatting, and press page image uploads have been stabilized.
Draft emailIvy task management, pitching stats, and platform improvements
Several updates are live across MVPR this week.
**Ivy and task management**
- Ivy can now create, list, and complete tasks inline with clickable checkboxes, so you can manage tasks conversationally without leaving your workflow. For example, after sending a chaser email you can tell Ivy to complete the chaser task directly.
- The company task board has new collaborator and time filters to make it easier to navigate, particularly when auto-generated tasks accumulate.
**Pitching and opportunities**
- Proactive pitching pages now show outreach statistics and coverage inline.
- Opportunities appear on the platform as soon as the email arrives, rather than waiting for a scheduled ingestion window. Formatting of ingested text has also been cleaned up.
**Press pages**
- Image and file uploads have been rebuilt. Uploads will now save and load reliably.
Ivy (the AI assistant) can now create, complete, and display tasks inline with clickable checkboxes. The company task board also has new collaborator and time filters. Proactive pitching pages now show outreach statistics and coverage, and opportunity ingestion is faster with better text formatting. Press page image uploads have been stabilized and will load more reliably.
Why we built it
Task filters were added because users working as a single company (not an agency) had a limited task board that became hard to navigate, especially when flooded with auto-generated tasks. Ivy task awareness was built so users can manage tasks conversationally without leaving their workflow. Outreach statistics on proactive pitching were added after a customer (VIVA) used the page and expected stats to be there. Opportunity ingestion was reworked for technical housekeeping, with faster delivery and cleaner formatting as user-facing benefits. Press page image uploads were rebuilt because images were disappearing, failing to load, and sometimes crashing.
Use cases
Filtering the company task board by collaborator or time to find relevant tasks quickly
Asking Ivy to list all tasks related to a thread or announcement and viewing them inline with checkboxes
Telling Ivy 'complete the chaser task' after sending a chaser email, without manually navigating the task board
Asking Ivy to create a task for a specific resource (e.g. an announcement) so it's automatically deep-linked
Viewing outreach statistics and coverage directly on the proactive pitching worktop page
Opportunities appearing on the platform immediately when the email arrives, rather than waiting for scheduled ingestion windows
Uploading images and files to a press page reliably without them disappearing or crashing
You can just ask Ivy about tasks, then you can ask Ivy to complete tasks. So for example, think of you have a thread and you've done the chaser. You could just tell Ivy, complete the chaser task. That is a use case that is possible now.
Flagged uncertain
Possible duplicate of task-list-v100-custom-recipes: The candidate describes Ivy task creation/completion with inline checkboxes and company task board collaborator filters, which overlaps significantly with task list features likely covered in 'Task List | v10.0 Custom recipes' or 'Task List | v9.0 Managing your day'. However, the candidate also includes additional features (proactive pitching outreach stats, opportunity ingestion improvements, press page image upload fixes) that suggest it may be a broader multi-feature release. The task-related features are suspicious matches but the full bundle doesn't clearly map to any single existing entry. Could also partially overlap with 'multiple-shipped-product-updates' or 'bugs-chores-improvements-q1-2026'.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·2026-03-02·conf 95%
Multiple new platform features and enhancements
Several new features have shipped to the MVPR platform, including independent system prompts per Ivy, integrated Google Alerts for competitors, Ivy assistants on Thought Leadership and Proactive Pitching pages, bulk outreach via a redesigned announcements-style right column, additional merge tags for sell-ins (journalist full name and publication), and Ivy-powered journalist list generation using vector search.
Draft emailNew: independent Ivy prompts, enriched Google Alerts, and more
Several updates have shipped across the platform this week.
**Google Alerts** now automatically identifies the journalist, publication, and story behind each alert. Click the journalist's name to open their modal and write a message, add them to a list, or start a news-track. Any journalist discovered this way is permanently added to the MVPR database. You can also ask Ivy to pull all journalists who have covered your competitors in a given period and add the resulting list in one action.
The other changes:
- **Independent system prompts per Ivy** — fine-tune AI behaviour for a specific company or workflow without touching the global policy
- **Ivy on Thought Leadership and Proactive Pitching pages** — generate sell-ins directly from those pages
- **Redesigned right column on Proactive Pitching** — bulk-outreach view now mirrors the Announcements layout
- **New merge tags** — journalist full name and publication name, alongside the existing first-name tag
- **Ivy journalist list generation** — Ivy can now add journalists directly to a list
Several new capabilities are now live on the MVPR platform: each Ivy assistant can have its own independent system prompt so you can fine-tune AI behaviour per company or per workflow without changing the global policy; Google Alerts for competitors now automatically identify the journalist, publication, and story, letting you click straight through to write a message, add to a list, or create a draft/news-track — and any net-new journalist discovered this way gets added to MVPR's database permanently; Ivy assistants are now available on the Thought Leadership and Proactive Pitching pages to generate sell-ins; the right-hand column on Proactive Pitching has been redesigned to look and work like the Announcements bulk-outreach view, making it easier to send to many journalists at once; merge tags now include journalist full name and publication name in addition to first name; and Ivy on journalist lists can now add journalists directly to a list.
Why we built it
The Google Alerts enrichment was built to unlock downstream workflows (messaging, list-building, story-tracking) that were impossible when alerts were plain text, and as a side-effect it auto-populates the database with journalists who cover competitors. Independent system prompts were added because a single global policy couldn't accommodate company-specific quirks without affecting all clients. The announcements-style right column on Proactive Pitching reflects that proactive pitching involves bulk outreach to many journalists rather than one-at-a-time pitches. Additional merge tags were requested for non-English markets (e.g. Ukrainian clients needing full names). Ivy on Thought Leadership/Proactive Pitching pages sets the foundation for more complex workflows in those areas.
Use cases
A user sees a competitor Google Alert, clicks the auto-identified journalist name, opens the journalist modal, and immediately drafts an outreach message or adds the journalist to a list.
A user asks Ivy 'give me all journalists that have written about my competitors in the last two weeks' and gets a linked list they can add to a journalist list in one action.
A CS manager sets a company-specific system prompt on the Opportunity Scanning Ivy to correct a recurring mis-classification without touching the global policy that applies to all other clients.
A user on the Proactive Pitching page adds multiple journalists one by one; they all appear in the announcements-style right column and can be bulk-emailed with personalised merge tags including full journalist name and publication.
A user generating a sell-in from the Thought Leadership or Proactive Pitching page uses the new Ivy assistant available directly on those pages.
When a new client is onboarded, competitors are added to Google Alerts; MVPR automatically discovers and ingests the journalists who cover those competitors, enriching the database and triggering ongoing story-tracking for them.
"if we figure out, oh actually this is an article by Tyler from Fintech Futures, then we can display it as such and link to it... since we know who it is, we can make these beautiful links where you just click on them and here you have the journalist modal — write a message, add them to a list."
Flagged uncertain
Possible duplicate of an existing entry: registry dedup error: Unterminated string in JSON at position 847 (line 4 column 767)
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U03T09Z4ML7
·2026-02-25·conf 82%
Individual system prompts per Ivy
You can now set individual system prompts for specific Ivys, allowing fine-tuned control over behaviors like opportunity response and newsjacking. These individual prompts override any company-level system prompts.
Draft emailSet individual system prompts per Ivy
You can now assign a system prompt to each Ivy individually, giving you precise control over how specific Ivys behave - without touching your company-level settings.
When an individual prompt is set, it overrides the company-level system prompt for that Ivy. This is useful when different Ivys need meaningfully different behavior, for example:
- **Opportunity response**: tune how a particular Ivy evaluates and responds to media opportunities
- **Newsjacking**: control how aggressively or cautiously an Ivy identifies and acts on breaking news angles
Ivys without an individual prompt continue to follow the company-level system prompt as before. You'll find the setting in each Ivy's configuration.
Blog post
none
Paper.Design
none
Social posts
none
✓ On blog (draft)
slack · U02MMAJFL6A
·2026-02-19·conf 82%
Real-time tool streaming in Ivy chat
When Ivy uses multiple tools to answer a question, each tool now appears in the chat as soon as it's ready instead of waiting for everything to finish. This gives you faster, more visible feedback so Ivy never appears stuck.
Draft emailIvy now shows tool results as they happen, not all at once
When Ivy runs multiple tools to answer a question, each result now appears in the chat the moment it's ready. Previously, Ivy waited until every tool had finished before showing anything, which could make it look like nothing was happening.
This change means you get a running view of what Ivy is working on in real time. If a source lookup finishes before a web search, you'll see it immediately. The conversation moves faster, and you always have a clear sense of progress.
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-02-17
Shareable pages | v1.1 All the pages
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-02-13
Audience | v1.0 Audience display
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-02-05
Workflows | v1.0 Google Alerts
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-02-02
Journalist database | v5.0 data lifecycles
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-01-26
Audience | v0.1 Broad deployment
Blog post
none
Paper.Design
none
Social posts
none
slack · U03T09Z4ML7
·2026-01-26·conf 95%
Multiple feature updates across platform
Several new capabilities have shipped across the platform: the resources section now supports markdown files, journalists without email addresses are flagged with a tag in the SHL, coverage recording now lets you change the journalist, and the coverage report supports editing and deletion. Additionally, you can now collect social media interactions manually via the plugin, delete archived threads, filter Newsjacking by language, and use the plugin to collect an audience for an objective.
Draft email8 platform updates: coverage editing, plugin improvements, and more
A batch of updates has shipped across the platform. Here is what you can now do:
- **Edit or delete coverage records** directly from the media coverage report — including changing the journalist on a record at any time
- **Flag journalists without email addresses** — they now appear with a tag in the journalist list so you know to add one before outreaching
- **Collect social media interactions manually** via the browser plugin, replacing the previous TeamFluence integration
- **Collect a target audience for an objective** using the plugin
- **Filter Newsjacking results by language** to cut out irrelevant stories
- **Delete archived threads** (admin only) for permanent removal of incorrect or bounced data
- **Upload markdown files** to the resources section
The coverage changes close a long-standing gap where non-thread coverage was locked from editing entirely. The social media collection flow is fully self-serve and replaces an unreliable third-party integration.
You can now upload markdown files to the resources section, journalists without email addresses are clearly flagged with a tag so you know to add an email before outreaching, coverage records can have their journalist changed at any time (even after the fact), and coverage can now be fully edited or deleted from the media coverage report. You can also manually collect social media interactions via the browser plugin, delete archived threads (admin only), filter Newsjacking results by language, and collect a target audience for an objective using the plugin.
Why we built it
Most of these changes are groundwork for improving the journalist database — enabling data to be unlinked and moved so journalists and publications can eventually be removed cleanly. The coverage editing/deletion fills a long-standing gap where non-thread coverage was locked. The social media interaction collection replaces the unreliable TeamFluence integration with a fully self-serve, accurate manual flow. The language filter addresses a practical annoyance caused by a large influx of Ukrainian-language stories appearing for all clients.
Use cases
A user writes to an editorial inbox but the coverage is published by a different journalist — they can now update the journalist on the coverage record to correctly attribute it.
A user needs to fix or remove incorrect coverage (e.g. a bounced message recorded as coverage) — they can now edit or delete it directly from the media coverage report.
A team member wants to see who engaged with a client's LinkedIn post — they use the browser plugin to visit each engager's profile and collect the interaction manually.
A user sets up an objective and wants to define the target audience — they use the plugin to collect LinkedIn profiles of their ideal audience members directly into the objective.
A client account has lots of Ukrainian stories cluttering Newsjacking — the language filter lets users restrict results to English only.
An admin needs to permanently remove a thread with wrong or bounced data — they can now delete archived threads for good (restricted to admins to prevent accidental data loss).
A user stores a markdown-formatted brief or document in the resources section — the platform now renders and supports markdown files.
"Coverage which is not from a thread, could not be edited or removed whatsoever. Right now you can. So if you click on coverage in this media coverage report, either here or when you see it in a worktalk, then it opens you a model of that coverage... in here you can edit and also delete and change the journalist if you want to. So that means that in theory you have no full self servant when it comes to cover."
Flagged uncertain
Possible duplicate of an existing entry: registry dedup error: Unexpected token 'L', "Looking at"... is not valid JSON
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-01-19
Ivy Browser Extension | v4.0 Audience Company Extraction
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-01-15
MVPR Entity Protocol | v1.0 Formalized references
Blog post
none
Paper.Design
none
Social posts
none
shortcut·2026-01-12
Coverage Monitoring | v1.1 Ivy support
Blog post
none
Paper.Design
none
Social posts
none
slack · U02MMAJFL6A
·2026-01-07·conf 82%
Bulk Follow Up and Funnel Status Auto-Select
You can now bulk follow up journalists who have a thread in the Announcement Worktop. You can also click on a Funnel Status to automatically select all journalists sharing that status.
Draft emailBulk follow-ups and funnel status selection in the Announcement Worktop
Two updates to the Announcement Worktop that reduce repetitive clicking when managing journalist outreach.
- **Bulk follow-up:** Select multiple journalists who already have a thread in the Worktop and send follow-ups in one action, rather than opening each thread individually.
- **Funnel status auto-select:** Click any funnel status label to instantly select all journalists sharing that status. Useful for bulk actions across a specific stage of your outreach.
Both changes are live now in your Announcement Worktop.
slack · U03T09Z4ML7
·2026-04-13·conf 92%·Sent 27 May 2026, 13:08
Ivy Scheduled Actions
You can now schedule Ivy to automatically run actions — like coverage checking, sending chasers, or scanning for opportunities — at a time you specify, including on a recurring basis.
Draft emailIvy can now run actions on a schedule you set
You can now schedule Ivy to run actions automatically — either once at a future time or on a recurring basis. Previously this was only possible for the internal team. Now you have full control.
Scheduled actions sit in your Ivy panel, run quietly in the background, and only create a task when Ivy finds something worth acting on. You can delete them at any time. A few ways teams are using this:
- **Recurring story or opportunity scanning** — set Ivy to check every morning for a client without any manual input
- **Staged coverage checking** — schedule checks at multiple points after an announcement (tomorrow, next week, next month)
- **Chaser personalisation** — queue it to run on a future date against a target list
- **Client offboarding** — delete scheduled actions when a client leaves so scans stop automatically
Open the Ivy panel to set up your first scheduled action.
You can now schedule Ivy to automatically run actions — like scanning for stories, checking for coverage, or sending chasers — at a time you specify, either once or on a recurring basis. These scheduled actions appear in your Ivy panel and can be deleted at any time. Unlike tasks, they run in the background without flooding your task board, and only surface a task when Ivy actually finds something actionable.
Why we built it
Previously, recurring actions like story scanning and opportunity scanning had to be manually keyed in by the team, meaning only internal users benefited. The team wanted to give all users control over when and how often Ivy runs these actions, and to decouple automated background work from the task board — so users aren't overwhelmed with generated tasks for routine checks that haven't yet yielded results.
Use cases
Setting up recurring daily story/opportunity scanning for a client so Ivy checks every morning automatically, without manual intervention.
Scheduling coverage checking at multiple future points (e.g. tomorrow, next week, and in a month) after sending an announcement, so Ivy monitors for coverage over time.
Removing scheduled actions when a client leaves, so Ivy stops running their scans.
Scheduling chasers personalization to run at a future date on a threat worktop.
Enabling software/self-serve clients (like Prosper) to set up their own scanning agents independently, without relying on the internal team.
Scheduled actions are pretty much an action, but it runs at a configured time... Previously it was only us where we had to key this in by hand when this happens. Which means that now everyone else can do this too.