Ohana360Help Center
App Guides

WhatsApp360: one-click templated messages from a record

A WhatsApp button on every record with a phone number: pick a template, edit the text, open WhatsApp; the send is logged as an activity.

4 min readUpdated: September 27, 2026Türkçe oku

What is it for?#

WhatsApp360 is an add-on app. Once enabled, records with a filled phone field get a WhatsApp button on their Activity card. The goal is to stop the team retyping the same sentences and to stop those conversations from disappearing outside the CRM.

Sending a message from a record#

  1. Open a record that has a phone number: a Contact, Lead, Account, Patient, Guest or Order.
  2. Press the WhatsApp button on the Activity card. The number appears at the top of the popup.
  3. Pick a template from the list. The text arrives already filled from the record's fields.
  4. Adjust the wording for this particular message if you want.
  5. Press Open in WhatsApp: the WhatsApp app opens on a phone, WhatsApp Web on a desktop, with the message ready. You press send yourself.

At the same moment a completed WhatsApp activity lands on the record: subject "WhatsApp: template name, number", type WhatsApp, owner you, description the exact text you sent. The timeline then shows who was told what.

Tip: The button only appears when the record holds a phone value of at least 10 digits, and a mobile field wins over a landline one. Store international numbers with their country code; Turkish numbers are converted to international form automatically.

Templates and merge variables#

Five ready templates ship with the add-on:

TemplateUse
IntroductionFirst contact with a new lead
Follow-upA nudge after a call
Appointment reminderBefore an appointment or meeting
Payment reminderA collection that is due
Thank youAfter a sale or a service

These variables are filled at the moment you click: {ad} (first name only), {adsoyad} (full name), {firma} (your organization name from Company Information), {kullanici} (the logged-in user). You can also use the record's own fields, such as {phone}, {email} or {city}. A variable with no value stays in the text as written.

The template editor#

Templates live on the WhatsApp Templates card under WhatsApp360 > Home, not in Setup.

  • New Template: a template name plus the body. Click a variable button to append it to the text.
  • Every row has Edit and Delete.
  • Reset to Defaults restores the five shipped templates.

The home page also shows how many messages went out this month and in total, a short "How it works" summary and a Recent messages list; clicking a row jumps to the related record. That home page is WhatsApp360's only tab: the app is deliberately small, with no separate message object and no inbox.

Setting templates up well#

  • Name the template the way your team will look for it: "Quote follow-up", "Shipping info", "Appointment confirmation". Keep the picker short and recognizable.
  • Keep the body single-purpose. Long messages get rewritten anyway, and the point of a template is lost.
  • Use the record's fields: an amount, a date or an order number inside the template personalizes the message and saves the team copying data by hand.
  • Write your company name as {firma}; change it in Company Information and every template follows.

Because sent messages are typed as WhatsApp, they appear with their own icon on the activity timeline and are easy to tell apart from call follow-ups. Group your task reports by type to see how much each channel is actually used.

Limits#

Important: WhatsApp360 is click-and-write by design. These do not exist: automatic sending, sending WhatsApp messages from a flow, bulk sending, or incoming messages landing in the CRM. WhatsApp360 is not the official WhatsApp Business API integration; it opens the message in your own WhatsApp account, and the decision and the send button stay with you.

Enabling it#

WhatsApp360 is an add-on, enabled from the Marketplace for a monthly fee (see Marketplace and Pricing). While the add-on is off, the WhatsApp button is hidden on records.

Was this article helpful?