Skip to main content

Messaging Best Practices

Messaging

Recommended practices distilled from across the Messaging guides, covering channel setup, templates, sending, conversations, delivery, and permissions. Each section below corresponds to its own detailed walkthrough.

Getting Started​

The order in which messaging is set up decides how much rework there is later.

  • Connect and test one channel at a time. Turn on the module, connect the provider, create one template and send it to your own address or number before moving to the next channel. A fault is then easy to place, because only one thing has changed.
  • Give each channel a distinct job before building anything. SMS suits a short notice such as a reference number, email suits detail and attachments, and WhatsApp suits an exchange in which the customer is likely to reply. Customers notice when the same notice arrives three times in three places.
  • Message only customers who have agreed to hear from you on that channel. Keep the consent and its date in the customer's record. WhatsApp in particular expects customers to have opted in.

Modules​

The Email and Messaging modules decide which provider carries every new message.

  • Treat the provider drop down of each module as a switch for the whole channel. The Email module sends through the one provider chosen under Email Configurations, and the Messaging module through the one chosen under Messaging Configurations. Changing the choice changes where every new message goes.
  • Change the active provider in a quiet period, then send a test straight away. Choose a time with little traffic, click Save Configuration, and send a message to yourself before agents resume sending.
  • Remember that the Messaging module covers SMS, not WhatsApp. Its description reads SMS provider management and configuration. WhatsApp is configured only as a plugin under Plugins.

Email Providers​

Mailgun, AWS SES and SMTP all send mail, but each asks for different details and each can fail in a different way.

  • Enter every sender you will use under From Emails, with a clear Display Name. The Send With Email list of a template offers only the addresses entered here, and the Display Name is what the customer sees. Use the arrows beside a sender to put the most used one first.
  • Copy the Mailgun Webhook URL into your Mailgun account straight after saving. Mailgun uses it to report delivery status back to the platform. Without it, messages leave but no delivery update returns.
  • Fill in the fields marked This field is required before you save SMTP. SMTP Host, SMTP Port and at least one From Emails address are required, and the form shows a red message beneath each one that is empty.
  • Tick Use Secure Connection and Use Authentication to match your mail server. Use Secure Connection turns on SSL or TLS. Use Authentication is needed only when the server asks for a user name and a password. A mismatch with the server is the most common reason an SMTP test fails.
  • Set a Reply To Address when replies should reach a different mailbox. It is optional. When it is empty, replies go to the sender address, which may not be watched.

SMS Providers​

Generic SMS, Twilio SMS and Dialog E–SMS differ mainly in how a sender is identified and how the reply is read.

  • Add more than one Sender Mask to Dialog E–SMS only when you really use them. Each mask is shown to recipients as the sender. Use the add button for another mask and the bin icon to remove one that is no longer needed.
  • Enter the Call Back URL for Twilio SMS. It is optional in the form, but it is the address that receives delivery status updates, so without it no delivery update comes back.
  • Check the three response paths of Generic SMS against a real reply from your gateway. Error Message Path, Success Path and Message ID Path tell the platform where to read the result. The defaults suit many gateways, but a gateway with a different reply shape needs its own paths.
  • Choose the Phone Number Format that your gateway expects. The options are Digits Only, Local Format, E.164 International and Original. A wrong format is a common reason a gateway rejects a number.

WhatsApp Plugin​

Most WhatsApp problems start in the Meta account, not in the platform.

  • Use a permanent Access Token. A temporary token expires, and messages then stop without a warning in the platform.
  • Make the Verify Token identical on both sides. The value in the plugin must match the value given to Meta, or Meta will not accept the Webhook URL.
  • Copy the Webhook URL from the plugin into the Meta App Dashboard. Meta sends incoming messages and delivery updates to that address. The copy icon beside the URL copies it in one click.
  • Keep the App Secret and the Access Token out of shared notes. Both are hidden after entry in the form, and anyone who has them can send as your business.

Email Templates​

The visual editor makes an email easy to design, and just as easy to leave half finished.

  • Choose the Module and the Send With Email address when you create the template. On an existing template the Module field is greyed out, so a wrong choice means creating the template again.
  • Start with the Generate box, then refine the design by hand. Describe the email in the box, let AI draft it, and then adjust it in Build or Code. It is faster than a blank page and you stay in control of the final wording.
  • Check the Preview tab on both the computer and the phone view. The two icons beside the tabs switch the size. Most customers read on a phone, so a design that works only on a wide screen is not finished.
  • Use placeholders in the Subject as well as the body. A subject that names the customer or the reference is opened more often and is easier to find later.
  • Attach files to the template only when every message needs them. Add Files attaches a file to every message that uses the template. A failed upload shows Failed to upload attachment, so keep files small.

