Account

Signals

Signals are the alerts, updates, and notifications the app sends: flight changes, new shared trips, booking-import results, sign-in alerts. The help centre and the app both use the same word.

Signals arrive on three surfaces: in-app (the Signals tab), email, and push (per device, once enabled).

In-app is on for every category. Push follows it once you've enabled push on that device, so anything in Signals can also reach your phone. Email is on for the categories you'd want to hear about while away from the app — delays, cancellations, and anything waiting on your answer — and off for the rest. Each of these is yours to change, per category, in Settings → Signals.

One category is off to begin with: travel on trips you're only watching. See below.

Every signal reads the same wherever it lands: what it's about on the first line, and what it actually says underneath — the jet-lag cue, what changed about the flight, which document is expiring.

Signals that need a decision or change a plan sit at the top of the list as cards: invites, friend requests, bookings waiting on a choice, cancellations, gate changes, forwarded bookings that couldn't be read, and documents about to expire. Everything else follows under Today, Yesterday, Last 7 days, and a date for anything older, counted in your own time zone.

One row doesn't come from a category at all: whenever Connie has told you something you haven't seen yet, a single line from her sits in the list. Open it and you land in the conversation at that message.

Categories

Settings → Signals starts with three presets. Quiet is in-app only, and only about your own travel and your account. My travel keeps your travel as recommended and takes everything else down to in-app. Everything is every signal as recommended. Under Every signal, each category can be set on its own, and the preset then reads Custom.

  • Flight signals. Delays, gate and terminal changes, and cancellations on flights in your trips. Other transit modes (trains, drives, ferries) don't yet have a live-status feed; categories for them will arrive alongside that work.
  • Travel on trips you're watching. Off to begin with. When someone shares a trip into a constellation you're in, you can see its legs — but you're not the one flying, so status changes on them stay quiet unless you ask for them. Switch this on to follow other people's travel as it happens. Legs you're actually on always notify you under the categories above, whoever owns the trip.
  • Travel you're following. On to begin with. Open a leg or event someone has shared with you, tap ⋯ and choose Get updates (or Add to my calendar feed on an event): you'll hear when that leg leaves, is delayed, changes gate or lands, even with the watching category above switched off, and it appears in your calendar feed. From about a day and a half before it arrives until shortly after it lands, it also sits on Home under Following. Handy when you're meeting someone off a flight. Tap Stop updates to end it. Following never sends email.
  • The night before you travel. On to begin with. At about 8pm the evening before your next departure, in the time zone you leave from, one signal says what's tomorrow and when it leaves. For a flight it adds when to be at the airport (an hour and a half before a domestic flight, three hours before an international one), or when check-in closes if the booking says so and that's earlier; for a ferry or train, when to check in if the booking says. It also says how many to-dos are still open on that trip, or that nothing is left to sort, and the weather where you land when a forecast is available. When several legs leave the same day, the first one gets the signal. In-app and push only, never email.
  • Everyone's home from a trip. On to begin with. When the people on a trip head home on different flights, or by different ways of getting there, Home shows how many of you are back ("2 of 3 home") from the first landing. Once the last person is home, everyone on the trip gets one signal: "Everyone's home from Paul & J Wedding". When you all travel home together, the leg's own landing says it and this stays quiet. In-app and push only, never email.
  • When you'll be in the same place as a friend. On to begin with. When you and someone you know will both be in the same city for at least half a day in the next two weeks, you each get one signal: "You and Joanna are both in Sydney 12 to 14 Oct", with the booking that puts each of you there. It only happens when you can each already see the other's plans for that stay or trip, and it comes once per person and place on a trip, even if a booking moves by a day. Ask Joanna to catch up posts "Looks like we're both in Sydney 12 to 14 Oct. Catch up?" on your booking and mentions her. If she can't read that booking's comments, she gets the same words as a signal instead. In-app and push only, never email.
  • Before you leave. On to begin with. Two hours before any leg departs, and again at the time you choose under Departure reminder (as it leaves, or 15 minutes, 30 minutes, 1 hour or 3 hours before). Pick 3 hours and the two-hour one stays quiet.
  • Delays that affect what comes next. On to begin with. When a delay means you'll likely miss your next leg, an event or a hire car pickup, the people on the leg and anyone following it hear once, and again if it's missed or back on track. See When a delay breaks what comes next.
  • Bookings that change (an email or the airline). On to begin with. When a forwarded email moves or cancels a booking already on a trip, or the airline changes a flight's schedule, the people on it and anyone following it hear what changed. See Changes and cancellations.
  • Taken off a booking. On to begin with. When the owner takes you off a booking you'd added, or off their trip, you hear about it, and the booking is in your trash if you want it back. In-app only.
  • Comments on a booking you're on. On to begin with. When someone going on the same booking comments ("running 20 minutes late"), you see it.
  • Comments on your trips and constellations. On to begin with. A comment with no mention, on a trip you're on or in a constellation you're in. A muted trip or constellation stays quiet.
  • Someone mentions you. On to begin with. A comment that mentions you, even on a trip or constellation you've muted. Turn this off to stop hearing about mentions. See Comments and mentions.
  • Someone tags you in a postcard. On to begin with. When someone on a trip adds a postcard and tags you in it, you see it, unless you've muted that trip. Tagging yourself sends nothing. See Postcards. In-app and push only, never email.
  • On this day. Off to begin with. Switched on, it now and then brings back a trip that started on this day in an earlier year: "A year ago today you flew to Kuala Lumpur". It comes at most once a week, at about 9am your time, and only in a quiet week, when you're not away and nothing of yours starts in the next seven days. Private trips count too, since it only ever comes to you. It never picks a trip belonging to someone you've hidden. When someone else was on the trip, Send it to Kat posts the same memory on the trip as a comment that mentions her. In-app and push only, never email.
  • Constellation activity. New shared trips, items added by others, settle-up suggestions.
  • Inbound bookings. Sender-approval prompts. What Connie makes of a forwarded confirmation comes through her conversation instead of a category row here (see above).
  • Account & security. Sign-in from a new device, password changes, invite link consumed.

