ReferencePlans and notifications
Notification catalogue
Nine events send a notification: a failed reply, a subscription nearing expiry, a page being connected, a page being disconnected, Facebook or Instagram access expiring, that access being restored, and an Instagram account being claimed by another AFP account. Each one is created in the app first, then copied to email and Telegram if those channels are set up and the matching setting is on.
Summary
Section titled “Summary”| Event | What raises it | Gated by | In app | Telegram | |
|---|---|---|---|---|---|
| A reply could not be sent | A reply you send from the inbox, or a reply on a comment, is refused by Facebook or Instagram | Expired page | Always | When set up | When set up |
| Your subscription expires soon | AFP checks the subscription and finds seven days or fewer left | Subscription ending reminder | Always | When set up | When set up |
| A page was connected | You link a page to your account | Page connections | Always | When set up | When set up |
| A page was disconnected | You disconnect a page, or another account takes the page over | Page connections | Always | When set up | When set up |
| Facebook access expired | A Facebook call fails with an error that means the access is permanently gone | Expired page | Always | When set up | When set up |
| Instagram access expired | An Instagram call, or a scheduled refresh, fails permanently | Expired page | Always | When set up | When set up |
| Facebook access restored | A Facebook call on that profile succeeds again | Expired page | Always | When set up | When set up |
| Instagram access restored | An Instagram call on that account succeeds again | Expired page | Always | When set up | When set up |
| An Instagram account was claimed | A standalone Instagram account you had connected is connected by another AFP account | Page connections | Always | When set up | When set up |
“When set up” means the channel has what it needs — a notification email address, or a linked Telegram chat — and both the master notification toggle and the event’s own toggle are on.
A reply could not be sent
Section titled “A reply could not be sent”- Raised by: a reply refused by Facebook or Instagram, sent from the inbox or published on a comment
- Carries: the platform’s own error message for the refusal
- Repeats: once per recipient, until the existing notification is removed
The most common cause is the page’s stored access no longer working, which makes every send on that page fail. Page permissions and tokens covers how to tell that apart and how to restore access.
Your subscription expires soon
Section titled “Your subscription expires soon”- Raised by: an access check on a subscription with seven days or fewer remaining
- Carries: how many days are left
- Repeats: once per day, and once per remaining-days value
The check runs when something you do needs an active subscription, not on a timetable, so the warning arrives the next time you use AFP inside those seven days.
A page was connected
Section titled “A page was connected”- Raised by: linking a page to your account
- Repeats: once per link
A page AFP links for you automatically sends nothing. Only a page you link yourself raises this notification.
A page was disconnected
Section titled “A page was disconnected”- Raised by: disconnecting a page yourself, or another AFP account taking that page over
- Repeats: once per disconnect
Disconnecting a page also switches off every campaign bound to it, so this notification and a set of suddenly inactive campaigns describe the same event.
Facebook access expired
Section titled “Facebook access expired”- Raised by: a Facebook call that fails with an error meaning the access is permanently gone
- Carries: the platform, the affected profile name, and where to reconnect
- Repeats: never — one standing entry per affected profile
A call that fails for a transient reason — a rate limit, a brief outage — raises nothing at all. The warning therefore means there is something to fix, not that a request happened to fail once.
Re-authorising the profile is what clears it. See Page permissions and tokens.
Instagram access expired
Section titled “Instagram access expired”- Raised by: an Instagram call, or a scheduled refresh, failing permanently
- Carries: the platform, the affected account name, and where to reconnect
- Repeats: never — one standing entry per affected account
As with Facebook, a transient failure sends nothing and is retried. Reconnecting the account through Instagram Business Login clears the expired state.
Facebook access restored
Section titled “Facebook access restored”- Raised by: a Facebook call on a previously broken profile succeeding again
- Repeats: once per recovery
Raising this also deletes the matching expired warning, so the panel does not keep showing a problem that has been fixed.
Instagram access restored
Section titled “Instagram access restored”- Raised by: an Instagram call on a previously broken account succeeding again
- Repeats: once per recovery
Also deletes the matching expired warning.
An Instagram account was claimed
Section titled “An Instagram account was claimed”- Raised by: a standalone Instagram account you had connected being connected by another AFP account
- Repeats: once per takeover
The account leaves your account when the takeover completes. The notification goes to the account that held it before.
Channels
Section titled “Channels”| Channel | Turned on by | Turned off by | Notes |
|---|---|---|---|
| In app | Nothing — always on | Nothing, beyond dismissing a notification | The panel loads the newest notifications 20 at a time |
| A notification email address in Settings | Clearing that address, the master notification toggle, or the event’s own setting | The address on your Facebook profile is never used as a fallback, so no address means no email | |
| Telegram | Linking Telegram in Settings | Disconnecting Telegram, the master notification toggle, or the event’s own setting | Delivered as plain text to the linked chat |
The in-app notification is created before any setting is read, so turning notifications off silences email and Telegram while the in-app record still appears. Dismissing a notification deletes it for good.
Linking Telegram starts in Settings: AFP gives you a link that opens a chat with its bot, and it stops working 15 minutes after it is issued. One chat is linked per account, not per Facebook profile.
What you can turn off
Section titled “What you can turn off”Four settings govern the nine events, under Settings → Notifications.
| Setting in Settings | What it covers | Can you change it |
|---|---|---|
| Enable Notifications | Email and Telegram for every event in this catalogue | Yes |
| Expired page | A reply that could not be sent, and all four access-expired and access-restored events | Yes |
| Subscription ending reminder | Your subscription expiring soon | No — shown as a required system notice |
| Page connected / disconnected | A page being connected, a page being disconnected, and an Instagram account being claimed | Yes |
Five events share the Expired page setting, so turning it off also silences the confirmations that access came back.
Three events share Page connected / disconnected, so turning it off also silences disconnects and takeovers — the two you are most likely to want.
Four further toggles appear in Settings and are marked Coming Soon: daily processed comments, monthly processed comments, new message alerts, and notification sound. Nothing raises them today.
Notification settings belong to the account. Where an account holds several Facebook profiles, the account’s own language and settings are used in preference to any one profile’s.
Who receives a notification
Section titled “Who receives a notification”On an account with no team, only you.
In a team, a notification can also reach teammates, chosen by whether they can act on it.
| Event | Also sent to |
|---|---|
| Your subscription expires soon | Every team member who can see billing |
| Any event carrying a specific page | Every team member with that page assigned |
| Everything else | Nobody |
Each recipient is gated by their own settings and receives the text in their own language. The person who triggered the event is never notified twice.
See Team roles and permissions and Limit a teammate to certain pages.
Duplicate suppression
Section titled “Duplicate suppression”Most events attach a reference to the notification they create — the recipient of a failed reply, or a subscription and a day. A second event with the same reference finds the first notification and creates nothing, which is why a campaign failing repeatedly on one recipient produces one notification rather than a stream.
Suppression works against notifications that still exist. A notification you dismissed, or one the 30-day cleanup removed, no longer suppresses anything, so a long-running problem can raise the same notification again later.
How long notifications are kept
Section titled “How long notifications are kept”Notifications older than 30 days are deleted once a day, across every account. Nothing else removes them, and nothing extends the window.
The badge on the bell counts the notifications from the current day, and which of them you have already seen is remembered by the browser you read them in. Opening AFP on another device shows the day’s notifications as unread again.
Account emails that are not notifications
Section titled “Account emails that are not notifications”| Sent when | Can it be turned off | |
|---|---|---|
| Verify your AFP account | You sign up with an email address, ask for the code again, or change your email address | No |
| Reset your AFP password | You ask to reset your password | No |
Both carry a code and a link back into AFP, and both go to the address you signed up with rather than to the notification email address. Neither is affected by notification settings.
- Notification text follows the language set on the profile, in the app and in email alike, and falls back to English.
- Email and Telegram delivery is attempted after the in-app notification is stored, and a failure on either is not reported back to you.
- Blocking the Telegram bot inside Telegram stops delivery without changing anything in AFP. Disconnect Telegram in Settings to stop it visibly.
- The settings screen offers more toggles than there are events in this catalogue. The four extra ones are marked Coming Soon and no event is mapped to them, so turning them on changes nothing.
- A reply on a support ticket sends no notification. It appears as an unread count on that ticket in your ticket list.
Related
Section titled “Related”- Page permissions and tokens — what an expired page or Instagram token means and how to restore access.
- Why is my campaign not replying? — the checks to run when a failed-reply notification points at a campaign.
- Connect a page — connecting and disconnecting the pages these notifications track.
- Subscription lifecycle — what the expiry warning is counting down to, and how to add days.