A practice prompt we wrote. No company or candidate report names it, so it carries no company tag.
How to answer
In an August 2026 Reddit thread about Salesforce’s (Agentforce) role, one commenter reported that the assessment they cleared included writing an email to a customer with unrealistic demands about shipping an AI system within a week; they did not say which role they had applied for. Source 1Forward Deployed Engineer (Agentforce) (comment by u/joemons)PublisherReddit r/SalesforceCareersSource typecandidate report on Reddit The reader of an email like this is busy and under pressure from someone above them. They will read the subject and the first two lines, so those lines must carry the plan. The lesson What customer rounds look like, and the core moves covers the other formats a customer round can take, from live role-plays to written replies like this one.
Before you write, find out what Monday is for. One message to your champion or a short call: what happens on Monday, and who is watching? A board review, a seasonal surge and a regulator’s visit each call for a different Monday deliverable. Build the Monday line around that event.
Then build the email top-down:
- Subject line: the plan, not the refusal.
Rollout plan: claims team live Monday, all regions by the 24thbeatsRe: Monday deadline. - Acknowledge the goal, not the demand. Name what they are trying to achieve and why it matters to them. Don’t agree to the date in the same sentence.
- State exactly what will be live on Monday. Which users, which features, and in what state. Make it real and specific.
- Give dates for the rest, with what each depends on. Features you haven’t built get either a date or a date by which you’ll have one, after a short scoping call.
- Make one request with a deadline. A decision, a name or an access grant that the plan needs from them.
- Offer to talk. One line, with a time.
- Align before you send. Copy your account lead, and warn your own manager, because a VP who hears no may escalate, and any escalation should land on people who already know the plan.
Keep the plan above the fold: subject, first line and the Monday block. Write the reasons after the offer, and only as many as they need to trust the dates.
Leading with the reasons is the first pitfall below: three paragraphs on why Monday is impossible before any offer. The reader stops at the second paragraph, forwards it upward as “they said no”, and the plan never gets read. The second is quieter: “we’ll do our best for Monday”, which is a promise you already know you’ll break.
Follow-ups
What the interviewer may ask next, once your first answer is on the table.
- What exactly can be live by Monday?
- Which sentence acknowledges their goal without agreeing to the demand?
- The customer replies angrily. What is your second email’s first line?
Where answers go wrong
- Writes a long explanation of why it is impossible before offering anything.
- Promises to “do our best for Monday”, which is a commitment the writer already knows they will break.
Answer this in two minutes
Write the answer you would say out loud. The clock starts with your first word.
Compare with the model answer
Model answer
The setting: our claims-summary assistant has been in pilot with one adjuster team at a regional insurer. Their VP of claims emails: every adjuster on it by Monday, plus automatic claim routing and Spanish-language summaries, neither of which exists. Her pilot lead told me Monday is when the storm-season backlog starts to build, and that storm claims land on the Northeast team first.
Subject: Rollout plan: Northeast team live Monday, all adjusters by the
24thKaren,
You want every adjuster working from summaries before the storm-season backlog builds, and the pilot results make that the right goal.
Live on Monday:
- All 40 adjusters on the Northeast team, where storm claims land first, up from the 12 in the pilot. Same features they have today, on your production claims system.
Next, with dates:
- The remaining 180 adjusters, in two waves: Midwest on Monday the
17th, everyone else on Monday the24th. The waves protect your claims system: we watch load for a week before adding more users.- Spanish-language summaries: the model can write Spanish today; what isn’t built is the check that Spanish summaries are accurate on your claims. I’ll have a date after a one-hour scoping call this week, including whether we can meet the
24th.- Automatic routing: not built yet, and it changes who owns each claim, so it needs your routing rules and sign-off from your claims operations lead. Send me the rules by the
17thand I’ll have a date for you by the24th.One thing I need from you: the name of an owner for the Midwest wave by Thursday, so we can book their walkthrough.
I can walk through this by phone tomorrow at 10 or 2. Which suits you?
Sam
Why each line is there. The subject line gives the whole plan, so it survives being forwarded unread. The first sentence agrees with the goal and the reason behind it, and says nothing about Monday. The Monday block is concrete: which team, how many people, which features, and it names the team where storm claims land first, so Monday answers the event she’s worried about. Each later date carries its dependency, so the dates read as a plan rather than a refusal. The unbuilt features each get a date by which she’ll have a date, because inventing one now would be the same mistake as agreeing to Monday. The Spanish line says where the work is: making the model write Spanish is easy, and checking that its Spanish summaries are accurate on her claims is the part that takes time. Routing gets one clause of reasoning, because it changes who owns a claim and she needs to know that. The one request the rollout needs sits in its own block, with a day; the routing rules are a condition on a feature she asked for, so they stay on that line. Before sending, I copied our account lead and told my manager, so if she escalates, my manager has already read the plan.
If she replies angrily, the second email’s first line restates the offer, not the reasons: “Karen, the Northeast team goes live Monday as planned. If some Midwest adjusters need it sooner, send me their names today and I’ll confirm by noon tomorrow whether they can join Monday.”