본문으로 건너뛰기

튜토리얼: 비즈니스 커뮤니케이션

목표: 전문적인 이메일, 회의록, 경영진 요약을 마스터합니다. 난이도: 초급~고급 소요 시간: 5분

시나리오 1: 빠른 이메일 답장​

긴 고객 이메일을 받았고, 몇 분 안에 전문적으로 답장해야 합니다.

1단계: 맥락 파악하기​

받은 이메일을 선택합니다:

"Hi, I wanted to follow up on our meeting last week. We discussed the Q3 projections and I'm concerned about the timeline. The board is asking tough questions and I need ammunition. Can we push the deadline? Also, the vendor situation is still unresolved. Let me know your thoughts."

2단계: "Draft Reply" 실행하기​

다음과 같은 명령을 사용합니다:

"Draft a professional reply to this email. Acknowledge their concerns, address each point, and suggest a constructive path forward. Keep it concise but thorough."

결과:​

"Hi [Name],

Thank you for following up. I understand the pressure from the board, and I want to ensure we address this effectively.

Regarding the timeline: I've reviewed our current progress and believe we can realistically accommodate a one-week extension without impacting downstream deliverables. Shall I prepare a revised schedule for your review?

On the vendor situation: I'm actively working with procurement. We should have resolution by EOD Thursday. I'll send you an update as soon as it's confirmed.

Happy to jump on a quick call if you'd prefer to discuss further.

Best regards"

시나리오 2: 60초 만에 회의록 작성하기​

브레인스토밍 세션에서 나온 정리되지 않은 메모가 있습니다. 이를 실행 가능한 회의록으로 바꿔보겠습니다.

1단계: 원본 메모 선택하기​

"Discussed new product feature. Sarah likes the blue design. John worried about timeline—2 weeks not enough. Need to check with engineering. Budget question—Mike checking. Marketing wants to announce early. Legal review pending. Next meeting Tuesday."

2단계: "Format Meeting Minutes" 실행하기​

"Structure these meeting notes into professional minutes with: Attendees (if mentioned), Key Decisions, Action Items (with owners/dates), and Next Steps."

결과:​

MEETING MINUTES – [Date]
Attendees: Sarah, John, Mike (+ others implied)

KEY DISCUSSION POINTS
• New product feature design reviewed (blue variant preferred)
• Timeline concerns raised (2-week deadline may be insufficient)
• Budget verification in progress
• Marketing eager for early announcement
• Legal review outstanding

ACTION ITEMS
• [Engineering lead]: Confirm 2-week feasibility – Due: [TBD]
• Mike: Verify budget allocation – Due: [TBD]
• [Legal contact]: Complete compliance review – Due: Before announcement

NEXT MEETING
• Tuesday [Time TBD]

시나리오 3: 경영진을 위한 요약 보고서​

20페이지 분량의 보고서가 있고, 임원 발표까지 5분 남았습니다.

1단계: Space 생성하기 (선택 사항이지만 권장)​

정확한 요약을 위해 전체 보고서를 "Q3 Report" Space에 업로드합니다.

2단계: "Executive Summary" 실행하기​

Space를 활성화한 상태에서:

"Create a one-page executive summary of this report for the CEO. Focus on:

  • Key findings (3 bullets max)
  • Risks and mitigations
  • Recommendations with ROI
  • Immediate action required Use confident, decisive language."

결과:​

EXECUTIVE SUMMARY: Q3 Performance Report

KEY FINDINGS
• Revenue exceeded targets by 12% ($5.2M vs. $4.6M projected)
• Customer acquisition cost reduced 18% through organic channels
• Churn increased in SMB segment (requires attention)

RISKS & MITIGATIONS
| Risk | Impact | Mitigation |
|------|--------|------------|
| SMB Churn | -$400K/year | Launch retention campaign (Q4) |
| Supply constraints | Medium | Diversify vendor relationships |

RECOMMENDATIONS
1. Invest $200K in SMB retention → Est. ROI: 4.2x
2. Accelerate enterprise sales hiring → Est. ROI: 3.1x

ACTION REQUIRED
Approve retention campaign budget by Friday to launch before renewal cycle.

시나리오 4: 어려운 대화​

관계를 해치지 않으면서 요청을 거절해야 합니다.

1단계: 상황 설명하기​

"I need to tell a client we can't meet their deadline. They're important but the request is unrealistic."

2단계: "Polite Decline" 실행하기​

"Write a professional response declining this request. Acknowledge their importance, explain constraints without over-apologizing, and offer alternatives. Preserve the relationship."

결과:​

"Thank you for your trust in our team to deliver on this initiative. After careful review, I need to be transparent: delivering by [date] would compromise the quality standards both you and we expect.

Here's what I can offer:

  • Option A: Full delivery by [realistic date] with all features
  • Option B: Phased delivery with core features by [original date]

I recommend Option A for the best outcome, but I'm committed to making either work for you. Can we discuss briefly to align on the best path forward?"

비즈니스 커뮤니케이션 명령 라이브러리​

명령사용 사례
"Email Reply"수신된 이메일에 답장하기
"Polite Decline"전문적으로 거절 의사 밝히기
"Meeting Minutes"원본 메모를 구조화하기
"Executive Summary"경영진을 위해 축약하기
"Action Items"논의 내용에서 작업 항목 추출하기
"Status Update"진행 상황 보고서 형식화하기
"Proposal Draft"비즈니스 제안서 구조화하기
"Follow-Up"회의 후 후속 연락

비즈니스 맥락을 위한 Space 활용​

회사 맥락 Space​

업로드할 항목:

  • 회사 스타일 가이드
  • 조직도 또는 팀 소개
  • 과거 성공적인 이메일/제안서

이 Space가 활성화된 상태로 명령을 실행하면, Rephlo는 회사의 어투를 맞추고 적절한 맥락을 참조합니다.

고객 맥락 Space​

주요 고객마다 Space를 하나씩 생성합니다:

  • 이전 커뮤니케이션 내역
  • 계약 요약
  • 관계 관련 메모

고객 X에게 답장하기 전에 해당 고객의 Space를 활성화하여 개인화되고 맥락을 인식한 응답을 받으세요.

실전 팁​

어조 조정​

명령 프롬프트에 다음을 추가하세요:

  • "Use a warm but professional tone" (고객 대상)
  • "Be direct and action-oriented" (내부 팀)
  • "Use formal corporate language" (이사회 커뮤니케이션)

긴급성 표시​

시급한 요청의 경우:

"Mark this as urgent in the subject line and opening sentence. Create clear deadlines for response."

문화적 민감성​

국제적인 커뮤니케이션의 경우:

"Adapt this for a Japanese business audience. Use appropriate formality levels and indirect communication style."

다음 섹션: 페르소나별 사용자 가이드