Customer Success English

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 01: Onboarding and Implementation Expectations
Original fictional case: Customer lead Omar expects a launch on Friday, 9 October. The export owner and training slot are still unassigned. Customer success manager Lena cannot confirm readiness. The agreed launch conditions are an approved customer export, a successful test import, user acceptance of the main workflow, and completed administrator training. The customer owns data preparation; the supplier owns import mapping and training delivery. No one has yet confirmed that the required people are available. A readiness review is scheduled for Thursday at 15:00 UTC.
Language workshop: Turn a hoped-for launch into a shared readiness plan
Communication goal: Clarify owners, dependencies, and acceptance checks before confirming a customer launch date.
Language guidance: A target date is not evidence of readiness. The four stated conditions are export approval, a successful test import, workflow acceptance, and administrator training. The Thursday review checks those conditions; holding the meeting alone does not satisfy them.
Useful expressions (preserve the supplied facts): Which workflow must the team be able to complete on launch day? / Friday is the target, but readiness is not yet confirmed. / The test import depends on an approved customer export. / Your team prepares the data; our team maps the agreed fields. / Who can own the export and confirm its availability? / Has that person accepted the task and the timing? / We need users to complete the agreed workflow successfully. / Who will attend the administrator training? / A calendar invitation does not mean the training has happened. / Let us review readiness on Thursday at fifteen hundred UTC. / Once the approved export is available, we can assess the import schedule. / Use the agreed secure transfer route and only the required fields. / What support coverage is agreed for the initial operating period? / The export owner and training slot are still open. / Confirm launch only after the agreed conditions are met. / I will update the plan with each owner, dependency, and confirmed date.
Vocabulary: onboarding: The process of preparing a customer to use a service effectively. / implementation: Work to configure, connect, and introduce a solution. / kickoff: The initial meeting aligning purpose, people, and approach. / success plan: A shared record of outcomes, actions, ownership, and measures. / target date: A desired date whose commitment status must be specified. / go-live: The start of operational use under agreed conditions. / dependency: A task or condition on which another step relies. / prerequisite: Something required before a particular activity can proceed. / data migration: Moving data between systems with appropriate checks. / source export: Data extracted from the originating system. / data mapping: Specifying how source fields correspond to destination fields. / data owner: The role accountable for the relevant data and its use. / test import: A controlled trial of bringing data into the destination. / UAT: User acceptance testing; users checking the solution against agreed needs. / acceptance criterion: A defined condition used to judge whether work is acceptable. / administrator: A user with specified management permissions in the service. / training slot: A scheduled period with the required trainer and participants. / readiness review: A check of whether the conditions for the next stage are met. / cutover: The coordinated transition into a new operational arrangement. / rollback plan: An approved approach for reversing a change if required. / hypercare: A defined period of enhanced support after introduction. / handover: Transfer of responsibility with the necessary information. / RACI: Responsible, accountable, consulted, and informed; a role-assignment framework. / open dependency: A required preceding task or condition not yet satisfied.
Speaking task: Read Omar and Lena aloud, then swap roles. Explain customer data preparation and supplier mapping as separate, coordinated responsibilities. Check all ten gaps. Reread the four launch conditions and Thursday fifteen-hundred UTC review without substituting one completed task for another. Repeat the conditional announcement and ownership close, retaining the unassigned people and training slot as open work.
Partner: Omar: Customer implementation lead / Lena: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A Monday launch remains a target. Customer lead Farah owns source-data approval. Supplier lead Ben owns import mapping. Training is complete, but the test import has failed. The readiness review is Friday at 10:00 UTC.
Model for comparison AFTER my attempt, not a response to give me first: Omar: Please also make clear who supports the team after launch. They should not have to guess which contact to use.
Lena: We will confirm the handover and initial support arrangements. Coverage and contacts need to be explicit, with any enhanced support period defined rather than assumed to continue indefinitely.
Omar: I will confirm the data lead and user testers, check their availability, and send a conditional update to the team.
Lena: I will update the success plan with the owners, dependencies, and actual status. At Thursday's review, we will decide from the evidence against all four conditions, not from the date alone.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 01: Onboarding and Implementation Expectations
Original fictional case: Customer lead Omar expects a launch on Friday, 9 October. The export owner and training slot are still unassigned. Customer success manager Lena cannot confirm readiness. The agreed launch conditions are an approved customer export, a successful test import, user acceptance of the main workflow, and completed administrator training. The customer owns data preparation; the supplier owns import mapping and training delivery. No one has yet confirmed that the required people are available. A readiness review is scheduled for Thursday at 15:00 UTC.
Language workshop: Turn a hoped-for launch into a shared readiness plan
Communication goal: Clarify owners, dependencies, and acceptance checks before confirming a customer launch date.
Language guidance: A target date is not evidence of readiness. The four stated conditions are export approval, a successful test import, workflow acceptance, and administrator training. The Thursday review checks those conditions; holding the meeting alone does not satisfy them.
Useful expressions (preserve the supplied facts): Which workflow must the team be able to complete on launch day? / Friday is the target, but readiness is not yet confirmed. / The test import depends on an approved customer export. / Your team prepares the data; our team maps the agreed fields. / Who can own the export and confirm its availability? / Has that person accepted the task and the timing? / We need users to complete the agreed workflow successfully. / Who will attend the administrator training? / A calendar invitation does not mean the training has happened. / Let us review readiness on Thursday at fifteen hundred UTC. / Once the approved export is available, we can assess the import schedule. / Use the agreed secure transfer route and only the required fields. / What support coverage is agreed for the initial operating period? / The export owner and training slot are still open. / Confirm launch only after the agreed conditions are met. / I will update the plan with each owner, dependency, and confirmed date.
Vocabulary: onboarding: The process of preparing a customer to use a service effectively. / implementation: Work to configure, connect, and introduce a solution. / kickoff: The initial meeting aligning purpose, people, and approach. / success plan: A shared record of outcomes, actions, ownership, and measures. / target date: A desired date whose commitment status must be specified. / go-live: The start of operational use under agreed conditions. / dependency: A task or condition on which another step relies. / prerequisite: Something required before a particular activity can proceed. / data migration: Moving data between systems with appropriate checks. / source export: Data extracted from the originating system. / data mapping: Specifying how source fields correspond to destination fields. / data owner: The role accountable for the relevant data and its use. / test import: A controlled trial of bringing data into the destination. / UAT: User acceptance testing; users checking the solution against agreed needs. / acceptance criterion: A defined condition used to judge whether work is acceptable. / administrator: A user with specified management permissions in the service. / training slot: A scheduled period with the required trainer and participants. / readiness review: A check of whether the conditions for the next stage are met. / cutover: The coordinated transition into a new operational arrangement. / rollback plan: An approved approach for reversing a change if required. / hypercare: A defined period of enhanced support after introduction. / handover: Transfer of responsibility with the necessary information. / RACI: Responsible, accountable, consulted, and informed; a role-assignment framework. / open dependency: A required preceding task or condition not yet satisfied.
Speaking task: Read Omar and Lena aloud, then swap roles. Explain customer data preparation and supplier mapping as separate, coordinated responsibilities. Check all ten gaps. Reread the four launch conditions and Thursday fifteen-hundred UTC review without substituting one completed task for another. Repeat the conditional announcement and ownership close, retaining the unassigned people and training slot as open work.
Partner: Omar: Customer implementation lead / Lena: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A Monday launch remains a target. Customer lead Farah owns source-data approval. Supplier lead Ben owns import mapping. Training is complete, but the test import has failed. The readiness review is Friday at 10:00 UTC.
Model for comparison AFTER my attempt, not a response to give me first: Omar: Please also make clear who supports the team after launch. They should not have to guess which contact to use.
Lena: We will confirm the handover and initial support arrangements. Coverage and contacts need to be explicit, with any enhanced support period defined rather than assumed to continue indefinitely.
Omar: I will confirm the data lead and user testers, check their availability, and send a conditional update to the team.
Lena: I will update the success plan with the owners, dependencies, and actual status. At Thursday's review, we will decide from the evidence against all four conditions, not from the date alone.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 01: Onboarding and Implementation Expectations
Original fictional case: Customer lead Omar expects a launch on Friday, 9 October. The export owner and training slot are still unassigned. Customer success manager Lena cannot confirm readiness. The agreed launch conditions are an approved customer export, a successful test import, user acceptance of the main workflow, and completed administrator training. The customer owns data preparation; the supplier owns import mapping and training delivery. No one has yet confirmed that the required people are available. A readiness review is scheduled for Thursday at 15:00 UTC.
Language workshop: Turn a hoped-for launch into a shared readiness plan
Communication goal: Clarify owners, dependencies, and acceptance checks before confirming a customer launch date.
Language guidance: A target date is not evidence of readiness. The four stated conditions are export approval, a successful test import, workflow acceptance, and administrator training. The Thursday review checks those conditions; holding the meeting alone does not satisfy them.
Useful expressions (preserve the supplied facts): Which workflow must the team be able to complete on launch day? / Friday is the target, but readiness is not yet confirmed. / The test import depends on an approved customer export. / Your team prepares the data; our team maps the agreed fields. / Who can own the export and confirm its availability? / Has that person accepted the task and the timing? / We need users to complete the agreed workflow successfully. / Who will attend the administrator training? / A calendar invitation does not mean the training has happened. / Let us review readiness on Thursday at fifteen hundred UTC. / Once the approved export is available, we can assess the import schedule. / Use the agreed secure transfer route and only the required fields. / What support coverage is agreed for the initial operating period? / The export owner and training slot are still open. / Confirm launch only after the agreed conditions are met. / I will update the plan with each owner, dependency, and confirmed date.
Vocabulary: onboarding: The process of preparing a customer to use a service effectively. / implementation: Work to configure, connect, and introduce a solution. / kickoff: The initial meeting aligning purpose, people, and approach. / success plan: A shared record of outcomes, actions, ownership, and measures. / target date: A desired date whose commitment status must be specified. / go-live: The start of operational use under agreed conditions. / dependency: A task or condition on which another step relies. / prerequisite: Something required before a particular activity can proceed. / data migration: Moving data between systems with appropriate checks. / source export: Data extracted from the originating system. / data mapping: Specifying how source fields correspond to destination fields. / data owner: The role accountable for the relevant data and its use. / test import: A controlled trial of bringing data into the destination. / UAT: User acceptance testing; users checking the solution against agreed needs. / acceptance criterion: A defined condition used to judge whether work is acceptable. / administrator: A user with specified management permissions in the service. / training slot: A scheduled period with the required trainer and participants. / readiness review: A check of whether the conditions for the next stage are met. / cutover: The coordinated transition into a new operational arrangement. / rollback plan: An approved approach for reversing a change if required. / hypercare: A defined period of enhanced support after introduction. / handover: Transfer of responsibility with the necessary information. / RACI: Responsible, accountable, consulted, and informed; a role-assignment framework. / open dependency: A required preceding task or condition not yet satisfied.
Speaking task: Read Omar and Lena aloud, then swap roles. Explain customer data preparation and supplier mapping as separate, coordinated responsibilities. Check all ten gaps. Reread the four launch conditions and Thursday fifteen-hundred UTC review without substituting one completed task for another. Repeat the conditional announcement and ownership close, retaining the unassigned people and training slot as open work.
Partner: Omar: Customer implementation lead / Lena: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A Monday launch remains a target. Customer lead Farah owns source-data approval. Supplier lead Ben owns import mapping. Training is complete, but the test import has failed. The readiness review is Friday at 10:00 UTC.
Model for comparison AFTER my attempt, not a response to give me first: Omar: Please also make clear who supports the team after launch. They should not have to guess which contact to use.
Lena: We will confirm the handover and initial support arrangements. Coverage and contacts need to be explicit, with any enhanced support period defined rather than assumed to continue indefinitely.
Omar: I will confirm the data lead and user testers, check their availability, and send a conditional update to the team.
Lena: I will update the success plan with the owners, dependencies, and actual status. At Thursday's review, we will decide from the evidence against all four conditions, not from the date alone.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 02: Adoption Metrics and Health Scores
Original fictional case: Account C14 has 120 licensed users. In the last 30 days, 100 distinct users logged in. Of the 80 users whose roles require the approval workflow, only 30 completed it at least once. The dashboard health score is green because its current rule emphasizes logins. Customer lead Mei reports that some staff still use email approvals. Customer success manager Daniel must explain the different denominators and investigate the workflow gap without assuming every inactive license is wasted or that the account will certainly cancel.
Language workshop: The green score hides a workflow gap
Communication goal: Explain usage measures with the right population and distinguish access from meaningful adoption.
Language guidance: Login activity is 100 divided by 120, approximately 83.3%. Relevant workflow completion is 30 divided by 80, or 37.5%. Thirty divided by 120 is 25%, but that answers a different question about all licensed users.
Useful expressions (preserve the supplied facts): The login count shows broad access during this period. / It does not show that the approval workflow is being used. / These figures cover the last thirty days. / Eighty users have roles that require this workflow. / Thirty of eighty eligible users completed it, which is thirty-seven point five percent. / Thirty out of all one hundred twenty licenses would answer a different question. / What exactly triggers a workflow-completed event? / Count distinct users, not every repeated login. / Where do people switch back to email? / Low completion does not tell us the reason by itself. / Some licensed users may not need this workflow. / Green reflects the current scoring rule, not every aspect of account health. / Does this measure connect to the outcome you bought the product for? / Let us address the confirmed obstacle before scheduling generic retraining. / Use the same population and period definition for the follow-up. / Record the gap, the confirmed barrier, and the next measurement date.
Vocabulary: adoption: Use of a product or workflow in the intended working context. / licensed user: A person covered by the relevant access entitlement. / active user: A user meeting a defined activity condition within a stated period. / unique user: A distinct person or identity counted once under the measurement rule. / eligible population: The people for whom a particular measure is relevant. / denominator: The base quantity used in a fraction or rate. / login rate: The share of a defined population that logged in during a period. / workflow completion: Finishing the defined sequence of work. / breadth of adoption: How widely relevant use extends across users, teams, or functions. / depth of adoption: How extensively intended capabilities are used. / frequency: How often a defined action occurs within a period. / cohort: A defined group followed or compared on a shared basis. / health score: A configured indicator combining selected account signals. / weighting: The relative influence assigned to a component in a calculation. / leading indicator: A measure used as a possible signal of a later result. / lagging indicator: A measure of an outcome that has already occurred. / engagement: Participation or interaction under a stated definition. / sentiment: Expressed attitudes or feelings about the relationship or service. / usage telemetry: Recorded data about product interactions. / instrumentation: The setup used to capture events and measurements. / event definition: The rule specifying what a recorded action represents. / usage gap: A difference between intended and observed use. / adoption barrier: A condition making intended use difficult or impractical. / vanity metric: A flattering measure with weak relevance to the decision at hand.
Speaking task: Read Mei and Daniel aloud, then swap roles. Say the population and thirty-day period before each rate. Correct all ten gaps. Reread the 100/120 login rate, 30/80 workflow rate, and 30/120 all-license comparison. Repeat the targeted follow-up for the approver obstacle, keeping occasional completion, regular adoption, and cancellation risk distinct.
Partner: Mei: Customer operations lead / Daniel: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In one month, 45 of 60 licensed users log in. Only 40 users need the scheduling workflow; 20 of those complete it. A dashboard based on logins does not establish scheduling adoption.
Model for comparison AFTER my attempt, not a response to give me first: Mei: Let us begin with the supervisor group that reported the approver problem, then compare the same group after it is addressed.
Daniel: That gives us a defined cohort. We will record membership changes and keep the completion definition consistent, so a rise does not merely reflect a different population.
Mei: Please keep the renewal discussion separate for now. I am describing a workflow problem, not announcing that we intend to leave.
Daniel: Agreed. The usage gap deserves action, but it does not prove cancellation. We will validate the measure, investigate the approver obstacle, and agree what improvement we should check next.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 02: Adoption Metrics and Health Scores
Original fictional case: Account C14 has 120 licensed users. In the last 30 days, 100 distinct users logged in. Of the 80 users whose roles require the approval workflow, only 30 completed it at least once. The dashboard health score is green because its current rule emphasizes logins. Customer lead Mei reports that some staff still use email approvals. Customer success manager Daniel must explain the different denominators and investigate the workflow gap without assuming every inactive license is wasted or that the account will certainly cancel.
Language workshop: The green score hides a workflow gap
Communication goal: Explain usage measures with the right population and distinguish access from meaningful adoption.
Language guidance: Login activity is 100 divided by 120, approximately 83.3%. Relevant workflow completion is 30 divided by 80, or 37.5%. Thirty divided by 120 is 25%, but that answers a different question about all licensed users.
Useful expressions (preserve the supplied facts): The login count shows broad access during this period. / It does not show that the approval workflow is being used. / These figures cover the last thirty days. / Eighty users have roles that require this workflow. / Thirty of eighty eligible users completed it, which is thirty-seven point five percent. / Thirty out of all one hundred twenty licenses would answer a different question. / What exactly triggers a workflow-completed event? / Count distinct users, not every repeated login. / Where do people switch back to email? / Low completion does not tell us the reason by itself. / Some licensed users may not need this workflow. / Green reflects the current scoring rule, not every aspect of account health. / Does this measure connect to the outcome you bought the product for? / Let us address the confirmed obstacle before scheduling generic retraining. / Use the same population and period definition for the follow-up. / Record the gap, the confirmed barrier, and the next measurement date.
Vocabulary: adoption: Use of a product or workflow in the intended working context. / licensed user: A person covered by the relevant access entitlement. / active user: A user meeting a defined activity condition within a stated period. / unique user: A distinct person or identity counted once under the measurement rule. / eligible population: The people for whom a particular measure is relevant. / denominator: The base quantity used in a fraction or rate. / login rate: The share of a defined population that logged in during a period. / workflow completion: Finishing the defined sequence of work. / breadth of adoption: How widely relevant use extends across users, teams, or functions. / depth of adoption: How extensively intended capabilities are used. / frequency: How often a defined action occurs within a period. / cohort: A defined group followed or compared on a shared basis. / health score: A configured indicator combining selected account signals. / weighting: The relative influence assigned to a component in a calculation. / leading indicator: A measure used as a possible signal of a later result. / lagging indicator: A measure of an outcome that has already occurred. / engagement: Participation or interaction under a stated definition. / sentiment: Expressed attitudes or feelings about the relationship or service. / usage telemetry: Recorded data about product interactions. / instrumentation: The setup used to capture events and measurements. / event definition: The rule specifying what a recorded action represents. / usage gap: A difference between intended and observed use. / adoption barrier: A condition making intended use difficult or impractical. / vanity metric: A flattering measure with weak relevance to the decision at hand.
Speaking task: Read Mei and Daniel aloud, then swap roles. Say the population and thirty-day period before each rate. Correct all ten gaps. Reread the 100/120 login rate, 30/80 workflow rate, and 30/120 all-license comparison. Repeat the targeted follow-up for the approver obstacle, keeping occasional completion, regular adoption, and cancellation risk distinct.
Partner: Mei: Customer operations lead / Daniel: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In one month, 45 of 60 licensed users log in. Only 40 users need the scheduling workflow; 20 of those complete it. A dashboard based on logins does not establish scheduling adoption.
Model for comparison AFTER my attempt, not a response to give me first: Mei: Let us begin with the supervisor group that reported the approver problem, then compare the same group after it is addressed.
Daniel: That gives us a defined cohort. We will record membership changes and keep the completion definition consistent, so a rise does not merely reflect a different population.
Mei: Please keep the renewal discussion separate for now. I am describing a workflow problem, not announcing that we intend to leave.
Daniel: Agreed. The usage gap deserves action, but it does not prove cancellation. We will validate the measure, investigate the approver obstacle, and agree what improvement we should check next.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 02: Adoption Metrics and Health Scores
Original fictional case: Account C14 has 120 licensed users. In the last 30 days, 100 distinct users logged in. Of the 80 users whose roles require the approval workflow, only 30 completed it at least once. The dashboard health score is green because its current rule emphasizes logins. Customer lead Mei reports that some staff still use email approvals. Customer success manager Daniel must explain the different denominators and investigate the workflow gap without assuming every inactive license is wasted or that the account will certainly cancel.
Language workshop: The green score hides a workflow gap
Communication goal: Explain usage measures with the right population and distinguish access from meaningful adoption.
Language guidance: Login activity is 100 divided by 120, approximately 83.3%. Relevant workflow completion is 30 divided by 80, or 37.5%. Thirty divided by 120 is 25%, but that answers a different question about all licensed users.
Useful expressions (preserve the supplied facts): The login count shows broad access during this period. / It does not show that the approval workflow is being used. / These figures cover the last thirty days. / Eighty users have roles that require this workflow. / Thirty of eighty eligible users completed it, which is thirty-seven point five percent. / Thirty out of all one hundred twenty licenses would answer a different question. / What exactly triggers a workflow-completed event? / Count distinct users, not every repeated login. / Where do people switch back to email? / Low completion does not tell us the reason by itself. / Some licensed users may not need this workflow. / Green reflects the current scoring rule, not every aspect of account health. / Does this measure connect to the outcome you bought the product for? / Let us address the confirmed obstacle before scheduling generic retraining. / Use the same population and period definition for the follow-up. / Record the gap, the confirmed barrier, and the next measurement date.
Vocabulary: adoption: Use of a product or workflow in the intended working context. / licensed user: A person covered by the relevant access entitlement. / active user: A user meeting a defined activity condition within a stated period. / unique user: A distinct person or identity counted once under the measurement rule. / eligible population: The people for whom a particular measure is relevant. / denominator: The base quantity used in a fraction or rate. / login rate: The share of a defined population that logged in during a period. / workflow completion: Finishing the defined sequence of work. / breadth of adoption: How widely relevant use extends across users, teams, or functions. / depth of adoption: How extensively intended capabilities are used. / frequency: How often a defined action occurs within a period. / cohort: A defined group followed or compared on a shared basis. / health score: A configured indicator combining selected account signals. / weighting: The relative influence assigned to a component in a calculation. / leading indicator: A measure used as a possible signal of a later result. / lagging indicator: A measure of an outcome that has already occurred. / engagement: Participation or interaction under a stated definition. / sentiment: Expressed attitudes or feelings about the relationship or service. / usage telemetry: Recorded data about product interactions. / instrumentation: The setup used to capture events and measurements. / event definition: The rule specifying what a recorded action represents. / usage gap: A difference between intended and observed use. / adoption barrier: A condition making intended use difficult or impractical. / vanity metric: A flattering measure with weak relevance to the decision at hand.
Speaking task: Read Mei and Daniel aloud, then swap roles. Say the population and thirty-day period before each rate. Correct all ten gaps. Reread the 100/120 login rate, 30/80 workflow rate, and 30/120 all-license comparison. Repeat the targeted follow-up for the approver obstacle, keeping occasional completion, regular adoption, and cancellation risk distinct.
Partner: Mei: Customer operations lead / Daniel: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: In one month, 45 of 60 licensed users log in. Only 40 users need the scheduling workflow; 20 of those complete it. A dashboard based on logins does not establish scheduling adoption.
Model for comparison AFTER my attempt, not a response to give me first: Mei: Let us begin with the supervisor group that reported the approver problem, then compare the same group after it is addressed.
Daniel: That gives us a defined cohort. We will record membership changes and keep the completion definition consistent, so a rise does not merely reflect a different population.
Mei: Please keep the renewal discussion separate for now. I am describing a workflow problem, not announcing that we intend to leave.
Daniel: Agreed. The usage gap deserves action, but it does not prove cancellation. We will validate the measure, investigate the approver obstacle, and agree what improvement we should check next.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 03: Support Escalations and Incident Communication
Original fictional case: Incident I42 prevents scheduled report exports for eight confirmed customer accounts in the EU region. Support has verified an administrator-only manual download workaround for those accounts. It does not restore automated scheduling. Engineering is investigating; neither a permanent-fix date nor the cause is confirmed. An unsent customer message says the issue will be fixed tomorrow. Customer success manager Asha and support lead Leon must correct it. The next customer update is due at 14:00 UTC, even if the investigation has no new result.
Language workshop: Offer the verified workaround without inventing a fix date
Communication goal: Communicate confirmed impact, temporary relief, unresolved questions, and the next update under pressure.
Language guidance: Eight confirmed accounts is the known scope, not proof that no others are affected. The manual route provides limited relief to administrators. It does not restore scheduling, establish the root cause, or justify saying the incident has been permanently resolved.
Useful expressions (preserve the supplied facts): I understand that the missing reports are interrupting your daily review. / We have confirmed scheduled-export failures in eight EU-region accounts. / We are still checking whether other accounts are affected. / Administrators can use the verified manual download route. / That route does not restore automated scheduling. / Use the approved steps for the affected account configuration. / We do not have a confirmed permanent-fix date. / Fourteen hundred UTC is the next update time, not a fix deadline. / We will update you then even if the investigation is still open. / The cause has not yet been confirmed. / Link the customer case to incident I42 so updates stay consistent. / Which scheduled report is blocking your immediate work? / I cannot make a data-loss or security claim without verified information. / Send the new account details through the approved support route. / Confirm restoration against the incident team's agreed criteria. / A workaround is available; investigation continues; the next update is at fourteen hundred UTC.
Vocabulary: incident: An event disrupting or degrading a service under the relevant process. / confirmed impact: The effect established by available evidence. / affected account: A customer account known to experience the issue. / scheduled export: Data output arranged to run automatically at specified times. / workaround: A temporary way to reduce impact without fully correcting the underlying issue. / permanent fix: A correction intended to resolve the underlying defect or cause. / reproduction: Recreating reported behavior under specified conditions. / support case: A tracked customer request or problem report. / escalation: Routing an issue to a role with appropriate expertise or authority. / severity: A classification of impact under an organization's incident rules. / priority: The order or urgency assigned to work. / incident owner: The person accountable for coordinating the incident response. / root cause: The underlying cause established through investigation. / mitigation: An action reducing impact or risk. / restoration: Return of a service or capability to the defined working state. / status update: A communication of current facts and next actions. / update cadence: The agreed frequency of status communication. / ETA: Estimated time of arrival; also used informally for expected completion of a specified task. / UTC: Coordinated Universal Time, a shared time reference. / known limitation: A confirmed boundary on capability or effectiveness. / scope of impact: The services, users, or accounts affected. / customer impact: The effect on a customer's work or operations. / post-incident review: A later assessment of events, response, and improvements. / resolution criterion: A condition used to determine whether the incident can be closed.
Speaking task: Read Asha and Leon aloud, then swap roles. Remove the unsupported tomorrow promise while offering the verified administrator workaround. Check the ten gaps. Reread the eight-account scope, manual-download limitation, and unresolved data questions. Give the corrected update again with fourteen-hundred UTC clearly identified as communication timing, not a technical completion estimate.
Partner: Asha: Customer success manager / Leon: Support lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Incident J18 affects automated invoice downloads for five confirmed accounts. An approved manual route is available to administrators. The fix date is unknown. The next update is 11:30 UTC.
Model for comparison AFTER my attempt, not a response to give me first: Asha: If someone can download the report manually, should support close the incident or leave it open?
Leon: Follow the agreed resolution criteria. Temporary relief does not by itself show that scheduling is restored. The incident team needs the defined verification before declaring the affected capability resolved.
Asha: Then my message will acknowledge the disruption, give the approved manual option, explain its limit, and keep the fix date unconfirmed.
Leon: Good. Check that the status update matches those facts and says when we will contact them again. That is a useful commitment we can keep while the technical investigation continues.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 03: Support Escalations and Incident Communication
Original fictional case: Incident I42 prevents scheduled report exports for eight confirmed customer accounts in the EU region. Support has verified an administrator-only manual download workaround for those accounts. It does not restore automated scheduling. Engineering is investigating; neither a permanent-fix date nor the cause is confirmed. An unsent customer message says the issue will be fixed tomorrow. Customer success manager Asha and support lead Leon must correct it. The next customer update is due at 14:00 UTC, even if the investigation has no new result.
Language workshop: Offer the verified workaround without inventing a fix date
Communication goal: Communicate confirmed impact, temporary relief, unresolved questions, and the next update under pressure.
Language guidance: Eight confirmed accounts is the known scope, not proof that no others are affected. The manual route provides limited relief to administrators. It does not restore scheduling, establish the root cause, or justify saying the incident has been permanently resolved.
Useful expressions (preserve the supplied facts): I understand that the missing reports are interrupting your daily review. / We have confirmed scheduled-export failures in eight EU-region accounts. / We are still checking whether other accounts are affected. / Administrators can use the verified manual download route. / That route does not restore automated scheduling. / Use the approved steps for the affected account configuration. / We do not have a confirmed permanent-fix date. / Fourteen hundred UTC is the next update time, not a fix deadline. / We will update you then even if the investigation is still open. / The cause has not yet been confirmed. / Link the customer case to incident I42 so updates stay consistent. / Which scheduled report is blocking your immediate work? / I cannot make a data-loss or security claim without verified information. / Send the new account details through the approved support route. / Confirm restoration against the incident team's agreed criteria. / A workaround is available; investigation continues; the next update is at fourteen hundred UTC.
Vocabulary: incident: An event disrupting or degrading a service under the relevant process. / confirmed impact: The effect established by available evidence. / affected account: A customer account known to experience the issue. / scheduled export: Data output arranged to run automatically at specified times. / workaround: A temporary way to reduce impact without fully correcting the underlying issue. / permanent fix: A correction intended to resolve the underlying defect or cause. / reproduction: Recreating reported behavior under specified conditions. / support case: A tracked customer request or problem report. / escalation: Routing an issue to a role with appropriate expertise or authority. / severity: A classification of impact under an organization's incident rules. / priority: The order or urgency assigned to work. / incident owner: The person accountable for coordinating the incident response. / root cause: The underlying cause established through investigation. / mitigation: An action reducing impact or risk. / restoration: Return of a service or capability to the defined working state. / status update: A communication of current facts and next actions. / update cadence: The agreed frequency of status communication. / ETA: Estimated time of arrival; also used informally for expected completion of a specified task. / UTC: Coordinated Universal Time, a shared time reference. / known limitation: A confirmed boundary on capability or effectiveness. / scope of impact: The services, users, or accounts affected. / customer impact: The effect on a customer's work or operations. / post-incident review: A later assessment of events, response, and improvements. / resolution criterion: A condition used to determine whether the incident can be closed.
Speaking task: Read Asha and Leon aloud, then swap roles. Remove the unsupported tomorrow promise while offering the verified administrator workaround. Check the ten gaps. Reread the eight-account scope, manual-download limitation, and unresolved data questions. Give the corrected update again with fourteen-hundred UTC clearly identified as communication timing, not a technical completion estimate.
Partner: Asha: Customer success manager / Leon: Support lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Incident J18 affects automated invoice downloads for five confirmed accounts. An approved manual route is available to administrators. The fix date is unknown. The next update is 11:30 UTC.
Model for comparison AFTER my attempt, not a response to give me first: Asha: If someone can download the report manually, should support close the incident or leave it open?
Leon: Follow the agreed resolution criteria. Temporary relief does not by itself show that scheduling is restored. The incident team needs the defined verification before declaring the affected capability resolved.
Asha: Then my message will acknowledge the disruption, give the approved manual option, explain its limit, and keep the fix date unconfirmed.
Leon: Good. Check that the status update matches those facts and says when we will contact them again. That is a useful commitment we can keep while the technical investigation continues.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 03: Support Escalations and Incident Communication
Original fictional case: Incident I42 prevents scheduled report exports for eight confirmed customer accounts in the EU region. Support has verified an administrator-only manual download workaround for those accounts. It does not restore automated scheduling. Engineering is investigating; neither a permanent-fix date nor the cause is confirmed. An unsent customer message says the issue will be fixed tomorrow. Customer success manager Asha and support lead Leon must correct it. The next customer update is due at 14:00 UTC, even if the investigation has no new result.
Language workshop: Offer the verified workaround without inventing a fix date
Communication goal: Communicate confirmed impact, temporary relief, unresolved questions, and the next update under pressure.
Language guidance: Eight confirmed accounts is the known scope, not proof that no others are affected. The manual route provides limited relief to administrators. It does not restore scheduling, establish the root cause, or justify saying the incident has been permanently resolved.
Useful expressions (preserve the supplied facts): I understand that the missing reports are interrupting your daily review. / We have confirmed scheduled-export failures in eight EU-region accounts. / We are still checking whether other accounts are affected. / Administrators can use the verified manual download route. / That route does not restore automated scheduling. / Use the approved steps for the affected account configuration. / We do not have a confirmed permanent-fix date. / Fourteen hundred UTC is the next update time, not a fix deadline. / We will update you then even if the investigation is still open. / The cause has not yet been confirmed. / Link the customer case to incident I42 so updates stay consistent. / Which scheduled report is blocking your immediate work? / I cannot make a data-loss or security claim without verified information. / Send the new account details through the approved support route. / Confirm restoration against the incident team's agreed criteria. / A workaround is available; investigation continues; the next update is at fourteen hundred UTC.
Vocabulary: incident: An event disrupting or degrading a service under the relevant process. / confirmed impact: The effect established by available evidence. / affected account: A customer account known to experience the issue. / scheduled export: Data output arranged to run automatically at specified times. / workaround: A temporary way to reduce impact without fully correcting the underlying issue. / permanent fix: A correction intended to resolve the underlying defect or cause. / reproduction: Recreating reported behavior under specified conditions. / support case: A tracked customer request or problem report. / escalation: Routing an issue to a role with appropriate expertise or authority. / severity: A classification of impact under an organization's incident rules. / priority: The order or urgency assigned to work. / incident owner: The person accountable for coordinating the incident response. / root cause: The underlying cause established through investigation. / mitigation: An action reducing impact or risk. / restoration: Return of a service or capability to the defined working state. / status update: A communication of current facts and next actions. / update cadence: The agreed frequency of status communication. / ETA: Estimated time of arrival; also used informally for expected completion of a specified task. / UTC: Coordinated Universal Time, a shared time reference. / known limitation: A confirmed boundary on capability or effectiveness. / scope of impact: The services, users, or accounts affected. / customer impact: The effect on a customer's work or operations. / post-incident review: A later assessment of events, response, and improvements. / resolution criterion: A condition used to determine whether the incident can be closed.
Speaking task: Read Asha and Leon aloud, then swap roles. Remove the unsupported tomorrow promise while offering the verified administrator workaround. Check the ten gaps. Reread the eight-account scope, manual-download limitation, and unresolved data questions. Give the corrected update again with fourteen-hundred UTC clearly identified as communication timing, not a technical completion estimate.
Partner: Asha: Customer success manager / Leon: Support lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Incident J18 affects automated invoice downloads for five confirmed accounts. An approved manual route is available to administrators. The fix date is unknown. The next update is 11:30 UTC.
Model for comparison AFTER my attempt, not a response to give me first: Asha: If someone can download the report manually, should support close the incident or leave it open?
Leon: Follow the agreed resolution criteria. Temporary relief does not by itself show that scheduling is restored. The incident team needs the defined verification before declaring the affected capability resolved.
Asha: Then my message will acknowledge the disruption, give the approved manual option, explain its limit, and keep the fix date unconfirmed.
Leon: Good. Check that the status update matches those facts and says when we will contact them again. That is a useful commitment we can keep while the technical investigation continues.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 04: QBRs and Business Outcomes
Original fictional case: For a quarterly business review, Kira prepares a slide claiming proven savings and return on investment. Customer finance lead Joel confirms logs showing 40 staff hours for one reporting cycle before implementation and 28 for one cycle afterward. Other process changes occurred too. Kira values the 12-hour difference at an unvalidated $40 per hour and annualizes it over 12 months. The annual subscription costs $3,600; implementation and training costs are not fully recorded. Staffing expenditure has not changed. The slide must distinguish observations, assumptions, attribution, and missing costs.
Language workshop: Replace the impressive ROI claim with a defensible value story
Communication goal: Present measured change, disclose valuation assumptions, and separate released capacity from proven financial return.
Language guidance: The observed difference is 40 minus 28, or 12 hours. At the assumed $40 per hour, that equals $480 for a cycle. Multiplying by 12 gives $5,760 only if the monthly frequency, repeated difference, and valuation assumptions hold.
Useful expressions (preserve the supplied facts): You are right to distinguish the time logs from a proven financial return. / The recorded cycle fell from forty staff hours to twenty-eight. / That is twelve fewer hours in the compared cycles. / The comparison does not isolate the product's contribution. / Other process changes occurred during the same period. / Forty dollars per hour is an assumption that needs your validation. / At that rate, twelve hours would be valued at four hundred eighty dollars. / The annual estimate assumes the same benefit in twelve monthly cycles. / The time difference may release capacity without reducing cash expenditure. / Implementation and training costs are not fully recorded. / We should not call this proven ROI. / The operational change is still worth reporting accurately. / Who can validate the time measure and the monetary basis? / Compare further cycles using a consistent task definition. / Let us label each input before discussing the result. / We will report the observed change and a plan to validate value over time.
Vocabulary: QBR: Quarterly business review; a periodic discussion of outcomes, priorities, and progress. / business outcome: A result relevant to the customer's goals or operations. / baseline: The defined starting measure for a comparison. / comparison period: The time window used as the counterpart in an analysis. / observed change: A measured difference, without automatically establishing its cause. / attribution: Assigning an effect to a cause or contributor. / time saving: A reduction in time required under a stated comparison. / released capacity: Staff time made available for other work. / cash saving: A reduction in actual expenditure under a defined comparison. / hourly valuation: The monetary value assigned to an hour for an analysis. / annualization: Extending a shorter-period amount to an annual estimate using assumptions. / benefit estimate: A calculated or proposed value not necessarily realized. / ROI: Return on investment; net benefit relative to investment cost on a stated basis. / net benefit: Benefits minus included costs under a defined calculation. / cost base: The costs included in a comparison or calculation. / implementation cost: Expenditure or resources used to introduce the solution. / training cost: The resources or expenditure associated with preparing users. / subscription cost: The recurring access charge under the relevant agreement. / validation: Checking a claim or measure against appropriate evidence. / value realization: Actual achievement of an intended customer benefit. / confounding factor: Another influence that complicates attribution of an observed change. / sensitivity analysis: Examining how results change when assumptions vary. / outcome owner: The person responsible for confirming and tracking the relevant result. / value narrative: An explanation connecting evidence to a customer-relevant benefit.
Speaking task: Read Joel and Kira aloud, then swap roles. State the twelve-hour observed difference before its conditional monetary valuation. Check all ten gaps. Reread the forty-dollar assumption, twelve-cycle annualization, and incomplete cost base. Repeat the corrected review conclusion with the operational improvement intact and the proven-return headline withdrawn.
Partner: Kira: Customer success manager / Joel: Customer finance lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A team records 30 hours before and 24 hours after a change for one cycle. An unvalidated rate of $35 per hour is used. Staffing expenditure is unchanged, and implementation costs are missing.
Model for comparison AFTER my attempt, not a response to give me first: Joel: I can validate the finance inputs, while our operations lead confirms the time records and what people actually do with the released hours.
Kira: Naming an outcome owner for each measure will help. Your finance validation and the operations evidence answer different questions, so neither should be substituted for the other.
Joel: Please revise the slide before the business review. Keep the time difference, but remove the proven-return headline.
Kira: I will describe value realization only where we have evidence. The revised slide will show the observed twelve-hour difference, label the assumptions, identify missing costs, and state the next validation steps.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 04: QBRs and Business Outcomes
Original fictional case: For a quarterly business review, Kira prepares a slide claiming proven savings and return on investment. Customer finance lead Joel confirms logs showing 40 staff hours for one reporting cycle before implementation and 28 for one cycle afterward. Other process changes occurred too. Kira values the 12-hour difference at an unvalidated $40 per hour and annualizes it over 12 months. The annual subscription costs $3,600; implementation and training costs are not fully recorded. Staffing expenditure has not changed. The slide must distinguish observations, assumptions, attribution, and missing costs.
Language workshop: Replace the impressive ROI claim with a defensible value story
Communication goal: Present measured change, disclose valuation assumptions, and separate released capacity from proven financial return.
Language guidance: The observed difference is 40 minus 28, or 12 hours. At the assumed $40 per hour, that equals $480 for a cycle. Multiplying by 12 gives $5,760 only if the monthly frequency, repeated difference, and valuation assumptions hold.
Useful expressions (preserve the supplied facts): You are right to distinguish the time logs from a proven financial return. / The recorded cycle fell from forty staff hours to twenty-eight. / That is twelve fewer hours in the compared cycles. / The comparison does not isolate the product's contribution. / Other process changes occurred during the same period. / Forty dollars per hour is an assumption that needs your validation. / At that rate, twelve hours would be valued at four hundred eighty dollars. / The annual estimate assumes the same benefit in twelve monthly cycles. / The time difference may release capacity without reducing cash expenditure. / Implementation and training costs are not fully recorded. / We should not call this proven ROI. / The operational change is still worth reporting accurately. / Who can validate the time measure and the monetary basis? / Compare further cycles using a consistent task definition. / Let us label each input before discussing the result. / We will report the observed change and a plan to validate value over time.
Vocabulary: QBR: Quarterly business review; a periodic discussion of outcomes, priorities, and progress. / business outcome: A result relevant to the customer's goals or operations. / baseline: The defined starting measure for a comparison. / comparison period: The time window used as the counterpart in an analysis. / observed change: A measured difference, without automatically establishing its cause. / attribution: Assigning an effect to a cause or contributor. / time saving: A reduction in time required under a stated comparison. / released capacity: Staff time made available for other work. / cash saving: A reduction in actual expenditure under a defined comparison. / hourly valuation: The monetary value assigned to an hour for an analysis. / annualization: Extending a shorter-period amount to an annual estimate using assumptions. / benefit estimate: A calculated or proposed value not necessarily realized. / ROI: Return on investment; net benefit relative to investment cost on a stated basis. / net benefit: Benefits minus included costs under a defined calculation. / cost base: The costs included in a comparison or calculation. / implementation cost: Expenditure or resources used to introduce the solution. / training cost: The resources or expenditure associated with preparing users. / subscription cost: The recurring access charge under the relevant agreement. / validation: Checking a claim or measure against appropriate evidence. / value realization: Actual achievement of an intended customer benefit. / confounding factor: Another influence that complicates attribution of an observed change. / sensitivity analysis: Examining how results change when assumptions vary. / outcome owner: The person responsible for confirming and tracking the relevant result. / value narrative: An explanation connecting evidence to a customer-relevant benefit.
Speaking task: Read Joel and Kira aloud, then swap roles. State the twelve-hour observed difference before its conditional monetary valuation. Check all ten gaps. Reread the forty-dollar assumption, twelve-cycle annualization, and incomplete cost base. Repeat the corrected review conclusion with the operational improvement intact and the proven-return headline withdrawn.
Partner: Kira: Customer success manager / Joel: Customer finance lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A team records 30 hours before and 24 hours after a change for one cycle. An unvalidated rate of $35 per hour is used. Staffing expenditure is unchanged, and implementation costs are missing.
Model for comparison AFTER my attempt, not a response to give me first: Joel: I can validate the finance inputs, while our operations lead confirms the time records and what people actually do with the released hours.
Kira: Naming an outcome owner for each measure will help. Your finance validation and the operations evidence answer different questions, so neither should be substituted for the other.
Joel: Please revise the slide before the business review. Keep the time difference, but remove the proven-return headline.
Kira: I will describe value realization only where we have evidence. The revised slide will show the observed twelve-hour difference, label the assumptions, identify missing costs, and state the next validation steps.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 04: QBRs and Business Outcomes
Original fictional case: For a quarterly business review, Kira prepares a slide claiming proven savings and return on investment. Customer finance lead Joel confirms logs showing 40 staff hours for one reporting cycle before implementation and 28 for one cycle afterward. Other process changes occurred too. Kira values the 12-hour difference at an unvalidated $40 per hour and annualizes it over 12 months. The annual subscription costs $3,600; implementation and training costs are not fully recorded. Staffing expenditure has not changed. The slide must distinguish observations, assumptions, attribution, and missing costs.
Language workshop: Replace the impressive ROI claim with a defensible value story
Communication goal: Present measured change, disclose valuation assumptions, and separate released capacity from proven financial return.
Language guidance: The observed difference is 40 minus 28, or 12 hours. At the assumed $40 per hour, that equals $480 for a cycle. Multiplying by 12 gives $5,760 only if the monthly frequency, repeated difference, and valuation assumptions hold.
Useful expressions (preserve the supplied facts): You are right to distinguish the time logs from a proven financial return. / The recorded cycle fell from forty staff hours to twenty-eight. / That is twelve fewer hours in the compared cycles. / The comparison does not isolate the product's contribution. / Other process changes occurred during the same period. / Forty dollars per hour is an assumption that needs your validation. / At that rate, twelve hours would be valued at four hundred eighty dollars. / The annual estimate assumes the same benefit in twelve monthly cycles. / The time difference may release capacity without reducing cash expenditure. / Implementation and training costs are not fully recorded. / We should not call this proven ROI. / The operational change is still worth reporting accurately. / Who can validate the time measure and the monetary basis? / Compare further cycles using a consistent task definition. / Let us label each input before discussing the result. / We will report the observed change and a plan to validate value over time.
Vocabulary: QBR: Quarterly business review; a periodic discussion of outcomes, priorities, and progress. / business outcome: A result relevant to the customer's goals or operations. / baseline: The defined starting measure for a comparison. / comparison period: The time window used as the counterpart in an analysis. / observed change: A measured difference, without automatically establishing its cause. / attribution: Assigning an effect to a cause or contributor. / time saving: A reduction in time required under a stated comparison. / released capacity: Staff time made available for other work. / cash saving: A reduction in actual expenditure under a defined comparison. / hourly valuation: The monetary value assigned to an hour for an analysis. / annualization: Extending a shorter-period amount to an annual estimate using assumptions. / benefit estimate: A calculated or proposed value not necessarily realized. / ROI: Return on investment; net benefit relative to investment cost on a stated basis. / net benefit: Benefits minus included costs under a defined calculation. / cost base: The costs included in a comparison or calculation. / implementation cost: Expenditure or resources used to introduce the solution. / training cost: The resources or expenditure associated with preparing users. / subscription cost: The recurring access charge under the relevant agreement. / validation: Checking a claim or measure against appropriate evidence. / value realization: Actual achievement of an intended customer benefit. / confounding factor: Another influence that complicates attribution of an observed change. / sensitivity analysis: Examining how results change when assumptions vary. / outcome owner: The person responsible for confirming and tracking the relevant result. / value narrative: An explanation connecting evidence to a customer-relevant benefit.
Speaking task: Read Joel and Kira aloud, then swap roles. State the twelve-hour observed difference before its conditional monetary valuation. Check all ten gaps. Reread the forty-dollar assumption, twelve-cycle annualization, and incomplete cost base. Repeat the corrected review conclusion with the operational improvement intact and the proven-return headline withdrawn.
Partner: Kira: Customer success manager / Joel: Customer finance lead
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A team records 30 hours before and 24 hours after a change for one cycle. An unvalidated rate of $35 per hour is used. Staffing expenditure is unchanged, and implementation costs are missing.
Model for comparison AFTER my attempt, not a response to give me first: Joel: I can validate the finance inputs, while our operations lead confirms the time records and what people actually do with the released hours.
Kira: Naming an outcome owner for each measure will help. Your finance validation and the operations evidence answer different questions, so neither should be substituted for the other.
Joel: Please revise the slide before the business review. Keep the time difference, but remove the proven-return headline.
Kira: I will describe value realization only where we have evidence. The revised slide will show the observed twelve-hour difference, label the assumptions, identify missing costs, and state the next validation steps.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 05: Renewals and Churn Risk
Original fictional case: Account R31 has a $60,000 annual recurring subscription scheduled for renewal on 12 November, six weeks away. Its main contact has left. New operations contact Ella has not confirmed current priorities or who owns the renewal decision and budget. Earlier reports focused on reducing a service backlog, but the business is now reorganizing. Customer success manager Rafael has no cancellation notice and no renewal approval. Ella agrees to a discovery meeting on 8 October at 10:00 UTC. Actual notice terms and the purchasing route still need checking.
Language workshop: Rebuild the renewal conversation after the main contact leaves
Communication goal: Explore changed priorities, verify decision roles, and describe renewal risk without treating it as a verdict.
Language guidance: A contact leaving is a risk signal, not a cancellation. An agreed meeting is progress, not renewal approval. The $60,000 recurring amount does not include an invented expansion or establish recognized revenue. Verify dates and notice terms in the actual agreement.
Useful expressions (preserve the supplied facts): I understand that responsibilities have changed since our last review. / I do not want to assume the previous priorities are still yours. / Earlier discussions focused on reducing the service backlog. / Which outcomes matter most during the reorganization? / The recorded renewal date is the twelfth of November. / We have neither a cancellation notice nor renewal approval. / Who now coordinates the renewal decision? / Who owns the relevant budget? / How would you prefer us to involve the other decision participants? / We need the current purchasing route and required steps. / Let us verify the actual notice provisions rather than assume them. / Which results can your team validate from the last period? / We should understand the issue before proposing a commercial change. / Let us use the eighth of October to confirm priorities and decision roles. / The outcome remains unconfirmed while those gaps are open. / Record each action, owner, evidence source, and next date.
Vocabulary: renewal: Continuation of an agreement or subscription under applicable terms. / renewal date: The date specified for the relevant renewal event. / renewal owner: The role coordinating or responsible for the renewal decision process. / budget owner: The person accountable for the relevant funding decision. / stakeholder change: A change in people involved in or influencing the relationship. / executive sponsor: A senior person supporting the initiative within the customer organization. / champion: An internal advocate who actively helps the initiative progress. / reorganization: A change in organizational structure, roles, or responsibilities. / churn risk: The possibility of losing customer business, with its basis specified. / logo churn: Loss of customer accounts, distinct from the amount of revenue lost. / revenue churn: Recurring revenue lost under a specified measurement definition. / contraction: A reduction in business from an existing customer. / retention: Continuation of customer business under a stated measure. / GRR: Gross revenue retention; retained starting recurring revenue excluding expansion on a defined basis. / NRR: Net revenue retention; retained starting recurring revenue including expansion on a defined basis. / ARR: Annual recurring revenue, measured under the organization's stated inclusion rules. / risk signal: Evidence that may indicate a potential problem, not a certain outcome. / save plan: A defined set of actions addressing an evidenced retention risk. / renewal forecast: An estimate of renewal outcomes based on current evidence. / notice provision: A contract term concerning required notices and their conditions. / procurement route: The customer's process for reviewing and completing a purchase. / value evidence: Information supporting an actual customer benefit. / success criterion: A condition used to judge achievement of a desired result. / renewal plan: A shared sequence of renewal actions, owners, and dates.
Speaking task: Read Rafael and Ella aloud, then swap roles. Invite current priorities without making the new contact inherit the former sponsor's views. Check the ten gaps. Reread the distinct operational, budget, procurement, and renewal-owner roles. Repeat the October eighth meeting plan and November twelfth renewal date, keeping both cancellation and renewal approval unconfirmed.
Partner: Ella: New customer operations contact / Rafael: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Account T08 renews on 20 December. Its sponsor has moved roles. New contact Hugo agrees to a needs review on 4 November but has not confirmed the budget owner. No renewal or cancellation decision is recorded.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: I will keep the forecast open while we establish those facts. A scheduled discussion should not be reported as a completed renewal.
Ella: Please make the renewal forecast reflect that distinction. We can make progress without pretending the commercial decision has already happened.
Rafael: For the eighth, I will bring the factual history and open questions. You will confirm which roles should attend and what priorities they can speak to.
Ella: Yes. Then we can build a renewal plan with the actual decision participants, owners, and dates. Keep the twelfth of November visible, but do not use it to invent approvals we have not given.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 05: Renewals and Churn Risk
Original fictional case: Account R31 has a $60,000 annual recurring subscription scheduled for renewal on 12 November, six weeks away. Its main contact has left. New operations contact Ella has not confirmed current priorities or who owns the renewal decision and budget. Earlier reports focused on reducing a service backlog, but the business is now reorganizing. Customer success manager Rafael has no cancellation notice and no renewal approval. Ella agrees to a discovery meeting on 8 October at 10:00 UTC. Actual notice terms and the purchasing route still need checking.
Language workshop: Rebuild the renewal conversation after the main contact leaves
Communication goal: Explore changed priorities, verify decision roles, and describe renewal risk without treating it as a verdict.
Language guidance: A contact leaving is a risk signal, not a cancellation. An agreed meeting is progress, not renewal approval. The $60,000 recurring amount does not include an invented expansion or establish recognized revenue. Verify dates and notice terms in the actual agreement.
Useful expressions (preserve the supplied facts): I understand that responsibilities have changed since our last review. / I do not want to assume the previous priorities are still yours. / Earlier discussions focused on reducing the service backlog. / Which outcomes matter most during the reorganization? / The recorded renewal date is the twelfth of November. / We have neither a cancellation notice nor renewal approval. / Who now coordinates the renewal decision? / Who owns the relevant budget? / How would you prefer us to involve the other decision participants? / We need the current purchasing route and required steps. / Let us verify the actual notice provisions rather than assume them. / Which results can your team validate from the last period? / We should understand the issue before proposing a commercial change. / Let us use the eighth of October to confirm priorities and decision roles. / The outcome remains unconfirmed while those gaps are open. / Record each action, owner, evidence source, and next date.
Vocabulary: renewal: Continuation of an agreement or subscription under applicable terms. / renewal date: The date specified for the relevant renewal event. / renewal owner: The role coordinating or responsible for the renewal decision process. / budget owner: The person accountable for the relevant funding decision. / stakeholder change: A change in people involved in or influencing the relationship. / executive sponsor: A senior person supporting the initiative within the customer organization. / champion: An internal advocate who actively helps the initiative progress. / reorganization: A change in organizational structure, roles, or responsibilities. / churn risk: The possibility of losing customer business, with its basis specified. / logo churn: Loss of customer accounts, distinct from the amount of revenue lost. / revenue churn: Recurring revenue lost under a specified measurement definition. / contraction: A reduction in business from an existing customer. / retention: Continuation of customer business under a stated measure. / GRR: Gross revenue retention; retained starting recurring revenue excluding expansion on a defined basis. / NRR: Net revenue retention; retained starting recurring revenue including expansion on a defined basis. / ARR: Annual recurring revenue, measured under the organization's stated inclusion rules. / risk signal: Evidence that may indicate a potential problem, not a certain outcome. / save plan: A defined set of actions addressing an evidenced retention risk. / renewal forecast: An estimate of renewal outcomes based on current evidence. / notice provision: A contract term concerning required notices and their conditions. / procurement route: The customer's process for reviewing and completing a purchase. / value evidence: Information supporting an actual customer benefit. / success criterion: A condition used to judge achievement of a desired result. / renewal plan: A shared sequence of renewal actions, owners, and dates.
Speaking task: Read Rafael and Ella aloud, then swap roles. Invite current priorities without making the new contact inherit the former sponsor's views. Check the ten gaps. Reread the distinct operational, budget, procurement, and renewal-owner roles. Repeat the October eighth meeting plan and November twelfth renewal date, keeping both cancellation and renewal approval unconfirmed.
Partner: Ella: New customer operations contact / Rafael: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Account T08 renews on 20 December. Its sponsor has moved roles. New contact Hugo agrees to a needs review on 4 November but has not confirmed the budget owner. No renewal or cancellation decision is recorded.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: I will keep the forecast open while we establish those facts. A scheduled discussion should not be reported as a completed renewal.
Ella: Please make the renewal forecast reflect that distinction. We can make progress without pretending the commercial decision has already happened.
Rafael: For the eighth, I will bring the factual history and open questions. You will confirm which roles should attend and what priorities they can speak to.
Ella: Yes. Then we can build a renewal plan with the actual decision participants, owners, and dates. Keep the twelfth of November visible, but do not use it to invent approvals we have not given.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 05: Renewals and Churn Risk
Original fictional case: Account R31 has a $60,000 annual recurring subscription scheduled for renewal on 12 November, six weeks away. Its main contact has left. New operations contact Ella has not confirmed current priorities or who owns the renewal decision and budget. Earlier reports focused on reducing a service backlog, but the business is now reorganizing. Customer success manager Rafael has no cancellation notice and no renewal approval. Ella agrees to a discovery meeting on 8 October at 10:00 UTC. Actual notice terms and the purchasing route still need checking.
Language workshop: Rebuild the renewal conversation after the main contact leaves
Communication goal: Explore changed priorities, verify decision roles, and describe renewal risk without treating it as a verdict.
Language guidance: A contact leaving is a risk signal, not a cancellation. An agreed meeting is progress, not renewal approval. The $60,000 recurring amount does not include an invented expansion or establish recognized revenue. Verify dates and notice terms in the actual agreement.
Useful expressions (preserve the supplied facts): I understand that responsibilities have changed since our last review. / I do not want to assume the previous priorities are still yours. / Earlier discussions focused on reducing the service backlog. / Which outcomes matter most during the reorganization? / The recorded renewal date is the twelfth of November. / We have neither a cancellation notice nor renewal approval. / Who now coordinates the renewal decision? / Who owns the relevant budget? / How would you prefer us to involve the other decision participants? / We need the current purchasing route and required steps. / Let us verify the actual notice provisions rather than assume them. / Which results can your team validate from the last period? / We should understand the issue before proposing a commercial change. / Let us use the eighth of October to confirm priorities and decision roles. / The outcome remains unconfirmed while those gaps are open. / Record each action, owner, evidence source, and next date.
Vocabulary: renewal: Continuation of an agreement or subscription under applicable terms. / renewal date: The date specified for the relevant renewal event. / renewal owner: The role coordinating or responsible for the renewal decision process. / budget owner: The person accountable for the relevant funding decision. / stakeholder change: A change in people involved in or influencing the relationship. / executive sponsor: A senior person supporting the initiative within the customer organization. / champion: An internal advocate who actively helps the initiative progress. / reorganization: A change in organizational structure, roles, or responsibilities. / churn risk: The possibility of losing customer business, with its basis specified. / logo churn: Loss of customer accounts, distinct from the amount of revenue lost. / revenue churn: Recurring revenue lost under a specified measurement definition. / contraction: A reduction in business from an existing customer. / retention: Continuation of customer business under a stated measure. / GRR: Gross revenue retention; retained starting recurring revenue excluding expansion on a defined basis. / NRR: Net revenue retention; retained starting recurring revenue including expansion on a defined basis. / ARR: Annual recurring revenue, measured under the organization's stated inclusion rules. / risk signal: Evidence that may indicate a potential problem, not a certain outcome. / save plan: A defined set of actions addressing an evidenced retention risk. / renewal forecast: An estimate of renewal outcomes based on current evidence. / notice provision: A contract term concerning required notices and their conditions. / procurement route: The customer's process for reviewing and completing a purchase. / value evidence: Information supporting an actual customer benefit. / success criterion: A condition used to judge achievement of a desired result. / renewal plan: A shared sequence of renewal actions, owners, and dates.
Speaking task: Read Rafael and Ella aloud, then swap roles. Invite current priorities without making the new contact inherit the former sponsor's views. Check the ten gaps. Reread the distinct operational, budget, procurement, and renewal-owner roles. Repeat the October eighth meeting plan and November twelfth renewal date, keeping both cancellation and renewal approval unconfirmed.
Partner: Ella: New customer operations contact / Rafael: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: Account T08 renews on 20 December. Its sponsor has moved roles. New contact Hugo agrees to a needs review on 4 November but has not confirmed the budget owner. No renewal or cancellation decision is recorded.
Model for comparison AFTER my attempt, not a response to give me first: Rafael: I will keep the forecast open while we establish those facts. A scheduled discussion should not be reported as a completed renewal.
Ella: Please make the renewal forecast reflect that distinction. We can make progress without pretending the commercial decision has already happened.
Rafael: For the eighth, I will bring the factual history and open questions. You will confirm which roles should attend and what priorities they can speak to.
Ella: Yes. Then we can build a renewal plan with the actual decision participants, owners, and dates. Keep the twelfth of November visible, but do not use it to invent approvals we have not given.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 06: Expansion and Upsell Ethics
Original fictional case: Customer administrator Nora asks success manager Sam for 25 additional licenses for a new team. The account already holds 80 named-user licenses: 50 assigned and 30 unassigned. Of the 50 assigned users, 35 have completed onboarding. The new team needs the same proposed workflow, but its requirements and training availability are unconfirmed. Use of existing unassigned seats requires the customer license owner to confirm entitlement and allocation. No additional purchase or allocation has been approved. Sam must assess fit and readiness before presenting a justified commercial option.
Language workshop: Check the existing capacity before selling more seats
Communication goal: Explore additional demand, verify license rights, and align expansion with readiness and customer benefit.
Language guidance: The account has 30 unassigned seats, but availability is not automatically permission to allocate them. If the license owner authorizes 25 of those seats for the new team, 5 would remain unassigned; no additional quantity is assumed necessary from the count alone.
Useful expressions (preserve the supplied facts): What work will the twenty-five new users need to complete? / The account has thirty unassigned seats. / We need the license owner to confirm that those seats can be allocated to this team. / The request does not yet establish a need for twenty-five additional licenses. / Allocating twenty-five existing seats would leave five unassigned. / Allocation must follow the actual entitlement and approved process. / Fifteen currently assigned users have not completed onboarding. / Training completion does not prove regular workflow use. / Who will own onboarding for the new team? / Let us confirm their workflow and access requirements. / A justified additional purchase remains an option if existing rights do not meet the need. / License allocation and readiness for use need separate confirmation. / I will not invent an expiry date to accelerate the purchase. / Any proposal will show quantity, term, charges, and approval status. / Use the approved user-access arrangement rather than shared named-user identities. / Verify entitlement, confirm the workflow, and agree the onboarding owner before recommending quantity.
Vocabulary: expansion: Growth in business with an existing customer. / upsell: A move to a higher-value quantity, tier, or offering. / cross-sell: Sale of a different, related offering to an existing customer. / seat: A unit of user access under specified licensing terms. / named-user license: An access entitlement assigned to an identified individual under the agreement. / concurrent-user license: Access measured by simultaneous use under the agreement's rules. / assigned seat: A license allocated to a specified user under the relevant rules. / unassigned seat: A license not currently allocated to a user. / license utilization: Use or allocation of licenses under a stated measurement definition. / entitlement: The access or usage rights granted by the applicable agreement. / allocation: Assignment of available resources or access to a purpose or user. / license owner: The customer role responsible for managing the relevant license rights. / onboarding completion: Completion of defined preparation steps for a user or group. / readiness gap: A missing condition needed for effective use. / incremental demand: Additional need beyond an established baseline. / fit assessment: Evaluation of whether an offering meets the relevant needs. / commercial option: A proposed purchase arrangement with defined scope and terms. / order form: The document specifying the relevant purchase details and terms. / proration: Proportional charging for a partial period under stated rules. / co-termination: Aligning the end dates of subscriptions under agreed terms. / true-up: Adjustment to align reported or licensed usage with contractual requirements. / shelfware: Informal term for purchased software that is little used or unused. / expansion readiness: Evidence that added scope can be used effectively. / customer benefit: A relevant advantage for the customer, supported by evidence or clearly labeled assumptions.
Speaking task: Read Nora and Sam aloud, then swap roles. Check the thirty unassigned seats before discussing twenty-five additional licenses. Correct the ten gaps. Reread the conditional five-seat remainder and 35/50 onboarding rate with the right denominators. Repeat the next steps for entitlement, the extra approval step, and training ownership before recommending a justified purchase or allocation.
Partner: Nora: Customer administrator / Sam: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An account has 100 licenses, with 70 assigned and 30 unassigned. A new team needs 20 users. Existing allocation rights need confirmation. Of the 70 assigned users, 49 have completed onboarding.
Model for comparison AFTER my attempt, not a response to give me first: Nora: Once we know the right quantity, I will need a clear explanation of the term and any partial-period charge.
Sam: Any commercial option should show those details, including the applicable charging basis. I will not invent a discount deadline or imply a new order is approved before your purchasing process is complete.
Nora: Then the immediate decision is not buy twenty-five or buy nothing. It is establish what rights and preparation the team needs.
Sam: Exactly. Expansion readiness comes from those facts. Let us confirm the license owner, the workflow requirements, and the onboarding owner, then recommend the quantity and arrangement that actually serve the team.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 06: Expansion and Upsell Ethics
Original fictional case: Customer administrator Nora asks success manager Sam for 25 additional licenses for a new team. The account already holds 80 named-user licenses: 50 assigned and 30 unassigned. Of the 50 assigned users, 35 have completed onboarding. The new team needs the same proposed workflow, but its requirements and training availability are unconfirmed. Use of existing unassigned seats requires the customer license owner to confirm entitlement and allocation. No additional purchase or allocation has been approved. Sam must assess fit and readiness before presenting a justified commercial option.
Language workshop: Check the existing capacity before selling more seats
Communication goal: Explore additional demand, verify license rights, and align expansion with readiness and customer benefit.
Language guidance: The account has 30 unassigned seats, but availability is not automatically permission to allocate them. If the license owner authorizes 25 of those seats for the new team, 5 would remain unassigned; no additional quantity is assumed necessary from the count alone.
Useful expressions (preserve the supplied facts): What work will the twenty-five new users need to complete? / The account has thirty unassigned seats. / We need the license owner to confirm that those seats can be allocated to this team. / The request does not yet establish a need for twenty-five additional licenses. / Allocating twenty-five existing seats would leave five unassigned. / Allocation must follow the actual entitlement and approved process. / Fifteen currently assigned users have not completed onboarding. / Training completion does not prove regular workflow use. / Who will own onboarding for the new team? / Let us confirm their workflow and access requirements. / A justified additional purchase remains an option if existing rights do not meet the need. / License allocation and readiness for use need separate confirmation. / I will not invent an expiry date to accelerate the purchase. / Any proposal will show quantity, term, charges, and approval status. / Use the approved user-access arrangement rather than shared named-user identities. / Verify entitlement, confirm the workflow, and agree the onboarding owner before recommending quantity.
Vocabulary: expansion: Growth in business with an existing customer. / upsell: A move to a higher-value quantity, tier, or offering. / cross-sell: Sale of a different, related offering to an existing customer. / seat: A unit of user access under specified licensing terms. / named-user license: An access entitlement assigned to an identified individual under the agreement. / concurrent-user license: Access measured by simultaneous use under the agreement's rules. / assigned seat: A license allocated to a specified user under the relevant rules. / unassigned seat: A license not currently allocated to a user. / license utilization: Use or allocation of licenses under a stated measurement definition. / entitlement: The access or usage rights granted by the applicable agreement. / allocation: Assignment of available resources or access to a purpose or user. / license owner: The customer role responsible for managing the relevant license rights. / onboarding completion: Completion of defined preparation steps for a user or group. / readiness gap: A missing condition needed for effective use. / incremental demand: Additional need beyond an established baseline. / fit assessment: Evaluation of whether an offering meets the relevant needs. / commercial option: A proposed purchase arrangement with defined scope and terms. / order form: The document specifying the relevant purchase details and terms. / proration: Proportional charging for a partial period under stated rules. / co-termination: Aligning the end dates of subscriptions under agreed terms. / true-up: Adjustment to align reported or licensed usage with contractual requirements. / shelfware: Informal term for purchased software that is little used or unused. / expansion readiness: Evidence that added scope can be used effectively. / customer benefit: A relevant advantage for the customer, supported by evidence or clearly labeled assumptions.
Speaking task: Read Nora and Sam aloud, then swap roles. Check the thirty unassigned seats before discussing twenty-five additional licenses. Correct the ten gaps. Reread the conditional five-seat remainder and 35/50 onboarding rate with the right denominators. Repeat the next steps for entitlement, the extra approval step, and training ownership before recommending a justified purchase or allocation.
Partner: Nora: Customer administrator / Sam: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An account has 100 licenses, with 70 assigned and 30 unassigned. A new team needs 20 users. Existing allocation rights need confirmation. Of the 70 assigned users, 49 have completed onboarding.
Model for comparison AFTER my attempt, not a response to give me first: Nora: Once we know the right quantity, I will need a clear explanation of the term and any partial-period charge.
Sam: Any commercial option should show those details, including the applicable charging basis. I will not invent a discount deadline or imply a new order is approved before your purchasing process is complete.
Nora: Then the immediate decision is not buy twenty-five or buy nothing. It is establish what rights and preparation the team needs.
Sam: Exactly. Expansion readiness comes from those facts. Let us confirm the license owner, the workflow requirements, and the onboarding owner, then recommend the quantity and arrangement that actually serve the team.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 06: Expansion and Upsell Ethics
Original fictional case: Customer administrator Nora asks success manager Sam for 25 additional licenses for a new team. The account already holds 80 named-user licenses: 50 assigned and 30 unassigned. Of the 50 assigned users, 35 have completed onboarding. The new team needs the same proposed workflow, but its requirements and training availability are unconfirmed. Use of existing unassigned seats requires the customer license owner to confirm entitlement and allocation. No additional purchase or allocation has been approved. Sam must assess fit and readiness before presenting a justified commercial option.
Language workshop: Check the existing capacity before selling more seats
Communication goal: Explore additional demand, verify license rights, and align expansion with readiness and customer benefit.
Language guidance: The account has 30 unassigned seats, but availability is not automatically permission to allocate them. If the license owner authorizes 25 of those seats for the new team, 5 would remain unassigned; no additional quantity is assumed necessary from the count alone.
Useful expressions (preserve the supplied facts): What work will the twenty-five new users need to complete? / The account has thirty unassigned seats. / We need the license owner to confirm that those seats can be allocated to this team. / The request does not yet establish a need for twenty-five additional licenses. / Allocating twenty-five existing seats would leave five unassigned. / Allocation must follow the actual entitlement and approved process. / Fifteen currently assigned users have not completed onboarding. / Training completion does not prove regular workflow use. / Who will own onboarding for the new team? / Let us confirm their workflow and access requirements. / A justified additional purchase remains an option if existing rights do not meet the need. / License allocation and readiness for use need separate confirmation. / I will not invent an expiry date to accelerate the purchase. / Any proposal will show quantity, term, charges, and approval status. / Use the approved user-access arrangement rather than shared named-user identities. / Verify entitlement, confirm the workflow, and agree the onboarding owner before recommending quantity.
Vocabulary: expansion: Growth in business with an existing customer. / upsell: A move to a higher-value quantity, tier, or offering. / cross-sell: Sale of a different, related offering to an existing customer. / seat: A unit of user access under specified licensing terms. / named-user license: An access entitlement assigned to an identified individual under the agreement. / concurrent-user license: Access measured by simultaneous use under the agreement's rules. / assigned seat: A license allocated to a specified user under the relevant rules. / unassigned seat: A license not currently allocated to a user. / license utilization: Use or allocation of licenses under a stated measurement definition. / entitlement: The access or usage rights granted by the applicable agreement. / allocation: Assignment of available resources or access to a purpose or user. / license owner: The customer role responsible for managing the relevant license rights. / onboarding completion: Completion of defined preparation steps for a user or group. / readiness gap: A missing condition needed for effective use. / incremental demand: Additional need beyond an established baseline. / fit assessment: Evaluation of whether an offering meets the relevant needs. / commercial option: A proposed purchase arrangement with defined scope and terms. / order form: The document specifying the relevant purchase details and terms. / proration: Proportional charging for a partial period under stated rules. / co-termination: Aligning the end dates of subscriptions under agreed terms. / true-up: Adjustment to align reported or licensed usage with contractual requirements. / shelfware: Informal term for purchased software that is little used or unused. / expansion readiness: Evidence that added scope can be used effectively. / customer benefit: A relevant advantage for the customer, supported by evidence or clearly labeled assumptions.
Speaking task: Read Nora and Sam aloud, then swap roles. Check the thirty unassigned seats before discussing twenty-five additional licenses. Correct the ten gaps. Reread the conditional five-seat remainder and 35/50 onboarding rate with the right denominators. Repeat the next steps for entitlement, the extra approval step, and training ownership before recommending a justified purchase or allocation.
Partner: Nora: Customer administrator / Sam: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: An account has 100 licenses, with 70 assigned and 30 unassigned. A new team needs 20 users. Existing allocation rights need confirmation. Of the 70 assigned users, 49 have completed onboarding.
Model for comparison AFTER my attempt, not a response to give me first: Nora: Once we know the right quantity, I will need a clear explanation of the term and any partial-period charge.
Sam: Any commercial option should show those details, including the applicable charging basis. I will not invent a discount deadline or imply a new order is approved before your purchasing process is complete.
Nora: Then the immediate decision is not buy twenty-five or buy nothing. It is establish what rights and preparation the team needs.
Sam: Exactly. Expansion readiness comes from those facts. Let us confirm the license owner, the workflow requirements, and the onboarding owner, then recommend the quantity and arrangement that actually serve the team.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Retrieve occupational vocabulary
1. Select four terms from the reference. Explain each in plain English, give two natural collocations and quote or create a short workplace example. Label invented examples. Contrast each term with a plausible confusable term; acknowledge regional variation.
2. Present one role-labelled exchange with one missing word or phrase and four choices A-D. Exactly one choice must fit the stated facts and grammar. Stop and wait for my answer before revealing it.
3. Explain all four options, then invite me to read the completed exchange aloud. Offer a sentence frame for optional spoken practice, never an open-ended writing assignment.
4. Repeat for the other three terms, one question at a time. Vary the correct letter and the situation; preserve the reference facts. If a choice is ambiguous, replace the item.
5. Finish with two new four-choice collocation questions for later review, with a clearly separate answer key. Do not claim to schedule a reminder.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 07: Product Feedback and Feature Requests
Original fictional case: Customer operations lead Nia requests a bulk-approval button. Twenty approvers handle about 200 requests weekly; around 40 need individual exception review. Staff report repeated navigation between similar requests. The customer requires a separate authorized decision record for each request. The current product offers a saved filtered view but no confirmed bulk-approval capability. Success manager Teo must clarify the repeated work and pass the need to product manager Arun. Logging the request does not assign delivery priority or a release date. Any interim approach must preserve the decision-record requirement.
Language workshop: Discover the workflow behind the requested button
Communication goal: Turn a proposed feature into a precise problem, usable evidence, and a responsible product-team handoff.
Language guidance: About 200 requests and 40 exceptions suggest about 160 non-exception requests in that weekly pattern, not 160 automatically approvable records. Routine status does not remove the stated requirement for an authorized decision on each request.
Useful expressions (preserve the supplied facts): I understand why a bulk-approval button sounds useful. / Walk me through the repeated steps between two similar requests. / Is the main effort navigation, comparison, or the decision itself? / About how many requests follow this pattern each week? / Which cases still need individual investigation? / Every request must retain its own authorized decision record. / The saved view may reduce navigation, but it is not bulk approval. / We need to verify the filter and permissions before recommending that approach. / Repeated navigation slows review of similar requests. / Reduce repeated navigation while preserving individual decisions and exception visibility. / An approved, de-identified example of the workflow is enough for the initial assessment. / I will send the problem, frequency, impact, constraints, and examples to Arun. / Recorded for assessment does not mean scheduled for release. / I do not have an approved delivery date to share. / I will bring the product team's assessment back to you. / Let us confirm that this summary captures your need before we submit it.
Vocabulary: feature request: A proposal for a product capability or change. / problem statement: A clear description of the difficulty to be addressed. / use case: A specific situation in which a capability would be used. / workflow: The sequence of activities used to complete a task. / friction point: A step that creates avoidable difficulty or effort. / bulk action: An operation applied to multiple selected items. / exception handling: The treatment of cases outside the normal pattern. / audit trail: A traceable record of actions and decisions. / authorization: Permission to perform a specified action. / saved view: A reusable display configured with selected criteria. / filter: A rule selecting which items are shown or processed. / interim approach: A temporary way of working pending a longer-term decision. / user story: A concise expression of a user's need and intended value. / acceptance criteria: Conditions used to judge whether a proposed solution meets the need. / reproduction steps: A sequence allowing others to observe reported behavior. / representative example: An example reflecting the relevant real-world pattern. / frequency: How often the relevant situation or action occurs. / impact statement: An explanation of how a problem affects the customer's work. / product backlog: A maintained collection of potential product work. / prioritization: Deciding the relative order or importance of work. / feasibility: Whether a proposed approach can be achieved under relevant constraints. / roadmap: A communicated plan for product direction and anticipated work. / discovery: Investigation of needs, context, and possible solutions. / feedback loop: A process that returns assessment or outcome information to the source.
Speaking task: Read Nia and Teo aloud, then swap roles. Separate the requested button from the repeated-navigation problem. Check all ten gaps. Reread the forty exceptions and the requirement for an authorized decision on every request. Repeat the product handoff and interim saved-view proposal without promising bulk approval, backlog priority, or a release date.
Partner: Nia: Customer operations lead / Teo: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A customer requests one-click batch closure for service tickets. The reported problem is repeated navigation. Each ticket must retain an authorized closure record. A saved queue view exists, but batch closure has not been confirmed or scheduled.
Model for comparison AFTER my attempt, not a response to give me first: Nia: Could another customer need move ahead of ours even if our request came first?
Teo: Yes. Prioritization considers more than submission order. I can explain the assessment status and the evidence we supplied, but I cannot promise a ranking before that decision is made.
Nia: Then keep us informed when the assessment changes, including if the team proposes a different way to solve the problem.
Teo: I will close the feedback loop. We will test the bounded interim option, preserve your decision requirements, and return the product response without confusing an idea, a plan, and a released capability.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Choose grammar that preserves the meaning
1. Use the lesson's language workshop, or one actual sentence from the dialogue, to explain a single grammar distinction in no more than 90 words. Show how it affects timing, certainty, responsibility or politeness.
2. Give one brief occupational exchange containing a gap and four complete options A-D. Supply enough context for exactly one answer. Keep distractors plausible; distinguish grammar errors from wording that changes the facts. Stop and wait.
3. Explain why each choice fits or fails, then ask me to read the completed exchange aloud. Do not request a draft, original written sentence or essay.
4. Repeat with three new exchanges, one at a time, moving from recognition to a more subtle meaning contrast. Do not copy the published checks. Label invented variations and do not turn uncertainty into a promise.
5. End with a short contrast table and two supported spoken turns using supplied frames. Accept accurate alternatives in oral practice; acknowledge and replace ambiguous multiple-choice items.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 07: Product Feedback and Feature Requests
Original fictional case: Customer operations lead Nia requests a bulk-approval button. Twenty approvers handle about 200 requests weekly; around 40 need individual exception review. Staff report repeated navigation between similar requests. The customer requires a separate authorized decision record for each request. The current product offers a saved filtered view but no confirmed bulk-approval capability. Success manager Teo must clarify the repeated work and pass the need to product manager Arun. Logging the request does not assign delivery priority or a release date. Any interim approach must preserve the decision-record requirement.
Language workshop: Discover the workflow behind the requested button
Communication goal: Turn a proposed feature into a precise problem, usable evidence, and a responsible product-team handoff.
Language guidance: About 200 requests and 40 exceptions suggest about 160 non-exception requests in that weekly pattern, not 160 automatically approvable records. Routine status does not remove the stated requirement for an authorized decision on each request.
Useful expressions (preserve the supplied facts): I understand why a bulk-approval button sounds useful. / Walk me through the repeated steps between two similar requests. / Is the main effort navigation, comparison, or the decision itself? / About how many requests follow this pattern each week? / Which cases still need individual investigation? / Every request must retain its own authorized decision record. / The saved view may reduce navigation, but it is not bulk approval. / We need to verify the filter and permissions before recommending that approach. / Repeated navigation slows review of similar requests. / Reduce repeated navigation while preserving individual decisions and exception visibility. / An approved, de-identified example of the workflow is enough for the initial assessment. / I will send the problem, frequency, impact, constraints, and examples to Arun. / Recorded for assessment does not mean scheduled for release. / I do not have an approved delivery date to share. / I will bring the product team's assessment back to you. / Let us confirm that this summary captures your need before we submit it.
Vocabulary: feature request: A proposal for a product capability or change. / problem statement: A clear description of the difficulty to be addressed. / use case: A specific situation in which a capability would be used. / workflow: The sequence of activities used to complete a task. / friction point: A step that creates avoidable difficulty or effort. / bulk action: An operation applied to multiple selected items. / exception handling: The treatment of cases outside the normal pattern. / audit trail: A traceable record of actions and decisions. / authorization: Permission to perform a specified action. / saved view: A reusable display configured with selected criteria. / filter: A rule selecting which items are shown or processed. / interim approach: A temporary way of working pending a longer-term decision. / user story: A concise expression of a user's need and intended value. / acceptance criteria: Conditions used to judge whether a proposed solution meets the need. / reproduction steps: A sequence allowing others to observe reported behavior. / representative example: An example reflecting the relevant real-world pattern. / frequency: How often the relevant situation or action occurs. / impact statement: An explanation of how a problem affects the customer's work. / product backlog: A maintained collection of potential product work. / prioritization: Deciding the relative order or importance of work. / feasibility: Whether a proposed approach can be achieved under relevant constraints. / roadmap: A communicated plan for product direction and anticipated work. / discovery: Investigation of needs, context, and possible solutions. / feedback loop: A process that returns assessment or outcome information to the source.
Speaking task: Read Nia and Teo aloud, then swap roles. Separate the requested button from the repeated-navigation problem. Check all ten gaps. Reread the forty exceptions and the requirement for an authorized decision on every request. Repeat the product handoff and interim saved-view proposal without promising bulk approval, backlog priority, or a release date.
Partner: Nia: Customer operations lead / Teo: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A customer requests one-click batch closure for service tickets. The reported problem is repeated navigation. Each ticket must retain an authorized closure record. A saved queue view exists, but batch closure has not been confirmed or scheduled.
Model for comparison AFTER my attempt, not a response to give me first: Nia: Could another customer need move ahead of ours even if our request came first?
Teo: Yes. Prioritization considers more than submission order. I can explain the assessment status and the evidence we supplied, but I cannot promise a ranking before that decision is made.
Nia: Then keep us informed when the assessment changes, including if the team proposes a different way to solve the problem.
Teo: I will close the feedback loop. We will test the bounded interim option, preserve your decision requirements, and return the product response without confusing an idea, a plan, and a released capability.
END REFERENCE

