Automatic drafts in tickets
Leave a ticket and pick up your reply or internal note later. Situnio saves the draft and its attachments in your account.
What changes in Situnio and its WordPress connector, date by date. The connector updates itself on your sites.
Leave a ticket and pick up your reply or internal note later. Situnio saves the draft and its attachments in your account.
With “Send later”, choose tomorrow at 9 am or pick a date and time in your account’s time zone. Open the ticket to edit the reply or cancel the send. If the client writes in the meantime, delivery is paused.
The “Emails” tab of the site page holds the settings, the test email and the emails sent per day. Client reports get an “Email sending” section: emails sent and failures over the period, with a calendar of how many emails went out each day.
The list can be filtered by tag, status or sending service to pick the sites of a bulk action. Failing sites come first, with the server’s full answer and its likely cause. The alert clears as soon as an email goes out correctly, and a failure from before a change of service no longer triggers it.
Free: choose for each site an SMTP server (your domain’s mailbox) or your Brevo, Mailjet, Postmark or Scaleway account, through their API or over SMTP. Forms, orders and passwords no longer go through the host’s mail() function, often marked as spam. Situnio checks the connection from the site before turning it on, sends a test email and counts sent emails and failures, with an alert if emails stop leaving. FluentSMTP is taken over as is (its key stays on the site), then deactivated, and comes back if you turn sending off. Situnio Connector 1.33.0, which updates itself.
Your clients find all their requests in a portal under your name, with no mention of Situnio: the list, each request’s thread with its attachments, replying, opening a new request and “My request is resolved”. No password: a login link is sent to them by email. Everyone only sees the exchanges they wrote or received, never your internal notes; a person on a client record can follow all of their company’s requests. A “Follow your request online” link is added to your emails. Open it in the ticket settings, one portal per identity.
Your logo shows at the top of the client portal. For people on a client record, a “My sites” page shows, as you choose, their sites’ availability (Monitoring pack) and the PDF reports you sent them (Client reports pack). On a ticket, you see when the client opened it in the portal, and whether they did so after your last reply.
Below each reply, the email quotes the previous exchanges with the customer, newest first: they get the whole thread, even if they forward the message to a colleague. Your internal notes and messages from another requester never appear there. When the customer replies, only their new text goes into the ticket.
On a backup’s page, “Deploy to new hosting” is now a button, right below the restore. Once started, the deployment shows each step (temporary file, server check, restore with the number of files, connection to Situnio) and updates on its own. If the new site does not respond properly at the end, the deployment is marked “Done, needs checking” with the error. The backup’s page shows the latest deployment.
When the Security pack firewall was active on the original site, a clone or deployment to another site on the same hosting could show “There has been a critical error on this website”: the clone loaded the original site’s connector. Restores and deployments now fix this file, and a critical WordPress error is explained in plain words instead of showing its HTML code. Situnio Connector 1.32.2, which updates itself.
On the Team page, a member can be shown only the tickets of some of your identities, for example someone who only looks after your second business: list, search, dashboard, customer records and notifications only show those, with or without a site. The same choice exists when inviting.
In the ticket settings, “Send from your own address” connects your sending (SMTP) server: replies and acknowledgements go out from your address and are signed by your domain. Each identity can have its own. A test email checks the server before it is used; if it refuses a message, the reply stays in the ticket with the error and is never sent from another address. Also: canned replies reserved for one identity, and on a customer’s record, the identity their tickets go out under.
Do you run several businesses, each with its own name and email address? In the ticket settings, “Your identities” adds up to two in addition to the main one. Each has its own receiving address, name shown to customers, language, signature and acknowledgement. Their tickets arrive in the same list, with their colour tag and a filter, and your replies always go out under the name of the ticket’s identity, never with another one’s signature. Everyone can write one signature per identity.
A client wrote twice, or two people report the same problem? “Merge with another ticket”, in a ticket’s column, or the checkboxes of the list bring the tickets together into one: messages, notes and attachments move to the ticket you keep, sorted by date. The old number leads to the ticket you keep, and a client who replies to an old email lands there too. Another requester is copied on replies only if you choose so. Nothing is sent to the client.
After starting a restore or a clone, the destination site’s page shows each step: files, database, address replacement for a clone, then the site check, with the number of files and queries. At the end, Situnio opens the site’s home page: if it does not respond properly, the restore is marked “Done, needs checking” with the error, instead of a plain “done”. The backup’s page shows the latest restore with a link to its progress.
The Backups tab of the site page now shows a calendar: each day is coloured according to its backups (full, differential, failed, missing). Clicking a day shows its backups and the one that keeps the site as it was at the end of that day: when a client asks for “Friday’s backup”, it is often Saturday morning’s. Backup dates also show the day of the week.
The Backups section of PDF reports now shows a calendar for each month of the period, day by day: full, differential, failed or missing backup. Quarterly reports have it too: until now, the strip of days only appeared for periods of two months or less.
WordPress.org sometimes announces a newer translation than the file it sends: it installs, then comes straight back. Situnio now notices this right after installation: the line turns to failed with the note “Still offered after installation”, the software, the language and both dates. Hovering over a site on the Updates page shows which plugins are concerned for each language. Requires Situnio Connector 1.32.1, which updates itself.
Several pending translation packs often concern a single language. The Updates page now shows the language or languages concerned under each site (for example “French (France)”), with the number of packs per language on hover, and the site’s page lists them next to “Translations”. Requires Situnio Connector 1.32.0, which updates itself.
Connector 1.31.1 strengthens SEO rendering, Markdown document privacy, user management permissions and HTTPS verification. Custom proxies must be declared as trusted relays; Cloudflare remains recognised automatically in its dedicated mode. Old SEO caches are invalidated and the static cache is rebuilt.
WordPress installs some updates by itself, with no backup beforehand and no site check afterwards. The Updates page gets a “WordPress automatic updates” section: WordPress patches, new versions, plugins, themes and translations, each left to WordPress or turned off. A default setting applies to every site; it can also be changed for the ticked sites or those of a tag, and on each site’s page. The setting is applied right away, and synchronisation catches up on a site that was not responding. Situnio Connector always keeps its own patches. Requires Situnio Connector 1.31.0, which updates itself.
A plugin, theme or WordPress updated by WordPress itself, or from its dashboard, is now recorded in the site’s update history, marked “In WordPress”. Situnio spots it at the next synchronisation: the date is when it noticed. Client reports count these updates, with a note about their date.
A plugin present on dozens of sites no longer stretches the page: only the first twelve are shown, the rest expands with a click, along with the share of your sites concerned (“All your sites but 2”). Two sites with the same name are told apart by their address. Situnio Connector, which installs itself, leaves the table and the counters (menu, site list, dashboard): it has its own collapsed line, with a button to install it right away.
Before you can browse a backup’s files, Situnio reads the table of contents of each of its archives. An archive slow to come back from the storage could stop everything without a word. It is now dropped after a few dozen seconds and read again, and the preparation resumes where it stopped instead of starting over. The page follows the progress live, without reloading: archives read, percentage, time since the last one, and a warning if an archive takes longer than expected.
A site’s Comments page gets a Settings card: comments open or closed on new content, pingbacks, mandatory approval, automatic closing of old content, applied on the site right away. A button closes or reopens the comments of every post and page already written, and the all-sites page does the same on the ticked sites or those of a tag, in the background. Every morning, as long as comments are waiting, the members who moderate receive an email summary (can be turned off from the page). Client reports gain a Comments section, to tick: received, published, spam, per day. Requires Situnio Connector 1.30.0, which updates itself.
A new, free Comments page gathers the pending comments of all your sites: approve, mark as spam, move to the trash or delete, one at a time or in bulk, even across different sites, and reply without opening WordPress. Each site has its own page with tabs (pending, approved, spam, trash) and a search. The number of comments to moderate shows in the menu, on the site page and on the dashboard. Nothing is copied to Situnio: comments are read from the site, and the connector never sends the author’s IP address. A new “Moderate site comments” permission decides who can act.
When WordPress could not install a language pack (failed download, language file not writable on the hosting), the translation update was still reported as successful, then came back at the next sync with no explanation. It now shows as failed, with, for each pack, the plugin or theme concerned, the language and the reason given by WordPress. Packs that were installed stay installed; only the failed ones remain to do.
On some hosting, creating WebP copies stopped at the first large photo with an HTTP 503 error: the host cut PHP off after it asked for too much memory to decompress the image. The connector now caps the conversion’s memory and sets aside an image too large for the hosting, which keeps being served as it is. Original photos that WordPress has already scaled down, never shown in pages, are no longer converted when they are too large. And if the site still cuts off along the way, the conversion resumes on its own as long as it makes progress.
Forms built with JetFormBuilder (version 3 and later) are now checked like the others, whether they submit with or without a page reload. Nothing to set up: once the connector is up to date, JetFormBuilder appears under “What is covered” on the site’s Anti-spam page, and its submissions count in your figures. Submissions received through the REST API, which come from an integration rather than a visitor, are not checked.
When the site had finished its integrity scan but its last reply got lost on the way (timeout, connection drop), Situnio asked for the next step, the site answered “no scan in progress” and the site page showed a failure, even though everything had been checked. The connector now keeps the last result and sends it again in that case. And when a scan really fails, the page shows the first error met, the only useful one, rather than that follow-up message.
In a report’s “Where attacks come from” section, the “Attacks across all your sites” option is no longer just a sentence: after the site’s map, it adds its own figures (attacks spotted, share from rented servers, countries of origin), its map and its main countries, without naming any site. The total is repeated in the summary. When those attacks are only the ones on the report’s site, a single sentence says so.
In the ticket settings, the “My signature” card lets everyone write their own, with the same editor as a reply: bold, links, a logo or a photo. Your replies to clients go out with your signature, a colleague’s with theirs. The shared team signature remains for members who haven’t written their own.
A new page brings together your sites’ whole security log over 7, 30, 90 or 365 days. By address, it ranks the IP addresses that come back the most, with their country, provider, the usernames tried, the number of lockouts and refused logins and the sites targeted, and offers to block them. Logins refused during a lockout are now counted address by address: you see right away who drives the counter up. Event by event, it lets you go back through the whole log. Filters by site, type, country and origin, and search by IP address or username. Open it from each site’s Security tab and from the Security page.
A logged-in administrator or editor has never been filtered by the firewall. But an external tool, an assistant or a script using the REST API with an application password was treated as a stranger: tracking code added to a site that way was refused as an attack. WordPress now checks those credentials before the firewall decides, and the firewall steps aside for the same accounts. Wrong or missing credentials are filtered as before.
In the security log, an address already blocked or allowed shows its state (until when, on this site or everywhere) with “Remove from the list”, instead of the buttons. An address that comes back after its block ends is offered for 30 days, then 90, with a reminder of the previous blocks.
An automatic send can use its appearance’s sections: ticking a new section in the appearance then adds it to every send that follows it. For existing sends, “Edit several sends” adds or removes sections, makes them follow their appearance or changes the appearance, on all the ticked sends.
A site’s report can show on a map the countries its attacks start from. Rented servers (Amazon, Google, OVH…) are left out, because their country is that of the data centre, not the attacker’s; their share is stated plainly. Optionally, a line sums up the attacks across all the sites you protect, without naming any. On the Security page, the map also opens without hosting networks, with a choice to show them alone or everything.
When a site receives at least ten times more malicious requests than usual in one day, you get an email with the countries of origin and the most active address, grouped if several sites are hit at the same time. The alert stays on the Security page, the site page and the dashboard for 48 hours.
The Security page places the attacks caught on your sites on a world map, over 7, 30 or 90 days, with the most active countries and networks and the share coming from servers or VPNs. Addresses targeting several of your sites are listed separately, with a button to block them everywhere for 7 days.
In the security log and the address lists, each IP address shows its flag, country and provider (Orange, Vodafone, OVH…), looked up on our own server with no outside service. A network of servers, VPNs or relays gets the “Hosting provider” tag. Administrator logins are compared with the account’s previous ones: a new country, a hosting network or a new provider triggers an alert, with the country and provider in the email; a new address from the same provider, such as a home router whose address changes, is only noted in the log.
From the statistics list, tick the sites whose tag is missing and start the installation: each site receives the ID of the Analytics property linked to it, the first ones right away, the others in the background. The result shows site by site in the Tag column: installed, not yet visible, or refused with the reason. A site that already carries another tag is only installed with “Install anyway”.
When you schedule automatic sending for a site linked to a customer record, its primary contact is already entered as recipient. The other people on the record can be added with one click, and the field searches your customer records and known requesters, as for a new ticket. The same help applies when sending an existing report.
The New ticket window offers “Attach files”, like replies: one or more files go out with the first message to the customer, or stay with the internal note. If sending is refused (file too large, invalid copy address), the window reopens with what you had entered.
Each ticket sits on a clear line: requester with initials, subject, customer and site as chips, status and unanswered delay, assignee, last activity. A new message from the customer stands out, as does a customer waiting for over 24 h. At the top, the useful figures: to handle, unanswered for over 24 h, waiting for the customer, closed over 30 days.
Monitoring, Security, Anti-spam, Compliance, SEO, Performance and Reports now show each site with its preview (or its initials), its name and its address, like the sites list. Rows are more spacious and still open with one click.
Requests from the same IP address on the same site now take a single line: “8 requests blocked”, the rules hit as chips, each request’s detail folded away, the “Block 7 days” and “Allow” buttons shown once. Administrator sign-ins and login lockouts follow the same layout, on the site page and on the Security page.
On the Backups page, each site sits on a clear line: schedule on one line, last backup as “… ago” with its exact date, space used with a gauge, status and buttons aligned. A site whose daily backup is more than two days old stands out in orange.
Type a few letters of a name in the phone field: it suggests the people and main numbers from your customer records, mobile and landline separately. A click or Enter calls right away. A few digits also find the record that holds that number.
Calls are grouped by day, each showing its direction and outcome at a glance, the person, their customer record and their site. At the top, the figures for the last 30 days: calls, connected, time on the phone, numbers to call back. Recordings and voice messages play in a cleaner player, with playback speed. The same layout on the customer record, where a call without a note now counts as the last interaction, as does a ticket.
The integrity scan now recognises known malware families (webshells, backdoors, spam scripts, injections) thanks to the Linux Malware Detect signatures, refreshed every day: patterns found in code and checksums of known malicious files. A recognised file is reported with its family name, on the site page and in the file review. The signatures are sent to the site when the scan starts. Connector 1.26.0 installs itself.
When the audit reports that the content of the media folder is shown as a list, the “Protect folder” button adds “Options -Indexes” to that folder’s .htaccess. The folder is checked from the outside right after: if the server rejects the rule, a second form is tried, and the file is restored if nothing works or if the server ignores .htaccess.
Some plugins exist as a free version on WordPress.org and a paid version under the same identifier, with different numbering (wpDataTables Lite 6.x and wpDataTables Premium 7.x). A vulnerability of the paid edition was then reported on the free one. Situnio now compares the name given by the vulnerability database with the version published on WordPress.org: a “Premium” or “Pro” vulnerability is no longer kept when the installed plugin is the WordPress.org one.
The database scan flagged as “injected code” the detection rules stored by some security plugins (Defender, Anti-Malware Security): they describe precisely the patterns a scanner looks for. These options are no longer scanned, and alerts already raised about them disappear at the next audit. Connector 1.25.3 installs itself.
With Twilio, two account settings: record calls (both voices, as soon as the call is answered) and voicemail when nobody answers, with an announcement in the language of the account’s country. Situnio fetches each file, keeps it encrypted, then deletes it from Twilio. A voice message stays “to call back”.
A call from a number not yet known stayed without a client, even after the number was added to a client record or a contact. Saving the number now links its past calls, with their note, and calls already logged are linked too.
If call recording or voicemail is turned on for your Zadarma PBX, Situnio fetches every recording and every message left. They can be played in the call log, on the client record and in the phone, and downloaded as MP3. A voice message stays “to call back”. Files are kept encrypted for 30 to 365 days, as you choose.
With only the extension password, the phone could make calls, but Zadarma did not pass incoming calls on to it: callers heard that the person was unavailable. Enter your Zadarma API key and secret in the account: the phone then connects the way Zadarma’s web phone does and receives calls.
Paste the address given by Situnio into your Zadarma PBX call notifications, together with its API secret: every call is then logged, even if nobody has Situnio open, or if it was answered on a desk phone or forwarded to a mobile. An unanswered call becomes “to call back”, and calls made from another device on the PBX show up too.
As soon as you have a line, the phone sits in a bubble at the bottom right of every page, so you no longer need to keep a window open. Calls ring as long as a Situnio tab is open: only one tab connects to your phone system, the others show the same phone, and you answer from the one you are looking at. During a call, the tab carrying it opens its links in a new tab so the call is not cut off. The separate window is still available.
The suggested Zadarma settings targeted SIP lines without a PBX and turned internal extensions away (logins like 123456-100). They now use the pbx.zadarma.com domain and the PBX WebSocket server, both editable, and dial numbers in national format. A Zadarma account you already saved keeps its values: edit it to change them.
In a new ticket, the email field searches your customer records and the people who have already written to you: choosing one fills in the name, the customer and the site. Choosing a customer makes its main contact the recipient, and you can copy other people right from the start. In a ticket, “Reply” and “Reply all” choose who receives your reply, the right-hand column shows who is in copy, and the thread shows who the customer wrote to. If you redirect your own address to Situnio, enter it in the ticket settings: “Reply all” then includes everyone the customer wrote to.
The Updates page now handles three sites at the same time, still one update at a time on a given site, then checks each of them. A bar shows how many updates are done, the time left, what each site is doing and what failed. Pending language packs also have their own section there, Translations, and are part of “Update all”.
Application passwords (REST API) are now subject to the same attempt limit as the login form. Behind a proxy set to X-Forwarded-For, the visitor’s address is read so that they can no longer choose it themselves. A local or private address is never blocked or banned any more: without a proxy setting, every visitor shares it. The firewall now inspects every parameter, including those named “token” or “secret” (never logging their content), long values in full, and bans IPv6 addresses by /64 block. Connector 1.25.2 installs itself.
When an address blocked after too many password attempts kept trying, each refused attempt could be counted as a new failure, and the log showed a new block every few minutes for the same address. An attempt during a block is no longer counted, and several simultaneous attempts now give a single event. Connector 1.25.1 installs itself.
On the Performance page, tick sites (or choose a tag) to turn code optimisation, the static cache or WebP images on or off in one go. Each site goes through the same checks as from its own page: a competing plugin or an unsuitable server only gets that site refused, with the reason on its row, and optimisation is turned off again if the home page stops responding. The table now also shows the state of each site’s WebP images.
The “Link several sites” button suggests, for each site, its Google Analytics property and its Search Console property based on its address, then on its name when the address is not enough (changed domain, property without an address). Sure suggestions are told apart from those to check, each list can be searched among all your properties, and a single click saves the ticked sites. Two gauges and new filters show the sites without Analytics, without Search Console or without the tag. A site connected later is linked on its own if it has the same address as a property.
After clicking a button or a link, a bar moves across the top of the screen and the button spins until the next page appears. If the operation takes a while (an outside service such as Google, or one of your sites, slow to respond), a short message asks you to wait. The button can no longer be sent twice.
Several sites are now synced at the same time. A progress panel appears above the list: sites processed, failures with their reason, time left. You can leave the page: the sync continues in the background, and the progress picks up again when you come back.
A premium plugin or theme whose licence is not active is now detected on its own (“Licence required”) and no longer counts in pending updates. You can also ignore an update yourself: this version only, always on this site, or everywhere. These updates stay visible separately, leave “Update all” and the dashboard, and client reports list them with the reason. A known vulnerability is always still reported.
In the sites list, the “Features” view gives each feature a narrow column, grouped under its module name: it fits on the screen, without scrolling the table sideways. Hover a dot to read its status in full; on a phone, the site name stays visible while the table scrolls.
In the Banner and Owner tabs of a site’s compliance, a button copies the texts, colours, site owner and documents from Complianz, or those of the Elya Manage banner with its translations and blocking rules, without waiting for activation and without touching the plugin. If the Elya Manage banner is running, turning ours on takes it over and stops it, then turns it back on if you turn ours off: never two banners at once.
On the Team page, choose what each member can do: Read only, Support (tickets and clients), Member, Technician (all the work on sites) or Full, or tick rights one by one. Organization-wide settings stay with the owner and administrators, and only the owner grants one-click WordPress admin. Current members keep what they could already do.
On the Team page, each member sees every site or only some: chosen one by one, by tag or by client, and the list follows sites added later. They see nothing of the other sites, whether on the site page, in backups, tickets, calls, reports, the calendar or the dashboard, and they only get ticket notifications for their sites. The owner and administrators always see everything.
This plugin sets a cookie on every visit, which left every page to WordPress: the cache stayed empty. That cookie no longer prevents caching. Pages with a payment button, the thank-you page and the purchase history are still served by WordPress, as are pages a plugin asks not to cache.
A small icon follows the name of every WordPress.org plugin that has an update, on the Updates page, the site page and the plugin manager. It opens its changelog, limited to the versions released since the installed one, with a link to the full changelog.
Type part of a name, an address, a tag or a customer: the list narrows with every letter, ignoring accents. It can also be filtered by status (unreachable, with updates, connection to finish) and sorted (needs attention first, updates, oldest synchronisation, most recently added). Filters stay in the page address, and “Sync all” now only re-reads the sites shown.
Elementor’s Video widget loads YouTube through a script, with no iframe in the page: the video and its cookies got through before the visitor’s consent. It is now blocked like other external content, with the “Show the video” button. Lazy-loaded iframes (WP Rocket, LiteSpeed, Perfmatters…) are blocked too, and page caches are cleared once to take this into account. The scan shows the page where each cookie was seen.
The overview of a site page gains a “This site’s features” card: one row per feature (backups, monitoring, security, optimisation, cache, SEO, statistics, anti-spam, cookies, white label, reports…) with its state, its scope (whole organisation, default setting or set for this site) and the button to act; a simple switch works right there. The sites list offers a third view, “Features”, showing the same thing for the whole portfolio, one column per module. The Backups, Security and Monitoring pages open their shared settings with an “Organisation settings” button at the top of the page.
A name typed in a site page’s settings was replaced by the WordPress name at the next synchronisation. It is now kept; an empty field restores the WordPress name, which then follows the site.
A script in the media folder or an unknown PHP file at the root or in a plugin can now be deleted from the site page or from its examination, after confirmation. It stays in the file manager trash for 30 days, and it is put back automatically if the site stops responding right after.
On hosting where PHP already compresses pages, the static cache could send a page compressed twice, which the browser displayed as unreadable characters. The page is now compressed only once, and a cache build that would produce an unreadable page is cancelled.
Installed plugins and themes have their own tab, with known vulnerabilities flagged on their row and a button to the manager limited to that site. Performance & SEO, Anti-spam and Compliance have theirs too, and the site’s calls move to the Follow-up tab. The overview keeps one tile per module, and a badge on a tab shows what needs your attention.
The menu now groups pages into sections you can collapse (Maintenance, Visibility, Client relations, On your sites), and a collapsed section still flags what needs your attention. Your account, team, subscription and help open from your name, at the bottom. With Ctrl+K (⌘K on a Mac), jump straight to a page, a site, a client or a ticket.
A chart shows, over 7, 30 or 90 days, the requests stopped by the firewall and the refused logins, for all your sites and for each one, with the most targeted sites; the curve also goes into your client reports. Allow your agency’s address so it is never filtered, or block an address for 24 hours, 7 days, 30 days or with no limit, on one site or all of them, in one click from the firewall log.
Make and take calls in the browser, with your own carrier: Zadarma, Asterisk, FreePBX, FreeSWITCH, Wazo, Twilio or any SIP server over secure WebSocket. Callers are recognised from your client records, their record shows during the call, and your after-call note joins their log. A call log for the whole team, missed calls to return on the dashboard, and an optional Calls section in your client reports. The voice does not go through Situnio, and the whole team is included in the price.
A complete, free client book: company or individual, prospect, active or former client, address with postcode, city and country, VAT and company numbers, account owner in the team, contact people (first name, last name, role, phone, mobile), a log of calls and meetings, linked sites and CSV export. Tickets link up on their own, based on the sender’s address, one of the client’s domains or the site, and each record lists the client’s requests.
A client wrote to you directly? Forward their email from an address you have authorized: the ticket opens in their name, with their subject, text and attachments, and your note becomes an internal note. The acknowledgement can now be written in your own words, with the client’s first name, the ticket number or the site.
Drag an event to move it, pull its edge to change its length, including in your connected calendars (one occurrence or the whole series). Everyone chooses their time zone in My account: the calendar, dates in the app and your emails follow your time, and an appointment keeps its own for colleagues elsewhere in the world.
Besides the month, the calendar now shows a day, a week or a work week, hour by hour: click a slot to create an event there. Choose the first day of the week, your working days and working hours, and show or hide each calendar from its legend, with its color.
Connect your CalDAV calendars (iCloud, Infomaniak, Fastmail, Nextcloud and most servers): your appointments show up in the calendar and on the dashboard, next to the team’s, and update on their own. Create, edit and delete their events from Situnio, one occurrence or the whole series, without ever overwriting a change made elsewhere. Invite participants (your calendar server or Situnio sends them the invitation) and reply to the invitations you receive. Each calendar stays personal, unless you make it visible to the team.
Install Situnio on your computer, phone or tablet: it opens in its own window, from its icon. “Install the app” button in the menu, or “Add to Home Screen” on iPhone and iPad. No page of your account is kept on the device.
The login page of your clients’ sites takes your logo (or theirs), your colors and your background. In the admin area: your footer, the WordPress logo removed, a cleaner dashboard with a box showing your contact details. No plugin to install, site by site or by tag. If another plugin already customizes the login, nothing is forced, and the login page is checked after each change.
Your clients write to you from their site’s admin area: a button in the admin bar, a box on the dashboard, a menu item. Each request lands in your tickets, linked to the right site, with the page concerned, the WordPress and PHP versions, the theme and the active plugins. The form is in your name, is turned on site by site, for ticked sites or by tag, and replies go by email as for any ticket.
Each site can have its own frequency (including a new monthly one), start time, retention period (up to one year) and excluded folders, or not be backed up at all. Double Backup can also be chosen site by site. Only backed-up, or copied, sites are billed: you pay for what you sold to your clients.
After a restore, differential backups copied the whole site until the weekly full backup, because every file put back had a new date. The backup that follows a restore is now a full one, and the next ones are light again.
An expired or revoked rescue kit can be removed from the site page in one click. Its encrypted content is erased from Situnio the day after it expires.
The “To handle” list now sorts tickets by priority, then puts the customer who has been waiting longest at the top, with the delay clearly shown. Search also finds words in the text of messages and shows an excerpt.
The new Broken links tab on the SEO page lists, every week, the links in your content, menus and widgets that lead to a page that cannot be found. You see where they are, then fix them in WordPress or redirect them in one click.
Save your recurring texts in the ticket settings and insert them in one click, with the customer’s name, the site or the ticket number already filled in. People the customer copied are included in your reply, and you can remove them before sending.
The reply form is now at the top of the ticket, collapsed until you need it, and messages run from newest to oldest. In a long thread, the messages in between are collapsed and obvious status changes no longer appear.
A reply that could not be sent no longer moves the ticket to waiting for the customer. A rejected attachment stops the sending with a clear message, instead of the reply going out without it, and the text you wrote is kept.
The Monitoring tab of the site page now shows how response time changes over 24 hours, 7, 30 or 90 days. You can see at a glance whether a site is slowing down, and since when.
Situnio shows for each site whether its home page contains the Analytics tag. If it is missing, you install it in one click with the linked property’s ID, or by pasting Google’s code. A tag already in place is flagged, so that visits are not counted twice.
A site managed by Elya can import its SEO settings without turning off wp-agent: only its SEO stops at the switch, and it resumes if you turn the engine off. The Elementor Pro Breadcrumbs widget and the Yoast block stay visible after moving to the SEO engine.
Each backup can be copied automatically to a second provider, in another country. If the first location stops responding, you restore from the second, including your rescue kit and downloads. The copy stays encrypted and is checked again every week.
Choose up to 10 keywords per site, with their country, language and device. Their position is checked every week among the first 30 results, with history and changes, and included in your client reports. Situnio also shows whether the site appears on the Google map or in the AI Overview. For a local business, the check can be made from a city.
Each media library image gets a lighter WebP copy, created on the site itself. Compatible browsers receive it at the same address, originals are never modified, and Situnio checks that a visitor really receives WebP before leaving the feature on.
Analyze a site’s database, then remove its revisions, auto-drafts and expired transients, on demand or every month. You choose how many revisions to keep for each piece of content, and published content is never touched.
The Plugins page becomes Plugins & themes. Switch theme, install one from WordPress.org or by zip, update and delete, on one site or a whole group. If a theme brings the home page down, the previous one comes back automatically, and themes used nowhere are flagged.
Overview, updates, backups, security, monitoring, follow-up and settings: each topic has its own tab, and nothing has been removed. A badge shows what needs your attention, and links received by email open the right tab.
The address, FTP and database are checked one after the other before a deployment starts. The database is tested from the new server, and a wrong folder or password shows up right away, with nothing to retype.
The delete button at the end of a restore is readable again, and a window sums up what will be restored before the operation starts.
wp-config.php and readme.html can now be fixed from the site page: the permissions of the first are set, the site is checked right after, and the second is removed, including after a WordPress update.
Your clients see how things evolved over the period: the site’s response time per day, speed score on mobile and desktop, visits and Google clicks. Response times are now kept per day, including for a quarterly report.
A site’s page now summarizes each module: counters, trends, charts over 7 or 30 days, compliance status and missing addresses to redirect. Buttons have icons, and each section of a PDF report starts on a new page.
Connect a Google account with read-only access: each site’s visits, clicks and queries arrive with their history, with an alert if Analytics tracking stops or clicks fall. They also join your client reports.
The app, the public site, the documentation, the emails and the reports are now available in Polish. So are the cookie banner and the online withdrawal on client sites.
The app, the public site, the documentation, the emails and the reports are now available in Dutch.
The app, the public site, the documentation, the emails and the reports are now available in Italian.
The app, the public site, the documentation, the emails and the reports are now available in Spanish.
The payment page and the billing area now follow the language of your account.
Every feature explained step by step, with screenshots and a search that tolerates typos.
Support, pre-sales question, billing, partnership: pick the subject and your request reaches the right place.
Everything new in Situnio and its connector, date by date.
Changing a password now closes, without exception, other sessions, logins waiting for a code and old reset links. WordPress login links are strictly single-use.
A check your visitors never see, with no Google and no cookie: WordPress, Elementor Pro, Divi, Contact Form 7, WPForms, Fluent Forms and WooCommerce. Monitoring mode lets you check nothing breaks before anything gets refused.
A cookie banner that really blocks trackers, automatic scan, Complianz import, online withdrawal function and the official legal guarantee notice.
Daily PageSpeed measurements, code optimisation, static cache, full SEO with Rank Math and Yoast import, redirects and 404 tracking.
PDF reports in your own branding, several looks, automatic sending every month or quarter.
What needs action comes first, then the state of your sites and which site to look at first.
Activate, deactivate, update, install or delete a plugin across several sites at once, with a home page check after each activation.
Events per site, automatic deadlines (certificate, domain, end of trial), email reminders and iCal subscription.
Record the work done on each site and the time spent. It feeds into client reports.
Pricing with a calculator and a page for each pack.
The address given when connecting a site is now verified by a signed request, and failure limiting can no longer cut you off from your own site.
Backups encrypted on the site before upload, restore, cloning to another site, rescue kit when WordPress won’t start, differential backups and moving to a new host.
Alerts on known vulnerabilities, protections set for the whole organization, daily integrity scan, injected-content search and a firewall.
Home page checked every minute, email alerts, certificate and domain monitoring, public status page.
An email address to receive your clients’ requests, reply and link them to a site.
Email invitations, three roles, several organizations, TOTP app and recovery codes.
Code editor, search, chunked uploads, 30-day history; Elementor and WooCommerce migrations run from Situnio.
Organise your sites, keep instructions on their page and manage their accounts without ever seeing a password.
A new version on WordPress.org is detected for all your sites at once, and the connector updates itself.
Accounts and organizations, connecting a site without a WordPress password, one-click login, update tracking.
WordPress, plugins and themes updated from Situnio, premium included, with health check and rollback.
Rename or hide the connector, hide plugins, with a recovery link for each site.
One subscription per organization, one line per pack, free trials with no credit card.