2018.08.22
英文メールの書き方：新商品について担当部署に問い合わせる
こんなシチュエーション、お仕事でありませんか？
別の部署が開発している新商品について、社内で発表がありました。もしかしたら顧客に紹介する機会があるかもしれないので、担当者に詳細についていくつか質問がしたい。
英文メールで「新商品について担当部署に問い合わせる」お手本を動画でチェック！
こちらの動画では、伝えるべきメッセージとニュアンスを書き手が考えているところから、以下の内容のメールを実際に英語で書く様子までをご覧いただけます。
———————
クリスさん、
ご多用のところお邪魔してしまい恐縮ですが、先日の発表を受けて、商品Xについてチーム内で2点ほど質問させていただきたいです：
1. 商品を試してみたいお客様にトライアルパッケージなどそういったものを提供する予定はございますか？
2. リファンドの方針はどのようになりますか？
いずれに関してもこれから決められることかと思いますが、ご都合の良い時にご教示いただければ幸いです。よろしくお願いします。
———————
今後の仕事での英語メールの参考になれば幸いです。
【動画内の”CC”ボタンをクリックして英語字幕を表示！】
【過去の動画を見るにはYoutubeページへ！Subscribe！】
0:00:04.490,0:00:10.679
Hello, everyone! Welcome to E-mail Picks. I just came out of a company-wide meeting and
0:00:10.679,0:00:15.660
in this meeting, we were informed that
the business development department was
0:00:15.660,0:00:20.760
going to launch a new product later this
year. The product doesn't directly relate
0:00:20.760,0:00:25.260
to our job, but I felt we could introduce
it to some of our customers. So, the
0:00:25.260,0:00:30.269
department head was giving a
presentation and at the end, as usual,
0:00:30.269,0:00:33.020
he asked the audience if they had any
questions.
0:00:33.020,0:00:37.649
Nobody had any questions. I guess we were
busy trying to understand the
0:00:37.649,0:00:41.610
presentation content and we couldn't
come up with any questions on the spot.
0:00:41.610,0:00:46.230
So he told us to contact him later if we
have any questions.
0:00:46.230,0:00:50.820
So, in our department, we discussed what
our customers would want to know in case
0:00:50.820,0:00:55.530
we have a chance to introduce the
product and we came up with two. So today,
0:00:55.530,0:00:59.640
I'm going to write an e-mail to the
business development department head to
0:00:59.640,0:01:04.080
ask those two questions. So here goes:
Hello Chris,
0:01:04.080,0:01:07.830
I'm sorry to bother you when you must be
very busy. After listening to your
0:01:07.830,0:01:12.450
presentation, our team came up with a
couple of questions about Product X:
0:01:12.450,0:01:16.200
1. Are you considering offering a trial
package or something of that sort for
0:01:16.200,0:01:21.360
customers who would like to test it?
2. What will the refund policy be like?
0:01:21.360,0:01:24.299
We suppose one or both of these points
are yet to be decided.
0:01:24.299,0:01:29.159
Please let us know at your earliest
convenience. Kyota. OK, so in the first
0:01:29.159,0:01:33.450
paragraph, I'm giving the background
information to let Chris know why I'm
0:01:33.450,0:01:37.409
emailing him. I didn't forget to say
something nice at the beginning. I wrote:
0:01:37.409,0:01:40.340
"I'm sorry to bother you when you must be
very busy"
0:01:40.340,0:01:45.299
then comes the two questions -- nothing
complicated. And in the final paragraph,
0:01:45.299,0:01:49.290
I wanted to tell Chris that we know
there's a little more planning to do
0:01:49.290,0:01:53.820
before launching the new product and his
department may not have decided on these
0:01:53.820,0:01:59.689
points, so I wrote: "we suppose one or both
of these points are yet to be decided"
0:01:59.689,0:02:03.960
then Chris will understand that we are
not in a rush to know, but we are
0:02:03.960,0:02:08.819
certainly curious. So there you go, an
e-mail to inquire about a new product
0:02:08.819,0:02:11.910
internally.
I respect Chris for his project
0:02:11.910,0:02:17.250
management skills, so I bet this new
product will be a blast. So anyway, thanks
0:02:17.250,0:02:21.530
for watching, that's it for today.
I'll see you next week.
Hello, everyone! Welcome to E-mail Picks. I just came out of a company-wide meeting and
0:00:10.679,0:00:15.660
in this meeting, we were informed that
the business development department was
0:00:15.660,0:00:20.760
going to launch a new product later this
year. The product doesn't directly relate
0:00:20.760,0:00:25.260
to our job, but I felt we could introduce
it to some of our customers. So, the
0:00:25.260,0:00:30.269
department head was giving a
presentation and at the end, as usual,
0:00:30.269,0:00:33.020
he asked the audience if they had any
questions.
0:00:33.020,0:00:37.649
Nobody had any questions. I guess we were
busy trying to understand the
0:00:37.649,0:00:41.610
presentation content and we couldn't
come up with any questions on the spot.
0:00:41.610,0:00:46.230
So he told us to contact him later if we
have any questions.
0:00:46.230,0:00:50.820
So, in our department, we discussed what
our customers would want to know in case
0:00:50.820,0:00:55.530
we have a chance to introduce the
product and we came up with two. So today,
0:00:55.530,0:00:59.640
I'm going to write an e-mail to the
business development department head to
0:00:59.640,0:01:04.080
ask those two questions. So here goes:
Hello Chris,
0:01:04.080,0:01:07.830
I'm sorry to bother you when you must be
very busy. After listening to your
0:01:07.830,0:01:12.450
presentation, our team came up with a
couple of questions about Product X:
0:01:12.450,0:01:16.200
1. Are you considering offering a trial
package or something of that sort for
0:01:16.200,0:01:21.360
customers who would like to test it?
2. What will the refund policy be like?
0:01:21.360,0:01:24.299
We suppose one or both of these points
are yet to be decided.
0:01:24.299,0:01:29.159
Please let us know at your earliest
convenience. Kyota. OK, so in the first
0:01:29.159,0:01:33.450
paragraph, I'm giving the background
information to let Chris know why I'm
0:01:33.450,0:01:37.409
emailing him. I didn't forget to say
something nice at the beginning. I wrote:
0:01:37.409,0:01:40.340
"I'm sorry to bother you when you must be
very busy"
0:01:40.340,0:01:45.299
then comes the two questions -- nothing
complicated. And in the final paragraph,
0:01:45.299,0:01:49.290
I wanted to tell Chris that we know
there's a little more planning to do
0:01:49.290,0:01:53.820
before launching the new product and his
department may not have decided on these
0:01:53.820,0:01:59.689
points, so I wrote: "we suppose one or both
of these points are yet to be decided"
0:01:59.689,0:02:03.960
then Chris will understand that we are
not in a rush to know, but we are
0:02:03.960,0:02:08.819
certainly curious. So there you go, an
e-mail to inquire about a new product
0:02:08.819,0:02:11.910
internally.
I respect Chris for his project
0:02:11.910,0:02:17.250
management skills, so I bet this new
product will be a blast. So anyway, thanks
0:02:17.250,0:02:21.530
for watching, that's it for today.
I'll see you next week.