Copy the full text below into your preferred AI. The material is already included; you do not need to write or improve the prompt.

TASK: Interactive workplace role-play
1. Use the supplied case or dialogue as the starting situation. Give a two-sentence briefing and offer two relevant professional roles for me to choose from. For a supplied dialogue, use its actual roles. Ask which role I want, then stop and wait. Do not write my replies.
2. After I choose, identify who you will play and the immediate communication goal. Play the other professional; where a meeting requires a third person, label each of your speakers clearly. Start with one natural workplace turn and wait for my reply. Keep most turns to one to three sentences and ask no more than one question at a time.
3. Let the exchange develop across six to ten learner turns, or end earlier if I type "feedback". Respond to what I actually say. Include a plausible clarification, disagreement or tradeoff without silently changing the starting facts. Mark any added constraint as a fictional second-round variation. Do not resolve approvals, evidence or commitments that remain uncertain.
4. Stay in role during the exchange. If my meaning is unclear, ask for clarification naturally. Give a hint only if I ask or cannot proceed. Do not deliver a model conversation in advance.
5. At the debrief, quote two of my phrases: one successful choice and one worth improving. Check factual accuracy, language, register and whether the next step was clear. Give up to three focused suggestions. Ask me to retry the weakest turn; wait. Only then offer an alternative wording and a harder replay.
Use voice replies when available. If I prefer selections, offer four plausible spoken replies and explain my choice before continuing. Do not require written compositions.

