Let's Join
  • Friend codes
  • Known people
  • Instant friendship

Brunch crew plans that start with a friend code

Six characters, no reset, instant friendship—then eggs. The code is the on-ramp, not a party trick.

Six characters, then a table.

The story

The code is a door, not a flyer

Priya kept meaning to get her old lab partner onto the brunch crew. The group chat said 'add her!' six times and nobody knew what add meant. On Let's Join it means a six-character friend code, one per person, no reset. Redeeming it is instant friendship. Then—and only then—a ping can include her.

People treat codes like party favors. They are not. They are how the graph stays made of known humans. You do not paste a code on a lamppost. You send it to someone whose face you can already picture over eggs.

The shipping app does not open a stranger discover surface so a brunch crew can 'grow.' City-radius public is a later phase sitting quietly in backend modules. Today, brunch crew plans using a friend code are the opposite of that: a specific person, a specific six characters, a specific Saturday.

Login remains email through Cognito. Phone is verify-only. Neither replaces the code. The first friend is a gate into the core feed. If your crew is still at zero friends, you are not skipping the gate with a cute brunch photo.

Once redeemed, do not linger in a welcome thread. Send the ping: the diner with the sticky menus, ten-thirty or Let's Decide, Close friends or a custom list that actually contains her, FoF off. The code did the graph work. The ping does the Saturday work.

Priya wrote the six characters on a sticky note because her lab partner still distrusted apps. Paper felt like 2011 and it worked. The partner redeemed on the tram, friendship instant, and asked what a ping was. Priya said: diner, Saturday, you plus two, not a city of strangers. The sticky note went in a pocket, not on a lamppost.

Paper sticky notes still beat lamppost codes. Known hands only.

Why crews stall on 'we should add them'

Adding in a chat is theater. Nobody's address book agrees. The person in question is half in, half myth. A code ends the myth. They are friends or they are not, in one redeem.

Crews stall because they want the vibe of a bigger table without choosing an audience. Audience lives on the ping. All friends is a real choice. Close friends is a real choice. A list named 'Sunday eggs' is a real choice. 'Whoever sees this story' is not a product.

FoF on a first-code brunch is usually noise. Friends-of-friends is a switch on that ping, not a lifestyle. Let Priya's lab partner eat in peace before you invite a second ring.

If two people both think they sent the code and neither redeemed, stop arguing in hangout chat. One person pastes it again. Instant. Then ping. Logistics chat should be thinner than the omelette.

Circle pings still carry no capacity field. You cannot 'save a seat' as a product action. If the booth only holds four, invite four. Honesty is the seating chart.

The stall of 'we should add her' had lasted eleven weeks. Add had meant nothing. Code meant a graph edge. After redeem, Priya did not send a welcome carousel. She sent the ping in the same hour so the edge had a table to point at. Edges without tables become another unused social graph, and she already had those.

An edge without a table is just another unused graph. Ping the same hour.

Hand the code like a spare key, not a coupon

Tone matters. 'Here is my code, redeem when you have a minute, I will ping the diner' is a spare key. 'JOIN OUR BRUNCH BRAND' is a coupon and people flinch.

There is no code reset if they screenshot badly. They still have the same six characters. Do not invent a ritual of generating new ones. The product will not play along.

If they are not in the same city yet, the code still works. Friendship is the graph edge. The ping can wait until they land, or you Let's Decide a weekend. Open pings that never lock cancel after seven days, which is useful when flights slip.

Parents in the crew should hear the practical line: code, then a ninety-minute window with an end time. Codes do not require a personality interview. They require thumbs.

Dating copy has no home here. A friend code is not a flirt mechanic. If the brunch is a date, you are using the wrong story. This page is a crew.

She told the crew not to clap in the old chat. Clapping turns a code into a ceremony. Ceremonies make people late to eggs. One person pasted 'she's on the ping' and stopped. That discipline is the whole anti-chaos move.

Clapping in the old chat is ceremony. Ceremony makes people late.

Ping shape after the redeem

Place you can describe in one breath. Time or Let's Decide. Audience that includes the newly redeemed friend on purpose, not by accident of 'all friends' if that list is huge and loud.

Host locks when the hour firms up. Let's Decide is not a personality. It is an open clock with a seven-day ceiling. Crews that love codes sometimes forget to lock because the novelty of the graph edge ate the week. Lock.

Hangout chat: dietary notes, stroller, late train. Not a recap of how you met in 2014. The table can hold memory. The thread should not.

If they decline the first ping, that is data, not a broken code. Send a smaller one later. Silent distance is allowed. Unfriend would silently drop them from upcoming pings, which is a stronger move than a no to eggs.

Rotate who shares codes. One person should not be the immigration officer of the crew. Everyone has a code. Everyone can ping.

The diner booth only held four. Priya invited four. She did not look for a capacity field to bless the limit. Furniture is a better API than theater. The new friend got a real chair, not a waitlist identity.

Furniture is the seating API. Four chairs, four invites, no waitlist field.

