BirdsEye ROI, Email Sequence Library, Part 1

Sequences 1 through 5. Sequences 6 through 10 live in email-sequence-library-part-2.md and are written separately.

Author: Shakespeare, Content Lead Date: 2026-08-02 Status: DRAFT FOR MIKE'S REVIEW. Nothing in this file has been sent.

The first version of this file led with platform internals and was replaced. It is kept at email-sequence-library-part-1-v1-data-led.md.bak for reference only.

Standing rules for every email in this file

The angle. positioning-why-i-built-it.md is the authority and it outranks anything here. We are not selling a call analytics platform.

For the operator: he looks at his phone for four seconds between jobs and knows what the business made. One number. The last call with a dollar next to it. A chart at the end of the day that tells him it worked.

For the agency owner: his problem is not generating calls, it is proving they were worth paying for. He wants a per service and per area report he is proud to send to a client on a Friday.

Two voices, not one. Sequence 1 is the operator. Sequence 2 is the agency. They must not sound the same. The operator is reading at a stoplight, so the sentences are short and the words are money words. The agency owner is a peer, so nothing explains what call tracking is and the subject is margin, retention, and the report he has to defend.

Sequences 3, 4, and 5 are written in the operator voice by default and each email carries an Agency swap giving the paragraph that changes when the contact is an agency owner. Swap the paragraph, keep the rest. Never send a body that mixes the two.

Banned from every subject line, preview line, and opening line in this file: the spam share, the total call count, and the tracked revenue total. Junk calls dropping out before they reach the number may appear late in a body as reassurance. Never as the lead.

Retired, never reuse: "Most call tracking tells you the phone rang. BirdsEye tells you which ring paid." Deck only.

The offer. BirdsEye is not sold as a SaaS subscription. The model is revenue share and profit share, and the terms are discussed live on the call. Every email in this library exists to earn the call. Not one of them quotes a price, a percentage, a split, a tier, a minimum, or a term length. If a prospect asks about structure by email, the answer is that it is a conversation, and the conversation is the call.

Numbers. FACTS.md is a ceiling on any figure that appears, not a brief. Most emails below need no platform figure at all. Dollar figures shown in creative are product illustrations. No invented clients, testimonials, quotes, logos, case studies, or results appear anywhere.

Merge fields. Only four fields exist and are safe:

There is no first name. The First Name column is empty on all 300 rows in icp-contacts-first-300.csv, and roughly 128 of the addresses are role inboxes (info@, service@, office@, support@, contact@, sales@, admin@, estimates@, scheduling@). No email below uses a first name, and none of them say "Hi there." Several open with no salutation at all, which reads better into a front desk inbox than a fake greeting does.

Business names in the list run up to 92 characters and some carry commas, ampersands, and trademark marks, so {{Business Name}} always sits inside a sentence and never alone on a salutation line.

Voice. No em dashes. No emojis. No stacked hype adjectives. Banned words: revolutionary, game changer, unlock, supercharge, seamless, cutting edge. Money words over metric words: made, paid, worth, landed, not attribution, ingest, normalize, unify. Full https:// URLs. One CTA per email.

Sequence 1: Cold outbound, local service business owners

Who it is for. Owners and operators of local service businesses with real inbound call volume: roofing, plumbing, HVAC, electrical, restoration. The contact fits ICP A in outreach-and-pipeline.md: runs paid lead flow from more than one source, has a tracking number setup somebody else built, and cannot name which channel produced the last ten jobs without guessing.

Voice. He is reading this between jobs, on a phone, standing up. Short sentences. No jargon. Nothing he has to learn. If a paragraph needs a second read, rewrite it.

Entry trigger. Contact added to the batch, ICP A confirmed, email verified, no prior touch on record. Stage 1, Identified.

Exit trigger. Any reply pulls the contact out immediately and into a human conversation. Otherwise the sequence exits after Email 5 on day 18. Day 21 with no reply moves the record to the 90 day re-approach list with a dated wake-up, which is the entry point for Sequence 4.

Sequence 1, Email 1

Day offset: Day 0

Subject: What was your last call worth? Alternate A: Four seconds, and you know if today paid Alternate B: A question about the calls coming into {{Business Name}}

Preview text: Not how many calls. What they were worth.

Body:

This is for whoever watches the money at {{Business Name}}.

