Have something to say?

Tell us how we could make the product more useful to you.

Eliminate Client Setup Headaches: Implement Subaccount OAuth for Direct Google Email Integration

Agency owners know the struggle of setting up email for review requests. The current process is complicated and time-consuming, leading to: Complex DNS Configurations: Technical setups create barriers and delays. Low Email Deliverability: Emails often land in spam, hurting our clients' reputations. Wasted Time: Valuable resources are spent on setup instead of strategy. Proposed Solution: Implement Subaccount OAuth to connect directly to clients' Google accounts. This will: Simplify Setup: No more DNS hassles. Boost Deliverability: Improve inbox placement for review requests. Enhance Client Satisfaction: Deliver better results with less effort. If you agree that this feature is crucial for our success, please vote for it!

RG About 3 hours ago

💡 Feature Request

Email headers decreasing INBOX placement

on Google workspace SMTP setup, I notice a lot of headers where I want to ask if they are necessary, I have tested multiple software vendors (GHL) and the data shows INBOX placement for EMR templates are decreasing, even on TEXT ONLY MESSAGES. List-Unsubscribe Enables “unsubscribe” UI in many clients. List-Unsubscribe-Post Enables one-click unsubscribe flows. Precedence Legacy hint that mail is list/bulk; can suppress auto-replies. Additionally, inquiring as to if these are really necessary? ESP HeaderWhat it’s forNecessary? X-EMR Vendor/system flag (classification/processing). Optional / vendor-specific X-PM-Metadata-send-uuid Vendor tracking UUID. (looks like postmark) Optional / vendor-specific emr-send-uuid Another tracking UUID (sender platform). Optional / vendor-specific X-SMTPAPI JSON metadata used by some ESPs (often SendGrid-style). Optional / vendor-specific Didn’t want to bother you on the chat, since it’s not “critical” in the sense, but since it’s part of the CORE mechanism for delivery for clients, I would argue this is one of the most important things to get right. According to GOOGLE AI (added context) these three headers often act as a signal for the Promotions tab, not the Primary inbox. If your goal is the Primary tab, these headers are a bit of a "double-edged sword." Here is how they impact your placement: 1. Precedence: list (The "Bulk" Signal) Effect: This header explicitly tells Gmail, "This is an automated mailing list message." Placement: It almost guarantees your email will be filtered out of the Primary tab and into Promotions or Updates. Gmail reserves the Primary tab for one-to-one, human-style conversations. 2. List-Unsubscribe & List-Unsubscribe-Post Effect: These are technical markers of a "Bulk Sender". Placement: Like Precedence: list, these signal to Gmail that the message is a newsletter or marketing blast, which naturally pushes it toward the Promotions tab. The Reputation Benefit: While they might keep you out of Primary, they are crucial for staying out of Spam. By making it easy to opt out, you prevent users from hitting the "Report Spam" button. A high spam complaint rate (above 0.3%) will sink your reputation and land you in the Spam folder.

RG 1 day ago

🐛 Bug Reports

EMR report generation at scale

Inside EMR, I can generate a Sales Intelligence Engine Intel Report (full analysis, 2-page HTML). After it completes, EMR creates a unique URL like: https://app.otzivipro.bg/business-report/ I need to automate this at scale: ~200 reports/day, then store the exact URL EMR generated for each prospect so I can insert it into the cold email. I can automate it via browser/UI scripting, but it’s fragile—any UI/Livewire change can break it. I’m not attached to any specific implementation—my only goal is a stable, supportable automation. Do you have a recommended way to: trigger Intel Report generation programmatically, and retrieve the generated report URL/token reliably once it’s ready? If there’s no public API, I’m fine with a developer-supported internal approach as long as it’s stable. Thanks a lot

OtziviPro.bg 6 days ago

💡 Feature Request

Fix Duplicate Prevention Display - Show Actual Campaign Setting Instead of Default 14 Days

Problem Description: In the campaign settings, users can configure "Ignore duplicate requests" with a custom duration (e.g., 180 days). However, the contact activity timeline always displays the default hardcoded message "an invitation has already been sent within the past 14 days" regardless of the actual campaign setting. This creates confusion when users have set a different duplicate prevention window. The system should dynamically display the actual configured value (e.g., "within the past 180 days") instead of the hardcoded 14-day default. Expected behavior: Display message should reflect the actual campaign setting

Jean-Gabriel 20 days ago

1

🐛 Bug Reports

Higher Customer Retention (Stickiness) with Automated Social Posts

The Social Proof feature in EMR is very cool, with compelling templates for review images to be posted on socials. However, there’s a gap in the posting process — it needs to be done manually. For DIY clients, it’s an extra layer of hassle, so the feature may be underused. For DFY clients, we can’t use this feature because we don’t have clients’ social credentials. It would be extremely powerful if the following could be added to Social Proof: Ability to publish reviews directly to the connected social platforms (Facebook/Instagram). Use AI to pre-generate text content in addition to the review image. Scheduled posting. Many thanks for your consideration.

Kevin Huang 23 days ago

💡 Feature Request

Ability to Edit/Update Published Replies

Current State: Once a review has been replied to, EMR displays a static, non-clickable "Replied" badge. There is no option to modify the response within the interface. The Problem: UX Friction: If a user notices a typo or wants to improve a generic response, they are forced to leave EMR, log in to the native platform (e.g., GMB), search for the specific review, and edit it there. Missed Business Value: We cannot easily demonstrate the "Before vs. After" value of EMR. A key use case is taking a client with a history of poor/generic manual replies and clicking "Edit" > "Regenerate with AI" to instantly show them the upgrade in quality. Currently, this workflow is blocked. Proposed Solution: Complete or replace the static "Replied" badge with an "Edit Reply" button (or make the badge clickable). Expected Behavior: Clicking "Edit" loads the existing response into the text editor. The user can manually edit the text OR use the AI to regenerate a better version. Clicking "Update" sends the API request (PUT/PATCH) to the platform to overwrite the previous reply.

Seb Gardies 27 days ago

💡 Feature Request