What's new – CRM

A contact's appointment history is labelled

The "Appointments" tab of the contact drawer carried no text anywhere, only the internal name the interface looks it up by - the heading, the error shown when loading fails, the hint for an empty history, the placeholder for an unknown appointment type, the unit behind the duration and all four status badges (confirmed, cancelled, needs rescheduling, no show). Two more places sat next to it: the "Uses" column of the ticket templates table and the name a screen reader announces for the button that removes an attachment from a reply. All eight places are now written down in German and English, and the duration carries a space between the number and the unit again.

Contact statistics stay up when the aggregate comes back empty

The tile row above the

SELLERLOGIC direct links in a contact point at the right place again

In the contact drawer

Contact merge now carries every history along

Merging two contacts now also re-links

CSAT response rate now compares the same time window

In CSAT analytics and the CSAT

Data export in the portal profile now shows errors

The export button ("Export my data") on

Revenue estimate now shows Starter and Advanced MRR

In the 12-month revenue forecast on

The call monitor stays connected

The small window that shows incoming calls holds a

A candidate becomes a card in four guided steps, and the category is now mandatory

the "Source" tab in portal management used to do nothing but list marked issues - getting from there to a customer-facing card was a manual trip through the card editor. There is now a Take in button and an assistant behind it: candidate, category, title and description per language, preview. Nothing is stored until the last step; abandoning it leaves no card behind. The internal issue title sits next to you throughout, visibly marked "Internal only", and is carried into no customer field - not even the preview, which comes from the same delivery path as the public roadmap and shows you how a customer reads the card in German or in English, including the note that appears when a translation is still missing. Two further changes: a card can only be published with a category (drafts may still sit without one), and the candidate list has an Intake column showing whether an issue has already been taken in, so nobody takes the same candidate twice. Details: Portal management.

Lead scoring rules for email and phone now work

A scoring rule under CRM → Lead Scoring that checked for "has email" or "has phone" never awarded its points - regardless of whether the contact actually had an email address or phone number on file. Both conditions are now evaluated correctly.

