# "Would you please.." vs. "Could you please..." vs. "Please do X." What sounds best?

**URL:** <https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394>\
**Category:** In My Humble Opinion\
**Created:** [January 20, 2011, 11:41pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394 "2011-01-20T23:41:11Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![Prelude\_to\_Fascination](https://avatars.discourse-cdn.com/v4/letter/p/a183cd/32.png) [@Prelude\_to\_Fascination](https://boards.straightdope.com/u/Prelude_to_Fascination)\
**Post date:** [January 21, 2011, 8:40pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/21 "2011-01-21T20:40:16Z")

</div>

I’ll go along with **WhyNot’s** answer. I send out price increases to customers, and state it simply: These are our new prices effective this date. Please use them from the effective date on…or something to that effect.

If I want a coworker to do something for me, I’ll ask, “Would you…?” and not “Could you…” for the same stated reasons.

So it depends on context, and the relationship I have with the person.

---

<div class="post-metadata">

**Author:** ![Rachellelogram](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/rachellelogram/32/8689_2.png) [@Rachellelogram](https://boards.straightdope.com/u/Rachellelogram)\
**Post date:** [January 21, 2011, 9:02pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/22 "2011-01-21T21:02:25Z")

</div>

Thanks so much for your business! We are asking that in the future, all of our clients utilize our webform for blahblahpurpose. If you wouldn’t mind, that would expedite blahblahprocess and let us help you even more efficiently/quickly/more cheaply/whatever imagined benefit.

I work in a call center and I would never use any of the three phrases you mentioned. They sound too commanding. Unless it’s a mandatory change you’re making. If it IS a mandatory change, then just say, “In the future you will need to blahblahwebform as our system is being transitioned into the new decade blahblahtechnology”

---

<div class="post-metadata">

**Author:** ![BigT](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/bigt/32/12044_2.png) [@BigT](https://boards.straightdope.com/u/BigT)\
**Post date:** [January 22, 2011, 1:53pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/23 "2011-01-22T13:53:16Z")

</div>

> [@spark240](#):
>
> I find phrasing-as-a-question obnoxious unless it’s meant to actually be a question. If there’s no room for a response of “no, we’re going to keep doing X because of Y,” and it’s really meant to be a directive, just say so directly.

I feel the same way about the word please. It makes the statement a request, and thus allows you to say no. Just be nice in the statement, and you should be fine.

I prefer something like “From now on, you will need to blah blah blah.” If you want to soften that, just explain why:"Due to abuse, we are disabling our email-based support system. From now on, if you need support, you will have to use a the web form at [website.com/contact.php](http://website.com/contact.php).

“We regret any inconvenience.”

There seems to be this illusion that you can’t be both direct and nice at the same time. That’s only true in a few emotional situations: it’s not a general rule.

---

<div class="post-metadata">

**Author:** ![6ImpossibleThingsB4Breakfast](https://avatars.discourse-cdn.com/v4/letter/6/e19adc/32.png) [@6ImpossibleThingsB4Breakfast](https://boards.straightdope.com/u/6ImpossibleThingsB4Breakfast)\
**Post date:** [January 22, 2011, 2:15pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/24 "2011-01-22T14:15:59Z")

</div>

> [@rachelellogram](#):
>
> Thanks so much for your business! We are asking that in the future, all of our clients utilize our webform for blahblahpurpose. If you wouldn’t mind, that would expedite blahblahprocess and let us help you even more efficiently/quickly/more cheaply/whatever imagined benefit.

Sorry, **rachelellogram**. As a client, if I received this, I’d stab someone in the eye with a pen.

---

<div class="post-metadata">

**Author:** ![WhyNot](https://avatars.discourse-cdn.com/v4/letter/w/c77e96/32.png) [@WhyNot](https://boards.straightdope.com/u/WhyNot)\
**Post date:** [January 22, 2011, 2:28pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/25 "2011-01-22T14:28:58Z")

</div>

> [@6ImpossibleThingsB4Breakfast](#):
>
> Sorry, **rachelellogram**. As a client, if I received this, I’d stab someone in the eye with a pen.

I think I could refrain from violence, but I would be thinking snarky thoughts along the lines of, “…and what if I \*do \*mind?!” :dubious:

---

<div class="post-metadata">

**Author:** ![cmyk](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/cmyk/32/3353_2.png) [@cmyk](https://boards.straightdope.com/u/cmyk)\
**Post date:** [January 22, 2011, 2:32pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/26 "2011-01-22T14:32:53Z")

</div>

When it come’s to clientele, I’ve found that clearly stating why and what you’re trying to do and why it’ll be mutually beneficial, that you’ll be fine so long as it sounds honest and professional.

---

<div class="post-metadata">

**Author:** ![Le\_Ministre\_de\_l\_au-dela](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/le_ministre_de_l_au-dela/32/12181_2.png) [@Le\_Ministre\_de\_l\_au-dela](https://boards.straightdope.com/u/Le_Ministre_de_l_au-dela)\
**Post date:** [January 22, 2011, 3:40pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/27 "2011-01-22T15:40:45Z")

</div>

“Please do X” is a straight-forward instruction. “Would you please do X” is more polite, but does not adequately carry the connotation of ‘this is the way to accomplish what you’re trying to do.’

I’m thinking of my mother-in-law, who is incapable of carrying out instructions without changing them. ‘Would you please not do the laundry while I’m out’ means that my hand laundry will be shrunk in the dryer when I get home. ‘Don’t do the laundry.’ _might_ just save my shirts.

‘Could you do X’ is right out.

---

<div class="post-metadata">

**Author:** ![Ruby](https://avatars.discourse-cdn.com/v4/letter/r/13edae/32.png) [@Ruby](https://boards.straightdope.com/u/Ruby)\
**Post date:** [January 22, 2011, 3:43pm UTC](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394/28 "2011-01-22T15:43:39Z")

</div>

> [@cmyk](#):
>
> When it come’s to clientele, I’ve found that clearly stating why and what you’re trying to do and why it’ll be mutually beneficial, that you’ll be fine so long as it sounds honest and professional.

and brief. I really don’t care about your business reasons for the change. If Newprocedure is my only option, then, if you don’t mind, don’t be wishy washy and lengthy. 😉 Just the facts, ma’am.

[Previous page](https://boards.straightdope.com/t/would-you-please-vs-could-you-please-vs-please-do-x-what-sounds-best/568394.md?page=1)
