Appearance
Message templates
Message templates are part of Qorekit Pro.
An email or an SMS that several automation rules send is written once, as a template, and their Send an email and Send an SMS steps use it instead of a text of their own, and so can people who send an SMS from a record. This page is also about what emails and SMS can hold, whether a step writes them itself or uses a template.
Templates
Administration › Automation › Templates lists the templates of every entity whose rules you manage, as a table: their name, kind (Email or SMS), entity, subject or the start of their text, and when they were changed. The entity chosen above narrows the list. Add an email template and Add an SMS template make one for the chosen entity.
- An email template has a subject, a body and its tables.
- An SMS template has a text.
A template belongs to an entity, and only that entity's rules use it; an email step uses only email templates, an SMS step only SMS templates. In a step, Text chooses Written here or a template.
The step reads the template as it runs, so changing the template changes the messages sent after. A template that rules use can't be deleted until their steps no longer name it.
Writing the text
A template's text names the record's fields the way every text of a rule does: {{ title }}, a related record's fields, sub-records, {% if %} and filters, as Texts that name the record says. Insert a value, under each text, puts in what the record holds.
Preview fills the text in with a record of yours: as you see it, as an address (or a number) outside Qorekit gets it, or, for administrators, as someone else would see it. For an email, Send me a test sends it to your own address. Each reader gets the text filled in with what they may see; an address or a number outside Qorekit gets it as the rule's author (whoever last saved the rule, or last changed this template) sees the record. A table lists only records of entities whose rules the person changing the template manages.
Emails
Formatting. The body's editor has what rich text fields have, and tables, alignment, a few text colours and highlights besides. Emails go out in Qorekit's layout, with these styled inline, so mail programs show them alike.
Tables in an email
Add a table, under an email's text, lists records in the email: the record's sub-records, the records a relation of it holds, or the records that point at it (a customer's invoices). Choose the columns and their headings, conditions (only the invoices not yet paid), an order and how many rows at most (up to 50); number columns can get a row of totals, counted over every record found. The table goes where the cursor is, as {{ table('unpaid_invoices') }}; Insert puts it in again, and Edit changes it.
Each reader sees only the records and fields they may see, an address outside Qorekit what the rule's author sees. A table that finds nothing is left out, and one with more records than its rows says how many more there are, with the link to the record.
SMS
An SMS is plain text, sent through an SMS connection.
Its length. Under an SMS's text, Qorekit counts its characters and parts as written: text in the GSM alphabet fits 160 characters in one message and 153 in each part of a longer one (€, [ and a few others count twice); one character outside it, such as ş, ğ or an emoji, makes the whole message Unicode, 70 characters in one and 67 in each part. Services charge by the part. The values put in change the count: Preview shows the message filled in, with its real count. A filled-in SMS is cut at 1600 characters.
How many go out
Emails. Rules send at most 100 emails an hour over the whole site unless you set otherwise in Automation › Settings; your mail provider may allow fewer. An email step at the limit waits, and sends the rest as the limit allows: its run shows as waiting until then. A step sends to 200 people and addresses at most.
SMS. Rules send at most 50 SMS an hour over the whole site unless you set otherwise in Automation › Settings, failed tries included: a guard against a rule that sends more than meant, since services charge for each message. A step at the limit waits like an email step. A message the service refuses is noted in the run and the others go on; if none went out, the step fails and the run is tried again. A step sends to 200 numbers at most. Test messages from Connections are not counted, nor codes sent to accounts.
SMS from records. Each person sends at most 20 an hour beside records' phone numbers (see Text messages), unless you set otherwise in Automation › Settings.