A 45-minute working session. Where the build stands, the path a reply takes to your scheduling team, and the answers we need from you before the first send.
For Mohamad Hamdan, Liam O’Hare and whoever leads your scheduling team · Wednesday, November 4, 2026, 9:00 AM Pacific · Working draft for the call
100 sending domains and 5,000 Microsoft mailboxes are set up and warming. Every domain points to elianelectronicsrecycling.com. The first emails go out in mid-November.
Your scheduling team calls back, checks the details and closes. The pilot feeds that team, and how the team works stays yours.
Where replies land, who picks them up, how fast, and how your team gets back to each lead. Each answer is read back before we move on.
An interested reply turns into a pickup only once your team has it. The faster a reply gets a call, the higher the book rate.
Sending domains, bought October 26 from the names Liam approved. Half carry an Elian name and half are generic.
Microsoft mailboxes, 50 on each domain, one for each of your approved sender names.
Of warm-up on every domain, counted from the day its mailboxes were set up, October 26 to 28.
Cold emails sent so far. Nothing goes out before the warm-up ends and the two business days for your comments have run.
Source: your sending workspace, read the morning of November 4, 2026 (100 domains, 5,000 mailboxes connected, warm-up on, no cold email sent). Domain and sender names as Liam approved them on October 22 and 23. None of your own domains or mailboxes is touched.
Under the signed agreement, a qualified lead is a business in a running lane, inside your service range, that asks for a pickup, a quote or a call and has been passed to your scheduling team. An interested reply alone does not count, so the handoff matters to both of us.
The orange steps are your team’s. LinkedIn replies take the same path as email.
Prices, pickups and every question about your service. We never quote a price, commit you to a pickup or answer a service question. Each of those goes to your team within minutes.
Calls back, checks the floor, the vehicle, the schedule and any insurance certificate the building needs, then closes. A word back on each one that closes puts it in the monthly report.
The whole thread and the company’s page, by email to the address you name, within minutes.
The contact’s details, the city, the nearest facility with the range check, and any items they named, at the top of every handoff.
What does your team ask on every first call today? Anything the company has already told us goes at the top.
| Option | How it works | Worth knowing |
|---|---|---|
| One shared address | Every reply lands in one inbox, and your lead hands each one to the right facility. | One place to watch, and one person owns it. |
| One address per region | Each region’s replies go straight to that region’s team. | Faster local pickup, and each address needs its own backup. |
| One person’s own address | Replies go straight to the person who calls back. | Quickest for a small team, and it stops when that person is out. |
Every interested reply reaches the address you name within minutes of landing.
The callback time is yours to set. Whatever your team can hold every day is the right number.
Every handoff carries the whole thread and the company’s page, with your region’s number on it, so the first touch is a call, the way your team works today.
Nobody logs into a sending mailbox while we run them, because a login from a second location harms the mailbox. Your team writes from its own address, with the whole thread in hand. Liam’s guidelines flag your main domain’s sending reputation, so the address matters.
The page carries a booking link for a pickup or a quote call if your team uses one. Without one, the page carries the region’s number and a way to reply.
The yes reply and the page go from the mailbox the company wrote to, within minutes. Everything after that is your team’s conversation.
When your team writes back to a lead, which address does it come from?
Do you use a booking link for pickups or quote calls? If not, are the phone number and a reply enough on the page?
| Region | Facility | Number on the page | Still right? |
|---|---|---|---|
| Southern California | Santa Ana | (714) 494-3242 | |
| Los Angeles | Huntington Park | (714) 494-3242 | |
| Northern California | San Jose | (408) 819-6515 | |
| Dallas and Fort Worth | Fort Worth | (972) 900-8882 | |
| Austin | Austin | (972) 900-8882 | |
| New Jersey and New York | Woodland Park | (917) 939-9900 | |
| Florida | Hollywood | (772) 867-2080 | |
| Illinois | Burr Ridge | (773) 801-6161 | |
| Georgia | Atlanta | (404) 990-9990 | |
| Ohio | Piqua | (773) 801-6161 |
No contacts are pulled and nothing is sent for Arizona, as Liam asked.
Paper shredding, CRT monitor recycling and TV recycling are mentioned only to California companies.
It is not a qualified lead under the agreement, and it still shows in the monthly report by state. On October 20 you told us requests from a state are how you decide where the next facility goes, and that you fly in and rent a truck to serve some of them. Send these to your team marked out of range, or hold them for the report?
Regions and numbers from Liam’s copy guidelines of October 22. Facilities from your coverage sheet, also October 22, with ten facility tabs and 3,191 entries in all, each a city or town of 1,000 people or more within a 90-minute drive.
| # | To settle | The options | Your answer |
|---|---|---|---|
| 1 | Where interested replies land | One shared address, one per region, or one person’s own address | |
| 2 | Who leads the scheduling team, and who covers | A named lead and a named backup | |
| 3 | How fast your team calls back | Your time in business hours, after hours, US mornings and Thanksgiving week | |
| 4 | Where your team writes back from | An address you choose, with the whole thread in hand | |
| 5 | A booking link on the page | Your link, or the region’s number and a reply | |
| 6 | The numbers by region | As on Liam’s list, or corrected today | |
| 7 | Replies from outside your range | Sent to your team marked out of range, or held for the report | |
| 8 | Who scores the first 30 days, and how closes reach us | Mohamad or a person you name, with a weekly note or a reply marked closed on each handoff |
Under the signed agreement, Elian names the handoff address, the phone number for the page and a booking link if the scheduling team uses one (section 4), and Elian or the person it names by email scores each lead (section 6).
| When | What | Who |
|---|---|---|
| Today | The eight answers on the page before this one | Elian |
| During the warm-up | The Technology company list, to mark any company that is a client of yours or in your pipeline | ECG to Liam |
| During the warm-up | The copy for every email step, every LinkedIn message and the yes reply, with a sample page | ECG to Liam |
| During the warm-up | Both LinkedIn accounts connected, with nothing changed on their passwords or security settings without your OK | ECG |
| When it is ready | Your short video on what Elian does and who it serves, one to two minutes. A phone recording is enough. | Elian |
| Mid-November | The first emails go out and ramp to full pace over the first week, with a note from Dan that day | Dan |
| From the first send | Your login to the live reporting view, and access to your own sending workspace to see and comment | ECG |
| Every Monday and Friday | The suppression record, with every bounced address, every opt-out and every domain that asked to come off | ECG to Liam |
| End of each monthly period | The written report, with every qualified lead tagged by state, and the full contact export | ECG |
Veterans Day, Wednesday, November 11, is a federal holiday, so it is not a business day under the agreement. The two business days for each list and for the copy count from the day it reaches you.