WhatsApp and Email templates
A sales rep types the same sentence thirty times a day: "Dear X, I would like to follow up on our quotation Y…". Templates remove that repetition — but the real gain is elsewhere: the text that was sent lands verbatim in the opportunity's activity log. A hand-typed message was recorded nowhere, so "what did we promise the customer" had no answer.
Templates: the CRM → Templates tab. Sending: the Send message button on the opportunity card.
1. Writing a template
You give a template a name, a channel and the text. The channel has three options: WhatsApp, Email, or both. Where the text should change per customer you place variables such as {{kisi}} or {{baslik}}; you insert them by clicking the list, so no names need memorising.
| Variable | What it fills in |
|---|---|
{{kisi}} · {{firma}} · {{carikod}} | The contact person (lead name, otherwise the account title), the account title and its code. |
{{baslik}} · {{tutar}} · {{ihtimal}} · {{durum}} | The opportunity's title, amount, win probability (%) and status. |
{{beklenen}} · {{sorumlu}} · {{bugun}} | Expected closing month (YYYY-MM), the opportunity owner and today's date. |
{{sonraki}} · {{sonraki_tarih}} | The next step you recorded in the last activity and its date — the heart of a follow-up message. |
{{tel}} · {{eposta}} | Phone and email. The recipient address is picked from these too. |
2. Sending
Press Send message on the opportunity card and pick the template and channel. Below you see a preview of the actual text and the recipient. You see exactly what will go out before you press Send.
If the opportunity has no phone, {{tel}} is not printed empty; it stays in the text as a placeholder and an amber warning appears in the preview. If you press Send, the system asks once more. The reason is simple: silently blanking it means sending the customer a message that starts "Dear ,".
The same template can go to WhatsApp and to email. Had we resolved the variables on the client, the two channels would produce two different texts — one going to the customer and another into the record. That is why merging happens in one place, on the server.
3. Where the sent message is recorded
If the send succeeds, the text, the recipient and the channel are written into the opportunity's activity log. Months later, "what did we promise this customer, and when" has an answer in the record. If the activity cannot be written, the notification tells you — the message may have gone out without being logged, and you need to know that.
WhatsApp/email delivery runs through a separate service. If it is not installed the system says so plainly and does not claim "sent". You can still prepare templates, see the preview, and copy the text to send it by hand.
Related guides: CRM and Sales · Account Card · Communication.
Related guides
- CRM Module — A Guide from Scratch for SalespeopleThis guide is written for a salesperson who has never used a CRM. The goal is not to make you memorise buttons but to explain why it works this way.
- The Account Card — Your Whole Relationship with a CustomerThe word "cari" (current account) sounds intimidating, but it simply means the debit-credit ledger between you and one customer or supplier.
- Communication — Messages, Mail and WhatsAppThe Communication group on the dock holds three windows that do very different jobs. This is what gets confused most: Messages is internal.
- My Sales Cockpit: the salesperson’s single daily screenThe cockpit gathers the six things a salesperson should check at the start of the day in one window: this month’s target and actual sales.
- Sales Counter: price, delivery, credit and approval on one screenWhen a customer asks “how much, when, can you deliver?” , answer without opening a document. The counter shows the price engine’s price and its reason.
- Customer Briefing: one paragraph before the visitCustomer Briefing gathers an account’s purchases over the last 12 months, payment habits, recent contacts and key contacts into one rule-based paragraph.