Social Engagement · Training SessionSocial Engagement · Sesi Training
De-escalationDe-eskalasi
Lowering the heat in public threads — and knowing when to move the conversation private.
Menurunkan “suhu” di thread publik — dan tahu kapan harus memindahkan obrolan ke private.
The 4-step flowFlow 4 langkah
The 4-part replyBalasan 4 bagian
LinkedIn + Facebook examplesContoh LinkedIn + Facebook
QuizKuis
Use ← → to navigate
Pakai ← → buat pindah slide
The goalTujuan
Why we take heated threads privateKenapa thread yang panas kita pindahin ke private
The goal is simple: shift the public discussion to a private conversation.
Tujuannya simpel: pindahin diskusi publik ke percakapan private.
Protect the brandJaga brand
We do not want the public to see the entire conversation, as it has the potential to affect the brand image.
Kita nggak mau publik lihat seluruh percakapan, karena bisa berdampak ke citra brand.
Protect sensitive infoJaga info sensitif
We do not want to disclose sensitive information in a public thread.
Kita nggak mau info sensitif kebuka di thread publik.
The flowFlow-nya
1
Label the sentiment — positive, negative, or neutral. Negative mostly needs the de-escalation flow.
Kasih label sentimen — positif, negatif, atau netral. Yang negatif biasanya butuh flow de-eskalasi.
2
Check for context — look for existing CRM records or Kodee Desk chats related to the issue.
Cek konteks — cari CRM record atau chat Kodee Desk yang berkaitan dengan masalahnya.
3
Reply in public once — use the 4-part pattern (next slide).
Balas di publik sekali — pakai pola 4 bagian (slide berikutnya).
4
Shift to DM or email — frame it as better service, not hiding.
Pindah ke DM atau email — bingkai sebagai layanan yang lebih baik, bukan menyembunyikan.
Analogy: Think of a restaurant manager at a loud table. They don’t argue in the middle of the dining room — they say “let me sort this out for you” and walk the guest somewhere quieter.
Analogi: Bayangin manajer restoran di meja yang lagi ribut. Dia nggak debat di tengah ruangan — dia bilang “biar saya bantu beresin” lalu ajak tamunya ke tempat yang lebih tenang.
The replyBalasannya
The core pattern: 4 parts, one replyPola inti: 4 bagian, satu balasan
Every public reply to a heated comment follows the same four moves, in this order.
Setiap balasan publik ke komentar yang panas ngikutin empat langkah yang sama, dengan urutan ini.
1
Acknowledge the feeling first — no “but”. Full stop. Adding “but” erases it.
Akui perasaannya dulu — tanpa “tapi”. Titik. Kalau ditambah “tapi”, empatinya hilang.
“This is honestly not something I want anyone to experience.”
2
Reframe the issue in neutral language. No blame, no defense, no policy talk.
Reframe masalahnya pakai bahasa netral. Nggak nyalahin, nggak membela diri, nggak ngomongin policy.
“Your support is useless, I got transferred 5 times” → “getting passed around without a fix”
3
Take action. Say exactly what you will do next. A name and a concrete action, not “we’ll look into it”.
Ambil tindakan. Bilang persis apa yang akan kamu lakukan. Nama dan aksi konkret, bukan “kami akan cek”.
“I’ll personally make sure this gets investigated and followed up on.”
4
Invite the conversation private. Asking permission keeps control with the customer.
Ajak ngobrol private. Minta izin supaya kontrol tetap di tangan customer.
“If you’re open to it, my DMs are open.”
Analogy: A good hospital receptionist: first “that sounds awful” (feeling), then “so you’ve been waiting without answers” (neutral recap), then “here’s what I’m doing right now” (action), then “come this way, we’ll talk privately” (invite).
Analogi: Resepsionis rumah sakit yang baik: pertama “wah, pasti nggak enak” (perasaan), lalu “jadi Anda nunggu tanpa jawaban” (rangkuman netral), lalu “ini yang saya lakukan sekarang” (aksi), terakhir “silakan ke sini, kita bicara di ruang privat” (ajakan).
What not to doYang jangan dilakukan
The failure mode: “however… our policy states”Kegagalan klasik: “namun… kebijakan kami”
One sentence can undo all your empathy. Read it out loud — then tap the highlighted parts.
Satu kalimat bisa menghapus semua empati kamu. Baca keras-keras — lalu tap bagian yang di-highlight.
✗ Escalates✗ Bikin makin panas
“I understand your frustration, however our policy states that account verification must be completed before any changes can be made.”
“However” cancels the empathy before it lands.
“However” menghapus empati sebelum sempat terasa.
“Our policy states” tells the person the company matters more than they do.
“Our policy states” bilang ke customer bahwa perusahaan lebih penting daripada dia.
✓ De-escalates (illustrative)✓ Meredakan (contoh ilustrasi)
“This is honestly not something I want anyone to experience. If you’re open to it, my DMs are open — share a bit more context and I’ll personally make sure this gets investigated.”
Feeling → action → private invite. No “but”, no policy, no verification demand in public.
Perasaan → aksi → ajakan private. Nggak ada “tapi”, nggak ada policy, nggak ada tuntutan verifikasi di publik.
Analogy: Saying “sorry, but…” is like handing someone a gift and taking it back in the same breath.
Analogi: Bilang “maaf, tapi…” itu kayak ngasih hadiah terus langsung diambil lagi di napas yang sama.
Real exampleContoh nyata
Example 1: LinkedInContoh 1: LinkedIn
A user posted that Hostinger support is the worst on planet Earth after spending 11 hours on one issue.
Seorang user posting bahwa support Hostinger yang terburuk di dunia setelah 11 jam ngurusin satu masalah.
1
We notice the negative comment — sentiment label: negative.
Kita sadar ada komentar negatif — label sentimen: negatif.
2
Acknowledgment with a real name and personal ownership. (Use the LinkedIn negative-handling flow with Matheus’ account.)
Pengakuan pakai nama asli dan ownership personal. (Ikuti flow handling negatif di LinkedIn dengan akun Matheus.)
3
Permission-based invite to DM: “If you’re open to it.”
Ajakan DM berbasis izin: “If you’re open to it.”
Result: the author asked Matheus to DM him. The heat left the public thread in one exchange.
Hasilnya: si author minta Matheus DM dia. Panasnya keluar dari thread publik dalam satu kali tukar balasan.
Real exampleContoh nyata
Example 2: FacebookContoh 2: Facebook
Clearly negative, and no context on file — so the comment is hidden first, then we ask for just enough to investigate.
Jelas negatif dan nggak ada konteks — jadi komentar di-hide dulu, lalu kita minta info secukupnya buat investigasi.
HiddenDi-hide
Comment (summary)Komentar (ringkasan)
Doesn’t recommend us: account deleted, can’t log in to back up websites, doesn’t know how to recover domains.
Nggak merekomendasikan kita: akun terhapus, nggak bisa login buat backup website, nggak tahu cara recover domain.
Engage noteEngage note
Sentiment: negative. No related CRM or Kodee chat found → no context.
Sentimen: negatif. Nggak ada CRM atau chat Kodee terkait → nggak ada konteks.
Public reply (illustrative wording)Balasan publik (contoh redaksi)
“This can happen for different reasons. Could you share your domain or account email at quality@hostinger.com so the team can investigate?”
“This can happen for different reasons. Could you share your domain or account email at quality@hostinger.com so the team can investigate?”
1
Hide first. Then the quality inbox isn’t exposed to the whole public thread — we can’t disclose it to everyone.
Hide dulu. Jadi inbox quality nggak kebuka ke seluruh thread publik — kita nggak boleh kasih tahu ke semua orang.
2
No CRM or Kodee chat = no context. Don’t guess. Ask for the domain or account email in one clear step.
Nggak ada CRM atau chat Kodee = nggak ada konteks. Jangan menebak. Minta domain atau email akun dalam satu langkah jelas.
3
Stay neutral. “This can happen for different reasons” is factual — no admitting fault, no arguing.
Tetap netral. “This can happen for different reasons” itu faktual — nggak ngaku salah, nggak debat.
Analogy: Hiding the comment first is like closing the door before you hand over a private phone number — the number only reaches the person it’s meant for.
Analogi: Nge-hide komentar dulu itu kayak nutup pintu sebelum ngasih nomor telepon pribadi — nomornya cuma sampai ke orang yang dituju.
The offline signalSinyal pindah offline
When to stop replying publiclyKapan harus berhenti balas di publik
Tick every signal you see in a thread. Even one is enough to take it offline.
Centang semua sinyal yang kamu lihat di thread. Satu aja sudah cukup buat pindah ke offline.
After 2 or 3 public exchanges with no progress.
Sudah 2–3 kali tukar balasan di publik tapi nggak ada kemajuan.
The person is escalating no matter what you say.
Orangnya makin panas, apa pun yang kamu bilang.
Other users are piling on — the thread is now a stage.
User lain ikut menyerang — thread ini sudah jadi panggung.
The next reply would need account details or anything sensitive.
Balasan berikutnya butuh detail akun atau hal sensitif.
The next reply would just repeat what you already said.
Balasan berikutnya cuma akan mengulang yang sudah kamu bilang.
0 / 5No signal yet — one strong public reply, then keep watching.Belum ada sinyal — satu balasan publik yang kuat, lalu terus pantau.
Analogy: When a thread becomes a stage, you’re performing for an audience instead of helping a person. A good host moves the conversation backstage.
Analogi: Kalau thread sudah jadi panggung, kamu tampil buat penonton, bukan nolong orang. Host yang baik memindahkan obrolan ke belakang panggung.
ToolkitToolkit
4 phrases you can reuse under pressure4 kalimat yang bisa kamu pakai saat tertekan
When a thread is moving fast, start from these. Tap Copy, then adapt with a name and the real issue.
Pas thread lagi bergerak cepat, mulai dari sini. Tap Salin, lalu sesuaikan dengan nama dan masalah aslinya.
Opener · acknowledgePembuka · akui perasaan
“This is honestly not something I want anyone to experience, and I appreciate you sharing it openly.”
Invite privateAjak ke private
“If you’re open to it, my DMs are open. Share a bit more context and I’ll personally make sure this gets investigated.”
Long wait or many transfersNunggu lama / banyak transfer
“You shouldn’t have had to spend this much time on this. Let me take it from here.”
Sensitive details neededButuh detail sensitif
“I’d rather not ask you to share account details publicly. Could you send them by DM so I can check properly?”
The whole flow: Sentiment label > check CRM and Kodee Desk > one strong public reply > shift to DM or email.
Seluruh flow-nya: Label sentimen > cek CRM dan Kodee Desk > satu balasan publik yang kuat > pindah ke DM atau email.
Check yourselfCek pemahamanmu
QuizKuis
Eight questions across the whole session. Pick one answer each.
Delapan pertanyaan dari seluruh sesi. Pilih satu jawaban tiap soal.