Outreach Queue

What it is

The Outreach page holds today's list of people the team should approach: a brand, a talent, or their agency. Each row says who to write to, why now, which channel to use, and hands over a message ready to copy.

At the top, Offers to unclaimed accounts lists offers, blasts, seeds and deals that reached an account nobody has claimed yet. Nothing has been sent for them. Each shows who it is for, the address research found and where it came from, and the offer in a line or two. Approve sends one message to that address with a link to claim the account and reply. While email sending is off, Approve saves the approval and the team sends it by hand, then presses Mark sent. Skip sends nothing. Who approved and when is kept, and the same offer is never sent twice.

It is the human step that deal seeding cannot do alone. Many brands and talent have no Zooly account, so an email or text from the product never reaches them. A person writes to them instead, and the queue makes that first message easy and consistent.

The queue is built when someone presses Rebuild today's queue. It can be pressed any number of times in a day: waiting rows refresh in place, and sent rows are left for their follow-up.

What each row shows

• Who. The person's name, their role, and their company. For an agency, it names the agent and the clients they speak for.
• Why now. One line explaining what is waiting: talent who are ready for this brand, a strong fit, or an ask that went unanswered.
• Which channel. LinkedIn, their agency, email, or no route yet, plus the exact place to send it.
• A score. A single number that sets the order of the list.
• A ready draft, in a box that can be edited before it is copied. Email rows also show a subject line.

Under the draft, the row shows the character count and says whether the message passes the outreach rules. If it does not, the row names what to change.

Where the people come from

Everyone in the queue comes from a deal seed. There are three reasons to write:

A fresh ask is left alone until it goes quiet. One message per person, so an agency with three clients gets a single note about all three.

How people are ranked

The list is ordered by a score. It rises with the strength of what is waiting: the top match, how many talent are already ready, and how much the brand wants them. It also rises or falls with the channel, because LinkedIn and agencies work better than a cold email.

A follow-up that has come due jumps up the list, because it is time-sensitive.

When two rows have the same score, the one updated most recently comes first. The top of the list is where a person should start.

Which channel applies

The queue picks the first route that exists, and skips one that bounced for that person last time.

• Talent: their agency first, because agents are the gatekeepers, then the talent's own LinkedIn, then email.
• Brands: LinkedIn first, then their agency, then email.
• Email is used only when nothing else is known.
• No route yet still appears, near the bottom, so someone can go and find the person.

What the draft must follow

Every draft, whether written from a template or by the optional rewrite, follows the same house rules:

• No dashes. No em dashes, en dashes, or double hyphens used as a dash.
• American English, never British spellings.
• A warm, human opening line, and a greeting line.
• One clear ask. Exactly one question in the message, and it ends with an open question such as "Open to a chat?".
• No order at the reader. The message never starts a sentence with "check", "click", "let me know", or similar.
• No link and no deck, in a first message or a follow-up.
• No stock phrases such as "just checking in", "circling back", or "hope this finds you".
• No price leak to a brand. A brand never hears the talent's own asking price, only the price Zooly is proposing.
• No other live counterparty named as social proof.
• A length range: 600 to 950 characters for a first message, and 250 to 600 for a follow-up.

A talent is only named to a brand after that talent has said yes. Other strong fits are described as a number, never named.

Nothing sends by itself

The queue never sends anything: not LinkedIn, not email, not an SMS. A person reads the draft, presses Copy draft, opens the channel, pastes it, and sends it themselves.

That is on purpose. These are personal messages from a named person, and the last step belongs to a human.

The sign-off on the draft follows whoever the row is assigned to.

What a person records after sending

After sending, one tap records what happened, and the row moves on:

• Sent starts the clock for follow-ups.
• Follow-up sent records a follow-up that was sent by hand.
• Replied ends the chase.
• Not interested asks for an optional reason and parks the person for a while.
• Bounced means the channel did not reach them, and the next build tries another route.
• Skip passes on the row for today.

When a follow-up is due, Sent is replaced by Follow-up sent. Skip shows only on a row that has not been sent yet.

Every row also keeps a History of past messages for that person, with the timeline of each step and what was sent.

Assigning work

Each row has an assignee dropdown with the team and an unassigned option. Tabs at the top filter the list to one person's rows, to unassigned rows, or to everyone, each with a count.

Two more filters narrow by reason and by channel, so each person can work only their own rows.

Follow-ups

Four days after the last touch with no reply, a follow-up draft appears. It always brings a new reason to answer rather than a plain nudge: a talent who said yes since, a fit reason not yet used, the price, another idea, or a one-page summary instead of a call.

There are at most two follow-ups. Four days after the second one goes quiet, the thread closes as no reply.

Who rests, and for how long

The queue keeps its own quiet periods, so nobody is pestered:

• After a reply or no reply: thirty days before the same person can appear again.
• After the team skips someone: seven days.
• After "not interested": ninety days, shown as a parked ruling on the Do not contact list. After that they can be approached about something else.
• After a bounce: no wait, and the next build tries a different route.
• When the reason goes away (the seed was answered, or closed): the row is dropped straight away.

Do-not-contact rulings

At the bottom of the page is the Do not contact list. A ruling can be killed, parked until a date, owned by someone else, asked us to stop, or another reason.

These people never appear in the queue. A ruling on either side of a deal idea takes the whole idea out, and the rebuild reports who was left out and why.

The optional AI rewrite

An AI rewrite button can polish one draft. It is off by default, and the button does not show until it is turned on. Even then, nothing is rewritten until a person taps it on a row.

The rewrite may only reword. It must keep every fact, name, and number, and it must pass the same house rules. If it breaks one, the original draft is kept and the row says why. Its cost is shown on the row.

What it does not do

• It does not find people. When there is no route, it says so and leaves the search to a person.
• It is not a customer record system. It keeps who, why, the draft, the status, and the timeline, and nothing more.
• It does not move the deal. A reply in the inbox still has to be marked on the seed.

Related Documentation

• Deal seeding — where the seeds behind each row come from
• Automation — what the product does on its own, and what waits for a person
• Deal Record — what happens after both sides say yes