Juggling Email and Chats on a Busy Singapore Workday.
Singlish for Living and Working in Singapore. Lesson 7.
Singapore offices run on both email and fast chats, often at the same time. In this review and integration lesson, you spend one busy project day juggling messages from your boss, team and an external partner. You see typical email openings and closings such as kindly see attached and noted with thanks, and you rewrite overly soft or overly blunt drafts into a tone that feels local but still professional for you. You also read realistic WhatsApp and Teams threads full of abbreviations like tmr, wfh and cfm, and practise writing short, clear updates that match local style without losing your own voice. Throughout, you recycle phrases from earlier lessons about deadlines, can and cannot and meeting follow ups. By the end, you can choose the right channel, length and level of formality, and you feel less stressed when your phone, inbox and chat all light up at once.
1. Morning: your inbox and chats light up.
Let us jump straight into your busy Singapore workday. It is 9.15am. You have just sat down with your kopi, maybe still a bit sleepy, and suddenly both your email and your work chat start to light up. Your boss Mei Ling has sent an email about a client presentation that needs to go out by tomorrow. At the same time, your project teammate messages you on WhatsApp asking for the latest deck. This kind of situation is very typical in Singapore offices. People use email and chat at the same time, and they expect quite fast replies, especially during office hours. In this block, I want you to focus on understanding the key information in a local-style email, even when it feels a bit rushed or full of short phrases. You will see one sample email from Mei Ling, and a short WhatsApp message from your colleague. Then you will listen to me reading the email, and your job is to pick out three main things: what she wants, by when, and any important attachment or next step. Do not worry yet about replying. Just practise catching the key details and noticing the tone. Later blocks will help you decide what to write in email and what to write in chat.
The scenario: 9.15am in your Singapore office.
You have just logged in. Your calendar is full, your phone is on the table, and two notifications appear almost at the same time.
Email from your boss, Mei Ling
> Subject: Client deck for tmr meeting
>
> Hi [Your Name], kindly see attached the latest draft from EcoPower.
>
> Please revert by 3pm today with your comments and updated slides, so I can review before sending to client.
>
> Thanks, appreciate the fast reply.
> Mei Ling
WhatsApp message from teammate (project group chat)
> Alex: Morning all, can send the deck by 10.30am? Need to cfm numbers before client call tmr.
Already you can see some very Singapore-style features:
Short forms like tmr for tomorrow and cfm for confirm.
Email phrases like kindly see attached, please revert and appreciate the fast reply.
A chat message that sounds informal but still polite, with can used as a quick request.
Email vs chat in this moment.
In many Singapore teams:
Email is used for things that involve clients, approvals, or a record of decisions. Here, Mei Ling is preparing something that will go to an external client, so she uses email.
Chat (WhatsApp, Teams, Slack) is used for fast coordination inside the team. Alex wants to clear numbers quickly, so he uses the project group chat.
Right now, do not worry about writing your reply. Focus on understanding.
Ask yourself:
What exactly is Mei Ling asking you to do?
What is the deadline she gives in the email?
Why do you think she wants your response by that time, not later?
What is Alex worried about in the chat?
In the listening activity, you will hear the email read aloud in a natural Singapore office style. Your task is to listen and then summarise the key information in your own words.
Practice & Feedback
Listen carefully to the email I read in the audio below. You already saw the written version on the screen, but now imagine you did not see it and only heard it quickly in a real office. After listening, write 2–4 full sentences in your own words that answer these questions:
What does Mei Ling want you to do?
By what time today?
Why is the timing important for her next step?
Do not copy the email sentence by sentence. Instead, pretend you are explaining the request to a colleague who just walked into the room and asked, "Eh, what did Mei Ling say?" Use simple, clear English. It is ok if you include one or two local phrases like "please revert" or "kindly see attached", but focus mainly on clarity. You do not need to reply to Alex yet; just talk about Mei Ling’s email.
2. Noticing local email openings and closings.
Just now, you focused on understanding the content of Mei Ling’s email. Now we zoom in on the style. In Singapore, emails are often quite short and efficient, but they also use certain fixed phrases that may sound a bit formal or old-fashioned to you, like kindly, revert and noted with thanks. The tricky part is that these phrases can sound perfectly normal locally, but a bit strange if you copy them in the wrong way or too often. In this block, you will compare a very stiff, textbook-style email with a more typical Singapore office email. I want you to notice especially the opening line, the request line, and the closing. Ask yourself, which version sounds more like what you have actually seen in your new office. After that, you will practise rewriting one opening or closing into a tone that is concise, respectful and feels comfortable for you. You do not need to become a copy of your colleagues, but you should be able to understand and reuse a few key phrases like kindly see attached and noted with thanks when they fit the situation.
Two emails to the same client.
Imagine you need to send updated slides to a client contact, Ravi from EcoPower. Look at these two draft emails.
Email A: Very stiff, textbook international style
> Subject: Updated presentation slides for your review
>
> Dear Mr Ravi,
>
> I hope this email finds you well. Please find attached the updated version of the presentation. I would be very grateful if you could kindly review the slides and share any feedback that you might have at your earliest convenience.
>
> Thank you very much for your time and consideration.
> Hi Ravi, kindly see attached the updated deck with the latest numbers.
>
> Please revert by today 5pm if any changes needed, so we can adjust before tomorrow’s call.
>
> Thanks,
> [Your Name]
What feels different?.
Email A is very polite, but also quite long and a bit distant. Phrases like I hope this email finds you well and thank you very much for your time and consideration are common in some cultures, but in Singapore they can feel slightly heavy for everyday project work.
Email B is shorter and uses local formulas:
Hi Ravi, kindly see attached – very common for sending files.
Please revert by today 5pm – revert here simply means reply or come back to me.
Thanks, [Your Name] – short, friendly closing.
Useful email chunks from this scene.
You will see these again later in the lesson:
Hi [Name], kindly see attached [file/updated deck].
Please revert by [time/day] if any changes needed.
Noted with thanks.
I’ll get back to you shortly.
Thanks, appreciate the fast reply.
For now, focus on recognising them and understanding how they shape the tone: concise, a bit formal but not flowery, and quite direct about deadlines.
Practice & Feedback
Read Email A and Email B again carefully. Imagine you are sending an email to Ravi that should feel more like Email B than Email A – clear, polite, but not too long.
Your task:
Rewrite only the subject and the first line of Email A to make them sound more like a typical Singapore office style.
Keep the meaning similar, but use shorter, more direct wording.
If you like, you can borrow phrases such as "Updated deck for tmr’s call", "Hi Ravi, kindly see attached" or "updated deck with the latest numbers".
Write your new subject line on one line, then your new opening sentence on the next line. You do not need to rewrite the whole email, just these two parts. Make sure your version still sounds professional enough for a client, but not overly stiff.
Original Email A opening:
Subject: Updated presentation slides for your review
Dear Mr Ravi,
I hope this email finds you well. Please find attached the updated version of the presentation.
3. Rewriting emails that are too blunt or too wordy.
So far, you have seen a very stiff email and a more typical Singapore neutral style. But in real life, you will also meet emails that are too blunt or, on the other side, too long-winded. Both can cause small problems. A blunt email might sound rude, especially to senior people or external partners. A very wordy email can make busy colleagues skip important details. In Singapore, people usually appreciate messages that are clear, a bit soft, but not filled with unnecessary phrases. In this block, you will look at two internal emails about the same situation: delaying a deadline. One is too direct, almost like a message to a close friend. The other is very long and apologetic. On the screen, I will show you improved versions so you can notice useful patterns such as can we extend until Friday, maybe need more time, and let me get back to you. After that, you will choose one draft in the activity and rewrite it yourself into a short, balanced email that would feel acceptable in a Singapore office. Think of this as your chance to practise that sweet spot: honest about problems, but still respectful and efficient.
Internal emails about a delay.
Imagine you are writing to Mei Ling about the client deck. You realise you cannot finish everything by 3pm.
Draft 1: Too blunt
> Subject: Cannot finish 3pm
>
> Hi Mei Ling,
>
> I cannot do by 3pm. Too many things. I will send tonight.
>
> [Your Name]
Problems:
Sounds like you are just refusing: I cannot do by 3pm. Too many things.
No sense that you understand her needs.
No alternative time that helps her plan.
Improved version of Draft 1
> Subject: Client deck timing
>
> Hi Mei Ling,
>
> Can we extend the 3pm timeline? Today is a bit tight on my side because of the report for HR. I can send you the updated deck by 5.30pm.
>
> Let me know if this timing works, or if you prefer I focus on only the key slides first.
>
> Thanks,
> [Your Name]
Notice:
Softer phrases: Can we extend…, a bit tight on my side.
You show you understand her needs and offer options.
Draft 2: Too wordy and apologetic
> Subject: Really so sorry about the slide deadline
>
> Hi Mei Ling,
>
> I am terribly sorry to inform you that I will unfortunately not be able to complete the slides by 3pm today because there are simply too many tasks on my plate at the moment and I am feeling a little overwhelmed. I sincerely hope this will not cause too much inconvenience to you.
>
> Best regards,
> [Your Name]
Improved version of Draft 2
> Subject: Request to adjust slide deadline
>
> Hi Mei Ling,
>
> I may not be able to finish all the slides by 3pm today. I’m still waiting for some numbers from Finance. Can I send you a first version by 4.30pm and final updates by tonight?
>
> Sorry for the short notice and thanks for your understanding.
>
> [Your Name]
Here the style is still polite, but more practical and shorter.
Practice & Feedback
Look again at Draft 1 and Draft 2 with their improved versions. Notice how the improved emails:
explain the reason briefly, without a long story;
suggest a new concrete time;
use softening phrases like "a bit tight on my side" or "may not be able to" instead of very strong or emotional language.
Now it is your turn.
Choose either Draft 1 or Draft 2.
Write a new email to Mei Ling about the delay.
Include: a subject line, greeting, 3–5 short sentences in the body, and a closing.
Your email should sound suitable for a Singapore office: honest about the problem, not rude, not over-dramatic. Try to use at least one phrase like "Can we extend…", "today is a bit tight", "I may not be able to…", "let me get back to you" or "thanks for your understanding". Write your full email in the box below.
You are writing to your boss Mei Ling about the client deck. Current deadline in her email: 3pm today.
You need a bit more time. You want to stay polite but practical.
4. Decoding and using fast work chats.
Email is only half the story. In many Singapore offices, a lot of real work happens in WhatsApp, Teams or Slack chats. Messages are short, full of abbreviations, and people expect replies quite quickly. If you only learned formal written English, this style can feel shocking at first. In this block, you will look at a realistic Teams thread from your project group. You will see common local abbreviations like tmr, wfh, cfm, OT, and short requests using can. We will also talk about when to keep something in chat and when to say, ok, let us move this to email, easier to track. Your goal here is not to memorise every abbreviation, but to get comfortable reading and writing short, efficient messages without sounding too cold or too heavy. After reading the chat, you will write a few short replies as if you are really inside that group conversation.
Teams chat: mid-day coordination.
It is now 11.45am. You and your teammates are in a Teams channel called EcoPower deck.
> Alex: Can send the deck by 1pm? Need to cfm numbers before client call tmr.
> Mei Ling: I’m in back-to-back mtgs, wfh today. Any urgent, just WhatsApp me.
> Jia: I updated the pricing slides already. Noted with thanks for the latest file from Finance.
> You:
> Alex: Ok can, I’ll update the group chat after lunch.
> Mei Ling: Short call later at 4pm can? Just to run through key points.
Common abbreviations in Singapore work chats.
tmr = tomorrow
wfh = work from home
mtgs = meetings
cfm = confirm
OT = overtime (common but not in this thread)
You also see some very local-style phrases from your chunk bank:
Any urgent, just WhatsApp me. – dropped words, but meaning is clear.
Noted with thanks. – confirmation plus polite thanks.
Ok can. – informal way to say yes, that is fine.
Short call later at 4pm can? – question without full grammar, but very common.
When to keep to chat, when to move to email.
In this situation, the team uses chat to:
check who is doing what;
confirm timing quickly;
arrange a short call.
Later, when you send the final deck to the client, Mei Ling prefers to keep that on email: easier to track versions and more professional for external contacts. That is why one of your useful phrases is: Let’s keep this on email, easier to track.
When you reply in chat, you can be shorter than in email, but still polite:
On the way, will send in 10 mins.
Sorry, I missed this, now then see.
Ok can, I’ll upload to the folder.
Wfh today, but can join call.
In the activity, you will step into the conversation and write a few realistic chat replies.
Practice & Feedback
Read through the EcoPower deck Teams chat again. Imagine you are really the "You" in that thread.
You need to:
Reply to Alex’s first message about sending the deck by 1pm. Maybe you can do it earlier, or maybe you need a bit more time.
Let the group know what you have already done on the slides.
Answer Mei Ling’s question about a short call at 4pm.
Write 3–5 short chat messages, each on a new line, as if you are typing in Teams or WhatsApp. You can be a bit more informal than email, but stay professional.
Try to use at least two phrases or patterns from this lesson, for example: "On the way, will send in 10 mins.", "Ok can.", "Noted with thanks.", "Short call later at 4pm can?", "Let’s keep this on email, easier to track." Adjust them to fit your voice. Keep each message under two sentences, like real chats.
Context reminder:
Alex wants the deck by 1pm to confirm numbers.
Mei Ling is WFH and in back-to-back meetings.
Some slides have already been updated by different teammates.
A short call at 4pm has been suggested.
5. Chat simulation with your Singapore boss.
Now we will move into a more realistic, flowing chat simulation. Imagine that after lunch, there is a small issue with the client deck. One of the numbers from Finance is still not confirmed, and this may affect the slides. Mei Ling messages you directly on WhatsApp to check what is happening. In Singapore, these one-to-one chats with your boss can feel a bit intense, because they are fast, informal, and very task-focused. However, the language is usually quite short. You do not need long sentences to sound respectful. Instead, you need to be clear and responsive. In this block, I want you to practise writing a mini back-and-forth conversation with Mei Ling. You will explain a small delay, reassure her that the deck is on the way, and maybe suggest a short call. Use phrases from the chunk bank like On the way, will send in 10 mins, Sorry, I missed this, now then see, and Wfh today, any urgent, just WhatsApp me, adapted to your situation. I will then respond as if I am your boss, and give you feedback on your tone and clarity. Think of it as a safe space to try this local chat style.
The situation: small delay, fast WhatsApp with your boss.
It is 2.45pm. You are putting the final touches on the EcoPower deck. One key number from Finance has arrived late, and you need a bit more time to update the slides properly.
Your boss, Mei Ling, sends you a WhatsApp message:
> Mei Ling: Hi, the client asking for the deck soon. Can send over by 3.15pm?
You know:
You probably cannot send the final perfect version by 3.15pm.
But you can send a good working version by around 3.30pm.
You want to sound honest, calm and reliable.
Useful chat-style chunks.
From the chunk bank and earlier blocks, here are some pieces you can reuse or adapt:
On the way, will send in 10 mins.
Sorry, I missed this, now then see.
I’ll get back to you shortly.
Can send the deck by 3pm today?
Short call later at 4pm can?
Wfh today, any urgent, just WhatsApp me.
Ok can, I’ll update the group chat.
In real chats, people often drop small words but keep the message clear. However, with your boss, you probably do not want to sound too casual or use heavy Singlish if you are not comfortable.
Examples of balanced replies:
"Almost done, on the way. Can send by 3.30pm if ok?"
"Still updating the Finance numbers, a bit tight for 3.15pm. I send first version by 3.30pm, then final tonight."
"If urgent, I can send partial deck first, then update the last few slides later."
In the activity, you will write a short 4–6 message conversation between you and Mei Ling.
Practice & Feedback
Imagine a real WhatsApp chat with your boss, Mei Ling, about the EcoPower deck.
Start with her message: "Hi, the client asking for the deck soon. Can send over by 3.15pm?"
Write 4–6 short messages in total: some from you, some from Mei Ling, like a real back-and-forth. You decide her exact words after the first message, based on how you reply.
Guidelines:
Keep each message to one or two sentences.
Show clearly whether you can or cannot meet 3.15pm, and suggest a realistic time.
Use at least two helpful chunks, such as "On the way, will send in 10 mins.", "I’ll get back to you shortly.", "Short call later at 4pm can?", or "Ok can". Feel free to adapt them.
Try to sound calm, responsible and reasonably friendly – not defensive, not overly apologetic.
Write the whole conversation in the box, marking each line with either Mei Ling: or You: so it is clear who is speaking.
Reminder of the key facts:
Original deadline from Mei Ling’s email: 3pm.
Client is now asking for the deck "soon".
Realistically, you can send a good version around 3.30pm.
You want to maintain trust with your boss.
6. End of day: choosing email or chat and writing both.
We have reached the end of your busy project day. You have checked Mei Ling’s email, handled the Teams chat with your colleagues, and managed a quick WhatsApp conversation about a delay. Now it is time for a small capstone task that brings email and chat together. Imagine it is 5.30pm. You have finally sent the updated EcoPower deck to Mei Ling, and she has forwarded it to the client, Ravi. A bit later, Ravi replies with some small comments and confirms that tomorrow’s call is on. Your job now is to write two things. First, a short, professional email back to Ravi that uses a neutral Singapore style – phrases like kindly see attached, noted with thanks or I’ll get back to you shortly, but not too much Singlish. Second, a very short update in your internal group chat so your teammates know the client has confirmed. This block is about making choices: what belongs in email, what belongs in chat, and how to keep your style consistent and comfortable for you. I will give you a simple checklist on the screen, and then you will write your email and chat messages. After that, I will give you detailed feedback as if I am your Singapore communication coach.
The final scene: client confirmed, now you reply.
Time:5.30pm.
You see this email from Ravi (EcoPower) in your inbox:
> Subject: Re: Updated deck for tomorrow’s call
>
> Hi [Your Name],
>
> Thanks for sending over the updated deck. Overall looks good. I made a few small comments in the slides, mainly on slide 5 and 8.
>
> Tomorrow’s call at 10am SGT is confirmed. Looking forward.
>
> Best,
> Ravi
You want to:
Reply to Ravi by email.
Update your internal EcoPower deck chat.
Email back to Ravi.
Your reply email should:
Acknowledge his message: Noted with thanks or Thanks for the quick review.
Confirm you will adjust the slides: I’ll update slide 5 and 8 accordingly.
Confirm the time of the call: See you tomorrow at 10am SGT.
Possible useful chunks:
Hi Ravi, noted with thanks for your comments.
I’ll update slide 5 and 8 and send the final deck shortly.
Kindly see attached the revised version.
Thanks, appreciate the fast reply.
Internal chat update.
In the group chat, you do not need to repeat the whole email. Just give the team the key points.
Example style:
"Ravi ok with the deck, just minor edits on slide 5 and 8."
"Call tmr 10am cfm."
"On the way, will upload final version after edits."
"Let’s keep detailed comments on email, easier to track."
Success checklist.
When you write your answers in the activity, check:
Channel choice: Email for Ravi, chat for your internal team.
Clarity: Does Ravi know what you will do next and by when? Does your team know the call is confirmed?
Tone: Email is neutral-professional; chat is short and informal but still polite.
Local fit: You use a few core local chunks, but the message still sounds like you.
Practice & Feedback
Now you will do the full mini performance for this lesson.
Write an email to Ravi.
Include a subject, greeting, 3–5 short sentences in the body, and a closing.
Acknowledge his comments, say what you will update, and confirm tomorrow’s 10am call.
Optionally attach the idea of a revised deck using phrases like "kindly see attached" or "I’ll get back to you shortly with the final version".
Write 2–3 short chat messages to your internal project chat to update the team.
Treat it like WhatsApp or Teams: 1–2 sentences per message.
Share that the client has confirmed, mention any key edits, and maybe say you’ll upload the final deck soon.
Put your email first, then a blank line, then your chat messages, each on a new line. Use what you learned about local email openings and closings, and about short, efficient chat updates.
Key facts to include:
Ravi says: overall looks good, only small comments on slide 5 and 8.
Tomorrow’s call at 10am SGT is confirmed.
You will update the slides and send a final deck.
Your team needs to know the call is confirmed and edits are minor.
