
use case · planning a date
Concrete walkthrough of the most common couples-coordination moment: the anniversary dinner. Two agents, four steps, no calendar copying. Adaptable to any other dinner-out scenario — birthdays, friend dinners, the “we should go out somewhere nice” Saturday.
You and Sam have been together five years. Anniversary is three Saturdays from now. You both vaguely want to do dinner. Sam is busy at work. You haven’t booked anywhere. Last year you ended up eating at the place downstairs.
Below is what happens when two paired AI agents handle this for you.
step 1
You text your agent: “find a Saturday this month for our anniversary dinner with Sam.” That’s the entire instruction. Your agent doesn’t need Sam’s calendar, doesn’t need the date of the anniversary, doesn’t need a list of restaurants — all of that is already in the shared zone or pullable.
Behind the scenes: your agent reaches out to Sam’s agent over a signed envelope. Sam doesn’t see the message yet — only their agent does, and only the request (“need a Saturday this month for an anniversary dinner”), not your prompt verbatim.
step 2
Sam’s agent checks Sam’s calendar for the four Saturdays in the month. It cross-references with the shared zone (the anniversary date) and the recall context (what you said last year about wanting somewhere nicer). Two Saturdays work for both of you. The 18th is the actual anniversary; the 25th is the next-best alternative.
Your agent gets the answer back: both Saturdays match, but the 18th is the actual date. The agents have already pulled three candidate restaurants from your shared saved-places list and Sam’s recent search history (with permission), filtered for ones that have openings on the 18th at 8pm.
step 3
Your phone buzzes: “Sam can do Saturday the 18th. Booked Filu at 8pm — you both saved it after the trip in March. Want me to put a card down for the deposit, or send Sam a confirm first?”
Sam gets a parallel notification: “Hey — your partner asked Junie to find a Saturday for dinner. The 18th works for both of you, and you both saved Filu in March. Confirm?” Sam taps “confirm.” The booking is made through the restaurant’s reservation API. No phone call. No calendar invitation back-and-forth. No “does this time work?” thread.
step 4
A week before, both of you get a reminder on whichever channel each of you uses (yours on iMessage, Sam’s on Telegram). The day of, your agent surfaces the reservation, the address, and the parking option you used last time. After dinner, when you tell your agent it was good, that detail goes into the shared zone: Filu, anniversary dinner 2026 — table by the window, the tasting menu, Sam liked the wine pairing.
Next year, your agent already knows.
SMS pairing handles this. Sam’s side of the conversation happens entirely in plain text messages. Your agent and theirs still talk over signed envelopes behind the scenes.
Tell your agent. It negotiates with Sam’s agent, proposes alternatives, updates the reservation, and moves the reminder. The shared decision log records the change so neither of you has to remember why.
That’s genuine information, not a bug. The agents surface the conflict (a work trip, a family event, something Sam blocked) and propose moving the dinner to the following weekend or to a weeknight.
Junie drafts a phone-call script and reminds you to call. The agreed time and date are still pre-negotiated between agents — the only manual step is the call.
questions
Set up your account in two minutes. Pair with your partner by SMS or QR. Free during private beta.