Notifications

JOGL Network notifies you about new direct messages, connection requests (and when someone accepts one you sent), meeting booking requests and what then happens to a booking (declined, expired, cancelled or confirmed; see Meetings), meeting requests at an event and what becomes of them (see Event mode), requests to join a community you administer and the answer to your own request to join one, and about notices from JOGL itself such as community invitations, through two channels you control in Settings → Notifications:

• Push notifications — instant notifications on your device. Turning the switch on asks your browser for permission and registers the device. Push works in the browser and in the installed app; if your browser has blocked notifications, the page tells you to re-enable them in the browser settings.
• Email notifications — the same events by email, except a booking or an event meeting becoming confirmed, whose invite email already goes out. Email is on once you have signed in, unless you turn it off here or on the last step of onboarding, which shows the same switch. A profile a community created for you gets none of these emails until you sign in to it, with one exception: when a member asks you for a meeting at an event whose organizers imported you with your email address, you get an email about it, unless your address has unsubscribed from JOGL's invitation emails, which the unsubscribe link this email carries does. You get at most three of these a day, and one member's requests send at most five a day to all such guests together; past either limit, the request still waits for you, without an email.

Both are simple on/off switches; there is no per-event configuration today. The Push notifications switch decides whether anything is pushed to you: the messages, requests and notices above, and news about work you started yourself (below). The one exception is a test notice a JOGL administrator can send you, which reaches every device you registered whatever the switch says. Turning the switch off also tries to remove the registration of the device you turn it off on, but the switch is saved as off even when that removal fails. To be sure a device gets no push at all, block notifications for JOGL Network in that browser's or device's settings.

