Per Our Conversation: 15+ Alternate Phrases to Use

“Per our conversation” is one of those business-email staples that shows up everywheremeeting recaps, vendor threads, HR follow-ups, you name it. It’s useful because it anchors your message to something you already discussed. The problem? It can also sound stiff, legal-ish, or (worst case) a little weaponized, like you’re building a case file instead of collaborating.

This guide gives you more natural, more strategic alternativesso you can confirm details, document decisions, and keep momentum without sounding like you’re about to cite “Exhibit A.” You’ll get 15+ phrases (with examples), plus quick tips for choosing the right tone and writing follow-ups that actually get replies.

Why “Per Our Conversation” Can Land Wrong

The phrase isn’t inherently rude, but it carries a formal vibe that can feel cold in day-to-day work. In some contexts, it can also imply: “I’m reminding you because you might forget,” or “I’m writing this down in case we argue later.” Sometimes you do want a paper trailbut you usually don’t want to sound like you’re already preparing for court.

The fix isn’t to ban the phrase. It’s to use a version that matches your goal: recap, confirm, clarify, or drive next stepswhile keeping your tone courteous and clear.

Pick the Right Alternative in 10 Seconds

Before you swap in a new phrase, ask yourself four quick questions:

• What’s the purpose? Recap? Confirm a decision? Request an action? Clarify a misunderstanding?
• What’s the relationship? Teammate, client, vendor, recruiter, leadershipeach expects different formality.
• How sensitive is the topic? Deadlines, money, compliance, or conflict may require more precise language.
• What’s the channel history? If you’re following a call, write the summary like it’s the official record (because it is).

If your message is low-stakes and internal, choose warmer, simpler wording. If it’s high-stakes (scope, payment, approvals), choose more explicit confirmation language and include the details in bullets.

15+ Alternate Phrases to Use (With Real-World Examples)

Below are alternatives grouped by tone and intent. Mix and matchyour goal is to sound human and be unmistakably clear.

Warm, Neutral, and Everyday (Great for Teams)

• As we discussed…
  Example: “As we discussed, I’ll draft the outline and share it by Thursday afternoon.”
• Following our conversation…
  Example: “Following our conversation, here’s a quick recap of the timeline and owners.”
• After we spoke…
  Example: “After we spoke, I checked with Financeour PO should be approved by Friday.”
• To recap…
  Example: “To recap, we’re shipping Phase 1 first, then adding reporting in Phase 2.”
• Quick recap from today…
  Example: “Quick recap from today: we agreed to pause feature X while we validate Y.”

Clear “Next Steps” Language (Keeps Things Moving)

• Here are the next steps we agreed on…
  Example: “Here are the next steps we agreed on: I’ll send the draft, you’ll review, we’ll finalize on Tuesday.”
• Action items from our call:
  Example: “Action items from our call: (1) I’ll share the deck, (2) you’ll confirm the attendee list, (3) we’ll lock the date.”
• As a next step…
  Example: “As a next step, could you approve the copy by EOD Wednesday so we can schedule the campaign?”
• Based on what we decided…
  Example: “Based on what we decided, we’ll use Option B and revisit pricing after the pilot.”
• Confirming responsibilities:
  Example: “Confirming responsibilities: I’ll handle the vendor outreach; you’ll handle internal approvals.”

Polite Clarification (When You Need to Correct Without Spark)

• Just to make sure we’re aligned…
  Example: “Just to make sure we’re aligned, the current deadline is March 12, not March 19.”
• To clarify…
  Example: “To clarify, the discount applies to annual plans only, not month-to-month.”
• My understanding is that…
  Example: “My understanding is that your team will provide the final data extract by Mondayplease confirm.”
• Just confirming the details…
  Example: “Just confirming the details: 30 attendees, 45 minutes, Zoom link in the invite.”
• Let me restate what we agreed to, to ensure accuracy:
  Example: “Let me restate what we agreed to, to ensure accuracy: we’ll deliver the prototype first, then iterate.”

More Formal (Useful for Clients, Vendors, and Approvals)

• As discussed on our call/meeting…
  Example: “As discussed on our call, we’ll proceed with the revised scope and updated delivery date.”
• In line with our discussion…
  Example: “In line with our discussion, the team will provide weekly status updates starting next Friday.”
• As agreed…
  Example: “As agreed, payment terms are Net 30, starting from the invoice date.”
• To document our decision…
  Example: “To document our decision, we’re selecting Vendor A and signing by February 28.”
• For the record, we agreed that…
  Example: “For the record, we agreed that any additional requests will be treated as out of scope.”

Ultra-Specific “Paper Trail” Options (High-Stakes Threads)

Use these when the stakes are real: budgets, scope changes, compliance, legal exposure, or repeated misunderstandings. Keep your tone professional the goal is clarity, not intimidation.

• To confirm in writing…
  Example: “To confirm in writing, the final approved budget is $24,000, inclusive of setup fees.”
