By KYN AI Advisory Team — AI implementation specialists, Singapore
A Bahasa Indonesia sales agent should address the customer as Bapak or Ibu with their name, use "Anda" or avoid the pronoun in formal B2B writing, mirror the customer's register on WhatsApp, and keep each message short enough to read on a phone without scrolling. Translating an English script word for word fails on all four. Treat register as a setting per customer, write the style rules as tested examples, and give a person the messages that carry price, complaints or anything unclear.
Why does a translated sales script fail?
English sales copy is direct, uses "you" for everyone and tolerates a brisk tone. Bahasa Indonesia encodes relationship in the words: who you are speaking to, their age and standing, and how close you are. A script that ignores those choices reads as cold, and sometimes rude.
Three typical failures from literal translation:
- "Dear Customer" becomes "Pelanggan yang terhormat", which sounds like a printed notice.
- "You" becomes "kamu" for everyone, which is too familiar for a first message to a company director.
- Long paragraphs in a single chat bubble, which customers skim or ignore.
The fix is a style guide the agent can follow, with examples it is tested against.
Which honorifics should the agent use?
Use the title the customer would expect, followed by a name.
| Situation | Form | Note | |---|---|---| | Man, older or senior, or unknown age | Bapak or Pak, plus name | Safe default for a business contact | | Woman, older or senior, or unknown age | Ibu or Bu, plus name | Safe default for a business contact | | Younger peer, retail or e-commerce | Kak, plus name | Common in consumer chat; warm and neutral | | Group or unknown gender | Bapak/Ibu | Use when the name does not indicate gender | | Written company documents | Anda | Formal "you"; many writers avoid pronouns altogether |
Rules for the agent:
- Take the title from the CRM field. If the field is empty, use "Bapak/Ibu" and the name as written, then ask for the preferred form if it matters.
- Never guess gender from a name alone when the name is ambiguous.
- Use the same form for the whole thread. Switching mid-conversation looks like a mistake.
- Do not use "kamu" or "lo/gue" unless the customer does first and the account is consumer-facing.
- Use "Saya" for the sender. For a team message, "kami" (we, excluding the customer) is correct.
These conventions are widely taught; have a native speaker on your team confirm them for your sector before launch, since usage varies by region and industry.
How should the agent set register?
Define three registers and store one per contact.
- Formal. Full sentences, titles, no abbreviations, closing with "Terima kasih". For first contact with companies, government-linked buyers and senior people.
- Neutral. Polite but conversational. Common words, light emoji only if the customer uses them. For repeat B2B contacts.
- Casual. Short, friendly, common abbreviations. For consumer chat where the customer started casual.
The agent starts formal for B2B and mirrors upward or downward only after the customer sets the tone. It never goes more casual than the customer.
What WhatsApp norms should the agent follow?
- Open with a greeting. "Selamat pagi, Bu Dewi" before any question. Choose pagi, siang, sore or malam by the customer's local time.
- Keep messages short. One idea per bubble, at most three or four lines.
- Use plain Bahasa. Avoid stacked English loanwords unless the customer uses them.
- Offer a way to continue. End with one clear question or next step, not three.
- Acknowledge before answering. "Baik, Pak, saya cek dulu" tells the customer the message arrived.
- Respect time. Avoid sending outside normal hours unless the customer wrote first. Many Indonesian businesses also observe prayer and holiday times; schedule with that in mind.
- Use voice notes only if a person sends them. The agent writes text.
For platform setup and costs, see WhatsApp Business for sales in Indonesia and sistem custom WhatsApp untuk bisnis Indonesia.
How do you handle language mixing?
Indonesian business chat mixes Bahasa and English, and regional languages appear too. Give the agent a rule:
- Reply in the language of the customer's last message.
- If the customer mixes, match the mix at their level, not above it.
- If the message is in a regional language or you cannot classify it, hand to a person.
- Never translate a price, a date or a term without a person approving the wording.
Numbers need care. Indonesian format uses a dot for thousands and a comma for decimals: Rp 1.250.000,00. Confirm the agent formats currency and dates consistently with the customer's documents, and run a test on this.
What must a person always handle?
Name these in advance. The agent stops and hands over on:
- price, discount, payment term or delivery date commitments;
- complaints, refunds and anything with legal wording;
- religious, political or family topics raised by the customer;
- any message the agent cannot classify with confidence;
- a request to speak to a person.
Hand-over wording matters. "Baik, Bu, saya sambungkan dengan tim kami" (I will connect you with our team) is better than silence. The agent should say a person will reply and give the working hours. This follows the same approval pattern as in our guide to approval gates for high-risk agent actions.
How do you test the agent before launch?
- Write 50 real customer messages, from past chats with identifying details removed, across formal, neutral and casual registers.
- Have two native speakers write what they would reply.
- Run the agent on the same 50.
- Score each reply on honorific, register, length, accuracy and hand-over.
- Fix the style guide, not individual replies, and retest.
Repeat after any change to the model or the prompts. Keep the 50 as a regression set.
A site and a sales system that carry the same language rules should also pass the same test. For websites, see trilingual websites for Singapore.
Where KYN fits
KYN builds Bahasa Indonesia sales agents as part of a larger system in the client's own cloud account: reply sorting, drafting from your catalogue and price list, CRM logging and follow-up queues. Outbound messages and anything about price wait for a named person, and every action is logged with the actor. See sales systems.
The first 14 days are a review of your stack and interviews with your team, including how your people actually write to customers. A full build ships in under 90 days. Rights in the custom code and configuration pass to you on full payment.
Frequently asked questions
Should the agent use "Anda" or "kamu"?
Use "Anda" or avoid the pronoun in formal and first-contact writing. Use "kamu" only for casual consumer chat and only after the customer does. When in doubt, use Bapak or Ibu with the name.
Can the agent write in Bahasa and English in the same thread?
Yes, if the rule is to reply in the language of the customer's last message. Hand off to a person for regional languages or unclear text, and never translate commitments without approval.
Who should review the style guide?
A native speaker who sells in your sector. A general translator catches grammar but may miss the register your customers expect. Review it again after the first 50 live conversations.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