Escalation and SLA now correctly honor business hours and priority overrides (#1533)

Several edge cases in the automatic escalation and SLA module were fixed. Business hours were previously ignored entirely by the escalation check; an SLA priority override (e.g. a shorter deadline for "urgent") was not applied when detecting breaches; checking for SLA breaches could unintentionally change data as a side effect; invalid business-hours or holiday times/dates caused a server error instead of a clear message; automatic reassignment on escalation picked an agent at random instead of distributing evenly across the group; and read-only users could not view SLA settings.

Portal management has an "Integrations" tab

The roadmap portal could not tell an external

A link now carries the open dialog with it

If you had a side panel or a window open in the

Portal accounts can now be blocked

Anyone abusing the roadmap portal - with spam requests,

Roadmap portal now shows how many requests are linked to a card

Publicly, a roadmap card

Roadmap portal rate limits are now configurable instead of hard-wired

How many feature

Ticket links from emails now only work in your own account

The "reopen ticket", "mark as

Call analyses no longer get stuck at "being analyzed" forever

A small share of call analyses (about 1%) stayed stuck at "being analyzed" for two reasons: for very long calls, the language model's response could be cut off by its own response-length limit, which was misreported as an "invalid response" - the allowed response length is now generously sized. A separate, rare queueing glitch could also leave an already-transcribed recording never handed off for analysis; a new recovery mechanism now picks those cases back up. A handful of already-affected recordings are being caught up separately.

"Mark as spam" in the ticket system fixed

Both the single-ticket action and the bulk "Mark as spam" action in the ticket list used to end in a server error regardless of which ticket was chosen - the database was missing five columns the underlying service requires. Automatic spam detection for incoming email was affected too: a message detected as spam could not create a ticket. Both paths now work as described in the manual.

Poll frequency for external review sources is now settable (#2882)

Every review source under "External Reviews" used to be checked automatically on a fixed ~20-hour schedule, with no way to change it. Editing a source now shows a "Poll Frequency" field with "Daily" (unchanged default) and "Weekly" options. "Check now" stays instantly available regardless of this setting.

The last two dropdowns in the customer area are now read out by name (#2859)

After the big wave in the customer area, two fields in the settings were still left: the signature assignment and the sync interval of the scoring integration. Anyone using them with a screen reader heard nothing but "combo box" there - with no hint of what was being selected. Both now carry a spoken name in German and English. Nothing changes visually. Signatures · Scoring ·

Split, merge and escalate in a ticket can be used again (#2829)

Opening any of these three dialogs from the ticket detail showed the dialog but left no way out of it: the window sat behind the ticket view, and every click on its close button was caught by the ticket header instead. On a phone the dialog was a dead end. The three dialogs now sit on top of the ticket view, take the full width on phone-sized screens and close on the first tap again.

The CRM's dropdowns are now announced by name (#2859)

Anyone working the CRM with a screen reader heard only "combo box" in 94 places, with no indication of what was being selected. This affected practically every filter bar and every form in the area: tickets including the sort order and the filters for channel, department, ownership, language and AI assessment, the contact and company lists, the pipeline, subscriptions, campaigns and drip mailings, the knowledge base, reviews, the customer portal with its bug reports, notifications and roadmap, and product adoption with guides, tooltips, segments, A/B tests and selector rules. All of them now carry a spoken label in German and English. Nothing changes visually, and working with a mouse stays exactly as it was. Tickets · Contacts ·

Turning a deal into a quote works again

In the pipeline, Create quote on a deal used to fail with a server error, in every tenant created since. The cause was in the database: the table the quote number is drawn from had never been created, and the quote itself was missing fourteen fields that are written when it is created, among them the quote number, the customer name, the email address and every amount field. Both are now created when the database is updated. The button creates a draft quote again, with a running number, linked to the deal. Existing quotes are unchanged.

The language chooser in the customer portal is the same everywhere (#2420)

The roadmap portal used to have two different language choosers: one in the header that showed only the abbreviations "DE" and "EN", and a second one in the profile. Both are now the same building block. The languages are written in their own spelling (Deutsch, English), so they stay readable even if you do not understand the language currently shown. The chooser is fully operable with the keyboard, the focused control has a clearly visible outline, and screen readers announce it by name ("Language"), including in the header where the caption is not visible. The choice takes effect immediately and is remembered on your device. The admin and the shop will get the same building block in one of the next steps.

Light theme now reachable in the roadmap portal, page language matches the display language

Roadmap candidates now come from the issue tracker

The new Source tab in portal management fetches issues that were explicitly marked for the roadmap and suggests a status and release quarter for each. Bug reports do not get through, even when someone marks them: they are listed under Refused with the reason. A candidate is not a card yet - only what you word and approve yourself is ever published. If the issue tracker does not answer, the tab says so explicitly and keeps showing the last successful state instead of an empty list.

The call monitor announces incoming calls again

The window that pops up on an incoming call with the caller's name and company had gone quiet. The connection to the call channel was never established: the browser could not tell the server which workspace it was reporting for, so the server turned the request away before it ever reached the call monitor. The channel is now opened the same way as every other call in the admin area, and it works again. Two things change for you along the way: your credential no longer appears in the address of the request - it was readable there for intermediaries such as your company network - and opening a page now costs the call monitor one request instead of two. There is nothing to configure; the call monitor reconnects by itself the next time the page loads. Anyone allowed to see calls (permission Read CRM) sees it as before.

Call monitor connects reliably again

The incoming-call display could fail to connect at all in large tenants - the more permissions an account held, the more certain the connection attempt was to fail, and it was retried endlessly. The connection now uses a short-lived access key and works regardless of how many permissions you hold. If it does fail permanently, the monitor no longer retries forever: it stops and shows a notice in the top right with a "Reconnect" button.

Roadmap cards carry German and English separately

A roadmap card's title and description existed exactly once - the card could not even hold two languages, although the customer portal runs in both. In the card editor you now maintain the text per language, and a language bar shows which one is still missing. Where a translation is missing, the customer does not see an empty card but the source language together with a note that their language is not available yet. Notification emails now name the card in the recipient's language as well.

SELLERLOGIC IDs now link directly

The UID and CID shown in the contact drawer's "SELLERLOGIC IDs" section now open the customer's SELLERLOGIC backend in a new tab. Both addresses come pre-configured and can be adjusted via the gear icon in the toolbar. Clear a template and the identifier stays plain text - it never becomes a link to nowhere.

Your own call numbers are now visible, other people's stay locked

On CRM → Calls → Analytics, the Read call performance permission (crm:call-performance:read) used to be all or nothing: without it you could not even see your own numbers. The permission now carries a scope. At "own" you see your own row in the callback backlog and nothing else; the "Top Agents" tile is not shown at all, because a ranking is only meaningful with other people's numbers. At "all" everything stays as before: every owner and the ranking. The scope is enforced on the server rather than hidden in the display - at scope "own" the server's response contains no other names in the first place. Roles that may read calls receive the self-service scope automatically; existing grants at scope "all" are untouched, so nobody sees less than before this change.

"Redeliver" in the delivery log now asks first - and names the target address

Redelivering from a webhook's delivery log used to fire on the first click. It is not a local retry: the payload goes to the address you configured, carrying a valid signature, and is indistinguishable there from the original delivery - depending on the receiving system it can trigger an order, re-open a case, or create a record twice. Nothing on this screen can recall it. A confirmation now appears before it is sent, naming the event and the target address the signed delivery goes to. Only confirming sends it; cancelling sends nothing. The delivery itself, the retries and the log are unchanged.

Deleting in the CRM asks consistently, and names the record

Email templates, email workflows and adoption segments could be deleted with differing levels of safety - segments with no question at all, the other two through a hand-built window. All three now use the same confirmation, and it names what is about to disappear instead of merely asking "Are you sure?".

Personal call performance data now gated on its own permission

On CRM → Calls → Analytics, the "Top Agents" and "Callback Backlog by Owner" tiles showed performance numbers for individual, named employees to anyone holding the general read permission for calls, including regular support staff with no lead or management role. Both tiles are now gated on the new Read call performance permission (crm:call-performance:read). The restriction is enforced on the server: calling the underlying endpoint directly without the permission also returns a rejection, never filtered or empty data. Every other tile (total calls, pickup rate, conversion rate, callback backlog total/overdue/trend) stays visible to anyone with read access, unchanged. Who is granted the new permission is decided by your role and permission administration.

Requesting a review now asks first - the mail goes to a real contact

In the contact detail view under CRM → Contacts, the Request review button sent the request on the first click as soon as exactly one review source carried a link. A misclick could not be taken back - the email was already in the contact's inbox. The button now asks first, and the question names the address the mail actually goes to. Only the confirmation triggers it; cancelling leaves the contact untouched. If several sources are configured, the picker opens as before - the picker is itself the asking and deliberately gets no second dialog in front of it. Editing and saving contact fields still does not ask.

Resolving and closing a ticket now asks first - an email goes to the customer

In the ticket detail view the Resolved and Close buttons fired on the first click. What few people realised: both automatically send a satisfaction survey (CSAT) by email to the customer. A misclick could not be taken back - the mail was already on its way. Both buttons now ask first, and the question names what is at stake: the ticket concerned, and the fact that a message leaves for the customer. Only the confirmation triggers it; cancelling leaves the ticket untouched. The remaining status buttons (In progress, Waiting for customer, Reopen, Spam) deliberately do not ask - they are reversible at any time, and asking on every single step would only train people to click the question away.

Calls: "My calls" / "All calls" are now one click away

The call list used to always start unfiltered, and every employee filtered it down to themselves by hand after every login. Two fixed tabs above the filter bar - modelled on the ticket tabs in the Service Desk - turn that switch into a single click. The list still starts on "All calls": nobody loses anything, and covering for a colleague or checking a customer's history remain unrestricted.

Eighteen CRM permissions did not keep the promise the rights screen made

Under Settings → Users & Roles you could tick permissions such as read/write activities, leads, read/write pipeline, delete contacts, export contacts, delete companies, assign ticket, write adoption and read/manage workflows - but no endpoint ever checked them. Granting one allowed nothing; revoking one forbade nothing. What actually decided access was always the coarse read CRM or manage CRM. Fourteen of them now take effect on their pages: activities, lead scoring, pipeline, contacts and companies, ticket assignment, adoption chapters and e-mail workflows. No role loses anything: the broad read CRM and manage CRM still open everything, and anyone who could write contacts keeps delete and export automatically. Three places change noticeably: the CSV export of the contact list now requires export contacts (the Viewer role does not hold it and can no longer export), assigning a ticket requires assign ticket rather than the general ticket write permission, and Editors can now maintain activities, lead-scoring rules, pipelines and adoption chapters, which previously needed the full manage CRM. Four further permissions stay without effect for now because the surface behind them does not exist: read/write inbox is a second name for the customer inbox permissions that already existed - the menu entry at least follows the ones that actually apply now - and read/write attribution never had a CRM page at all; channel attribution lives in Marketing and is governed by the marketing permissions. Both pairs remain in the list and will be removed in a follow-up step.

Portal e-mails now lead to a real address for freshly created tenants

As long as nobody had filled in the domain settings, customer-portal notifications - sign-in, status changes, releases, request and bug updates - carried only a bare path with no address, so the link in the e-mail led nowhere. The portal address is now derived from the tenant's short name as well, the same way the admin address already was since the last change, whenever no domain has been configured. A stored custom portal or shop address still takes priority and is left untouched.

The call overview can now find calls by customer number (CID) too

Until now, the calls list could only be searched by name, company, and other fields - the customer number, the fastest and most unambiguous identifier for support, had no way in, which stung especially with unknown phone numbers or companies with several contact people. A purely numeric entry in the general search box is now automatically recognized and matched as a CID; a dedicated "CID / Customer number" field is also available under "More filters". Name search is unchanged - a company with digits in its name is still found.

Placing a call is now a permission of its own - and a double click does not dial twice

Anyone allowed to set the phone system up was also allowed to dial with it: the same permission opened the configuration page and the click-to-call button. Placing a call now has its own permission, Place a call. Roles that could dial before still can - the new permission was handed to them automatically; what is new is that you can take it away on its own. On top of that, a call request submitted twice no longer opens a second connection: the system answers with the result of the first attempt instead of dialling again.

Calendar dates in CRM, shop and marketing no longer convert to world time

the collection date of a SEPA direct debit and the due date of an invoice payment, the day axis of the callback report, the default periods of funnel, cohort and marketing reports, and the date in the signature of outgoing messages used to be cut out of world time (UTC). Between midnight and 02:00 German time that was the previous day. Two consequences were expensive: the "five banking days" term was counted on a timestamp in the server's zone and then cut by world time, so the collection date reported to the bank could land on a weekend or a day early; and a due date produced at 00:30 was a day early, which put customers into the dunning run a day early. On top of that, the bar for the current day in the callback curve stayed permanently at zero. All of these now come from the tenant's time zone (Settings > Time zone). Document numbers, export file names and the sitemap lastmod values deliberately stay in world time - only a search engine reads those. Nothing is rewritten retroactively.

Field captions in customer relations are now linked to their field

Across the CRM pages - tickets, contacts and companies, calls, the knowledge base, email campaigns and rules, subscriptions, reviews, satisfaction, escalation, the support settings and user guidance - the input fields carried a caption above them that was not technically linked to the field. That had two noticeable consequences: clicking the caption did not put the cursor in the field, and a screen reader announced the field without a name - you heard "edit box" instead of "Subject, edit box". 291 fields now carry that link. Nothing changes visually - captions, spacing, colours and field sizes are unchanged. Fifteen places sound different: there the heading did not sit above a single input field. Where what follows is only a read-only value or a list - such as "Stages" in the pipeline settings, the "Variants" of a campaign, or a survey's type - it is now read out as ordinary text instead of as the caption of a field that does not exist. Where what follows is a group of several switches or buttons - such as the campaign type, a contact's opt-out switches, a webhook's event selection, or the icon and type pickers in the resource centre - a screen reader now announces a group with that name.

Field captions in the CRM settings are now linked to their field

Under Settings → CRM - signatures, the Google Mail setup, Google Calendar, the SES configuration and the lifecycle stage editor - the input fields carried a caption above them that was not technically linked to the field. That had two noticeable consequences: clicking the caption did not put the cursor in the field, and a screen reader announced the field without a name - you heard "edit box" instead of "Subject, edit box". That link is now in place. Nothing changes visually - captions, spacing, colours and field sizes are unchanged. Three places sound different: the speech recognition provider picker and the AI model picker in the SES configuration, and the colour picker of a lifecycle stage, are not single fields but a group of several buttons; a screen reader now announces a group with that name there. The rich text editor of a signature is not an ordinary input field either - it is now announced with its caption all the same.

Field captions in the list filters are now linked to their field

In the filters of the contact and company lists - text filter, numeric range, date range, multi-select, yes/no filter and relation picker - and in the tag picker, the input fields carried a caption above them that was not technically linked to the field. That had two noticeable consequences: clicking the caption did not put the cursor in the field, and a screen reader announced the field without a name. That is fixed. Nothing changes visually - captions, spacing, colours and field sizes are unchanged. The range filters sound different: numeric range and date range consist of two fields (from/to); their caption is now announced as a group rather than as the caption of a single field that does not exist as such.

The CRM area now asks before something is deleted or leaves the house

Across 33 CRM screens - contacts and companies, tickets and ticket templates, live chat, calls, the knowledge base, email campaigns, rules and templates, drip campaigns, segments, contact forms, satisfaction surveys, lead scoring, pipelines, sales automation, support settings and user guidance - 35 consequential buttons now sit behind a confirmation that names the consequence: which record, how many for bulk actions, and who is reached wherever something goes outside. Every browser window has disappeared from the CRM, and so have the two hand-built variants #1916 found there - the overlay without a dialog marker in contacts, and the pipeline buttons that relabelled themselves into their own confirmation on the first click. Confirmations now look the same everywhere and work the same way with keyboard and screen reader. Two actions that had no confirmation at all were noticed on the way and have one now: sending an email campaign to a whole segment, and activating a drip campaign, which then starts mailing every enrolled contact. Eleven panels deliberately get no dialog and now respond to the Enter key instead - there you fill in fields and send them off deliberately, and that send button is the confirmation: logging an activity, editing a call, the bulk action on calls, the editors for email campaign, rule, template and workflow, the rule test run, the knowledge base article draft, and the settings for closing tickets automatically. Deleting a contact used to work only through the multi-select - the button in the individual row had had no effect for some time. It works again.

Activities and the call list load again in newly created workspaces

The activity overview, the upcoming activities and the telephony call list reported a server error in workspaces created since the move to encrypted personal data. They still read the owner's name from the old plaintext fields of staff management. The name now comes from the encrypted fields; the pages load again and show the same name as before.

Customer relations moved to the shared controls (technical)

Across the CRM pages - contacts and companies, tickets and inbox, calls, deals, email templates and rules, subscriptions and the support settings - buttons as well as input, select and text fields now come from the interface's shared building blocks instead of per-page code. Look and behaviour stay the same; what becomes consistent is keyboard focus, contrast in dark appearance and the behaviour of disabled fields. Icon-only buttons additionally carry a screen-reader label throughout.

Live chat: a transcript now provably belongs to exactly one visitor

Until now, the identifier of a conversation was enough to read its entire transcript and write your own messages into it - including the other party's name and email address. Anyone who knew such an identifier, for instance from a forwarded link or a server log, reached someone else's support transcript with no further hurdle. From now on, the chat window receives a session proof when a conversation starts. It stays in that one browser and is valid only for that one conversation with that one tenant; it expires after 24 hours. Without it, every request about a conversation is refused - and refused before SELLERLOGIC even checks whether the conversation exists, so the error message gives nothing away either. The same applies to the live connection: a visitor connection now only works inside its own conversation, switching into someone else's is no longer possible. Nothing changes for your visitors: there is still no sign-in, the proof is issued in the background. Only chat windows still open at the moment of the change need to be reloaded once; they then start a new conversation, and the previous transcript stays fully visible to your team.

Unique page titles

Several help pages carried exactly the same name as a page of the same name in another area, which made them impossible to tell apart in search results and listings. Affected in this area: Subscriptions (CRM), Automation Rules (CRM) and Webhooks (CRM). The page addresses do not change, so saved links and bookmarks keep working.

Cards, rows and legends across the CRM now also work without a mouse

In several places in the CRM, an action could previously only be triggered with a mouse click - anyone working with a keyboard or a screen reader could not get through. That is fixed: a transcript segment in the call detail view now also jumps to the matching spot in the recording with Enter or the space bar, a knowledge base article opens the same way, a section on the knowledge base start page can be expanded and collapsed, a deal on the pipeline board opens its detail view, and a step in the guide editor can be selected. The same applies to tasks in the company file, templates in the email template list, rules in the email rules, a center in the knowledge base management, and the series legend of the subscription charts.

Conversation list in the Customer Inbox now reachable without a mouse

In the Customer Inbox, a conversation in the list could previously only be opened with a mouse click. Fixed: the row can now be reached with the Tab key and opened with Enter or the Space bar.

Lead scoring settings: number fields no longer lose focus while you type

Under Settings → CRM → Integrations → Lead scoring, the text cursor jumped out of a weighting field after the first digit, so the remaining digits went nowhere and the value could only be set cleanly with the plus and minus buttons. The cause was that the row was rebuilt on every state change of the page. The rows now stay put: you can type a value as usual, the focus stays in the field, and expanding or collapsing another section no longer interrupts your input.

Contact forms are protected against bulk submissions and now really do notify

A public form under CRM → Contact Forms is found by automated programs sooner or later. Every submission therefore now runs through three checks your customers never notice - there is still no picture puzzle and no third-party service: an invisible extra field only a program can fill in, a timing check (nobody types a form in under three seconds), and a comparison against the learned spam patterns that already apply to incoming email. In all three cases the sender sees the same success message as always, but no ticket is created - a program that sees an error message would otherwise try the next variant. On top of that, five submissions per minute per sender are allowed instead of the previous hundred. Discarded submissions do not increase the "Submissions" counter. Second change in the same step: the addresses stored under Notification emails were saved but never written to - now every genuine submission sends a message there. Delivery runs after the ticket has been created and never blocks it: if it fails, the enquiry still exists as a ticket.

Historical import of large time windows reliably returns a partial result instead of a network error

Under Settings → CRM → Integrations → 3CX in Time window mode, a very large window could previously still run into the connection deadline despite the time limit (message "Failed to fetch") or abort with the "window too large" hint and no result at all - because even reading just the first page of data from the phone system was not tied to the time budget. The run now caps every individual step (logging in to the phone system and each page it reads) to the remaining time budget and therefore reliably answers within the deadline. If the time is not enough for the whole window, you get a partial result with the number of calls fetched and processed and a hint to fetch the rest with a smaller window or via "Import full history" - instead of an empty error message. Calls already imported are kept, and the automatic sync every few minutes still resumes exactly where it left off, so no call is lost.

3CX import finds all calls of a time window again

Since the evening of Aug 10, the call import wrongly merged all calls of a run into a single one - a historical import spanning two days would report, for example, only "1 calls in the window", and the automatic 5-minute sync also picked up at most one call per run. The cause was a call identifier that the phone system does not populate in its report list; the import treated the placeholder value as a real identifier. The import now recognizes unusable identifiers and falls back to the always-unique record identifier - every call is imported individually again. To recover calls missing since Aug 10, run a historical import in Time window mode; existing entries are corrected rather than duplicated. Two safeguards are new as well: if the phone system reports only 0 or 1 call for a window longer than 24 hours, the result shows an amber warning instead of a silent mini-result; and if the phone system delivers rows without a usable call identifier, the run aborts with a clear error message including an error code instead of creating a merged catch-all record.

Automation system message no longer announces a closure

When a customer does not reply within the configured period, the automation marks the case as resolved - but the customer-visible system message in the timeline claimed the ticket had been "closed". In fact the case remains open for feedback at this step; it is only closed later by the second automation run. The message now correctly says that the ticket was automatically marked as resolved. In addition, both automation system messages now use a plain hyphen instead of the long dash.

Historical email import reports errors in plain language

When the historical import under Settings → CRM → Integrations → Gmail or on the mailbox detail page failed, the message could previously appear as a technical placeholder or not at all. You now always see an understandable message: a dedicated hint when you lack the permission, otherwise the server's message, and a translated fallback text when the server provides none. The message also stays visible in the section instead of only flashing up briefly.

AI assistance when recording a bug

The intake form under CRM → Portal management → Bugs now helps you fill it in. "Prefill with AI" turns your note, the linked support ticket and the linked call into a draft: an internal and a customer-facing title, a summary, suggestions for severity, area and product, plus the template fields observed behavior, expected behavior, steps to reproduce and environment/version. Along with it come a "What is still missing?" list and up to three suggested questions to the reporter that can be adopted into the question feature with one click. Everything stays a suggestion: every item has its own "Adopt", next to it there is "Adopt all", and the bug is only created when you click "Record" - nothing is saved automatically. Only products that actually exist in your setup are suggested; if none fits, the field stays empty. Second, SELLERLOGIC checks the existing reports while you type the internal title and shows up to five similar bugs under "Possible duplicates" with similarity in percent, status and severity, each of which can be opened directly - this runs by calculation only and causes no AI costs. Before the analysis, the system removes email addresses, phone numbers, IBANs, long digit sequences and credentials and replaces them with placeholders; internal ticket notes are not included at all. Triggering the draft requires the permission to manage bugs, read access is enough for the duplicate display. If no AI assistance is available or the monthly budget is used up, the form says so in plain words and you fill it in by hand as before.

Ask a single reporting contact a question

If a detail is missing while you work on a bug, you can now ask for it directly. In the detail panel of a bug under CRM → Portal management → Bugs, the new "Question to one contact" section lets you pick exactly one of the contacts linked to the bug and send them your question. The question is emailed to that one contact only; there is deliberately no broadcast to all notified customers. The contact sees the question in the customer portal on the page of their report and answers it there exactly once; the answer then appears in the bug's timeline, visible to your team and to the contact who was asked, never to other customers and never in the public "Known issues". While an answer is outstanding, the bug list shows the new "Questions" column with the count and the opened bug shows the "Open questions" notice; both disappear once the answer arrives. Asking a question requires the permission to manage bugs; read access is enough to follow along.

Call list: talk times are now correct, and sync outages no longer leave gaps

Two defects in the 3CX integration are fixed. First, the call list under CRM → Calls showed 1 minute for almost every call, because for calls routed through a queue only the first leg of the call was counted; the actual talk time is now captured to the minute across all legs. Second, calls could be lost for good when the synchronization with the phone system was temporarily down (for example during an update); the sync now reliably remembers where it stopped and catches up on the entire missed time window after an outage. Calls that are still in progress at sync time are completed automatically with their end time and real duration once they finish. To correct already imported calls with a wrong duration, re-read the affected period via the manual synchronization - existing entries are corrected in place, not duplicated.

Catch up on calls for a specific time window

The phone system's backfill now has two modes. Under Settings → CRM → Integrations → 3CX, tab Configuration, section Historical Import, the mode Time window is new and preselected: you enter From and To with date and time - for the first time to the minute rather than by whole days, in your own time zone - and catch up on exactly that period from the phone system. Existing calls are corrected instead of duplicated, and the ongoing automatic sync is left untouched, so no new gap appears. The result is shown right in the section, for example "Import finished: 12 new, 3 updated, 15 calls in the window."; the calls then appear under CRM → Calls and in the activities. The previous route is now called Full Import and remains unchanged as the tracked job across the entire history with a progress bar, pause, resume and cancel - the right choice for the initial load. Also new is that you get any feedback at all: while the run is working the section shows "Import running - reading the time window from the phone system …", afterwards the result or a plain-language error message (missing permission, no 3CX connection set up, phone system unreachable). Until now a failure stayed invisible and the button appeared to do nothing. The chosen time window is kept in the address bar and survives a reload or sharing the link. Starting the run requires the permission to manage the CRM or write access for telephony.

CRM now works on a phone

The CRM pages with special layouts now work on a smartphone (390px) and tablet (768px) without the whole page shifting sideways. The pipeline board scrolls within its own area; on touch devices you move a deal card by pressing and holding it for a moment and then dragging - a plain swipe still scrolls the board. In the ticket detail view the conversation gets the full width on narrow screens; the two side columns (the case's other tickets and the ticket details) open via two new buttons in the header. Wide tables - a subscription's billing periods, the ticket list on the support dashboard, the cohort matrix and tables inside email content - scroll in their own container instead of being cut off on the right. In the customer inbox, list and conversation stack vertically on a phone, and the guide editor shows step list and preview in a single column; its actions are always visible on touch devices instead of only on mouse hover.

The customer portal for roadmap and bug reports now works on a phone

The header carried up to seven navigation items plus the brand, the language picker and sign-in on a single, non-wrapping line - that needs roughly 1200 pixels, which was not always available even on a desktop and pushed the whole page sideways on a phone. On narrow screens the navigation now sits behind a menu button; above that it stays a bar that scrolls within itself if needed instead of taking the page with it. Filter rows, search fields and forms (report a bug, submit a request, profile) take the full width on a phone and stack vertically. Long titles, comments and e-mail addresses wrap instead of running past the edge. Buttons, vote arrows and select fields have a finger-friendly size.

A status change made directly in the bug board now notifies as well

When a staff member set a report's status directly in the board to In progress, Resolved or Closed, no customer email used to go out - only the route via the update composer triggered the send. Now every change into one of these three states notifies the affected customers who have notifications on, no matter which route was taken. No double send occurs: if an update contains a customer-facing text AND a status change, each recipient still receives exactly one email. Every email carries the unsubscribe link. A change to Confirmed and a purely internal note still trigger nothing.

Affected customers now learn about a report the moment it is filed

Until now the first email only went out with the first update. From now on the reporter (for a report filed via the customer portal) and the customers assigned by support who have notifications on receive a confirmation right when the report is created, letting them know it has been logged and that you will inform them automatically once there is news. The internal title stays protected: assigned customers without a customer-safe title see a neutral placeholder, and the reporter sees their own submitted title.

Bug intake with context

Recording a bug in the bug tracker is now complete: straight from a call or a support ticket, "Record bug" opens the intake form with company, contact and the call or ticket reference already prefilled. Also new are structured details following the official template (observed behavior, expected behavior, steps to reproduce, environment/version - all optional) and internal attachments: screenshots and files can be stored on the bug, and when starting from a ticket you can adopt existing ticket attachments by selection. Attachments and structured details are visible to your team only and never appear in the customer portal.

Email attachments keep their original name

When downloading an attachment from a ticket, the file is now saved under its original file name instead of the technical storage name. Umlauts in the file name are preserved.

Call details stay usable even when transcript data is faulty

When a call's transcript segments were stored in an unexpected format, the entire call detail view crashed with an error message - analysis, rating, notes and recording became unreachable as well. Now only the transcript section shows a notice in such a case; all other details of the call remain visible and usable. In addition, the application automatically sanitizes such faulty legacy data when delivering it.

Consistently "Company"

The CRM entity is now labelled Company everywhere in the German interface as well ("Unternehmen") - in lists, filters, columns, search, deal views, portal reports, product analytics and email variables. Previously the German labels alternated between two different words for the same record. Only the address fields on invoices and in the checkout keep their postal wording. Labels only - no data and no workflows change.

Straighten out existing calls with swapped speakers in one go

With new transcripts now assigning speakers based on the call direction, the older stock remained open: earlier transcripts still carried the previous AI guess, in which "Employee" and "Contact" could be swapped. Under CRM → Calls → Analytics the new "Speaker roles in existing transcripts" block shows how many of your existing transcripts still carry an unverified mapping - grouped into "direction present and contradictory", "direction missing" and "no speaker labels". A "Dry run" shows in advance how many calls a run would correct without changing anything; "Apply correction" straightens the affected existing transcripts based on the call direction (translation included), without re-transcribing and therefore with no AI costs. The correction is logged, requires write permission for calls, and only touches unverified transcripts - a second run does not flip already-corrected calls again. Genuine doubt cases (no recorded direction) stay flagged as "Speaker mapping unverified" and can still be corrected individually in the call detail via "Swap speakers".

Call transcripts assign the speakers correctly again

"Employee" and "Contact" were regularly the wrong way round in the transcript - names included. The transcript therefore stated literally the opposite of the conversation, which also skewed call analyses and every later quotation. The cause was that the roles were guessed from the conversation content alone. From now on the call direction decides: whoever answers speaks first - so on an outbound call the first voice is the contact, on an inbound call it is your team. If someone introduces themselves using the responsible employee's name, that evidence counts on top. When the mapping cannot be backed by evidence, the note "Speaker mapping unverified" appears next to the "Transcript" heading instead of silently asserting a wrong mapping. For existing calls there is a new "Swap speakers" button: it flips the roles throughout the transcript (translation included), can be undone with a second click, and is logged.

The English interface really does speak English in the CRM now

If you switched the language to English, several CRM areas still showed German labels - most visibly in the ticket detail view. Affected were the ticket sidebar ("Priorität", "Komplexität", "Fällig", "Abteilung", "Zugewiesen"), the split and merge dialogues including their explanatory texts, the snippet and template pickers in the reply box, the chat area, the email-rule editor together with all field and comparison labels, the picker in the condition row, the pipeline settings, the placeholders on the reputation page, the subscription flow diagram, and the tiles on the support overview and the sync health page. Those texts were hard-wired into the program and bypassed the language switch; they are now maintained in German and English. Nothing changes for the German labels.

Automatic ticket assignment and the workload overview run again

The "Round robin" and "Least busy" assignment strategies as well as the per-agent workload overview failed with a server error for every group that had members, leaving tickets unassigned. Both strategies distribute again, and the workload overview shows figures again.

Blocked numbers can be maintained again

On the CRM → Blocked Numbers page neither adding nor unblocking a number was possible. New is the "Block number" button above the list: you enter the phone number and a reason and can now block numbers for which there is no call at all. The entry is validated immediately, so an unusable number is never sent off. On top of that, roles holding the overarching CRM management permission saw no buttons whatsoever even though they are allowed to use them; that is fixed. If unblocking fails, you now get a message instead of nothing.

Cleaner lists and detail views without initials circles

Names used to be preceded by a colored initials circle - it has been removed everywhere in the CRM: from the contact list, the contact and company detail views, the deal list and the cards on the deal board, and the "Agent performance" report. The views show the name directly, so rows take up less horizontal space.

Notifications about new external reviews arrive again

When a new review came in from Trustpilot, Google, Capterra or the Amazon Appstore, it was stored, but nobody in the configured recipient list was told about it - neither by in-app message nor by email. The recipients you configured on the review source are notified again.

Search in activities works again

As soon as you typed a search term under CRM → Activities, the list answered with a server error instead of results. Without a search term the list behaved normally. Searching across subject, description, company and contact name returns results again.

The adoption cohort report shows figures again

The user-retention report aborted as soon as a calendar week contained any users at all - in practice, always. The report calculates and displays again.

The Gmail inbox processes incoming mail again

Syncing a connected Gmail mailbox aborted before a single message was turned into a ticket. From your side it simply looked as if nothing arrived from that mailbox any more. The cause was a faulty hand-over of the collected thread and sender identifiers to the database. Incoming messages are turned into tickets again and matched to existing threads and known contacts.

Unsubscribing from roadmap cards works again

Customers could subscribe to a roadmap card but never end the subscription: both the click on the card and the unsubscribe link in the email ran into a server error. Both routes end the subscription again.

"Known issues" returns to page 1 when the product changes

Customers who had paged to page 3 in the portal and then switched products saw an empty list, because the page number stayed put. Switching products now starts at the first page again.

Adoption: the code snippet for your shop is now called SCSAdoption

The snippet under CRM → Adoption → Adding it to your shop now goes by the name SCSAdoption instead of V3NDRAdoption. The old name stays on as a second name and points at exactly the same place. Snippets you have already embedded, and your own calls such as V3NDRAdoption('lang','de') on your pages, therefore keep working unchanged, even if you never swap anything out. If you are placing the snippet afresh anyway, please use the new name: the command overview on the same page already shows it. The address the snippet is loaded from has not changed.

Affected customers hear about bug updates

when you write an update on a bug report with a customer-facing text and/or set a new status, that information goes out automatically by email to all assigned and reporting customers. A purely internal note still triggers nothing, and every customer can unsubscribe per report.

Answers to your own requests arrive by email

whoever submitted a feature request is now informed automatically: when the request moves into review, when it is accepted and connected to a roadmap card, when it is declined with a reason, and when there is an official comment from SELLERLOGIC. You do not have to write a message for this. The notification is on by default and can be switched off in the portal profile with the "Notification about own requests" toggle.

Customer portal: "Known issues" is publicly reachable again

The public "Known issues" page of the roadmap portal wrongly asked for a sign-in and stayed empty for visitors who were not signed in. The cause was an access check scoped too broadly, which also covered pages that are meant to be public. The known-issues list and detail view are freely readable again, just like the public roadmap and the release archive. The visibility rules are unchanged: issues rated critical stay out of the public view until they are resolved, and personal areas (reporting an issue, "My reports", feature requests, voting, profile) still require a sign-in.

Feature requests can no longer slip into an impossible state

A declined request could afterwards be set to accepted without any roadmap card being linked to it. The lifecycle of a request is now fixed: Accepted arises only through the linking wizard, Declined only through declining with a reason, and both end states stay put.

Follow roadmap cards

signed-in customers can now follow a published roadmap card and choose separately whether they want to hear about status changes or about the release by email. One click on the card is enough, a second one ends the subscription. Every notification carries an unsubscribe link, and the new My subscriptions section in the portal profile lists all active subscriptions for removal. Without a deliberate subscription nothing is sent.

Help button points at the right page

On the requests page the help button led to the customer-portal manual page instead of the requests page. Both manual pages now have an unambiguous assignment.

Manage products yourself

The roadmap and known issues are structured by product, but products could not be created until now. The new Products tab allows creating, renaming, sorting, activating and deactivating. There is no delete, so cards and bugs already assigned keep their assignment.

New "Notifications" view in the admin

under CRM → Roadmap portal → Notifications you see who follows which roadmap card (filterable by card, customer, company and kind, with a CSV export of the subscriber list) and which notifications actually went out: event, template, language, recipient, time, status and, for failures, the reason. The page is for information only; there is deliberately no button to send anything. Read access to "Roadmap Portal" is enough to view it.

No duplicate sends

every notification that goes out is recorded. The same event never reaches the same person twice, no matter how often an action is repeated. A failed send is marked as such and retried with the next event.

Open panels on the bug board can now be linked

On the "Portal bugs" page, the detail panel and the panel for recording a report kept their state in memory only. A copied link opened an empty list for the recipient, and the browser's back button skipped straight past the open panel. Both panels now live in the address bar: a shared link opens the same view, and going back closes it again. Your filters and page number are preserved.

Portal emails are editable like every other template

the five new templates for sign-in, status change, release, request update and bug update exist in German and English under Settings → Email templates and can be reworded there. Sending always uses the language the customer selected in their portal profile.

Portal management: everything about the customer portal on one page

Maintaining the customer portal was split across two menu entries in two different areas. Both now sit together under CRM → Portal management, divided into the tabs Roadmap content, Feature requests, Bugs, Moderation and Products. The selected tab is stored in the address bar, so you can bookmark it and pass it on. Your existing bookmarks keep working and open the matching tab.

Re-importing the call list no longer fails with "Failed to fetch"

A re-import covering a large time window (a full day, say) ran long enough for the connection to be cut off in transit - the app showed nothing but an obscure network message, and whether anything had been imported stayed unclear. The run now stops by itself in good time and tells you how many calls out of how many were taken over, together with a note to fetch the remainder using a smaller window or via "Import entire history". That import runs in the background and is not time-limited. Calls already taken over are kept; the regular sync that runs every few minutes resumes exactly where it left off, so no call is lost. If the phone system does not answer at all, you now get a clear error message instead of a hanging display.

Release quarter instead of a date

For released cards you choose quarter and year, not a calendar day. The entry is mandatory for status Released, because the release archive is grouped by quarter.

Reported content becomes visible again

Customers could report posts, but the application had no place where those reports showed up. The new Moderation tab lists all open reports with reason and timestamp and lets you resolve them.

Reports about requests and comments are now guarded

When reporting a contribution, there was no check whether the reported item existed at all or was visible to the reporting person, and there was no upper limit. Both are in place now: only what you are allowed to see can be reported, and at most 20 reports per day and account are possible.

Roadmap cards can finally be created in the application

Until now cards could only be created directly in the database, which is why the roadmap in the customer portal stayed empty. The new Roadmap content tab brings a list and an editor: customer-facing title and description, product, status, release quarter, plus a switch that adds a card to the roadmap or withdraws it again. Publishing requires a customer-facing title and description so no half-finished card reaches the outside.

Signing in to the customer portal now actually works

the 6-digit sign-in code was created but never sent, so in practice nobody could get into the portal. Your customer now receives the sign-in email immediately, with the code and a link that signs them in directly. The code is valid for 15 minutes and can be used only once. If sending fails for once, the code stays valid and can be requested again.

Status filter in "My reports" in the customer portal

The portal already evaluated a status filter from the address bar but offered your customers no control for it. There is now a select field for the processing status above the list; the selection goes into the address bar and can be shared. An unknown value in the address bar is silently ignored instead of causing an error.

The customer portal stays usable when data is missing behind the scenes

If part of the roadmap portal was missing from a tenant's data store, the public roadmap, the release archive, the product list and "Known issues" all answered with a generic server error - so for visitors, a gap in the master data looked like a complete outage. Those pages now show an empty list, and detail pages report "not found". Your operations team is not left in the dark: the fault is still logged and appears in the platform's error overview. All other faults (a dropped connection, for example) are still reported as errors and are never silently presented as "empty".

The customer portal's error page speaks English too

The fallback page shown after an unexpected error was hard-wired to German. It now follows the language selected in the portal.

The help button in the roadmap portal opens the right guide

On the "Roadmap portal" page, the "?" button led to the customer-portal guide instead of the guide for the review queue. The two manual pages are now cleanly separated and cross-linked.

Ticket routing now takes language into account

Assignment used to go by skills alone - language was part of the calculation but had no effect, because no member of staff had any languages recorded. Language is now a genuine exclusion criterion: anyone who does not speak the required language is neither suggested nor auto-assigned, whatever their skills. In the “Assign agent” area you set the ticket's required language (pre-filled from the automatic detection, correctable at any time) and use “Show agent languages” to record which languages the assigned member of staff speaks. Anyone with no languages recorded is still suggested - recording languages narrows the pool, it never locks anyone out. If nobody speaks the required language, the mask says so along with the number of staff skipped, and the ticket stays assignable by hand. For existing staff the languages are taken over once from the personnel record. Which languages are selectable is not built in and can be recorded in the support settings.

The call detail no longer flickers while loading

While a translation ran in the background - for transcripts sometimes for minutes - the whole page flickered. Two effects combined to cause it: the detail panel lays a blurred veil across the entire page, and the pulsing loading bars on top of it forced the browser to repaint everything behind that veil on every single frame. The detail panel now shields its own rendering, and the loading bars no longer pulse. The spinner in the line above still shows that something is running.

Calls: AI analysis and transcript now appear fully translated instead of switching language mid-view

When opening a call while using a different interface language, the AI analysis first appeared in the call's language and then visibly switched; the transcript stayed in the original language entirely. Both sections now show a loading indicator while the translation runs in the background and appear only once they are complete. In addition, the transcript is now translated as well - timestamps, speakers and jumping to a point in the conversation all keep working. Use "Show original" to return to the original wording at any time; translations are stored and shown instantly the next time you open the call.

Calls: internal routing numbers no longer appear as handler

Calls that only passed through an internal routing number (e.g. the dial-in number for English-language calls) wrongly showed that number in the "Handler" column. Such numbers are no longer displayed there; short internal extensions (e.g. "1028") remain visible as a hint when no name can be resolved.

Calls: the "Handler" filter now lists all handlers

In the call list (CRM → Calls) the "Handler" (Bearbeiter) filter previously showed only some staff, and picking one often returned no matches. It now offers every handler actually assigned to calls - including handlers imported from the phone system (3CX) - and the selection reliably filters to exactly that person.

Review links with identifiers in the address are now accepted

When adding an external review source (CSAT → External Reviews), certain Google Maps links were wrongly rejected as a "suspicious request" because their technical identifiers looked like an attack pattern. The security check now distinguishes more precisely; genuine attack patterns are still blocked.

Review requests are now delivered reliably - optionally with all platforms

Emails triggered via "Request review" previously got stuck in the queue unnoticed and were never sent; this is fixed, and a delivery failure now shows up immediately in the log and the UI. New: with several review sources configured you can pick "All platforms" (the default) - the email then lists the review links of all linked platforms. The request is written in German or English automatically, matching the contact's country.

Shared ticket links with filters work again

If a filtered ticket view was bookmarked or sent to a colleague, the page could fail with an error whenever a filter was set to "All". Such links now open correctly - "All" simply means "no filter".

Block/unblock a caller right from the call view

The "Block as Spam" button now sits at the bottom right of the call detail and reflects the current state: if the number is already blocked it turns into "Unblock" (with a confirmation), otherwise it stays "Block as Spam". You can see at a glance whether a caller is blocked and lift the block from the same place.

Bug tracker: record bugs, assign customers, publish "Known issues"

Under "CRM → Known issues" you record reported bugs and assign several affected customers (company and optional contact). Using the update composer you write updates with a separate customer-facing text and internal note, and set the status. Selected bugs are published to the public portal page "Known issues" (only with a customer-safe title). Bugs classified as critical stay hidden from the public until they are resolved - only affected customers see them confidentially in "My reports". In the customer portal your customers report bugs themselves and follow their reports; notifications for affected customers can be unsubscribed per report.

Call AI analysis now in your language

A call's AI analysis (summary, topics, buying signals, objections, follow-up reason) has so far been generated in the language of the conversation. It now appears automatically in your interface language: if the conversation language differs, the text is translated once when you open it and cached; a "Translated from …" hint shows the original language, and one click shows the original. If your language is not (yet) available, English is used as a fallback. Value-neutral fields (sentiment, intent, quality) were already translated.

Customer portal: public roadmap & passwordless sign-in

Your customers can now use a dedicated portal to view the published product roadmap (grouped by status) and the release archive (by quarter) - the roadmap is visible without signing in. For personal features a customer signs in via a sign-in link: they receive a 6-digit one-time code by e-mail (valid 15 minutes), with no password. In the profile they can set display name, language and notifications about their own requests, and export their own data.

Customer portal: votes & comments only for published roadmap cards

Signed-in portal customers could fetch the votes and comments of a roadmap card even when the card was not yet published (a draft). Fetching is now restricted to published cards - just like voting and commenting already were - so unpublished cards are no longer visible to customers. Nothing changes in your usual workflow.

Number blocking now reliably reaches the phone system

Blocking a number via "Block as Spam" is now correctly forwarded to your 3CX phone system - previously the block stayed stuck in "pending"/"error" due to a wrong API call and never took effect on the system. Blocked numbers are now submitted consistently in international format (e.g. +49…) so the system recognises them reliably.

Roadmap portal: feature requests, voting & comments

Signed-in portal customers can now submit feature requests (with selectable visibility: private/company/public), vote on ideas and roadmap cards (Critical/Important/Nice to have) and join the discussion. In the admin area under CRM → Roadmap portal you review submitted requests (filter by status, visibility and company), link them to exactly one roadmap card via a wizard (three outcomes; votes are transferred to the card), decline them with a reason and comment officially as SELLERLOGIC. Permissions: "Manage/Moderate Roadmap Portal".

Safer rendering of email and product content

Displaying HTML content in the ticket view (incoming emails, translation preview), the activity timeline, help articles and the product preview has been hardened: active content (scripts and the like) is reliably removed before the text is shown. Nothing changes visually for you - content appears as usual, just safely.

Block callers as spam (3CX blacklist)

From the call detail view you can now block a number with a single click on "Block as Spam" (with a mandatory comment). The number is added to the blacklist of your 3CX phone system and additionally recorded for auditing - with a comment, the blocking employee and the timestamp. Under "Calls → Blocked Numbers" you manage all blocks and can unblock numbers again (the history is retained). If 3CX is temporarily unreachable, the block is still saved locally and can be re-synced later. Permission: "Manage telephony".

Company timeline: subscription events now in chronological order

In a company's timeline (tab "Timeline", filter "Subscriptions"), subscription events did not reliably show the newest entry on top - active subscriptions floated up because of their future end date, and entries appeared grouped by product. The timeline now sorts subscription events by when they actually occurred (newest first). The date shown per entry (the subscription's start/end date) is unchanged.

New review source: Capterra

Under "External Reviews" → "Sources" tab you can now add Capterra as a source. Just paste the Capterra product address (e.g. capterra.com.de/software/1077726/SELLERLOGIC) - the product identifier is picked up automatically. Individual reviews are fetched via a secured browser request, as with Google Maps.

Adoption metrics explained

The Adoption Analytics, Content Analytics, Guides and Surveys pages now explain how the HEART score, completion rate/guide health, quality indicator and NPS/CSAT scores are calculated - including value ranges, thresholds and concrete improvement tips.

AI reply drafts now know the official help pages

The draft button in the ticket reply now additionally draws on the help-center articles (support.sellerlogic.com, all languages). Matching articles feed into the suggestion and appear beneath the draft as clickable sources; where useful, the suggested reply links the article directly for the customer. The knowledge base is synced with one click in the support settings ("AI" tab).

Calculated values explained

The CRM manual pages now explain exactly how the lead score, customer health & adoption, CSAT/NPS, call and ticket quality, MRR/ARR/churn, the routing score and the sync error rate are calculated - with factors, ranges, refresh timing and concrete levers to improve them.

Call search finds phone numbers in any format

The search under "Calls" (list and analytics) now finds numbers regardless of notation - "+49 176…", "0049176…", "0176…" or with spaces/dashes - and also supports partial search (e.g. just the last digits). For outbound calls the dialed number is now searched too, and an error that temporarily made the search return no results at all has been fixed.

Company view: "Products & Subscriptions" now shows every subscription plan

Besides the products in use, the tab now also lists each individual subscription plan - including trial and freemium plans without revenue, which could previously be missing. Every plan shows its type (Trial/Freemium/Paid), its period, and a "Scheduled" marker for follow-up plans that only start in the future. In the history, "Subscription started" entries now carry the plan name and the actual start date, so multiple plans of the same product can be told apart.

From a contact straight to the company

In the contact detail view, clicking the company name now opens the company detail view as an overlay - without leaving the current page. The reverse direction (company → contact) already worked this way.

Groundwork for the roadmap portal and bug tracker

SELLERLOGIC SCS is preparing a customer portal where SELLERLOGIC customers can view the product roadmap and report bugs; support can record bugs and tag the affected customers, who are then informed about updates. This release ships the technical groundwork (data model, the new “Roadmap Portal” and “Bug Tracker” permissions, product list). Nothing changes in the interface yet - the screens follow in upcoming releases.

Owner filter on calls now available for all roles

Under "Calls" → "More filters", the "Owner" dropdown was previously empty for staff members without team-management rights. The list is now populated for every staff member with CRM access; if it ever fails to load, a hint appears instead of a silent empty list.

Review links & "Request review"

Every review source (Sources tab under External reviews) can now store its public review link - the URL where a customer leaves the review (Google, Trustpilot, Amazon App Store, …). All stored links are visible at a glance on the source cards. New on the contact: the "Request review" quick action sends the contact a friendly email with the review link of the selected platform; the send appears in the contact timeline, and SCS asks first before sending again within 30 days.

Tickets are now truly auto-assigned

New support tickets automatically get an owner - based on skills, language and current workload. A technical defect had silently prevented automatic distribution until now. Also new: in the support settings ("Routing Rules" tab) you define an agent pool - only these staff members receive tickets - and "Assign all open tickets now" distributes the existing backlog in one click (oldest first, max. 200 per run).

Work on tickets without a language barrier

Every staff member can now read a ticket's entire conversation in their own interface language with one click (translate icon in the conversation header) - each message carries a "Translated from …" note, and previously translated content loads instantly. Simply write replies in your language: if the customer's language differs, SCS automatically shows a preview of the translated reply before sending ("Send translated" / "Send original").

CRM: modernized, unified controls

Buttons, input and select fields, toggles and tables across the entire CRM area (Tickets & Support, Pipeline, Calls & Analytics, Product Adoption, Reputation & Automation) now use the shared system building blocks. The look is more consistent; behavior and features are unchanged.