Alerts and follow-ups
Copilot warns you when something worth your attention happens, without you having to open the app.
The alerts
- Out of stock on a product that sells.
- Falling sales compared with your usual days.
- Abandoned carts to follow up.
- Serious finding found by an analysis (a published vulnerability, for example).
You choose which alerts you want to receive, by email and in the mobile app. Every email carries a link to unsubscribe from that alert in one tap.
The nightly analysis and the Monday summary
Every night, at your store’s local time, Copilot records its state: stock and out-of-stock products, active and inactive product pages, pages without an SEO title or description, without an image or priced at zero, and the average price per category. It only reads what your store exposes, changes nothing and uses none of your requests. In My store, the 7- and 30-day trends are compared with the day before and with the same day the week before. The time zone is set in the alert settings; if you don’t set one, the one PrestaShop declares is used.
When an alert has a ready answer (set a stock level, deactivate a page that has no price, prepare a promo code), it shows it with a Prepare button. Preparing changes nothing in your store: the proposal waits for your approval in To approve. Only people allowed to edit products see this button.
On Monday morning, at your store’s local time, Copilot emails you a summary and keeps it in My store: what changed over 7 days, what it suggests, what it did. At most one a week; a link at the bottom of the email turns it off.
Notifications on your phone
In the mobile app, Copilot can also warn you with a notification, without you opening the app. The app only asks for the phone’s permission at the right moment — when you answer yes to the alerts, or after your store is first connected — never at startup, and only once.
Four sources, which you turn on or off one by one (in the app: Notification settings, under the alerts; on the web: the alert settings):
- the store’s alerts, after your “yes”;
- decisions to approve that Copilot prepared on its own (nightly analysis, scheduled job) — never the ones you just asked for in the conversation: you are already in front of the screen;
- the Monday summary;
- the support replies to your requests.
A few notifications a day at most, and never between 10 pm and 8 am, your store’s local time — except for a serious alert, which goes through at once. A notification only holds what you need to find your way: never the text of a support reply, never the detail of a change.
Approve in one tap. The notification for a decision has two buttons, View and Approve. Both open the app on the card, with the preview of the changes already unfolded; Approve highlights the approval button. Nothing is ever approved unless you have the preview in front of you and tap that button yourself.
A phone belongs to one account at a time; it is removed when you sign out.
Following up abandoned carts
Copilot spots abandoned carts, prepares the follow-up and shows it to you: who it goes to, with what text. Nothing is sent without your approval. Emails are sent from your store, with its sender address.
Standing issues: told once
Some findings describe a lasting state: an access key with wider rights than needed, a published weakness in your PrestaShop version, a forgotten debug mode, missing security headers. Copilot does not repeat them.
- Only once. The morning journal, the Monday summary, emails and notifications mention it the first time, then only if something new appears (a new weakness, new excess rights, a new version).
- Always at hand. In the app (My store) the item stays displayed until you dismiss it, with the Stop showing button.
- Dismissed, not lost. It stays available in the list of dismissed items, where you can restore it. If it changes, it comes back by itself with the note “New weakness: …”.
Severity, seen from your store
Severity is not that of a security expert: it measures what matters for your sales and your customers.
- Critical: it affects your sales or customers right now: store down, payment, publicly exposed data, an actively exploited weakness. Only this level triggers a serious alert.
- Important: to handle within the week, nothing immediate, for example a published weakness with no known exploitation, or a PrestaShop version that is no longer maintained.
- Minor: keep it in mind, for example an access key slightly too broad or a missing security header.
A published weakness with no known exploitation is therefore never “critical” for your store.