Somebody called you an hour ago. Do you know what that call was worth?

Most systems will tell you it lasted six minutes. Six minutes is not a number you can spend.

I built BirdsEye so an owner can look at his phone for four seconds between jobs and know what the business made. One number on the screen. The last call with a dollar next to it. Nothing to dig through and nothing to learn.

I am not going to pitch you software over email. I would rather show you what your last 90 days of calls look like with a dollar on each one, and let you decide from there.

CTA: Reply "show me" and I will send the one screen it puts on your phone for a {{Niche}} operation.

Sequence 1, Email 2

Day offset: Day 3

Subject: It should already be on the screen Alternate A: You should not have to go looking for it Alternate B: End of the day, without you asking

Preview text: A chart at the end of the day that tells you it worked.

Body:

The specific reason I reached out.

Nobody wants another dashboard. You already have logins you never open, and every one of them was sold to you as clarity.

So this is not a place you go look. It is a number that shows up. End of the day and end of the week, a chart you do not have to interpret. Up or down, and what the work was worth.

That is the whole test I hold it to. If you have to learn it, I built it wrong.

Nothing in it asks you to sit down at a desk, which matters when the desk is a truck.

CTA: Reply "day" and I will send you what the end of day view actually looks like on a phone.

Sequence 1, Email 3

Day offset: Day 7

Subject: You do not have to change your phone numbers Alternate A: Your numbers stay on the trucks Alternate B: Nothing changes on your side

Preview text: Same numbers, same forwarding, different screen.

Body:

Please pass this to whoever handles the phones at {{Business Name}}.

The first thing everybody asks is whether they have to reprint the trucks, the yard signs, and the door hangers. No.

BirdsEye reads the tracking numbers you already have across Twilio, SignalWire, CallFire, and CallRail. Your numbers stay. Your forwarding stays. Nothing on your side moves.

What changes is what you see. Every call carries a dollar figure and a plain answer to what the person actually wanted. Roof replacement. Burst pipe. Price shopping for spring.

And the junk drops out before it reaches the number, so what is left on the screen is real work instead of robocalls and people selling you SEO.

CTA: Give me 20 minutes and I will put your own calls on screen with dollars on them: https://birdseyeroi.com

Sequence 1, Email 4

Day offset: Day 12

Subject: Why I built this Alternate A: I was tired of guessing Alternate B: The short version of the whole thing

Preview text: No pitch. Just the reason it exists.

Body:

Twelve days of emails, so here is the honest version.

I built this because I was tired of guessing.

The calls were tracked. They were tracked in four different places. And at the end of the month I still could not tell you which spend produced the jobs, so I made the call anyway and hoped.

So I put it in one place and made every call carry a dollar. Now I look once and I know.

That is the whole product. The transcribing, the reading, the junk filtering, all of it only exists so that one look is true.

One more thing, so you read the rest of this correctly. This is not a monthly software bill you approve and then have to justify every quarter. We work on a revenue share and profit share basis, which only makes sense if the calls are producing money we can both see. What that looks like for {{Business Name}} is a conversation worth having live, not a number I am going to invent in an email.

CTA: Book 20 minutes, we will walk your own calls, then talk structure: https://birdseyeroi.com

Sequence 1, Email 5

Day offset: Day 18

Subject: Closing your file Alternate A: Last one from me Alternate B: I will stop here

Preview text: No pitch in this one. Just the close-out.

Body:

Last note to {{Business Name}}.

A few emails and no reply, which usually means one of three things. You have this handled, the timing is wrong, or it is not the fire you are fighting this quarter. All three are fine answers and none of them need a reply.

I am closing your file so I stop landing in your inbox.

If it comes back around, the thing worth keeping is small. Whatever you end up using, make it put a dollar on the call. A call count is not money, and the owner of a {{Niche}} business in {{City}} should not have to dig for the part that is.

Everything is at https://birdseyeroi.com whenever.

CTA: Reply "later" and I will check back in six months. Otherwise this is the last one.

Sequence 2: Cold outbound, lead-gen and marketing agencies

Who it is for. Owners and operations leads at lead generation and marketing agencies running call flow for multiple clients. ICP B in outreach-and-pipeline.md: multiple client accounts across more than one call provider, a recurring reporting obligation, pay per call economics somewhere in the model, and churn driven by clients who doubt lead quality.

