ramaaditya49/tutur/tutur-korporat-profesi

Tutur Korporat Profesi

Overview

Use this skill to write Indonesian professional communication that matches the role, channel, audience, and business goal. It covers sales, CS/support, admin/ops, HRD/recruitment, finance reminders, marketing, leadership, and general corporate chat.

Default to clear, concise Indonesian. Use English corporate terms only when the audience naturally uses them.

Search And Discovery

Relevant searches: bahasa sales Indonesia, script sales WhatsApp, customer service bahasa Indonesia, template chat CS, bahasa admin kantor, bahasa HRD rekrutmen, email profesional Indonesia, corporate communication Indonesia, bahasa kerja sales CS admin HRD, copywriting profesional Indonesia.

Use this skill for role-aware corporate writing. It must follow company policy and must not invent prices, salary, discounts, guarantees, legal claims, refund rules, or SLAs.

Workflow

1. Identify the role and objective.

• Sales: prospect, follow up, qualify, handle objection, close softly.
• CS/support: acknowledge, empathize, clarify, solve, set timeline, close.
• Admin/ops: coordinate tasks, documents, schedule, reminders, status.
• HRD/recruitment: invite, reject, offer, update, explain process, policy.
• Finance/admin billing: remind, confirm payment, clarify invoice, escalate.
• Leadership/corporate: update, align, decide, unblock, summarize.

1. Identify channel and audience.

• WhatsApp: shorter, warmer, direct.
• Email: structured, subject-aware, complete.
• Internal chat: concise, task-first, low ceremony.
• Public-facing: standard Indonesian, no risky claims.

1. Choose register.

• Formal: official, complete, no slang.
• Professional: clear, respectful, efficient.
• Startup/corporate casual: direct, light code-mix if natural.
• Sales/CS warm: friendly without fake intimacy.

1. Compose.

• Lead with context.
• State the ask, issue, or next step.
• Include owner, deadline, and dependency when relevant.
• Avoid empty corporate jargon and unsupported claims.

Output Style

• For direct writing requests, provide the message first.
• For review requests, list role/tone risks, then give a better version.
• For multiple roles, provide labeled variants.
• Do not invent policy, prices, legal terms, salary promises, discounts, SLAs, or product claims.

Resources

• references/offline-brief.md: compact local brief for agents without internet access.
• references/local-mirror.md: local mirror of role/register rules and semantic guidance.
• references/usage-patterns.md: task patterns and review checklist.
• references/sources.md: research base and source notes.
• references/style-guide.md: role-by-role language rules.
• references/examples.md: target-register examples.