A renewal note went out on a Tuesday to the champion who had been on the thread since the pilot. She replied the same afternoon: "Adding Marcus from procurement so he can take the commercial questions." Marcus showed up on the CC line. She stayed on To. Three days later the sequence sent the scheduled follow-up to her, same subject, opening with "following up on my note below." Marcus never got a question he could answer. She forwarded that follow-up internally with no comment. The deal sat in the same stage for another month, and the CRM still treated her as the person who owed the next reply.
Marcus was the person who could answer, and the sequence never wrote to him. It wrote to the champion because she was the last one to hit send. That is the rule I keep finding in the sequences I review. It misses the handoff as soon as a new address from the customer's company is on the thread.
A name on CC is often the handoff
A deal is easy to describe while the champion is the only customer on the thread, and a success issue is easy to describe while the admin is the only customer on it. A third address at their domain breaks that description.
Procurement is added once a price has been discussed. A questionnaire brings in someone from the security review. A VP who has never been on a call gets added when the champion writes that a manager needs to see the thread. An implementation owner can arrive in that same reply, and from then on the commercial question and the setup question belong to different people under one subject, even when the reply itself is only a polite sentence.
I look at that address before I lean on the friendly tone. "Happy to keep helping," beside a new finance address, usually means the champion has finished the part they can do. A reply that goes only to them asks them to stay with a question they already handed to someone else. They will write that they are checking with their team. After that the thread stalls, because the person who can answer is on the CC line and still has not been asked anything.
Name that person early in the next note, and give them one action that does not need a meeting. "Marcus, the open item is the net-30 language in section four. If that language works, reply here and I will send the order form to you." The champion can stay on the thread and does not have to translate. If you still need a follow-up, send it to Marcus, and start the timer from the note you sent him.
Support threads create the same stall from the other direction, and the CC feels considerate enough that nobody takes it out of the draft. A customer says something is still broken. The success manager replies and copies the account executive so the history is on the thread. From there the customer waits for the seller who described the fix on the demo, the account executive treats the thread as belonging to success, and the success manager is waiting on a confirmation. When I draft these, the note says who is writing back. "I am on this, and I will confirm by Thursday whether the patch landed. Alex is copied so the account stays informed. You do not need to bring Alex in separately."
Courtesy copies on your side
A manager, a solutions engineer, a legal alias, and a shared success inbox can each have a reason to be copied. The customer's job gets less clear each time another one is added.
People reply when they can see who is waiting. A note between one sender and one recipient makes that obvious. A note with several people from your company on CC asks the customer to choose, and many of them will not. They wait for your side to settle who is speaking. Your side waits too, because anyone on that CC line can tell themselves that someone else is already writing.
A manager can hear about the thread without being on it. Put the update on the deal, or send a separate note that the customer never sees. Once the manager's address is on the live thread, the customer knows a manager is reading, and what comes back is shorter and more careful. I leave the header with the person who owns the reply, and I tell the manager afterward. Everyone inside the company can see the crowded thread, and the next morning it still has no answer.
People reach for BCC when they want a colleague to see the note without widening the header the customer can see. On a thread the customer might forward, that choice goes wrong later. The colleague can read, and the customer has no way to know. If the colleague then hits reply-all, the customer learns someone was included without being listed. Explaining a normal CC in the note is a smaller problem than that surprise. If someone on your team needs the thread, add them and say why they are there. If they only need to know how it turned out, tell them separately and leave the header alone.
Sequences that keep writing to the champion after she has widened the thread hit the same stall a few days later. The follow-up goes to her address again, opens with a soft "checking in," and says nothing about the new names on the last reply. She already introduced the person who can answer. Asking her again means she has to make that introduction a second time.
The follow-up after the header changes
When a reply lands, compare its To and CC addresses with the note before it. A new address at the customer's domain may now own the next reply. If the new address is at your company, the customer may not know who should receive theirs. A sequence written last week should not ignore either change.
If the new address is theirs, write the next note to that person and keep the champion on the thread. Send procurement the clause that is still open. Tell the security reviewer where the questionnaire stands. For a manager, write the decision that was deferred and list the choices, so they can answer in a few lines. Hold the older steps that were aimed at the champion until you see whether the new person answered. If those steps go out anyway, the buyer gets two different asks under one subject.
When the new address belongs to your own company, make ownership plain near the top of the note. Say who will respond and on which day, and mention anyone who is only there to read. Point the follow-up timer at the customer. A comment your solutions engineer has not written yet is an internal task, and it should not hold the customer thread open.
Reply-all is a poor fit once the header is crowded. A legal alias, a billing alias, a second champion, and a VP who attended one meeting should not have to sort out, on every follow-up, which of them is speaking. Send a new note to the person who can approve, and mention the earlier thread so they can find the history. Leave the long thread as it is. Copy the paragraph that still matters. Later follow-ups can stay with the person who has the decision.
A queued step still carries the old recipient and the old wording. It will send before anyone on your team has read the CC line. Pause that step the same afternoon, and write to the new person while the champion's note is still the latest thing in their inbox. If they have not answered after four business days, the sequence can resume, aimed at them.
After the note goes to Marcus, look at what the CRM still lists as the owner. If the champion replies that Marcus is handling it, the thread gets marked engaged and the activity looks fine, even though he now owes the reply. A stalled-deal view that still names the champion will send the rep back to her, and the log fills with notes the buyer did not ask for.