Voice. Peer to peer. Nothing in this sequence explains what call tracking is, because he sells it. His problem is not generating calls, it is proving they were worth paying for. The subject is the Friday report, the renewal conversation, and the fact that being judged on volume is a fight nobody wins.

Entry trigger. Contact added to the batch, ICP B confirmed, email verified, no prior touch on record. Stage 1, Identified.

Exit trigger. Any reply pulls the contact into a human conversation immediately. Otherwise the sequence exits after Email 5 on day 18, and day 21 with no reply moves the record to the 90 day re-approach list.

Sequence 2, Email 1

Day offset: Day 0

Subject: The report you have to defend on Friday Alternate A: You are not short on calls Alternate B: Proving the leads were worth paying for

Preview text: Per service, per area, ready to send.

Body:

For whoever builds the client reporting at {{Business Name}}.

You are not short on calls. You are short on proof.

Friday comes, the client asks how it is going, and the honest answer takes two hours in a spreadsheet you rebuild every month from three different places.

BirdsEye turns the calls you already produce into a report with dollars on it, broken out per service and per area. Roofing did this. HVAC did that. The north side beat the south side. What moved since last month.

Something you send, not something you build. On brand, and good enough to go out without editing.

CTA: Reply "report" and I will send the format we would run for one of your accounts.

Sequence 2, Email 2

Day offset: Day 3

Subject: Being judged on volume is a fight nobody wins Alternate A: Deliver 400, get asked for 500 Alternate B: Change the unit

Preview text: Volume has no ceiling. Value has a number.

Body:

The structural problem with the way most agencies get graded.

Deliver 400 calls and get asked for 500. Deliver 500 and get asked why they are worse than the 400. There is no version of that conversation you win, because volume has no ceiling, no floor, and no relationship to whether the client made money.

The way out is to change the unit. A report that shows which services and which areas produced revenue puts the conversation on the ground where you actually performed, and it turns a monthly interrogation into a monthly comparison.

That is what this produces. Same calls you are already delivering, with a dollar on each one and split the way the client thinks about his own business.

Nobody churns over a bad month. They churn when they stop being able to see it worked.

CTA: Reply with one client account name and I will send the report shape for it.

Sequence 2, Email 3

Day offset: Day 7

Subject: You keep your stack. It gets a dollar column. Alternate A: Nothing gets ripped out Alternate B: No client conversation about changing numbers

Preview text: No migration. Just the column nobody has.

Body:

The practical version, since the first question is always about migration.

You do not rip anything out. Whatever mix of Twilio, SignalWire, CallFire, and CallRail your accounts sit on, BirdsEye reads all of it and adds the one column nobody else has, which is what the call was worth.

Then it splits that by service and by area, which is how your client thinks about his own business anyway. He does not think in channels. He thinks about the fact that the roof jobs came from the north side and the drain jobs did not.

Junk calls drop out before the totals, so the number you send survives the client checking it against his own booked work. That is the part that matters on a renewal call, because a number he can verify is a number he stops arguing with.

CTA: Give me 20 minutes and I will build the view against one live account: https://birdseyeroi.com

Sequence 2, Email 4

Day offset: Day 12

Subject: Why I built this, and how it works between us Alternate A: Not a per-seat license you resell Alternate B: The part most agencies ask about second

Preview text: The honest version, including the commercial side.

Body:

Four emails in, so here is the honest version and the part you are actually weighing.

I built this for myself first. I was running lead flow and I could not prove, on a Friday, that any of it landed. I could prove the phone rang. Nobody pays for the phone ringing.

So I made every call carry a dollar, then made the output something I would be proud to send instead of something I had to get on a call and explain.

On the commercial side. This is not a per-seat license you buy, mark up, and resell. We work on a revenue share and profit share basis, built around what the call data actually surfaces, which means it only works if we can both see it working.

I am deliberately not putting terms in an email. Your account count, your provider spread, who owns each client relationship, and how your reporting obligation is structured all change the shape of it. Quoting a structure before I know those things would be a guess, and you would be right to discount a guess.

CTA: Book 20 minutes and we will talk structure against your actual account mix: https://birdseyeroi.com

Sequence 2, Email 5

Day offset: Day 18

Subject: Closing the loop on this Alternate A: Fit or no fit, both are useful Alternate B: I will stop here

Preview text: One thing worth keeping either way.

Body:

