Escalating from success to the account executive

A customer-success note that forwards the ticket history asks an AE to become support. Give them one decision — credit, extend, or hold — plus the three facts that make that decision possible.

3 min read

The customer is angry. You have done what success can do. The AE owns the commercial lever. The draft that feels thorough is a forward of the thread with "can you weigh in?" They now have a second job: becoming you, for an hour, before they can do theirs.

A customer escalation handoff exists so the next person does not make the customer start over. This note has that job too. It has a second job the handoff does not: a decision only the AE can make.

Three facts, then the choice

What they want now. An outcome, present tense. "A credit for the March overage and a sentence they can send their own client." Not "they are unhappy."

What has been promised. Who said it, when. Include the soft ones. The AE's next email either keeps a promise or breaks one.

What has been tried. Each attempt and what it ruled out. So they do not offer the restart you already did.

Then the choice they own:

  • Issue the credit now.
  • Hold the credit until cause is confirmed.
  • Extend instead of crediting.
  • Take it to their manager.

Your recommendation, and the fact that would flip it. "I would issue it. I would hold if you know a renewal conversation this month where the credit will be more useful as a card than as a gesture."

Do not hand them a dump

A dump is how an AE answers "I will look at the thread" and then does not. They have a quota and a calendar. If the decision is not visible on a phone, it will wait until it is a fire, and then they will decide with less of this context rather than more.

Quote the customer's own ask and any date they set. Paraphrase drops the sentence they will forward. Keep heat out unless the heat is the content — usually it is not.

This is not a project handoff. You are not leaving. You still own the relationship mechanics. They own the money decision. Say that split so the customer does not gain two owners and no answers.

Send one briefing, then stop

You approve the words. No attachments. Link the ticket. If the AE has an account, you need an accepted contact. If they do not, they get email and a page.

A nickname you use for the customer stays on your side. The AE should see the name the customer uses. If you already share a nickname with them, that is a choice you made on the contact; it is not a default.

Default: "If I have not heard by 17:00 UTC I will tell the customer we are holding the credit pending cause, in those words." A default they can live with is how you avoid a second ping during their call.

If the afternoon is already in a session, connect your assistant and have it list the promises before you write the ask.

Frequently asked questions

How is this different from handing off a customer escalation?
A support handoff gives the next owner the story so the customer is not asked to repeat it. An AE escalation asks that owner for a commercial decision. Same three facts at the top. The last line is a choice, not a take this one.
What decision should success put in front of an AE?
A closed list the AE actually owns — issue the credit, extend the term, hold until engineering confirms cause, or escalate to their manager. Do not ask them to read forty messages and invent the ask.
Should I include the whole ticket thread?
Point at it. Put what the customer wants, what was promised, and what was tried in the briefing. The AE should be able to decide without opening the thread. If they cannot, the brief is not done.