• As confirmed on [date]…
  Example: “As confirmed on February 10, the deliverables include A, B, and C.”
• Per our discussion on [date/time], the agreed outcome is:
  Example: “Per our discussion on February 10 at 2 p.m., the agreed outcome is: launch on March 1 with feature set X.”
• Summarizing the agreement for accuracy:
  Example: “Summarizing the agreement for accuracy: you’ll provide assets; we’ll deliver the build; QA starts Monday.”
• Please reply to confirm the following is correct:
  Example: “Please reply to confirm the following is correct: scope, pricing, timeline, and owners listed below.”

How to Write the Follow-Up So It Works (Not Just “Exists”)

The best phrase in the world won’t save a messy email. If you want a response (or want to prevent confusion later), structure matters.

Use a Subject Line That Signals Purpose

• Recap: “Recap + next steps: Project Phoenix (Feb 23)”
• Confirmation needed: “Confirming scope & timeline reply requested”
• Decision: “Decision recorded: Vendor selection + kickoff date”

Start With the Main Point (Then Details)

Put the “why you’re emailing” in the first 1–2 lines. If someone is skimming on a phone between meetings, they should still catch the headline.

Make Details Skimmable

Bullets beat paragraphs when you’re summarizing decisions. A clean list also reduces “But I thought you meant…” drama.

Be Explicit About What You Need (And When)

If you need a reply, ask for it directly and politely: “If this matches your understanding, please reply ‘confirmed’ by 3 p.m. Wednesday.”

Copy-and-Paste Mini Templates (With Better Alternatives)

1) After a Meeting: Recap + Next Steps

2) After a Call: Confirming Details

3) Friendly Follow-Up When Someone’s Busy

4) Clarifying a Misunderstanding (Without Lighting a Match)

5) High-Stakes Documentation (Professional, Not Threatening)

Common Mistakes (And How to Avoid Them)

• Being vague: “Per our conversation…” (about what?) → Add the decision, date, and specifics.
• Sounding accusatory: “Per our conversation, you said…” → Try “As discussed, the plan is…” and focus on outcomes.
• Burying the lead: Don’t hide the ask in paragraph four. Put it up top.
• Over-formality for simple tasks: Save “pursuant to” energy for contracts, not calendar invites.
• No call-to-action: If you need approval, say so and give a deadline.

Conclusion

“Per our conversation” isn’t wrongit’s just not always the best tool for the job. When you swap it for a phrase that matches your intent (recap, confirm, clarify, or drive next steps), your emails get clearer, friendlier, and far more likely to produce action. Keep it simple, lead with the point, and make the details easy to scan. Your future selfand everyone stuck in the threadwill thank you.

Extra: of “In-the-Wild” Experience and Lessons

In real workplaces, “per our conversation” tends to show up in three recurring situations: (1) someone’s trying to be helpful and organized, (2) someone is trying to prevent confusion, or (3) someone is quietly frustrated and wants a written record. The tricky part is that readers can’t always tell which one you meanso they guess. And when people guess tone, they usually guess wrong (or at least dramatically).

One common pattern goes like this: a quick hallway chat turns into a half-remembered agreement. A day later, the follow-up email begins with “Per our conversation…” but doesn’t include specifics. The recipient thinks, “Wait, what conversation?” and now you’ve added confusion instead of removing it. The fix is boringbut effective: add two concrete anchors. When was the conversation (today’s standup, Monday’s call), and what is being confirmed (decision, owner, date). Even a single sentence like “Following our conversation this morning, we agreed to ship the draft by Friday” reduces misreads.

Another situation: cross-functional work where deadlines slip because nobody wants to be the “pushy” person. Eventually someone writes, “Per our conversation, you said you’d send this last week.” That may be factually true, but emotionally it’s a tiny slap. A softer option keeps the record without escalating: “Just to make sure we’re aligned, I’m tracking the asset handoff as end of week. Does that still work on your end?” You’re still documenting the timeline, but you’re inviting confirmation instead of assigning blame.

Then there’s the high-stakes version: scope changes, pricing, approvals. Here, documenting isn’t pettyit’s professional. The best “experienced” move isn’t using a fancier phrase. It’s pairing your phrase with a clean, skimmable summary. Think: “To confirm in writing…” followed by bullets for deliverables, dates, and responsibilities. People don’t argue with clarity as much as they argue with ambiguity. If a conflict ever happens, the email that saves the day won’t be the one with the most formal vocabularyit’ll be the one with the cleanest list.

Finally, here’s the quiet truth: many teams don’t actually need “per our conversation” at all. They need better habitsclear owners, explicit deadlines, and short recap notes after meetings. When those habits improve, the phrase becomes optional. Until then, your best strategy is to choose language that matches your intent, stay courteous, and write as if your future self will reread the thread at 4:57 p.m. on a Friday. Because… there’s a strong chance they will.