Following posts and boards
People follow a post automatically when they write it, vote on it or comment on it, and anyone who is signed in can follow a post by hand with Subscribe. Boards can be subscribed to as well, to hear about new posts; your workspace members are subscribed to boards automatically.
Following is what decides who hears about a request, so the people who asked for something are the ones told when it moves.
Customer-facing notifications
Followers of a post are told when its status changes, when it is merged into another post, and when it passes a vote milestone. Authors hear about new comments on their posts and replies to their comments, and the outcome when a post they submitted is approved or rejected. People added to a private board are told they have access.
When a changelog entry that resolves a post is published, its followers can be sent one message telling them that something they asked for has shipped, listing what they asked for.
Team notifications
Your team is told about new posts on the boards they are subscribed to, posts waiting for approval, posts assigned to them, @mentions, and each published changelog entry.
To bring feedback into chat, connect Slack or Discord. A Slack subscription posts the events you choose to a channel, optionally limited to certain boards, so triage can happen where your team already works. Slack also lets people capture a message as Looph feedback and search or submit with the /looph command.
Channels and personal settings
Notifications arrive by email, in the in-app notification bell, and as push notifications on devices where people have turned them on. Each person controls their own notifications for status changes and mentions, the in-app notices for votes and comments, and digest emails that gather activity into one message.
Digest emails come with the paid plans: a weekly digest from Starter, and daily as well as weekly digests from Growth.
Admins set the defaults that new members start with under Settings, then Moderation settings, in Default notification preferences. Existing members keep their own choices.
What each switch controls
Each member sets their own preferences in Settings, then Notifications. A switch saves as soon as you flip it and applies only to the workspace you are in.
Status changes covers the email and in-app notice when a post you follow moves to a new status, and the message when a changelog entry ships something you asked for. Mentions covers the email and in-app notice when someone @mentions you in a post or comment.
Votes on my posts and Comments switch the in-app notice for vote milestones and for new comments on posts you follow. The emails for those events, and for replies to your comments and merged posts, have no switch on this page and are on by default; to stop them for one post, choose Subscribed on that post to stop following it.
You are not notified about your own actions. A comment that replies to you or mentions you sends that one notice, not a second one as a new comment. Vote milestones are sent at 10, 25, 50, 100, 250, 500 and 1,000 votes.
Digest emails
A digest gathers activity into one email per person, with a section for each workspace you turned it on for. Owners and admins receive an operator digest: new posts, comments and votes, the top posts, posts still waiting for triage and failing automation rules. Members receive their own, covering what they posted, commented on and voted for.
The weekly digest goes out on Mondays at 14:00 UTC and the daily digest every day at 06:00 UTC. Weekly digest starts switched on and Daily digest switched off. A digest with nothing to report is not sent.
The digests depend on the plan: weekly from Starter, daily from Growth. On a plan without one, its switch shows Not included on and the plan's name. After an upgrade the digest resumes with your choices as you left them.
Push notifications
Push sends the notices that reach your in-app bell to your browser, even when the tab is closed. Turn it on for each browser from the bell: choose View all notifications, then use the switch in the Push notifications section. The browser asks for permission the first time.
Connected browsers lists every browser that receives push, and you can remove any of them there. There is no push setting per event: push follows your in-app settings, so turning off an in-app notice turns off its push too.
Deliverability and unsubscribing
Notification emails come from Looph's sending domain, under your workspace's name, and you can set a reply-to address in Settings, then General, so replies reach your team. Sending from your own domain is not available.
Every notification email carries a one-click unsubscribe that mail providers recognise, and if a post's status is announced again within 24 hours, followers are not notified a second time.
Unsubscribing, bounces and the notification log
The unsubscribe link in a notification email, and the one-click unsubscribe your mail app offers, stop notification email sent through Looph from every workspace: replies, status updates, mentions and digests. Email about your account, billing and security still arrives, and carries no unsubscribe link.
Customers who are not members of the workspace have no Notifications settings page. They choose what they hear about with the Subscribe button on a post or board, and with the unsubscribe link.
If mail to an address bounces permanently, or its owner reports a Looph email as spam, Looph stops sending to that address altogether, account and billing email included.
Owners and admins are emailed about billing whatever their settings: the trial ending, a failed payment, an expiring card, a plan change and a cancellation. To see what went out, admins can open Settings, then Notification log, which lists every notification sent for the workspace in the last 24 hours on every channel, with counts of sent, queued, failed, suppressed and skipped.
How often is too often
Every notification a customer receives is a request for their attention, so send the ones that answer the question they asked: a status change on their request, and the shipped message when it is done. When you change a status, add a short public comment saying why; it is the most useful thing a follower can read.
For the team, a digest suits most people; instant email is worth it only for whoever works the moderation queue or a board that needs a same-day response. Revisit the settings when people start creating mail filters for them.