Nội dung chính
1. Tại sao prompt văn phòng quan trọng?
Khoảng 30-40% thời gian làm việc của nhân viên văn phòng đi vào:
- Viết email (2-3 giờ/ngày)
- Soạn báo cáo (4-5 giờ/tuần)
- Viết memo / follow-up (2-3 giờ/tuần)
- Tạo proposal (5-10 giờ per proposal)
Trước AI: Bạn viết từ đầu, sửa, rồi sửa lại. Mất hàng giờ chỉ để một email "sound professional".
Sau AI: Bạn dùng prompt, AI draft trong 30 giây, bạn edit lại 5 phút. Total: 5.5 phút vs. 30 phút. Tiết kiệm 24.5 phút/email, 10 email/tuần = 4 giờ/tuần tiết kiệm.
2. Mười prompt copy-paste ready
Prompt #1: Email yêu cầu từ sếp/client (Urgent request)
Viết email yêu cầu [REQUEST] từ [WHO: sếp/client/partner].
Thông tin cần có trong email:
- Lý do yêu cầu: [REASON]
- Deadline: [DEADLINE]
- Tài liệu đính kèm: [ATTACHMENTS if any]
- Follow-up: Hỏi khi nào có kết quả
Tone: Chuyên nghiệp nhưng urgent, không quá formal nhưng cũng không casual.
Ví dụ:
- Yêu cầu: "update Q2 budget projection"
- Từ: CEO
- Lý do: "Final budget review trước cuối tuần"
- Deadline: "Thu này 5 PM"
Output:
Subject: Q2 Budget Projection - Needed by Thu 5PM
Hi [Name],
I need to finalize the Q2 budget projection before our final review this Friday.
Could you please provide the updated budget numbers by 5 PM Thursday?
I've attached the Q1 template for reference.
When you send, please include:
- Revenue forecast by department
- Expense breakdown by category
- Year-over-year comparison
Thanks for the quick turnaround!
Best,
[Your name]
Mẹo: Nếu super urgent, thêm: "I know this is tight — let me know if you need any support."
Prompt #2: Email từ chối yêu cầu (Polite no)
Viết email từ chối yêu cầu [REQUEST] một cách lịch sự.
Context:
- Ai yêu cầu: [WHO]
- Yêu cầu gì: [REQUEST]
- Lý do từ chối: [REASON]
- Đề nghị alternative: [ALTERNATIVE if any]
Tone: Lịch sự, sorry nhưng firm, không mở ra discussion lại.
Ví dụ:
- Yêu cầu: "Join team X, report to them instead"
- Lý do: "I'm committed to team Y until year-end"
- Alternative: "Happy to join Jan 1st, or do cross-team projects"
Output:
Subject: Re: Team X opportunity
Hi [Name],
Thanks for thinking of me for Team X — I'm flattered by the offer.
However, I've committed to delivering Project Y through year-end,
and shifting teams now would compromise our timeline.
That said, I'm definitely interested in Team X. How about this:
I join on January 1st, and in the meantime,
I can support you on some cross-team initiatives (e.g., [project]).
Let me know if that works.
Best,
[Your name]
Mẹo: Luôn offer alternative, không để người ta cảm thấy completely rejected.
Prompt #3: Báo cáo hàng tuần (Weekly report)
Viết báo cáo hàng tuần (Weekly Report) với cấu trúc:
1. Điểm đã hoàn thành: [3-5 items]
2. Điểm đang làm: [2-3 items]
3. Blocker/Challenge: [1-2 issues cần help]
4. KPI/Metrics: [ví dụ: Sales +10%, Support ticket -15%]
5. Next week priority: [2-3 focus areas]
Info:
- Week: [WEEK]
- Department/Team: [TEAM]
- Key achievement: [HIGHLIGHT]
- Any risk: [IF ANY]
Tone: Chuyên nghiệp, data-driven, highlight achievements nhưng cũng honest về challenges.
Output:
WEEKLY REPORT — Week of April 16-20, 2026
Sales & Marketing Team
✅ COMPLETED:
- Launched Q2 campaign "Summer Sale" on all channels
- Generated 50 new leads via webinar (conversion rate 8%)
- Completed 3 customer interviews for product feedback
⏳ IN PROGRESS:
- Finalizing Q3 budget proposal (due Friday)
- Setting up new CRM automation for lead nurturing
⚠️ BLOCKERS:
- Waiting for Finance to approve vendor contract (delays campaign v2)
- Need UX team to design new landing page variant
📊 METRICS:
- New leads: +25% (vs. last week)
- Email open rate: 32% (target 30%) ✓
- Website traffic: +18%
📌 NEXT WEEK PRIORITY:
1. Launch Q2 Phase 2 campaign
2. Conduct customer feedback session
3. Prepare Q3 budget presentation
---
[Your name]
[Department] | [Company]
Mẹo: Luôn include metrics, không chỉ nói "work hard". Sếp chỉ quan tâm con số.
Prompt #4: Memo họp (Meeting notes)
Viết memo tóm tắt cuộc họp.
Thông tin:
- Cuộc họp về: [TOPIC]
- Ngày: [DATE]
- Participants: [WHO]
- Duration: [HOW LONG]
Cấu trúc memo:
1. Key decisions made: [DECISIONS]
2. Action items: [WHO sẽ làm GÌ, deadline KHI]
3. Next steps: [FOLLOW UP]
4. Questions still pending: [IF ANY]
Tone: Structured, clear, easy to scan.
Ví dụ:
- Topic: Q2 Product Roadmap Review
- Attendees: CEO, Product, Engineering, Design
- Duration: 1 hour
- Key decision: Focus on mobile app (vs. web first)
Output:
MEETING MEMO
Date: April 17, 2026 | Topic: Q2 Product Roadmap Review
Attendees: CEO, Product Lead, Engineering Manager, Design Lead
🎯 KEY DECISIONS:
1. Prioritize mobile app development (iOS first, Android Q3)
2. Delay web redesign to Q3
3. Allocate 30% team capacity to technical debt reduction
📋 ACTION ITEMS:
| Owner | Task | Deadline |
|-------|------|----------|
| Product | Update roadmap document | Apr 18 |
| Engineering | Sprint planning for mobile features | Apr 20 |
| Design | Design system for mobile first | Apr 22 |
| CEO | Communicate timeline to board | Apr 19 |
🔄 NEXT STEPS:
- Engineering to start sprint on Apr 21
- Weekly syncs every Monday 10 AM to track progress
- Monthly review with board on May 15
❓ PENDING:
- Budget allocation for contractor support (CFO to confirm)
- Third-party API selection (Engineering to evaluate)
---
[Your name] | [Date sent]
Mẹo: Memo phải short enough để scan trong 2 phút, nhưng detailed enough để ai không attend cũng hiểu.
Prompt #5: Proposal / Quote email
Viết proposal email cho [CLIENT] về [SERVICE/PRODUCT].
Client info:
- Company: [NAME]
- Contact: [PERSON]
- Budget range: [BUDGET if known]
- Timeline: [TIMELINE]
- Needs: [WHAT THEY NEED]
Proposal structure:
1. Problem statement: Vấn đề họ đang gặp
2. Proposed solution: Cách bạn giải quyết
3. Timeline: Khi nào hoàn thành
4. Investment: Chi phí (có thể hide trong attachment)
5. Next step: Hỏi khi nào discuss further
Tone: Consultative, solution-focused, not salesy.
Output:
Subject: Proposal — AI Content Tool for [Company] Marketing Team
Hi [Name],
Thanks for the call last week. Based on our conversation,
I understand that your marketing team spends 20+ hours/week on content creation.
Here's how we can help.
## THE CHALLENGE
Your team manually writes product descriptions, social media captions, and email campaigns.
This is time-consuming and blocks faster content velocity.
## OUR SOLUTION
We implement an AI-powered content platform that:
- Generates product descriptions in 5 minutes (vs. 30 min manual)
- Drafts social media posts in bulk (100 posts/hour)
- Creates email campaign copy automatically
- Result: Your team focuses on strategy, not execution
## TIMELINE
- Week 1: Setup & training
- Week 2-4: Ramp-up & optimization
- Ready to scale: Month 2
## INVESTMENT
I've attached a detailed proposal with pricing based on your team size.
Rough range: $5K-15K/month depending on volume.
## NEXT STEPS
Would you be open to a 30-min demo this week?
I'll show you live results on sample content from your brand.
Available: Wed 2-4 PM, Thu 10 AM-12 PM.
Let me know!
Best,
[Your name]
[Your company] | [Your phone]
Mẹo: Luôn offer demo, không chỉ send document. Client prefer talking vs. reading.
Prompt #6: Follow-up email (aftermeeting)
Viết follow-up email sau cuộc gặp/call.
Context:
- Họp với ai: [WHO]
- Khi: [WHEN]
- Chủ đề: [TOPIC]
- Kết quả: [OUTCOME]
- Bạn cần họ làm gì: [YOUR ASK]
Cấu trúc:
1. Thank you + recap ngắn
2. Confirm next steps / action items
3. Your ask (if any)
4. Timeline
5. Open door for questions
Tone: Warm, professional, not pushy.
Output:
Subject: Following up — [Topic] discussion
Hi [Name],
Thanks for taking the time to meet last Thursday.
I really enjoyed learning more about your vision for [project].
To recap what we discussed:
- Your team wants to launch [feature] by Q3
- You're looking for a partner to handle [specific work]
- Timeline: start planning now, execution June 1st
Here's what I'm committing to:
1. Send detailed proposal by Wed, April 20
2. Schedule technical deep-dive with my team (April 22)
3. Provide reference calls with similar clients (by request)
On your end, if possible, could you:
- Share the technical requirements document?
- Confirm the budget range?
I'm excited about the possibility to work together.
Let me know if you have any questions in the meantime.
Best,
[Your name]
Mẹo: Always recap + confirm action items. Không để hang. Follow-up trong 24 giờ.
Prompt #7: Apology / Sorry email
Viết email xin lỗi vì [MISTAKE/DELAY].
Situation:
- Sai lầm: [WHAT WENT WRONG]
- Impact: [WHAT HAPPENED BECAUSE OF IT]
- Root cause: [WHY IT HAPPENED]
- Fix: [WHAT YOU'RE DOING TO FIX]
- Prevention: [HOW TO PREVENT FUTURE]
Cấu trúc:
1. Admit mistake (không excuse)
2. Apologize genuinely
3. Explain what went wrong (briefly)
4. What you're doing to fix
5. Prevention going forward
6. How to make it right (if applicable)
Tone: Sincere, accountable, not defensive.
Output:
Subject: Apology — Missed deadline on [Project]
Hi [Name],
I owe you an apology. We missed the April 15 deadline for [deliverable],
and I should have communicated the delay sooner.
That's on me.
Here's what happened:
- Our designer had an unexpected medical leave
- I underestimated the complexity of [specific task]
- I didn't escalate early enough to find solutions
Here's what I'm doing now:
- Brought in a contractor to fill the gap (starts tomorrow)
- Revised timeline: delivery by April 22 (firm)
- I'm personally overseeing the final review
To prevent this in the future:
- We'll implement weekly check-ins instead of biweekly
- I'll escalate at 50% of deadline if I see risk
- You'll get a status update every Tuesday
I understand if this impacts your plan.
How can I make this right?
Would a discount on this project help?
Again, my apologies for dropping the ball.
Best,
[Your name]
Mẹo: Apology email hành động là key. Hãy concrete về fix + timeline, không chỉ sorry.
Prompt #8: Delegation email (assign task)
Viết email giao việc cho [PERSON] về [TASK].
Task info:
- What: [SPECIFIC TASK]
- Why: [WHY IT MATTERS to company/them]
- When: [DEADLINE]
- Expected outcome: [WHAT SUCCESS LOOKS LIKE]
- Resources: [WHAT HELP/INFO THEY GET]
- Your availability: [HOW TO REACH YOU]
Tone: Clear, motivating, not micromanaging.
Trust them, but give guardrails.
Ví dụ:
- Task: "Prepare client presentation for Q2 review"
- Deadline: "Friday EOD"
- Outcome: "10-slide deck, includes: Q1 results, Q2 plan, risks, budget"
Output:
Subject: Task — Prepare Q2 Presentation Deck
Hi [Name],
I'd like to assign you the Q2 client presentation. This is important —
our client depends on this to make budget decisions.
THE TASK:
Prepare a 10-15 slide deck covering:
1. Q1 performance vs. target (include key metrics)
2. Q2 strategic plan and priorities
3. Budget proposal with ROI breakdown
4. Risk factors & mitigation
5. Timeline for milestones
DEADLINE: Friday, April 20, 5 PM
RESOURCES YOU HAVE:
- Q1 final report (in Dropbox/analytics folder)
- Template: /shared/presentations/client-template.ppt
- Me: Happy to review draft by Thu 3 PM if you want feedback
WHAT SUCCESS LOOKS LIKE:
- Slides are clear (1 idea per slide)
- Data is accurate (double-check all numbers)
- Story is compelling (client walks away with confidence)
Let me know if you have questions. I'm here to help.
Best,
[Your name]
Mẹo: Always explain WHY task matters. Employee will do better job nếu they understand impact.
Prompt #9: Difficult conversation email (prepping for meeting)
Viết email setting up một difficult conversation (performance review, salary talk, vài cái khác).
Context:
- Conversation topic: [TOPIC]
- With whom: [WHO]
- Why necessary: [WHY]
- Your goal: [WHAT DO YOU WANT?]
- Their likely concern: [WHAT MIGHT THEY WORRY ABOUT]
Cấu trúc email:
1. Acknowledge this is important
2. Suggest time/place (comfortable)
3. Preview what you want to discuss (no surprise)
4. Reassure (if needed)
5. Open to their input
Tone: Respectful, transparent, not threatening.
Ví dụ:
- Topic: "Performance concerns & expectations"
- With: Team member
- Goal: "Align on improvement plan, understand their perspective"
Output:
Subject: Let's talk this week — [Name]
Hi [Name],
I'd like to schedule a time for us to talk about your performance this quarter.
I know "let's talk" can be anxiety-inducing, so let me be clear upfront:
I want to understand how you're feeling about your role and projects,
and also share some feedback I've observed.
My goal is for us to align on expectations and see how I can support you better.
Some topics I'd like to cover:
- How you're feeling about project X (seemed stressful?)
- My observations on collaboration with the team
- How we can set you up for success
This is a conversation, not a lecture. I want to hear from you too.
Are you available for 45 min this week?
Prefer: Wed 2 PM, Thu 10 AM, or Fri 3 PM.
We'll talk in the quiet meeting room — comfortable space.
Let me know.
[Your name]
Mẹo: Difficult conversations go better khi receiver knows what's coming. Transparency builds trust.
Prompt #10: Celebration / Recognition email
Viết email khen ngợi / celebrate achievement của [PERSON] hoặc [TEAM].
Achievement:
- What: [WHAT DID THEY DO]
- Impact: [WHAT WAS THE IMPACT]
- How it affected: [COMPANY/CLIENTS/TEAM]
- Their quality: [WHAT QUALITY SHINED - creativity, resilience, collaboration]
Tone: Specific, genuine, celebratory.
Not generic "thanks for your hard work" — be concrete.
Ví dụ:
- What: "Launched new feature 2 weeks early"
- Impact: "Helped customer close $500K deal"
- Quality: "Amazing project management + collaboration with design team"
Output:
Subject: Major win! 🎉 — Feature launch
Hi [Name & Team],
I want to celebrate a major win with you.
Last month, you launched the [Feature Name] 2 weeks ahead of schedule.
That's not just punctual — that's exceptional.
Why this matters:
Because of your speed, our customer [Company] was able to close a $500K deal
they thought they'd miss. That deal literally wouldn't have happened without you.
What impressed me most:
You could have said "it's tight, we'll do our best" and cut quality.
Instead, you found a creative solution (the component reuse idea),
coordinated perfectly with Design, and shipped something clean.
That's the kind of problem-solving and collaboration that defines our culture.
I want to make sure you know the impact you had.
You're exactly the kind of teammate that makes a difference.
Great work. Seriously.
[Your name]
Mẹo: Public praise (all-hands, email to team) has bigger impact than private. Try both.
3. Bí quyết ít người biết
Bí quyết 1: "Tone + Context" ít ai dùng
Bạn có thể thêm vào bất kỳ prompt nào:
Tone: [formal/casual/friendly/stern]
Context: [who is reading this]
Length: [short/medium/long]
Ví dụ:
"Tone: Casual but professional
Context: Team of 5 engineers who respect efficiency
Length: Keep it under 50 words"
AI sẽ adjust style theo preference.
Bí quyết 2: "Reject & Suggest" pattern
Nếu bạn không thích output lần 1, không dump email đó. Gõ:
That's too formal. Make it warmer and more direct.
Reduce length by 30%. Focus on the ask, not the explanation.
AI sẽ revise. Better than start from scratch.
Bí quyết 3: "Draft + personalize" flow
AI draft = 70% done. Bạn personalize = 100%.
Ví dụ:
- AI draft: "Thanks for the meeting"
- You personalize: "Thanks for the 1-hour call despite your packed schedule. That's what I appreciate about working with you."
Small touch = big difference in how people receive message.
Điều này ảnh hưởng gì đến bạn?
Nếu bạn làm việc văn phòng:
- Trước: 10-15 giờ/tuần viết email, báo cáo, document = mệt, mất sáng tạo
- Sau: 5 giờ/tuần + chất lượng cao hơn = thư giãn + có năng lượng cho strategic work
- Hành động ngay:
- Chọn 1 loại email bạn hay viết (follow-up? weekly report? proposal?)
- Lấy 1 prompt phía trên phù hợp
- Copy-paste vào ChatGPT, edit thông tin
- So sánh: cách AI draft vs. cách bạn viết — AI nhanh không?
- Nếu nhanh + tốt, dùng tiếp với email tiếp theo
Pro tip: Tạo 1 folder "Prompt favorites" trong Notes/Evernote, paste 3-4 prompt bạn dùng lâu dài. Mỗi lần cần, chỉ copy vào ChatGPT.
Sources
| # | Title | URL | Ghi chú |
|---|---|---|---|
| 1 | OpenAI Academy | https://openai.com/academy | Hướng dẫn ChatGPT chính thức |
| 2 | FPT Shop Resources | https://www.fptshop.com.vn/ | Platform công nghệ VN |
| 3 | VietnamNet Business | https://vietnamnet.vn/ | Tin tức kinh doanh VN |
| 4 | MediaZ Marketing Hub | https://mediaz.vn/ | Resources marketing & office productivity |
| 5 | Harvard Business Review | https://hbr.org/ | Best practices văn phòng & leadership |