SMS Templates​

An SMS is short, and the values that fill it decide how long it really is.

  • Watch the character and message counters before you send. The Send Message window shows how many characters the message has and how many messages it becomes. A long name or value can push an SMS into a second part.
  • Say who you are, what happened and what to do next. Choose the sender under Send As so the customer knows who wrote. Leave out abbreviations the customer may not know.
  • Insert fields from the chips instead of typing the brackets. After you choose the module, every field of it appears as a chip, such as First Name or Mobile Number. Inserting one avoids a spelling mistake in the name.

WhatsApp Templates​

WhatsApp templates are approved by Meta, which is why several fields are locked once the template exists.

  • Decide the Template Name, Language, Module and Category before you click Create. On an existing template all four are greyed out. To change one, create a new template.
  • Choose the Category that matches the message. Utility suits an update about something the customer already did, such as a booking. Marketing suits an offer. Meta treats them differently, so a wrong category can delay approval.
  • Stay inside the limits shown by the counters. The Body allows 1024 characters and the Footer 60. The counter turns red when you go over.
  • Give each variable a Preview Value under Dynamic Variables. The WhatsApp preview then shows a real looking message, which makes mistakes easy to see before the template is submitted.
  • Add a Quick Reply button when you want a simple answer. A button such as Received gives the customer a one tap reply and keeps the answer in the same conversation.

Placeholders​

A placeholder is replaced only when its name matches, and an unmatched one is sent exactly as typed.

  • Write each placeholder exactly as the field is named, with the same capital letters. A name that does not match is sent as typed. A message that reads {{customerName}} in the customer's hands is the sign of a mistyped name.
  • Use only fields that belong to the template's module. The module chosen on the template decides which record fields are available, so a template for one module cannot read the fields of another.
  • Send a test from a record that has every field filled in. A record with an empty field produces a message with a gap, which is not the template's fault but still reaches a customer.

Sending Messages​

Most mistakes happen at the moment of sending, when an agent is busy and the customer is waiting.

  • Check the email address or phone number on the record before you send. One wrong digit sends a customer's information to a stranger. Read the detail back to the customer when you can.
  • Read the preview every time and look for text that did not fill in. The preview is the last point at which a mistake costs nothing.
  • Ask an administrator for a missing template instead of rewriting it by hand. Only the templates of the record's module and the chosen channel are offered, so a short list is normal and a missing one means a template is needed.
  • Check the ticks and the provider before you send a message again. A message that looks stuck may already be on its way, and a repeat annoys the customer.
  • Read the message the page shows after a WhatsApp send. WhatsApp message sent confirms success, and Error sending WhatsApp message means the template or the token needs attention.

Conversations​

Conversations keeps the history of a customer in one place, but only if replies are handled there.

  • Click Unread at the start of every shift and clear the list in order. A customer who replied overnight should hear back first. The blue number on a row shows how many messages you have not read.
  • Read the second line of a row before you open it. It names the module and the channel, for example Contacts and SMS, so you know which record the message belongs to and where your reply will go.
  • Search the customer's address or number before you write. An earlier message may already answer the question, and the search box above the list finds it.
  • Report a message that shows raw placeholder text. Text such as {{customerName}} in a sent message means a template has a mistyped placeholder. Tell the template owner so it is fixed for everyone.

Message Delivery and Logs​

When a customer says nothing arrived, the quickest answer comes from checking in a fixed order.

  • Check the ticks first, then the provider dashboard, then the platform logs. The ticks tell you whether the platform recorded the message. The provider dashboard tells you whether the message left. Monitoring, Logs explains a failure that happened before the provider.
  • Register the delivery webhook before judging the ticks. Mailgun and WhatsApp show a Webhook URL, and Twilio SMS shows a Call Back URL. Without them, delivery updates cannot return, and ticks will not move on.
  • Search the log for the provider name or the customer's address. Searching on one of the two narrows a large log file to the few lines that matter.

Permissions​

The five Messaging permissions are independent settings, and the two view permissions carry a scope.

  • Do not assume that Send Message includes the right to see sent messages. Send Message, View Sent Message and View Sent E–mail are separate. A person may send and still see nothing until the view permissions are set.
  • Choose the smallest scope that does the job. Use Own for agents, Group for supervisors and All only for people who must see everything. Sent messages contain personal details.
  • Give Manage Message Templates and Manage Email Templates to a few people. A changed template changes what every customer receives.
  • Expect the System Owner role to open read only. Its fields are greyed out and it has no Save button, so create a role of your own when you need different access.
  • Use Clear All when a role should have no Messaging access. One click switches every permission of the group off, instead of changing each one separately.