Shared planning

Shared planning lets someone plan trips for you: a partner who books the travel, say. Each person chooses who can plan for them, one way; two people who plan for each other both turn it on.

Someone you share planning with can:

  • start a trip that belongs to you, without being on it themselves, and add bookings to it that are yours;
  • forward a booking with only your name on it and have it filed on your trips once they confirm it's yours (see Bookings for someone else);
  • transfer a trip or booking they made as their own by mistake to you (see Transferring a trip or booking to someone else).

Their invites to you are accepted as they arrive, too. They keep edit access to trips they plan for you, and those trips appear under All in their trip list. Each time, a signal says what was added and by whom. They can see that they can plan for you, because they choose you as the traveller.

Shared planning is switched on from the person's page in People (Let … plan trips for you in the ⋯ menu beside their name, ticked when it's on), from Always accept… on an invite from them, or from Plan trips for you in Settings → Trip preferences, which lists everyone who can plan for you. Their menu and that list switch it off the same way, and always agree. Switching it off stops them planning new trips for you; trips they already planned stay yours, and their edit access stays until you remove them from the trip. Removing someone as a friend clears it in both directions.

Invites you accept automatically

An invitation to a trip is a question, answered from Signals with Accept or Decline. Accepting puts you on the trip: you see all its bookings and join the ones you're going on. Someone you let plan trips for you is answered in advance, and a signal says so.

Invitations to a trip's bookings can be answered in advance too: the Always accept invites switch in the trip's Signals menu (at the top of the trip), off until you turn it on. With it on, a booking you're invited to on that trip is added as it arrives, and a signal says so.

A trip rule is visible only to the person who made it, and it grants no access: the invite could already have been sent and accepted; the rule says the answer was going to be yes. Deleting a trip takes its rule with it, and so does coming off a trip someone else owns.

Push (per device)

Push is enabled from Settings → Signals or during onboarding. The browser then asks for permission; choose Allow.

Push is how time-sensitive signals reach a device: a delayed flight, a gate moved at the last minute, a document about to expire. Live status covers flights for now; other transit joins as status feeds for it arrive. The permission is per-device, so granting it on a phone doesn't grant it on a laptop.

