What’s new? v4.71 to v4.75 The CRM grows

v4.75.0 — The CRM email package No campaign went out with an unsubscribe link. The consent gate, bounce suppression and the unsubscribe page were built… and the email went out with no way to unsubscribe. Now it’s a requirement: without a public domain configured, the campaign refuses to send instead of going out without…

v4.75.0 — The CRM email package

No campaign went out with an unsubscribe link. The consent gate, bounce suppression and the unsubscribe page were built… and the email went out with no way to unsubscribe. Now it’s a requirement: without a public domain configured, the campaign refuses to send instead of going out without one.

The email body respects line breaks and declares whether it’s text or HTML; before, plain text arrived collapsed into a single paragraph. And the unsubscribe page is a real page, which no longer applies itself when a security filter visits the link before the person does.

An embeddable contact form on the firm’s website with a single line. It fills the CRM on its own, and doesn’t duplicate anyone who’s already there: it logs the message on their record. What the form brings in fills gaps; it doesn’t overwrite what the salesperson corrected by hand.

And you can reply from the record of the lead or the opportunity, staying in the same thread. Half a conversation in a case file is worse than none, because it looks complete.

Includes a CRM database change that runs on its own. No existing campaign changes meaning.

v4.74.1 – v4.74.3 — Minutes from the record, and what research left loose

The chat on an opportunity or a lead now offers to save what it drafts. Asking it for the minutes of a meeting ended up as a block of technical text instead of a button; now there’s a preview, formatting, and the document is linked to that record. “Use Prompt” also appears when you open a document from any module, not only from Documents.

Editing a document from a record no longer fails the second time. Saving it from a lead, an opportunity, a quote or a signature request gave a false conflict warning: nobody had touched the document.

And company research stays on its opportunity. It used to leave the profile loose in Documents, without attaching it to the opportunity and without marking it as a profile, so “Generate sales script” was never enabled. Both take minutes and now notify you when they finish, with a link to the opportunity.

No database changes.

v4.73.0 — The decision-maker’s email reaches their opportunity

The email for a big sale comes from whoever signs, not from the lead that was registered. The system knew who they were —they’re registered as a contact on the opportunity— and sent it to “unassigned.” Now it looks there too.

Attachments on an unassigned email are no longer lost. They’re always saved and open from the thread. Correspondence can also be read from the lead’s record, not only from the opportunity. And the owner of an opportunity is visible and can be handed off to someone else on the team.

The sales library is reachable from the CRM, with adding, editing and removing collections. And the dashboard shows open opportunities and pipeline value, instead of a “Total Cases” that added up closed and archived ones.

Includes a CRM database change that runs on its own.

v4.72.0 — The AI-powered CRM finally really works

Seven fixes, no improvements: these are features that failed silently or while looking like a normal result.

The lead search ran without verifying anything and could make up companies and contacts; now it checks on the internet. And when it failed, the screen painted it in green as “0 candidates” — that is, as if there simply wasn’t anyone.

“Research the company” refused with a false reason: the page reader thought it was banned from almost the entire web because it misread the sites’ permissions.

And the biggest one wasn’t in the CRM but in the infrastructure: the add-ons’ scheduled tasks had never run. Without them, the sales inbox, cadences, scheduled campaigns, ticket email and the ERP cache didn’t run. Nothing visibly failed: it simply didn’t happen.

No database changes.

v4.71.0 — Products in the catalog, and a bar that no longer leads nowhere

The billing catalog only let you add services. Now it distinguishes products from services, with the SAT unit code defaulting according to the type. Nothing already entered changes: what existed was a service and stays that way.

“Modules” in the navigation bar led to a nonexistent screen and gave a 404, and the module sections showed up in English. Each module now declares its short name.

And the screenshots in the add-on manuals had been broken for a while inside the application: they showed up when you downloaded the PDF, which is why nobody had noticed.

Includes a billing database change that runs on its own.

← Back to the index