Have something to say?
Manual upload with “Send immediately” still schedules new contacts 3h later
Hi Mannie, I’d like to report a bug on Organization 57 (Salon Prestige), campaign 91 “SMS PRESTIGE”. My client regularly does manual bulk uploads of contacts and selects “Send immediately”. According to him, part of the batch always goes out right away, but another part is scheduled 3 hours later. The contact list shows “Envoi dans 3 heures” (sending in 3 hours) on these contacts, even though he picked “Send immediately”. What I see in the data for today’s upload (2026-11-14, around 17:17 UTC): Contacts that already existed in list 53 were processed immediately at 17:17 UTC. In the examples I checked (contacts 83765, 83482, 82281), they were marked “ignored” (not sent), which is expected because of our duplicate filter. All 47 contacts newly created by this upload (for example IDs 84401 to 84417) got send_at = subscribed_at + 3h exactly. Contact 84417 was added at 17:17:31 UTC and has step 1 scheduled for 20:30 UTC. The 3h delay matches the campaign’s normal delay for contacts added through the API (for example contact 83765, added 10:22 UTC on Nov 13 and invited at 13:33 UTC). So it looks like “Send immediately” on a manual upload does not override the campaign’s step delay for newly created contacts. It only seems to apply to contacts that already existed. Expected behavior: when “Send immediately” is selected on a manual upload, every contact in the batch (new or existing) should be sent right away, within the campaign’s send window, without the campaign delay. Could you take a look and let me know if this is a bug or a setting I’m missing? Thanks, Jean-Gabriel
Incorrect TXT Record Instructions for Amazon SES Domain Verification
The Amazon SES domain verification section incorrectly instructs users to add a TXT record for verification. Amazon SES DKIM verification requires only the three CNAME records provided by Amazon SES. A TXT record is not required. Expected Fix: Remove the incorrect TXT record instructions. Display only the three required DKIM CNAME records. Correct the verification guidance to match Amazon SES requirements. Ensure the same incorrect instructions are not displayed elsewhere in the platform. Impact: The incorrect instructions can confuse users, cause unnecessary DNS configuration changes, and prevent users from completing their email domain setup smoothly. Please correct this issue.
The email preview shows the logo picked in the step, but customers receive a different one
Each email step of a campaign has its own logo setting, and the preview shows the logo you pick there. The email that actually goes out ignores it and uses the organization's logo from Settings. I only found out when a client's first test email arrived with the wrong logo, after I had checked the preview. For an agency running several brands, or a client with a wide and a square logo, the preview gives false confidence: what you approve is not what customers get. What happens today (reproduced on a demo organization, 9 November 2026) Campaign editor → email step 1 → Logo: upload and select a test image ("STEP LOGO"). The preview shows it. Send a test: the email received shows the organization's logo (Settings → Organization), not "STEP LOGO". On a client account, changing the organization's logo changed the logo received; the step setting had no effect. Proposal Send the logo selected in the step. Or, if the organization logo is meant to win, remove the step setting and show the organization logo in the preview.
Switching client in one tab silently switches every other tab: the banner shows one location, the next window works on another
While preparing a client's launch, the session I was working in switched by itself to another client of mine, one with almost 2,000 contacts, because the active client had been changed elsewhere in the same account. I was about to delete test contacts. Nothing was deleted, but one more click and I would have acted on the wrong client's data. I work with several tabs open all day; this makes every bulk action a gamble. What happens today (reproduced on a demo organization with two locations, 9 November 2026) Tab A: location "Movers" active, banner "You're in … Movers". Tab B: switch to location "Kitchens". Back in tab A, without reloading: the banner still says "Movers", but the next window opened ("Import contacts") already works on "Kitchens": its campaign list is empty instead of showing Movers' two active campaigns. The "Delete selected contacts" confirmation names no client, no location and no count: "Are you sure you want to delete the selected contacts?" Proposal Keep the active organization and location per tab (in the URL or the page), not per account session. At minimum, when the active location changed elsewhere, reload the tab or show a clear warning before any action. In every destructive or bulk confirmation (delete contacts, import, send), name the organization and location and the number of items affected.
Our test SMS went out under another client's brand: an unregistered sender ID is silently swapped by the provider
My client's first test SMS arrived signed with another client's name. The custom sender ID set in the organization's SMS settings was not registered with Brevo for France, so Brevo silently replaced it with another sender ID already approved on the same account, which happened to be another client's brand. Nothing in the platform flagged it: the test window still said "Sending from:" with the sender I had typed. Had I not tested on my own phone first, real customers would have received a review request signed by a different business, with no way to know who was really texting them. For a white-label agency, that is about the worst first impression possible. What happens today (reproduced on a demo organization, 9 November 2026) Platform → Messaging → SMS → our Brevo provider → Organizations → add the organization with the custom sender "DemoTest", never registered with Brevo. The form shows a warning ("Only use a sender you've already registered with your SMS provider") but accepts any value. The "Test" button ("Tester") on that organization: the window says "Sending from: DemoTest". The test SMS arrives under a different sender ID: another client's approved ID from the same Brevo account. Brevo's statistics confirm it was delivered with that other sender. No error, no warning in the platform. On the real client account, two test SMS also left under other sender IDs. Once I registered the ID in Brevo (Settings → SMS sender IDs, per country) and it was approved, the next test and the real messages went out with the right sender. Proposal In the test window and the campaign's SMS settings, say plainly that the sender is only used if it is registered and approved at the provider for the recipient's country, and that the provider may replace it otherwise. When the provider reports the sender actually used, show it in the test result and the contact's activity ("Requested: DemoTest, delivered as: …"), and flag any mismatch. If the provider's API allows it, check the custom sender ID against the provider's approved list when it is saved, and block or warn before any message goes out.
Missing Approve button and approval links for MCP review reply drafts
Hi Manny, I use the EGR MCP integration to draft review replies for Holistic Massage & Spa (organization 5, location 5). Something changed in how drafts appear, and I’d like to know whether it was intentional. What changed: 1. The draft_review_response call used to return an approval_url and a customise_url. Since about 11/3 it returns only the queue status, with no links. 2. In the Auto-Respond approvals queue, these drafts now show only a Customize button. There used to be an Approve button as well. What still works: the drafts do register in the queue. I click Customize and submit, and the reply goes out normally. So this is a workflow change, not a failure. Examples: - Review 136 (Parthkumar Pathak), draft 83, created 11/3 - Review 137 (Jordan Frederiksen), draft 84, created 11/5 - For comparison, review 133, draft 82, created 10/28 returned both links. Auto-respond rule is “MCP Drafts” (id 3). Questions: Was this change intentional? If so, is Customize then submit the intended approval path for MCP drafts? If not, can the Approve button and the links be restored? Thanks, Anil
Not able to add domain for custom email address
The function of adding domain & connecting custom email address doesn’t work as expected, especially for Emailit provider. Steps to replicate issue: In customer account, Navigate to Settings > Email Settings Add Domain > Save Nothing happened where the customer was supposed to get DNS records to verify their sending domain.
Edge Mobile Browser white screen issue
White screen issue. I have replicated the issue I found yesterday of a white screen instead of the 5-star screen loading from a QR code scan. See video. The customer is Butter Bee Bagel and it's a new customer I'm prospecting. They will use only a qr code. Using Chrome and Edge browsers, the issue seems to be solely on Edge. Notes: I am using an iPhone 17 Pro Max with the Edge browser as default. I have deleted the data save in the browser app. I do not see this issue with Chrome browser.
QR Codes
I see that sms and emails can be limited in a package. what about QR codes? can they be limited for the number for scans that will work? Can they be disabled, or do you just delete them and they will stop working?
Feedback form not showing
Feedback forms are showing anymore: https://a.cl.ly/01a19d5f-8e73-7636-a98e-c1692ca2f769
Organization logo uploaded through the API is saved as a temporary file path
Hi team, First, thank you for the API — the Agency endpoints have made onboarding our customers genuinely pleasant, and we use them every day. I think we have found a small bug in PUT /api/v1/organizations/{id}. When a logo is uploaded through that endpoint, the request succeeds and the organization is updated, but the stored logo path is the PHP temporary upload name instead of the saved file. The image then 404s everywhere it is shown. What we send: POST /api/v1/organizations/{id} _method=PUT name=... logo=@logo.png (PNG, 20 KB, 192x192) -> 200 OK What is stored afterwards: https://cdn.revw.me//tmp/phpnn7FR1 -> 404 (note the double slash and the /tmp/php... name) What we expected is a stored media URL, like the one the interface produces when the very same file is uploaded by hand: https://cdn.revw.me/ /profile-photos/.png -> 200 A few details that may help: Reproduced with two different PNG files (20 KB and 27 KB), both well under the documented 250 KB limit. Uploading the same file through the web interface works perfectly, so it looks like only the API path is missing the step that moves the uploaded file into storage. A real PUT with multipart/form-data is not parsed at all (it answers "The name field is required"), so POST + _method=PUT appears to be the only way to send a file — and that is the path showing the issue. There is no remove_logo field, so once a broken logo has been set, it can only be cleared from the interface. Thank you very much for looking into it, and thanks again for the work you put into the platform.
SMS Successfully Sent but Still Showing as Pending in Campaign Tracking
I manually added around 10 SMS messages to an existing campaign. In the campaign's sending history, the status is inconsistent: For some contacts, it correctly shows "SMS sent". For others, it only shows "Added to campaign", with the next step being Message #2 — Email, scheduled to be sent in 3 days. This makes it look as though the SMS is still pending and has not actually been sent. However, the SMS has been sent successfully. When checking the actual sending activity, the tool was triggered and the SMS was successfully sent through GatewayAPI. What's strange is that the SMS sending itself works correctly, but the "SMS sent" status is sometimes missing from the campaign's sending history. Steps to Reproduce Manually add SMS messages to a campaign. Open the sent message (campaing) in the interface. Check whether the SMS step is displayed in the campaign flow. Compare it with the data available in GatewayAPI to confirm that the SMS messages were actually sent. Observed result: The SMS step may be missing from the campaign interface even though the corresponding SMS messages are present in GatewayAPI. Expected behavior Whenever a manually added SMS has been successfully sent through GatewayAPI, the campaign history and statistics should reflect this and show the SMS as sent, rather than leaving it as "Added to campaign" or "Pending".
Wrong Booking.com page url (carries agency domain)
After booking.com connected, the external link to the booking.com page, was wrongly configured and carries the agency domain in the domain part.
"Mention score over time" chart renders empty in AI Search view
In the AI Search option, the "Mention score over time" section (subtitle: "Track your AI presence week over week") displays no content. The card header and subtitle render correctly, but the chart/data area below is blank — no graph, data points, or empty-state message.
Agency Dashboard
Has anyone else seen a difference in the agency Reporting dashboard, where the number of active subscriptions, ARR, and MRR is way off from what is actually verifiable account data? I went through each customer account to make sure that they were in 'good standing' and clicked the SYNC with Stripe button for good measure.
Form preview shows wrong flow or content
Description The form preview does not always match the selected form type or the current configuration. In some cases, the preview shows content from a different flow or displays fields/pages that do not belong to the form being edited. Steps to reproduce Open the form editor. Go to the “Content & Flow” tab. Open the relevant configuration sections in the left-hand sidebar. Create or edit a testimonial form. Configure testimonial-specific fields/content. Check the preview on the right side while editing and switching between sections. Actual result The preview sometimes displays unrelated review-flow content, wrong thank-you pages, platform options, or fields that are not part of the current form. Examples observed: A testimonial form preview shows a review/thank-you page with Kununu as a platform option. The preview shows fields that were not created in the testimonial form. The editor and preview appear to show different form states. Expected result The preview should always reflect the currently selected form type and its active configuration. Impact Users cannot reliably see what the published form will look like, which creates confusion and increases the risk of publishing the wrong flow.
Multiple message fields in testimonial forms overwrite/misroute input
Description We wanted to use a testimonial form for an employee survey. For this, we added multiple “Message” fields, where each message field represented a separate question. Example questions: “How satisfied are you with your current work environment?” “How do you rate the opportunities for professional development within the company?” “What could be improved in internal communication?” Steps to reproduce Create a testimonial form. Add multiple “Message” fields. Use each message field as a separate question. Open the public form link. Try to answer the first message field. Actual result Input entered into one message field appears in another message field instead. The individual questions cannot be answered separately. Expected result Each message field should work independently and save the answer for its own question. Impact Customers cannot use testimonial forms for structured employee surveys or feedback forms with multiple open questions.
Wall of Love Widget
We noticed that when customizing the WOL widget and choosing to remove the customer's thumbnail, the grey outline remains, throwing off the overall design. This is the only widget where this happens.
Bug Report: "vs last month" delta is inverted / miscalculated ?
The number contradicts reality and undermines trust in the dashboard. A new onboarded client (Salon le W /) flagged it during a review meeting: he collected far more reviews this month than last, yet every Time Period filter shows a large negative delta. Likely cause The current window counts only dated reviews (48 in 2026, avg 5.0), but the baseline seems drawn from the full All Time set (179, avg 4.6, inflated by undated imported Google reviews). A small numerator over a large baseline yields a negative percentage on every window. Not confirmed — a plain inverted sign or a wrong reference month would also fit. Summary The "% vs last month" delta shown under "Total Reviews" is wrong for every Time Period filter. It displays large negative percentages while the underlying data shows strong positive growth. The sign appears inverted and/or the comparison baseline is incorrect. Notably, the "Great Momentum! You're collecting more reviews than last month" banner in the same UI shows the correct positive direction, so two components are reading the same data with opposite results. Ground-truth data (from API) Monthly review counts, 2026: Jan: 1 Feb: 4 Mar: 1 Apr: 0 May: 3 Jun: 32 Jul (1-6): 7 Correct month-over-month delta, June vs May: +966% (32 vs 3). This matches the "Great Momentum! / 1200% increase" banner (Last 30 Days: 39 vs Previous 30 Days: 3), which uses the correct direction.