Looped

Looped takes over the waiting. CC one address on any email where you need a reply, and NetworkOS watches the thread, reads what each reply means, and sends pre-approved follow-ups from your own inbox until the conversation resolves. No reminders to set, no nudges to write.

It's built for the threads that quietly stall: an intro you offered, a term sheet you're waiting on, a deliverable that's late, a decision that hasn't come back.

1. 1

   CC the loop address

   When you send or reply to an email where you're waiting on the other person, add cc@loop.thenetworkos.com to the CC line. That's the whole setup, there's nothing to configure first.

2. 2

   Get your confirmation

   NetworkOS finds that message in your Gmail, starts a loop, and emails you a confirmation that lists the participants, the cadence, and the exact follow-up it will send.

3. 3

   Replies are read for you

   As replies arrive, NetworkOS reads each one and classifies it: resolved, still deciding, a clear no, or unclear. A 'still deciding' reply pushes the next nudge further out instead of sending one.

4. 4

   Follow-ups send if it goes quiet

   If nobody replies, NetworkOS sends your pre-approved follow-up from your own Gmail, in the same thread, every few days, up to a limit you set.

5. 5

   The loop closes itself

   A clear answer resolves the loop, a hard no closes it, and silence after the last follow-up ends it. You get a short notice either way, and you can stop any loop yourself at any time.

Every follow-up is pre-approved copy, so nothing goes out that you haven't already signed off on. Your confirmation email shows the exact message before it ever sends. NetworkOS can also tailor the wording to match the tone of your original email, and it rotates the phrasing so a second nudge doesn't read identically to the first.

Each loop freezes its copy when it's created. You can edit the message, the cadence, or the number of follow-ups on the loop's own page, or stop it entirely.

Under Settings, the Looped section sets the defaults for every new loop:

• Days between follow-ups, how long Looped waits before each nudge (4 by default).
• Maximum follow-ups, how many times it will nudge before it gives up and marks the thread no-response (3 by default).
• Default follow-up message, the copy used when you don't set a per-loop one. Leave it blank to use the built-in default.
• On or off, a master switch. When it's off, CCing the loop address does nothing.

The Loops page lists every active loop and recent closed ones, with who you're waiting on, the next nudge, and how many follow-ups have gone out. Open any loop for a full timeline: when the thread was found, every reply and how it was read, each follow-up sent, and how the loop ended.

Want to try it before you rely on it? The empty state has a Send a test loop button that sends a short note from your own Gmail with the loop address CC'd, so you can watch the whole flow end to end.

Looped only ever reads the threads you CC it on, and only to detect replies. The rest of your inbox is never touched. Follow-ups send from your own connected Gmail, not a NetworkOS address, so they come from you. A loop can only start from a message that's actually in your mailbox, which means someone can't spoof your address to create loops in your account. See Privacy & your data for the full picture.

Making introductions · Tasks & follow-ups · Settings & billing