When a long job you started yourself ends, JOGL tells you by push and by email, each only while its switch is on, in the language of your profile. That covers an enrichment run, an import of an event's guests from Luma, Eventbrite or HelloAsso (and, for JOGL administrators, a file import on the admin import dashboard), and a CRM sync. The notice says what ran, in which community, and whether it finished or failed. A finished job shows its counts, such as the profiles enriched or the records created and updated, except that an import where some batches got no answer leaves out its failed count, since those profiles may still have been imported; a failed one says it stopped and that you can start it again from the same place, which the notice's button opens. When the first enrichment of a community you have just created finishes, the notice says the community is ready. You are told of an outcome only while it still holds when the notice goes out: if a job that failed then finishes before the failure notice went out, you are told only that it finished, and if it finishes after, you are told both, in that order; if it then fails again, you are told that too. No end is told twice, unless JOGL fails to record that its notice went out, in which case it can go out a second time later. No notice is sent for a job you cancelled, for the enrichment that follows an event import (the import's notice covers it), for an import the Luma or Eventbrite auto-sync started on its own, for a re-sync of an event refused because the community is read-only, which a notice from Jojo told you at once, for an enrichment refused for lack of credits as you started it, which the page told you at once, for an enrichment started through the JOGL API or an assistant connected over MCP, which can follow the run itself, or once you can no longer administer the job's community. A CSV import of members from a community's admin console sends no such notice.

JOGL also emails you, whatever the Email notifications switch says, when something changes on your account's access: when your account's email address is changed (this email goes to the address you had before, and shows the new one only by its first letter and its domain), when an API key is created on your account, when an app is connected to it over MCP (or connected again), and when two-factor authentication is turned off. Each says when it happened and opens the settings page it concerns. If you did not make the change, reply to the email.

Onboarding also offers push: turning it on there asks for the browser's permission, registers the device and turns the Push notifications switch on, as turning it on here does. While the switch is on, the app can also register a device that has given permission when you open it. Signing out tries to remove the push registration from that device but never blocks on it, so if the browser refuses the registration can outlive the sign-out. Before handing over a shared device, turn push off and block notifications for JOGL Network in its browser settings.

After onboarding, if push is not on for the device you are using, a card at the bottom of the app offers Turn on, which asks your browser for permission, registers the device and turns the Push notifications switch on, as the switch does. When meeting requests are waiting for your answer, the card says how many; when none are, it says how many connection requests are. On iPhone and iPad (iOS 16.4 and later), Safari only gives notifications to JOGL once it is added to your Home Screen, so there the onboarding step and Settings → Notifications say so and offer Show me how, which walks you through installing the app; open JOGL from the Home Screen afterwards to turn notifications on. On an iPhone the banner that offers to install the app already asks this, so the card asks it only where that banner does not show, as on an iPad, and not while you have put the banner off (I'll do it later or Never again). Not now puts the card away on that device for two weeks, and after the third time it stops coming back there; on a card that asks you to install, it also puts the banner off, as I'll do it later does. It does not appear if you turned the switch off or your browser blocks notifications, it waits a few days on the device where you have just been through onboarding and, for a day after onboarding, wherever nothing waits for your answer, turning push on or off in Settings puts it away for the rest of the visit (done in another tab, or turned off on another device, it goes once you come back to the tab showing it), and the card and the install banner never both show in one visit. Neither shows on the welcome pages you see after signing up, nor while you import members or contacts, where it would cover the page's buttons; the card then waits for a later page.

On the search page, Jojo asks this itself (Turn on), under the card's own rule and once it has nothing more pressing to say, so from the moment Jojo appears the card holds back until you next open or reload the app. Later on Jojo's question puts the card away as Not now does, and after a second Later on a device Jojo stops asking there, until you choose Bring them back in Settings → Jojo. With Jojo turned off, or Let Jojo point out what's waiting on me off, the card shows as before.

Right after you send a meeting request, the card can also ask, saying why: to know as soon as the other person answers. It comes once the window you sent the request from is closed. It asks only where your browser has neither allowed nor blocked notifications for JOGL yet and push already works on the device, not if you turned the switch off, and not in a visit where the card has already been put away (on iPhone and iPad in Safari, it asks instead to add JOGL to your Home Screen, with Show me how, taking the install banner's place, unless you have put the banner off); it then asks the next time you open JOGL on that device, within a day of the request and while one of your requests still waits for an answer. It can ask even after Not now has put the card above away, since it comes with a reason the card did not give. Its Turn on does what the card's does. Not now on it stops this ask on that device for good, and keeps the card above away for a few days; on the ask to install, it also puts the install banner off, as I'll do it later does.

The same kind of ask, saying why, comes at a few other moments: on an event's page once you have told Jojo your goals for it, to hear when someone there asks to meet you and shortly before each meeting; above the message box once you write to someone who has not written to you in that conversation yet; after you send a connection request; and, for community admins, once invitations go out. Each asks only where the ask after a meeting request would, comes once any open window is closed, and is answered on its own: Not now on one stops that one on the device for good, and keeps the card above away for a few days. On iPhone and iPad in Safari, where only the app on your Home Screen gets notifications, each of them keeps its reason and asks instead to add JOGL to your Home Screen, with Show me how, taking the install banner's place, unless you have put the banner off; there, Not now also puts the banner off. On Android, while your browser offers to install JOGL, the button on the card above and on each of these asks reads Install and turn on: it opens your browser's install dialog first, then asks to allow notifications, whatever you answered (they work in the browser too, and reach the installed app as well); closing the install dialog, or Not now on such a card, puts the install banner off, as I'll do it later does. The first time you open JOGL from your Home Screen, or as an app installed on your computer or phone, once you are signed in it greets you with Welcome to the JOGL app and Turn on, under the same rule; until you answer, it asks again each time you open the app, and Not now stops it on that device for good. While one of these shows, the card above does not.

While Jojo builds your full profile after you sign up, Finish later comes as the same kind of ask, where this device can be asked: Notify me and finish later turns push on for it and takes you into the app (it does too if your browser blocks the notifications), and I'll wait for it to finish keeps you on the screen, stops that ask on the device for good and brings back the plain Finish later. On iPhone and iPad in Safari it asks instead to add JOGL to your Home Screen, with Show me how, as the others do there. Once your profile is ready to check, JOGL pushes Your profile is ready, as your Push notifications switch allows, and the notification opens it. Jojo still tells you on the search page.

When you bring your LinkedIn connections or your phone contacts into your personal network, the same kind of ask shows under the import's progress once your contacts are on their way and the page can be left, to hear when they are in, under the same rule as the others. Once the import is done, JOGL pushes Your contacts are in, as your Push notifications switch allows, and the notification opens your network's people. When your plan's limit held some of them, it says the rest wait for a plan; when it held all of them, because your network was already full, it says Your network is full and that they wait for a plan. An import that stops early is not pushed: the import page says why.

While you have JOGL Network open in front of you, a new message from another member appears as a short preview in the app rather than as a push; click it to open the conversation. A notice from Jojo shows no preview: the unread count and Jojo tell you about it. Email is not affected, and with push on, a community invitation is pushed even then.

A request to join a community you administer reaches you at most once an hour for that community: when more requests arrived in the meantime, the next notice says how many are waiting. Its Review requests button opens the community's Join requests section, where you approve or decline them. You are never told about a request you made yourself. Admins are told about at most five requests from the same person in a day, across all communities; any more still wait in the Join requests section, without a notice. When the admins answer your own request, you are told whether it was accepted, with a button to the community, or declined, with how many days are left before you can ask again. A request you withdraw, or one closed because the community was made private or archived, sends nothing.

An invitation to a community reaches a member who already uses JOGL as a card from Jojo in Messages, with Accept and Decline, and is pushed as your Push notifications switch allows. It also comes by email whatever the Email notifications switch says; the email's button opens the community picker on your pending invitations, and its unsubscribe link stops invitation emails and the emails of an add to a community only. When you declined that community's last invitation, or you or the inviter blocked the other, the invitation's email follows the Email notifications switch instead, like any message. An invitation email sent to someone who has not signed in yet, to claim the profile a community made for them, carries the same kind of unsubscribe link.

When someone accepts your invitation to a community, or joins it through your invite link, you are told by a notice from Jojo, and Jojo mentions it, but it is neither pushed nor emailed, so a community that fills up quickly does not flood you with notices. You are not told once you can no longer invite people to that community, nor about someone who blocked you, or whom you blocked.

The same goes for someone you invited to claim the profile a community made for them: when they sign in and claim it, a notice from Jojo tells you, and only in the app.

When an admin makes you an admin or the owner of a community, a notice from Jojo tells you, pushed and emailed as your Push notifications and Email notifications switches allow. When an admin adds you to a community, a notice from Jojo tells you too, pushed as your Push notifications switch allows and emailed whatever the Email notifications switch says, as an invitation is; when you or that admin blocked the other, the email follows the Email notifications switch instead, and the notice does not name the admin. The notice names the admin who added you and carries Open the community, and its email says who added you to which community, with a button into it; its unsubscribe link stops invitation emails too. When an admin adds you to an event, the message is pushed but not emailed, since an admin often adds a whole community at once; it opens the event, and it is sent only while the event is open to members (not a draft its organizers are still setting up) and has not ended, and you are a member of its community. As an admin, you are not told of a change you made yourself, such as adding yourself to an event.

On your phone and in your inbox, a notice from Jojo carries the same name: it is the title of most pushed notices, and the sender in the subject of a notice that has no email of its own (New message from Jojo).

When an admin invites a community's members to an event whose networking is open, a notice from Jojo with See the event reaches each member who does not attend it yet, pushed but not emailed, and only before the event ends; a member already invited to that event in the last 30 days is not invited again. When an admin sends a message to an event's participants, it reaches you as a notice from Jojo in the admin's name, pushed but not emailed (the push shows the start of the message), with See the event once the event is open to members. It can come at any time, after the event too, and replying is not possible there. The admin can choose to send it by email as well; that email carries its own unsubscribe link. A message an admin sends to an event's participants from the community's People page goes by email only.

For an event you attend in a community you are a member of, JOGL also pushes you a reminder about a day before it starts (a few hours before for one created 8 hours to a day ahead, and none for one created less than 8 hours ahead), and a notice from Jojo tells you when its networking opens (pushed, not emailed) and when an admin cancels it, by deleting it before it is over (pushed and emailed as your switches allow; an event with no end date counts as over a day after it starts). The reminder is a push only, with no message, and is sent again if the event moves. An event with no start date gets no reminder.

About a quarter of an hour before a meeting starts, an event meeting or a booking of your open slots, JOGL pushes a reminder to both of you, naming the other person when you can see their profile. It is a push only, with no message, and is not sent for a meeting booked, or confirmed by its host, less than half an hour before, nor between two people either of whom blocked the other, nor for an event meeting once either of you no longer attends the event. If JOGL can no longer read your Google Calendar (you removed its access, or the access expired), a notice from Jojo tells you, pushed and emailed as your switches allow, since people booking you could then be offered times when you are busy; reconnect it under Settings → Meetings. If you reconnect it before the message goes out, it does not.

Notices about money go to whoever pays: to you for your own plan and credits, and to the owners and admins of an organization who hold a seat in it for what the organization pays. They come by email whatever the Email notifications switch says, because they concern your payments or credits, and are pushed when Push notifications is on; each links to the Billing page in Settings. They are: a renewal payment for your plan that your card declined, while the plan stays unpaid, once per invoice; a free trial ending within three days, and then ended, when no paid plan covers it; credits running low (less than a fifth of your latest grant or top-up left) or out, each once until your next grant or top-up, and only after credits were spent in the last 30 days; and, for a community that will be archived on a set date because its plan lapsed or its owner holds more communities than the plan allows, a reminder 30 days before that date and a last one 7 days before.

At an event, a meeting request reaches the attendee you sent it to by push and email, as their switches above allow, and their answer reaches you the same way, except that an acceptance comes by push only, since the calendar invite is already emailed to you both. An imported guest who has not signed in yet gets only the email described above, on the terms given there. If you withdraw a request, the other person is told only if they were told of the request. If either of you cancels a confirmed meeting, the other is told the same way, as their switches allow. Each of these notices opens the event's Meetings tab, except that a cancellation reaching someone who can no longer see the event opens their meeting settings instead. You are told of at most five new requests a day from the same person.

When a JOGL administrator marks feedback you sent as resolved, you get one email saying so, quoting what you wrote, while Email notifications is on. If you administer a community, JOGL also emails you, whatever that switch says, when the community's CRM connection is refused access and its syncs have stopped, or when Eventbrite refuses the community's Eventbrite connection so new orders and attendees are not imported. The CRM email comes once each time the connection breaks, and the Eventbrite one at most once a week while Eventbrite keeps refusing; its button opens the community's CRM sync for that platform, or the community for Eventbrite.

Notices and their emails are written in the language you chose in the app, English or French; the email with your sign-in code is in the language of the sign-in page. The email to an imported guest who has not signed in yet is in French when their profile or the person asking is set to French, and in English otherwise.

If JOGL cannot read your switches when a notice is due, it sends nothing rather than guess. Most notices then wait and go out once your switches can be read again, provided that happens within a day; a notice still waiting after a day is dropped without being sent. Notices about money wait longer, for as long as they are still due. Notices about a new message, a new connection request, a booking request, and a meeting request at an event or what becomes of it can be lost that way instead. The message, or a request still waiting for an answer, still shows in the app; a meeting request that was declined or withdrawn does not, so a lost notice about it leaves no trace there.

There's no separate notification centre. Notices from JOGL, such as community invitations, arrive in Messages from Jojo, in a conversation marked Notifications that you can't reply to; its link at the bottom opens Settings → Notifications. New messages put an unread count on the Messages button, connection requests show a count next to My Network (in the All my network view), event meeting requests waiting for your answer show a count next to Events, and pending community invitations put a dot on the community picker at the top.