Last note to {{Business Name}} on this.

No reply usually means the fit is not there, the timing is not there, or you already have somebody producing this. All three are fine and none of them need explaining. I am closing the loop so I stop crowding your inbox.

One thing worth keeping regardless of what you do with us.

The report you send is more of your product than the leads are. A client who can see, per service and per area, what your work was worth does not have the "I am not sure this is working" conversation with you in month seven. He has it with somebody else, about somebody else.

Whatever tool you use, make the top of that page say what the work was worth.

https://birdseyeroi.com if you want it later.

CTA: Reply "later" with a month and I will check back then. Otherwise this is the last one from me.

Sequence 3: Re-engagement, went quiet partway through the cadence

Who it is for. A contact who engaged and then stopped. They opened, or replied once, or took a call, and then went silent somewhere between Email 2 and Email 4 of the cold cadence. This is not a cold contact and must never be written as one. They know who we are.

Voice. Operator by default. Each email carries an Agency swap.

Entry trigger. Contact showed at least one engagement signal (a reply, an answered call, a booked and then cancelled slot, or repeat opens on two separate touches) and has since gone 14 days with no response while still inside stages 2 through 4 of the pipeline.

Exit trigger. Any reply, of any temperature, exits the sequence into a human conversation. A clean no exits to closed-lost with a reason recorded and a re-approach date. No response after Email 3 exits to the 90 day re-approach list.

Note for the sender. Do not resend the cold pitch. The job here is to name the silence without any guilt in the phrasing, and to make replying cheaper than ignoring.

Sequence 3, Email 1

Day offset: Day 0

Subject: Did this fall off the list? Alternate A: Picking this back up, or not Alternate B: Still worth your time?

Preview text: One question. A no is a completely fine answer.

Body:

We were talking about putting a dollar on the calls coming into {{Business Name}}, and then it went quiet on my end.

That is usually a scheduling problem, not an interest problem, so I am not reading anything into it.

One question and I will work off whatever you say. Is this still worth your time this quarter, or did it fall off the list?

If it fell off, tell me and I will stop. That is a real answer and it is faster for both of us than me guessing for another month.

Agency swap (replace the opening line):

We were talking about the reporting side at {{Business Name}}, the per service and per area version, and then it went quiet on my end.

CTA: Reply with one word: yes or no.

Sequence 3, Email 2

Day offset: Day 5

Subject: The part that got your attention the first time Alternate A: Still the same thing Alternate B: Worth 60 seconds even if the answer stays no

Preview text: One look, and you know what the business made.

Body:

No answer yet, so I will make this useful whether or not you ever reply.

What got your attention originally was not a feature. It was that you should be able to look at your phone for four seconds between jobs and know what the business made today, and right now you cannot.

That has not changed and it is not going to. The number is either on the screen without you asking for it, or you are going to keep making spend decisions on a feeling about which month felt busy.

You can fix that with us or without us. But fix it before the next budget decision, because a call count is not money and a busy week is not a good week.

Agency swap (replace the middle two paragraphs):

What got your attention originally was not a feature. It was that the proof of your work should be sitting there ready to send on a Friday, per service and per area, instead of taking two hours to rebuild.

That has not changed. Either the report exists before the client asks, or you spend every renewal call defending a volume number that was never the point.

CTA: Reply "screen" and I will send you the one view, no call required, whether or not you ever become a customer.

Sequence 3, Email 3

Day offset: Day 12

Subject: Closing this out unless you say otherwise Alternate A: Last one, then I will leave it Alternate B: Open, later, or closed

Preview text: Three words, and I will file it however you want.

Body:

Housekeeping, not a pitch.

I do not want to be the person still emailing {{Business Name}} in six weeks about something that quietly stopped mattering in June.

So: open, later, or closed.

Open means I follow up next week with something specific. Later means I put a dated reminder on it for the quarter you name and go quiet until then. Closed means done, and I will not take it personally.

If none of those are true and there is an actual objection sitting underneath this, send me the objection instead. I would rather answer the real thing in one email than keep circling it.

Agency swap: none. This email is the same for both audiences.

CTA: Reply with one word: open, later, or closed.

Sequence 4: Win-back, told us no within the last 90 days

Who it is for. A contact who gave a clean no inside the last 90 days. They took the conversation seriously enough to close the door properly, which makes them a better prospect than most of the cold list. The reason for the no is recorded on the record and should inform which alternate subject line gets used.