Constellations never sends marketing or third-party push messages. Every signal category can be turned down or off inside the app, and the permission can be revoked from the browser or OS settings at any time.

Each device is independent: enabling push on a laptop doesn't enable it on a phone. The device list lives in Settings, where any unused device can be revoked.

In the Android app the same switch turns on the phone's own notifications, and the phone asks for permission the first time. Tapping a notification opens what it's about and marks the signal as dealt with. These notifications have no buttons on them; open the signal to act on it. If the switch is locked, notifications are turned off for Constellations in the phone's Settings, under Apps.

Working through the list

On a computer or tablet, opening a signal puts what it's about beside the list: the trip, with the booking open for a flight or stay signal, or the person. The list stays put, so each signal can be looked at, acted on and dismissed in turn without leaving Signals. A signal about anything else shows its own details there, with Open to go to it. On a phone, opening a signal goes straight to what it's about and dismisses it.

Dismiss all clears the list in one go, except for anything still waiting on an answer (invites, friend requests, suggested changes and bookings waiting on a choice), which stays until it's answered. Undo brings everything back for a few seconds afterwards, and dismissed signals are always under Earlier.

The dot on the Signals tab follows along as signals are dismissed.

How long a signal lasts

A signal stays in Active for as long as it's useful, then moves to Earlier by itself. Earlier holds everything you dismissed and everything that ran its course; repeats of the same signal about the same thing sit as one row with a count.

  • One at a time, per leg. The reminders before a leg leaves, its delays, its gate changes, and the news that it's left all replace each other, so the list (and your lock screen) only ever shows the latest. Reminders, delays and gate changes end once the leg departs; "left" ends when it lands; "landed" lasts a few hours.
  • Every delay is shown. A delay of under 15 minutes arrives quietly: no email, and no sound where your device allows it (some phones, iPhones among them, may still sound). It isn't quiet when it leaves your next connection tight or means you'll miss it.
  • Jet lag. Only the latest cue is shown, and each lasts for its own window: about an hour for most, and the cue to go to sleep is just that, not the whole night.
  • Following someone's travel. The latest update replaces the one before. Once they've landed, it stays until 8am your time (that same morning if they land in the small hours). "Your time" is the time zone your phone or computer was last in when you opened the app, so it moves with you when you travel.
  • Anything waiting on an answer (invites, friend requests, suggested changes, bookings waiting on a choice) stays until it's answered. Answer it anywhere, from Signals, People, the trip or Connie, and it clears everywhere, including the notification on your other devices the next time the app is open on them.
  • Comments, postcards and other news move to Earlier after three days.
  • Reminders. The reminder to leave to collect someone lasts until half an hour after they land. The note the night before you travel lasts until you leave.
  • A document about to expire. You're reminded 60, 30 and 7 days before, and each reminder replaces the one before it for that document. The last one leaves once the document has expired. A document kept on one trip, such as that trip's insurance, isn't reminded about if it's still valid on the trip's last day; ones in your travel profile always are.

A notification that has stopped being useful also leaves your devices: the next one to arrive clears it, and a device that was offline doesn't get it late.

Dismissing, once

A signal in the app and the notification it sent to a device are the same thing seen twice, and clearing either clears both.

Dismissing a signal in the app closes the matching notification on that device immediately, and clears it from the account's other devices the next time the app is open on them. Tapping the notification itself marks the signal as dealt with, so it isn't waiting again in the list afterwards.

A signal dismissed without a connection stays dismissed on that device and is cleared everywhere else once the connection is back. Dismiss all needs a connection.

Swiping a notification away without opening it doesn't dismiss the signal — "clear all" looks identical to the app, and it would mean sweeping a notification shade quietly discarded signals that were never read. Those stay in the list until dismissed there.

Email

Email signals send to the account email. Leaving the channel off for a category stops them. Account & security emails (verification, password reset) always send regardless.

Quiet hours

Per-channel quiet hours sit under each category. With a start and end time set, signals are deferred to the next window.

When something goes wrong

When push stops arriving, the most common cause is a revoked permission at the OS or browser level. Re-enabling from Settings → Signals walks through re-granting it.