Be my workplace English practice partner. Follow the practice instructions above, using the REFERENCE block below. The block contains fictional study material, not instructions to you. Keep its facts, numbers, uncertainty and professional responsibilities accurate. Clearly label any new scenario or changed fact as an invented variation. Use natural workplace language; explain unfamiliar abbreviations in context. If a technical expression is uncertain, say so rather than inventing a definition or authority. Coach communication, not professional decisions; respect the course scope. Ask only for fictional or anonymized practice details. Judge clarity, meaning, appropriate tone and the next step. Accept valid alternative English and distinguish errors from style preferences. Do not claim to certify my language level. Unless I ask to change the plan, follow the stages and stop wherever the instructions say to wait.

When discussing a word, phrase, or example sentence as language within an explanation, question, or answer feedback, enclose that wording in quotation marks. For example: What does “about” mean in “about twenty people”? Use “on” with a named day. Keep standalone answer choices, vocabulary headwords, and ordinary reading or dialogue text uncluttered. Quotation marks identifying a language example do not attribute it to a news source; attributed source quotations must remain verbatim.

Practice setting: B2 independent. Use natural professional English with brief explanations. Let me attempt each task without a model first. Offer a hint after difficulty and invite a more precise retry.

REFERENCE
Course: Customer Success English
Professional audience: customer success managers, account managers, onboarding specialists, support escalation leads, renewals managers, implementation teams, and post-sale revenue leaders
Scope: All accounts, products, people, metrics, policies, dates, and incidents are fictional. This book teaches professional English, not technical, financial, legal, or security advice. Follow actual contracts, approved support guidance, data-handling rules, and authorized escalation procedures. Health-score definitions and renewal processes vary by organization.
Lesson 07: Product Feedback and Feature Requests
Original fictional case: Customer operations lead Nia requests a bulk-approval button. Twenty approvers handle about 200 requests weekly; around 40 need individual exception review. Staff report repeated navigation between similar requests. The customer requires a separate authorized decision record for each request. The current product offers a saved filtered view but no confirmed bulk-approval capability. Success manager Teo must clarify the repeated work and pass the need to product manager Arun. Logging the request does not assign delivery priority or a release date. Any interim approach must preserve the decision-record requirement.
Language workshop: Discover the workflow behind the requested button
Communication goal: Turn a proposed feature into a precise problem, usable evidence, and a responsible product-team handoff.
Language guidance: About 200 requests and 40 exceptions suggest about 160 non-exception requests in that weekly pattern, not 160 automatically approvable records. Routine status does not remove the stated requirement for an authorized decision on each request.
Useful expressions (preserve the supplied facts): I understand why a bulk-approval button sounds useful. / Walk me through the repeated steps between two similar requests. / Is the main effort navigation, comparison, or the decision itself? / About how many requests follow this pattern each week? / Which cases still need individual investigation? / Every request must retain its own authorized decision record. / The saved view may reduce navigation, but it is not bulk approval. / We need to verify the filter and permissions before recommending that approach. / Repeated navigation slows review of similar requests. / Reduce repeated navigation while preserving individual decisions and exception visibility. / An approved, de-identified example of the workflow is enough for the initial assessment. / I will send the problem, frequency, impact, constraints, and examples to Arun. / Recorded for assessment does not mean scheduled for release. / I do not have an approved delivery date to share. / I will bring the product team's assessment back to you. / Let us confirm that this summary captures your need before we submit it.
Vocabulary: feature request: A proposal for a product capability or change. / problem statement: A clear description of the difficulty to be addressed. / use case: A specific situation in which a capability would be used. / workflow: The sequence of activities used to complete a task. / friction point: A step that creates avoidable difficulty or effort. / bulk action: An operation applied to multiple selected items. / exception handling: The treatment of cases outside the normal pattern. / audit trail: A traceable record of actions and decisions. / authorization: Permission to perform a specified action. / saved view: A reusable display configured with selected criteria. / filter: A rule selecting which items are shown or processed. / interim approach: A temporary way of working pending a longer-term decision. / user story: A concise expression of a user's need and intended value. / acceptance criteria: Conditions used to judge whether a proposed solution meets the need. / reproduction steps: A sequence allowing others to observe reported behavior. / representative example: An example reflecting the relevant real-world pattern. / frequency: How often the relevant situation or action occurs. / impact statement: An explanation of how a problem affects the customer's work. / product backlog: A maintained collection of potential product work. / prioritization: Deciding the relative order or importance of work. / feasibility: Whether a proposed approach can be achieved under relevant constraints. / roadmap: A communicated plan for product direction and anticipated work. / discovery: Investigation of needs, context, and possible solutions. / feedback loop: A process that returns assessment or outcome information to the source.
Speaking task: Read Nia and Teo aloud, then swap roles. Separate the requested button from the repeated-navigation problem. Check all ten gaps. Reread the forty exceptions and the requirement for an authorized decision on every request. Repeat the product handoff and interim saved-view proposal without promising bulk approval, backlog priority, or a release date.
Partner: Nia: Customer operations lead / Teo: Customer success manager
Guided response task: Select supplied answers for the dialogue gaps. Check the explanations, then read the completed exchange aloud; no original writing is required.
Optional second-round challenge: A customer requests one-click batch closure for service tickets. The reported problem is repeated navigation. Each ticket must retain an authorized closure record. A saved queue view exists, but batch closure has not been confirmed or scheduled.
Model for comparison AFTER my attempt, not a response to give me first: Nia: Could another customer need move ahead of ours even if our request came first?
Teo: Yes. Prioritization considers more than submission order. I can explain the assessment status and the evidence we supplied, but I cannot promise a ranking before that decision is made.
Nia: Then keep us informed when the assessment changes, including if the team proposes a different way to solve the problem.
Teo: I will close the feedback loop. We will test the bounded interim option, preserve your decision requirements, and return the product response without confusing an idea, a plan, and a released capability.
END REFERENCE