Lists, Close friends, and the new edge

After redeem, decide whether they belong on Close friends or on a wider list. Close friends cannot be deleted as a system list. Do not dump every newly coded human there out of politeness. Soft lists stay soft by staying small.

A custom list called 'brunch crew' can grow as codes redeem. That list is who gets notified when you choose it on the ping. It is not a public channel.

If someone should not see this Saturday, do not choose all friends. The kindness is the smaller audience, not a secret second chat.

When a member is removed from a list, they are silently kicked from upcoming pings. Use that when the crew actually changed. Do not use it as a jump scare.

FoF off keeps the new edge from sprouting extra chairs. Turn it on later for one ping if the table can stand it.

FoF stayed off. Priya’s lab partner did not need to meet a friend-of-a-friend while still learning the menu. Second rings can wait until the first ring can pass the salt without a tour of everyone's jobs.

Second rings can wait until the first ring can pass salt without a tour.

Keep going

What the code will not do

It will not find you a brunch stranger in Berlin's radius. That discover path is not in the shipping UI. Do not wait for it.

It will not reset when you feel awkward. Awkwardness is solved by a smaller ping, not a new identity string.

It will not carry event-type badges. Brunch is your word in the invite text. The API is not a festival taxonomy.

It will not replace showing up. After redeem and ping, someone still walks to the diner. The product is allergic to pretending otherwise.

It will not announce unfriends. If the lab partner leaves the graph, upcoming pings simply stop including them. Eat with who remains.

Someone asked if they should reset codes 'for the new era of the crew.' Priya said the product would not, and neither would she. Stability is how a human who screenshots badly still belongs next month. Novelty belongs on the pastry, not on identity strings.

Identity strings should be boring. Pastries can be the novelty.

Seven days, flights, and first tables

New friends on the graph often have messy weeks. Let's Decide, then lock when the landing is real. If the week dies, the ping dies at day seven. Send another. That is cleaner than a zombie brunch.

Indoor twin if the diner patio is theater in November. Put the backup in the first ping so the new person does not need a second negotiation.

Money: say the diner is cheap. First-code brunches die when someone performs a tasting menu as hospitality.

Phones face-down after the first pour of coffee. The new person should meet faces, not a table of lock screens proving how busy the crew is.

Leave on time. Published ends teach the newly redeemed friend that yes is safe. Open-ended brunches teach them to lie next time.

When the partner declined the first Saturday because of a conference, Priya did not take it as a failed onboarding. She locked a smaller Tuesday counter-ping. Codes create possibility. They do not purchase attendance. A clean no kept the edge warm.

A declined first Saturday is not a failed redeem. Try a smaller Tuesday.

When two crews collide via codes

Sometimes two brunch crews code each other and suddenly the graph is bigger than any booth. Split pings. Two rooms. Do not crown a mega-brunch with fake capacity numbers.

Choose audience per ping. One Saturday can be Close friends. The next can be the custom list. Nothing requires combining every coded human into one noisy meal.

If schedules clash, do not force a union brunch. Let's Decide on the smaller crew. The other crew can have its own ping. Friendship is not a merger.

Chat stays per hangout. Do not paste both crews into one endless thread 'for simplicity.' Simplicity is the ping object.

If it gets awkward, shrink. Codes made the edges. They did not obligate a banquet.

Two crews almost merged because everyone had coded everyone. Priya split the Sunday. Lab people at 10:30, neighborhood people at 1:00. Friendship is not a corporate merger. Two objects, two audiences, one city.

Two coded crews can stay two rooms. Mergers are for companies.

After the eggs, the graph is still the graph

A good first-code brunch feels ordinary. That is success. Ordinary is repeatable.

Send the next ping while plates are still out, or by Tuesday. The code already happened. Do not wait for another onboarding feeling.

If they want to bring someone, that someone also needs a code and a place on an audience. No plus-one fog. FoF is the honest switch if you mean it.

Keep the six characters out of public captions. Known people, private graph, public eggs if you want a photo. The code is not marketing.

You still have to tap send. The friend code only removed the fake 'add them' loop. Saturday still needs a place and a clock.

After eggs, the partner sent their own ping for the following week, same diner, Close friends. That was the success metric: another thumb learned to tap. The code had done its only job. Saturday now belonged to the crew, not to the on-ramp.

Success is another thumb sending next week, not a welcome carousel.

How Let's Join fits

Friend code → ping → meet IRL

  1. Friend on the graph first

    Share a six-character friend code. Redeeming it is instant friendship. The feed stays closed until that first friend exists.

  2. Ping with an audience

    Place plus time, or Let's Decide. Choose all friends, Close friends, or a list. FoF is a per-ping switch, not a city mode.

  3. Show up, then stop

    RSVP honestly. Keep hangout chat thin. Host locks time. Honor the published end. Unfriend kicks are silent.

Good to know

Questions friends actually ask

They need to be on your friends graph. Code redeem is instant. Then ping.

brunch-crew-plans-using-a-friend-code