Voice. Operator by default. Each email carries an Agency swap.

Entry trigger. Record sits in stage 7b, Lost, with a reason recorded and a re-approach date that has now come due at or near 90 days from the no.

Exit trigger. Any reply exits into a human conversation. A second no exits to long-term nurture with a 12 month wake-up and no further outbound sequence. No response after Email 3 exits to the same 12 month list.

Note for the sender. Never argue with the original no and never imply they made a mistake. The premise is that circumstances change, not that they were wrong. If the recorded reason was budget, lead with Email 2 rather than Email 1.

Sequence 4, Email 1

Day offset: Day 0

Subject: You said no in the spring. Checking if that still holds. Alternate A: Circling back exactly when I said I would Alternate B: Not relitigating the no

Preview text: Same question, 90 days later. Same clean no is fine.

Body:

You told me no a few months back on the call revenue conversation, and I said I would check in rather than keep pushing. This is that check-in.

I am not relitigating it. The reason you gave was a good one at the time and I wrote it down.

The only thing I am testing is whether the circumstances underneath it have moved. Three months is long enough for a provider change, a budget cycle, a new person owning the reporting, or a quarter where the marketing spend at {{Business Name}} stopped producing what it used to.

If none of that has changed, say so and I will set the next reminder further out.

Agency swap (replace the third paragraph's examples):

Three months is long enough for an account to churn, a new client to land, a provider to change underneath you, or a renewal call that went worse than it should have.

CTA: Reply "same" if nothing has changed and I will move the reminder out another six months.

Sequence 4, Email 2

Day offset: Day 7

Subject: The part I did not explain well the first time Alternate A: If the no was about another line item, read this Alternate B: A short note, and no ask attached

Preview text: It is not a monthly bill you have to justify.

Body:

One thing, then I will get out of the way.

Looking back at our conversation, I do not think I explained the arrangement properly, and I suspect that is what the no was actually about.

This is not a monthly software subscription you approve and then have to defend every quarter. We work on a revenue share and profit share basis, tied to what the call data actually surfaces. If it is not producing money we can both see, the arrangement does not make sense for either of us, which is a very different commitment than a line item.

What that looks like for {{Business Name}} depends on your volume and your service lines, so it is a live conversation and not a number I am going to invent in an email.

If the original no was about committing to another vendor bill, that is worth 15 minutes to re-check.

Agency swap (replace the fourth paragraph):

What that looks like for {{Business Name}} depends on your account count, your provider spread, and who owns each client relationship, so it is a live conversation and not a number I am going to invent in an email.

CTA: Reply "structure" and I will get 15 minutes on the calendar to walk it through properly.

Sequence 4, Email 3

Day offset: Day 18

Subject: Filing this as a real no Alternate A: Last one, and I mean it this time Alternate B: Marking it closed unless you tell me otherwise

Preview text: No follow-up after this one.

Body:

I said I would check in once at 90 days, and I have now done that twice, which is the edge of what is reasonable.

I am marking {{Business Name}} as a closed no. No further sequence, no drip, no quarterly nudge.

If it ever becomes relevant, everything is at https://birdseyeroi.com and my address does not change. The thing worth keeping is the same one it always was. Whatever you use, make it put a dollar on the call, and make the number show up without you going to look for it.

Thanks for giving me a straight answer the first time. That is rarer than it should be and it made this easy.

Agency swap (replace the third paragraph's last sentence):

Whatever you use, make the top of the client report say what the work was worth, per service and per area, before he has to ask.

CTA: No action needed. Reply only if you want the door left open.

Sequence 5: Post-demo nurture, saw it and did not close

Who it is for. A prospect who took the demo, saw the product against their own situation, and did not move to proposal. They have seen the screens, so nothing here re-explains the product. The job is to surface the real hesitation and force a decision without a second demo.

Voice. Operator by default. Each email carries an Agency swap.

Entry trigger. Demo held and logged, stage 4, and 48 hours have passed with no proposal request and no scheduled next step.

Exit trigger. A proposal request exits to stage 5. A clean no exits to stage 7b with the reason recorded and a 90 day re-approach date set, which is the entry point for Sequence 4. No response after Email 3 exits to the same 90 day list.

Note for the sender. This is an alternate to the three-email nurture in Section 2 of copy-emails-social.md. Different day offsets, different angles. Run one or the other, never both.

Sequence 5, Email 1

Day offset: Day 2 (2 days post-demo)

Subject: The one screen from our call Alternate A: The part that actually puts the dollar on the call Alternate B: Picking up where the demo left off

Preview text: Not a recap. The single screen that mattered for you.

Body:

Thanks for the time on the demo. Rather than a recap of everything, here is the one piece that matters for your situation.

Revenue rules are what put the dollar on the call. You set what a booked roof is worth, what a drain job is worth, what a service call is worth. Per service, per niche, as rough or as exact as you want to be on day one.

After that the screen stops being a list and starts being money. The end of day number is just true, and you can look at it for four seconds and be done.

That is the layer a phone provider does not have. A provider can tell you the call happened. It has no idea what the call was worth.

Nothing else has to change on your side. Your numbers, your forwarding, and your providers stay where they are.

Agency swap (replace the third paragraph):

After that the report writes itself. Per service and per area, each line carrying a dollar figure, sorted so the client sees which service carried his month without you narrating it on a call.

CTA: Reply with your two biggest service lines and I will write out how the revenue rules would be configured for them.

Sequence 5, Email 2

Day offset: Day 9

Subject: The objection I should have answered on the call Alternate A: If the hesitation is the commitment, read this one Alternate B: What I did not explain well during the demo

Preview text: The real hesitation, answered straight.

Body:

Thinking back on the demo, I do not think I answered the real hesitation, so let me do it now.

When somebody sees it, likes it, and still does not move, it is usually not the product. It is the commitment. Another vendor, another monthly line item, another thing to justify when the quarter gets tight.

So here is the part I should have led with. This is not a monthly software subscription. We work on a revenue share and profit share basis, built around the money the call data actually surfaces. If it is not producing, the arrangement does not make sense for either of us.

What that looks like specifically for {{Business Name}} depends on your volume, your provider mix, and your service lines, which is why it belongs in a live conversation and not in an email where I would be guessing.

If the hesitation is something else entirely, tell me what it is and I will answer it straight in one email. No second demo required.

Agency swap (replace the fourth paragraph):

What that looks like specifically for {{Business Name}} depends on your account count, your provider spread, and who owns each client relationship, which is why it belongs in a live conversation and not in an email where I would be guessing.

CTA: Reply with the actual hesitation and I will answer it in one email.

Sequence 5, Email 3

Day offset: Day 21

Subject: Should I close this out? Alternate A: Where do you want to leave this? Alternate B: Open or closed, either is fine

Preview text: One question, and no follow-up if the answer is no.

Body:

No pitch here, just housekeeping.

You have seen it, so there is nothing left for me to show you. One direct question instead: should I keep this open or close it out?

If it is timing, name the quarter and I will go quiet until then. If it is a no, that is genuinely fine and I will stop.

If it is still a maybe, the fastest way through is not another demo. Send me one month of your calls and I will put a dollar on each one and send it back. You will know in about a minute whether that number is worth having in your pocket, and it costs you an afternoon of mine rather than another hour of yours.

Agency swap (replace the last paragraph):

If it is still a maybe, the fastest way through is not another demo. Give me one month of calls from a single account and I will send back the report you would have handed that client on a Friday. Then you are judging the actual deliverable instead of a screenshare.

CTA: Reply with one word: open, later, or closed.

Sender checklist before any of this goes out

1. Rewrite {{Business Name}}, {{City}}, {{State}}, and {{Niche}} to the sending platform's syntax and map each to the exact CSV column name.
2. Confirm no email in the send references a first name. There is no first name in this batch.
3. Confirm the audience matches the sequence. Sequence 1 to operators, Sequence 2 to agencies, Sequences 3 through 5 with the correct track selected. Never a mixed body.
4. Confirm no subject line, preview line, or opening line contains a spam share, a total call count, or a tracked revenue total.
5. Confirm the retired category line appears nowhere in the send.
6. Confirm no email quotes a price, percentage, split, tier, or term length. The terms conversation happens live, on the call, every time.
7. Confirm any product figure that does appear is on FACTS.md, and any dollar figure in creative sits inside a product frame with no business attached.
8. Confirm a reply of any kind pulls the contact out of automation and into a human conversation the same day.
9. Log every touch before the next one goes out.