Feature Request
Upload a sales PDF or deck to auto-generate a campaign
It would be great to be able to upload a sales deck or PDF directly into Campaign Co-Pilot and have Sendr read it, work out the ideal audience, and automatically generate a campaign based on the content. No more starting from scratch: just drop in your existing collateral and let Sendr do the heavy lifting. As a bonus, it would be useful if the uploaded file could also be offered as an attachment in a follow-up step within the sequence, sent automatically to prospects who respond positively and ask for more information. This would make Sendr incredibly easy to demo and onboard with: hand someone a flyer at an event, upload the PDF, and walk away with a live campaign.
John Bromley 5 days ago
💡
Upload a sales PDF or deck to auto-generate a campaign
It would be great to be able to upload a sales deck or PDF directly into Campaign Co-Pilot and have Sendr read it, work out the ideal audience, and automatically generate a campaign based on the content. No more starting from scratch: just drop in your existing collateral and let Sendr do the heavy lifting. As a bonus, it would be useful if the uploaded file could also be offered as an attachment in a follow-up step within the sequence, sent automatically to prospects who respond positively and ask for more information. This would make Sendr incredibly easy to demo and onboard with: hand someone a flyer at an event, upload the PDF, and walk away with a live campaign.
John Bromley 5 days ago
💡
Feature Request
Outbound webhook event for LinkedIn connection requests (sent/accepted)
Add a webhook event category for LinkedIn connection actions in the Sequencer, so customers can route this data to external tools (CRMs like GoHighLevel, Zapier/Make, etc.) the same way page/sheet events already work. Requested events: - connection_request:sent — fires when a Send Connection step sends a request to a contact - connection_request:accepted / connection_request:declined — fires on the existing internal Unipile-backed acceptance signal (already used internally to advance sequences, but not currently exposed as a subscribable outbound event) Customer context: a user wanted to push "people I sent a LinkedIn connection request to" from Sendr into GoHighLevel via a webhook, to trigger their own GHL automation. Today this isn't possible — Sendr's outbound webhook catalogue only covers page render, page engagement, template, and sheet events (see Webhook Events Reference). The connection-accept/decline signal exists internally (Send Connection step listens for a Unipile webhook to advance the sequence) but is not exposed externally. Related existing requests: "Subscribe to reply notifications via webhooks" and "Wait for connection acceptance in sequences, with automatic accepted/not-accepted branching" reflect the same underlying gap (LinkedIn/sequence events not exposed as webhooks).
John Bromley 9 days ago
💡
Feature Request
Outbound webhook event for LinkedIn connection requests (sent/accepted)
Add a webhook event category for LinkedIn connection actions in the Sequencer, so customers can route this data to external tools (CRMs like GoHighLevel, Zapier/Make, etc.) the same way page/sheet events already work. Requested events: - connection_request:sent — fires when a Send Connection step sends a request to a contact - connection_request:accepted / connection_request:declined — fires on the existing internal Unipile-backed acceptance signal (already used internally to advance sequences, but not currently exposed as a subscribable outbound event) Customer context: a user wanted to push "people I sent a LinkedIn connection request to" from Sendr into GoHighLevel via a webhook, to trigger their own GHL automation. Today this isn't possible — Sendr's outbound webhook catalogue only covers page render, page engagement, template, and sheet events (see Webhook Events Reference). The connection-accept/decline signal exists internally (Send Connection step listens for a Unipile webhook to advance the sequence) but is not exposed externally. Related existing requests: "Subscribe to reply notifications via webhooks" and "Wait for connection acceptance in sequences, with automatic accepted/not-accepted branching" reflect the same underlying gap (LinkedIn/sequence events not exposed as webhooks).
John Bromley 9 days ago
💡
Feature Request
A/B testing for personalized page templates
Customer request (via Ana / support, Keith Su, 8/29/2026): wants to A/B test different page template variants to compare conversion rates. Related comment from the same customer: feels page templates aren't customizable enough overall (no further specifics given yet - worth a follow-up to scope what's missing, e.g. layout, styling, sections).
John Bromley 16 days ago
💡
Feature Request
A/B testing for personalized page templates
Customer request (via Ana / support, Keith Su, 8/29/2026): wants to A/B test different page template variants to compare conversion rates. Related comment from the same customer: feels page templates aren't customizable enough overall (no further specifics given yet - worth a follow-up to scope what's missing, e.g. layout, styling, sections).
John Bromley 16 days ago
💡
Feature Request
Sequencer: Add Image to Email Step
The customer is inquiring about the ability to add images to email steps within a sequencer. They are seeking guidance on how to implement this functionality.
Michelle Matandac 19 days ago
💡
Feature Request
Sequencer: Add Image to Email Step
The customer is inquiring about the ability to add images to email steps within a sequencer. They are seeking guidance on how to implement this functionality.
Michelle Matandac 19 days ago
💡
Feature Request
Mark messages as unread in the Unibox
We'd love the ability to manually mark a conversation as unread in the Unibox. Right now, opening a conversation automatically marks it as read. If you open a message but aren't ready to reply, there's no way to re-flag it, so it's easy to lose track of conversations that still need action. With a "Mark as unread" option, you could re-flag any conversation and have it resurface as unread until you're ready to deal with it, keeping your inbox accurate and nothing slipping through the cracks.
John Bromley 20 days ago
💡
Feature Request
Mark messages as unread in the Unibox
We'd love the ability to manually mark a conversation as unread in the Unibox. Right now, opening a conversation automatically marks it as read. If you open a message but aren't ready to reply, there's no way to re-flag it, so it's easy to lose track of conversations that still need action. With a "Mark as unread" option, you could re-flag any conversation and have it resurface as unread until you're ready to deal with it, keeping your inbox accurate and nothing slipping through the cracks.
John Bromley 20 days ago
💡
Feature Request
Duplicate a campaign via the API
What you'd be able to do: Create a new campaign (and its sheet) via the API by duplicating an existing one, instead of only being able to read campaigns and sheets. Why it helps: Teams onboarding clients on a repeatable template need to spin up a new campaign programmatically. Cloning a known-good source campaign covers this without needing full sequence-builder access via API. Today: Campaigns are read-only (GET) via the API, and sheets can only be created by uploading a file in the app.
Ben Kill 22 days ago
💡
Feature Request
Duplicate a campaign via the API
What you'd be able to do: Create a new campaign (and its sheet) via the API by duplicating an existing one, instead of only being able to read campaigns and sheets. Why it helps: Teams onboarding clients on a repeatable template need to spin up a new campaign programmatically. Cloning a known-good source campaign covers this without needing full sequence-builder access via API. Today: Campaigns are read-only (GET) via the API, and sheets can only be created by uploading a file in the app.
Ben Kill 22 days ago
💡
Feature Request
Delete a sheet row via the API
What you'd be able to do: Remove a row from a sheet through the API, not just add one. Why it helps: If a contact asks to be removed, or lands on a client's suppression list after being added to a sheet, there's currently no automated way to take them out. Agencies and teams managing outbound on behalf of clients need removal to be as scriptable as addition, especially where data protection obligations are involved. Today: Rows can only be removed manually in the app; there's no API endpoint for it.
Ben Kill 22 days ago
💡
Feature Request
Delete a sheet row via the API
What you'd be able to do: Remove a row from a sheet through the API, not just add one. Why it helps: If a contact asks to be removed, or lands on a client's suppression list after being added to a sheet, there's currently no automated way to take them out. Agencies and teams managing outbound on behalf of clients need removal to be as scriptable as addition, especially where data protection obligations are involved. Today: Rows can only be removed manually in the app; there's no API endpoint for it.
Ben Kill 22 days ago
💡
Feature Request
Central video library: reuse a recorded video across page templates, workflows and sequences
Customer request (raised via support conversation with Lennart Øster, 2026-08-25): Today a video recorded in one context (e.g. a mail flow) cannot be reused elsewhere (e.g. a landing page template) without re-recording from scratch. The customer built a video for a mail flow, then needed the same video on a landing page template and found no way to move or attach it there, forcing a full re-record. Requested: a video library/asset store where a video recorded once can be selected and attached to any template, workflow, or automation, instead of being tied to the single context it was recorded in. Impact: significant time cost and friction any time a template, workflow, or automation changes and reuses the same base video. Directly cited as a reason the customer considered leaving. Related but distinct from the existing "Re-use lipsync videos" request (reusing a lipsync render for repeated first-name contacts within one campaign) — this request is about reusing one base video asset across different templates/workflows/campaigns.
John Bromley 22 days ago
💡
Feature Request
Central video library: reuse a recorded video across page templates, workflows and sequences
Customer request (raised via support conversation with Lennart Øster, 2026-08-25): Today a video recorded in one context (e.g. a mail flow) cannot be reused elsewhere (e.g. a landing page template) without re-recording from scratch. The customer built a video for a mail flow, then needed the same video on a landing page template and found no way to move or attach it there, forcing a full re-record. Requested: a video library/asset store where a video recorded once can be selected and attached to any template, workflow, or automation, instead of being tied to the single context it was recorded in. Impact: significant time cost and friction any time a template, workflow, or automation changes and reuses the same base video. Directly cited as a reason the customer considered leaving. Related but distinct from the existing "Re-use lipsync videos" request (reusing a lipsync render for repeated first-name contacts within one campaign) — this request is about reusing one base video asset across different templates/workflows/campaigns.
John Bromley 22 days ago
💡
Feature Request
Subscribe to reply notifications via webhooks
Right now, if you want to trigger an action when a lead replies, you have to add a "Send a Request" step inside a specific sequence. That means your webhook only fires for replies within that one sequence, not globally. What we're asking for: a REPLY_RECEIVED webhook event you can subscribe to once in Settings > Webhooks. Whenever any lead replies, your endpoint gets notified automatically, regardless of which campaign or sequence the reply came from. This would make it much easier to keep your CRM in sync, trigger follow-up automations, or send real-time alerts to your team the moment a lead responds.
John Bromley 29 days ago
1
💡
Feature Request
Subscribe to reply notifications via webhooks
Right now, if you want to trigger an action when a lead replies, you have to add a "Send a Request" step inside a specific sequence. That means your webhook only fires for replies within that one sequence, not globally. What we're asking for: a REPLY_RECEIVED webhook event you can subscribe to once in Settings > Webhooks. Whenever any lead replies, your endpoint gets notified automatically, regardless of which campaign or sequence the reply came from. This would make it much easier to keep your CRM in sync, trigger follow-up automations, or send real-time alerts to your team the moment a lead responds.
John Bromley 29 days ago
1
💡
Feature Request
Show which filters generated a list of leads
Requested by Treg (Lucky Growth) via Kalkidan on a customer call. Currently there is no way to see, after the fact, which Lead Finder filters/criteria were used to produce a given list or sheet of leads. Users want to view the exact filter set that generated a specific list, so they can reproduce or tweak the search later. Related to but distinct from "Save the searches in Lead Finder" (reuse for future searches) and "Save Filter Settings as Template" (templating) which are about saving filters going forward, not viewing what was used historically.
John Bromley 29 days ago
💡
Feature Request
Show which filters generated a list of leads
Requested by Treg (Lucky Growth) via Kalkidan on a customer call. Currently there is no way to see, after the fact, which Lead Finder filters/criteria were used to produce a given list or sheet of leads. Users want to view the exact filter set that generated a specific list, so they can reproduce or tweak the search later. Related to but distinct from "Save the searches in Lead Finder" (reuse for future searches) and "Save Filter Settings as Template" (templating) which are about saving filters going forward, not viewing what was used historically.
John Bromley 29 days ago
💡
Feature Request
Evergreen campaign mode: automatically top up campaigns with new contacts each month
Right now, keeping an outbound campaign running means manually finding and adding new contacts every month. If you run always-on outreach to a defined target audience, that's a recurring task that pulls you out of your flow. The request: an "Evergreen" mode for campaigns. Turn it on, define your target audience once, and the campaign automatically pulls in fresh matching contacts on a monthly schedule, skipping anyone you've already reached out to. This would let teams run a true set-and-forget outbound engine without needing to revisit their campaigns each month just to keep them alive.
John Bromley about 1 month ago
💡
Feature Request
Evergreen campaign mode: automatically top up campaigns with new contacts each month
Right now, keeping an outbound campaign running means manually finding and adding new contacts every month. If you run always-on outreach to a defined target audience, that's a recurring task that pulls you out of your flow. The request: an "Evergreen" mode for campaigns. Turn it on, define your target audience once, and the campaign automatically pulls in fresh matching contacts on a monthly schedule, skipping anyone you've already reached out to. This would let teams run a true set-and-forget outbound engine without needing to revisit their campaigns each month just to keep them alive.
John Bromley about 1 month ago
💡
Feature Request
Create Batching or campaign to campaign contact sending.
Having a list of 500 people and turning on the sequence renders 500 Videos at once, which makes it hard to review and might cost unnecessary credits. Better would be a drip feed setting or batch function to limit rendering in a certain timeframe, or link it to the sending limit.
Valentin Mühldorfer about 1 month ago
💡
Feature Request
Create Batching or campaign to campaign contact sending.
Having a list of 500 people and turning on the sequence renders 500 Videos at once, which makes it hard to review and might cost unnecessary credits. Better would be a drip feed setting or batch function to limit rendering in a certain timeframe, or link it to the sending limit.
Valentin Mühldorfer about 1 month ago
💡
Feature Request
German names are pronounced English
I love the product, but the english pronunciation of german names makes half of my batch unusable. My settings and original content are of course also in German, but it still renders the english versions, which sound super unnatural in an otherwise German context.
Valentin Mühldorfer about 1 month ago
💡
Feature Request
German names are pronounced English
I love the product, but the english pronunciation of german names makes half of my batch unusable. My settings and original content are of course also in German, but it still renders the english versions, which sound super unnatural in an otherwise German context.
Valentin Mühldorfer about 1 month ago
💡
Feature Request
AI campaign emails: structural variety and fully editable content per contact
When using AI to build outbound campaigns, every email in a sequence should feel genuinely different, not a slight variation on the same template with the same call-to-action every time. We'd love Sendr's AI campaign builder to: Generate emails with structurally varied opening angles, body formats, and CTAs across contacts and sequence steps Let users freely edit any part of an AI-generated email before it goes out, including the CTA Ensure personalisation goes beyond swapping a first name, so each message feels written for that specific person This would give teams the confidence that their outreach stands out, and the control to tweak it when the AI's first draft isn't quite right.
John Bromley about 1 month ago
💡
Feature Request
AI campaign emails: structural variety and fully editable content per contact
When using AI to build outbound campaigns, every email in a sequence should feel genuinely different, not a slight variation on the same template with the same call-to-action every time. We'd love Sendr's AI campaign builder to: Generate emails with structurally varied opening angles, body formats, and CTAs across contacts and sequence steps Let users freely edit any part of an AI-generated email before it goes out, including the CTA Ensure personalisation goes beyond swapping a first name, so each message feels written for that specific person This would give teams the confidence that their outreach stands out, and the control to tweak it when the AI's first draft isn't quite right.
John Bromley about 1 month ago
💡
Feature Request
Sequencer: Dynamic Date/Time Wait Step for Meeting Reminders
A sequencer functionality to send a WhatsApp message at a specific date and time, derived from a contact field. The primary use case is to send a message 2 hours before a meeting, where the meeting date and time are stored in a contact field and processed by SendrAI. The current 'Wait' step only supports fixed delays, not dynamic dates/times from contact data.
Marcelo Bacchi about 1 month ago
1
💡
Feature Request
Sequencer: Dynamic Date/Time Wait Step for Meeting Reminders
A sequencer functionality to send a WhatsApp message at a specific date and time, derived from a contact field. The primary use case is to send a message 2 hours before a meeting, where the meeting date and time are stored in a contact field and processed by SendrAI. The current 'Wait' step only supports fixed delays, not dynamic dates/times from contact data.
Marcelo Bacchi about 1 month ago
1
💡
Feature Request
Use SendrAI as a Sequence Trigger to Monitor Intent Signals
We'd love the ability to set SendrAI as a trigger for a sequence, so it monitors a chosen signal each day (like hiring activity or company news) and automatically enrolls matching contacts when that signal is detected. Once enrolled, a SendrAI step in the sequence could then generate a personalised intro line based on that exact signal, making outreach timely and relevant without any manual effort. Today, sequence enrollment is manual or rule-based. This would make it possible to let live intent signals drive who gets reached out to, and why, automatically.
John Bromley about 1 month ago
💡
Feature Request
Use SendrAI as a Sequence Trigger to Monitor Intent Signals
We'd love the ability to set SendrAI as a trigger for a sequence, so it monitors a chosen signal each day (like hiring activity or company news) and automatically enrolls matching contacts when that signal is detected. Once enrolled, a SendrAI step in the sequence could then generate a personalised intro line based on that exact signal, making outreach timely and relevant without any manual effort. Today, sequence enrollment is manual or rule-based. This would make it possible to let live intent signals drive who gets reached out to, and why, automatically.
John Bromley about 1 month ago
💡
Feature Request
Run your outbound from inside Claude with a Sendr MCP connection
We want to build a public Sendr MCP server so you can connect your Sendr account to Claude (and other AI assistants that support MCP) and run your outbound motion by natural language. What you'd be able to do: Build and launch campaigns by describing what you want Create and manage lead lists without leaving your AI assistant Connect and manage sending channels Generate personalised outbound assets on the fly Instead of switching between tools, you could say "build me a campaign targeting Series A SaaS founders in London, write the copy, and add it to my email sequence" and Sendr handles it. Why it matters: Many of you already live in AI assistants for planning and writing. This brings Sendr into that workflow so you can drive your whole outbound motion from one place, without having to learn a separate UI for every action. We're scoping which actions to expose first and the account connection flow. If this is something you'd use, upvote and let us know what you'd want to do first.
John Bromley about 2 months ago
1
💡
Feature Request
Run your outbound from inside Claude with a Sendr MCP connection
We want to build a public Sendr MCP server so you can connect your Sendr account to Claude (and other AI assistants that support MCP) and run your outbound motion by natural language. What you'd be able to do: Build and launch campaigns by describing what you want Create and manage lead lists without leaving your AI assistant Connect and manage sending channels Generate personalised outbound assets on the fly Instead of switching between tools, you could say "build me a campaign targeting Series A SaaS founders in London, write the copy, and add it to my email sequence" and Sendr handles it. Why it matters: Many of you already live in AI assistants for planning and writing. This brings Sendr into that workflow so you can drive your whole outbound motion from one place, without having to learn a separate UI for every action. We're scoping which actions to expose first and the account connection flow. If this is something you'd use, upvote and let us know what you'd want to do first.
John Bromley about 2 months ago
1
💡
Feature Request
Language detection and formality matching for AI replies
If you operate in multilingual markets, you need Sendr to respond to contacts in the language they use, not a hardcoded default. Right now there is no workspace-level language setting, so AI-generated replies can switch languages unexpectedly mid-thread and break the trust you have built up with a contact. What we'd build: A workspace language preference that carries across all AI-generated copy and replies. Automatic detection of the language a contact replies in, so Sendr matches it rather than defaulting to your workspace language when the two differ. Formality register support: for languages like German (Sie/Du) and French (Vous/Tu), Sendr defaults to the formal register and only switches to informal once the contact initiates it. Why it matters: An unexpected language switch mid-conversation signals to a contact that they are talking to a bot, destroys credibility, and turns warm leads cold. Getting language and formality right is table stakes for outreach in multilingual regions like Switzerland, Belgium, and Luxembourg.
John Bromley about 2 months ago
💡
Feature Request
Language detection and formality matching for AI replies
If you operate in multilingual markets, you need Sendr to respond to contacts in the language they use, not a hardcoded default. Right now there is no workspace-level language setting, so AI-generated replies can switch languages unexpectedly mid-thread and break the trust you have built up with a contact. What we'd build: A workspace language preference that carries across all AI-generated copy and replies. Automatic detection of the language a contact replies in, so Sendr matches it rather than defaulting to your workspace language when the two differ. Formality register support: for languages like German (Sie/Du) and French (Vous/Tu), Sendr defaults to the formal register and only switches to informal once the contact initiates it. Why it matters: An unexpected language switch mid-conversation signals to a contact that they are talking to a bot, destroys credibility, and turns warm leads cold. Getting language and formality right is table stakes for outreach in multilingual regions like Switzerland, Belgium, and Luxembourg.
John Bromley about 2 months ago
💡
Feature Request