Canned responses

Variables

Getting started

You can easily customize your responses or templates with dynamic content like your recipient's name by using our variables templating engine.

A response like this:

Hi {{ recipient.first_name | default: 'there' }},

… if it matches a recipient.first_name would render something like this

Hi Philippe,

… and if it didn't match anything something like this:

Hi there,

Adding a variable to a response is as easy as clicking the {{ icon in the response composer:

A new popup will open where you can easily create your variable without knowing the exact syntax.

You can also create a response with dynamic content that entirely change depending if a variable is present or not.

It would look like this:

{% if recipient.first_name == null %}Hello,
{% else %}Hi {{ recipient.first_name }},{% endif %}

... if there's no recipient first name, it will render like this:

Hello,

... and if there's a recipient's first name, it will render like this:

Hi Philippe,

Build forms

When adding a variable, you don't have to use one that matches a data point provided by Missive (recipient, user). You can create a variable linked to no data, like in this screenshot:

Make sure to use underscores and dots instead of spaces.

When inserted in a draft, a form will ask the Missive user what should the value be:

Instead of using text placeholders (that you might forget to replace), this technique lets you create forms your team always has to fill in when inserting a response.

Liquid.js

Our templating engine is based on liquid.js and supports all of its tags and filters. Make sure to read the documentation if you want to go deeper and create complex logic.

Objects

recipient object

The recipient data is matched by first looking into the user contacts for matches based on the message recipient address, then on the message data itself.

Labels

Contact labels can be used to scope the search. For instance {{ recipient.work.phone_number }} would search only in phone numbers with the label work.

user object

The user object data is matched with the logged-in Missive user (you).

conversation object

The conversation object data is matched with the current conversation.

message object

The message object data is matched with the current draft.