SquidSupport
Product reference / Outbound

Outbound

In the app: Outbound

Needs the 'View Outbound Templates' permission.

Outbound sends an email to a customer before they write to you, built from a template and filled with the customer's Shopify order data. You can send one email, or upload a file and send up to 200 at once. Every email waits five minutes before it leaves, so it can still be cancelled.

Access and tabs

Opening Outbound needs two permissions together: 'View Outbound Templates' and 'Create Conversations'. With only one of them the page shows which one is missing.

The page has three tabs:

  • "Send": choose a template and send one email or a batch.
  • "Pending": emails that are scheduled and have not left yet.
  • "History": every outbound email of the organization.

"Pending" and "History" show the whole organization's emails to everyone who can open the page, also to a teammate whose access is limited to certain stores. Sending is narrower for such a teammate: a single email can only be sent for a store they have access to, and looking up, sending and cancelling a batch is refused, because a file can name any store.

Templates are written under Settings → Outbound: their languages, text, variables, required columns, sender address per store, spreadsheet lookups and tags. That page explains them; this page only uses them. "Manage Templates" opens it for people with the 'Edit Outbound Templates' permission.

Template Selection

  • "Store": the store the email is sent for. It decides the sending address and the Shopify store the order is looked up in. When the template has its own subject, text or variable values for that store, those are used instead of the general ones. Shown for a single send only; in a batch each row names its own store.
  • "From": the address the email is sent from. A store with one sending address shows it as text. A store with several lets you choose: the address the template names for that store is selected to start with, otherwise the store's primary address, which is marked "(store default)". Choosing another store or template sets it back to that starting choice. A store without a verified sending address shows no "From", and a send for it fails.
  • "Template": the template to send. Only active templates are offered. When there are none, the page says "No templates yet." with "Create one →" for people who can edit templates; everyone else is told to ask an administrator, by name when Squid knows one. If the list could not be loaded, the page says "Couldn't load the templates." with "Try again".
  • "Language": the language version of the template to send, one button per language the template has. The template's default language is selected to start with. When you choose another template, the selected language stays if that template also has it; otherwise its default is selected. Shown for a single send only; in a batch each row gets the primary language of its store when the template has that language, and the template's default language otherwise.
  • "Send Mode": "Single" for one email, "Bulk" for a file of orders. The page opens on "Single".

Order Information

For a single send, fill in who the email goes to.

  • "Order Number" and "Lookup": type the order number and click "Lookup", press Enter or leave the field. Squid searches the store's Shopify for the order and fills in the recipient and these values: the order's number, fulfilment status, total and date; the customer's name, first name and email address; the carrier, tracking number and tracking link of the order's latest shipment; and the store's name and website. When Shopify returns more than one order for what you typed, the first one is used. With a template and a language chosen, the lookup also shows the preview. You need a store and an order number first; the button says so otherwise. The order number is optional: an email can be sent without one, with the recipient typed in.
  • "Recipient Email" and "Recipient Name": filled in by the lookup, and editable. A lookup replaces what was in them, also with nothing when the order has no email address. The email goes to the address that is in "Recipient Email" when you send, and that field is required.
  • "Manual Variable Overrides": opens one field for each of the thirteen standard variables (customer, order, tracking and store values), whether the template uses them or not. The lookup fills in what it can. What is in these fields when you send, looked up or typed, wins for this one email, also over the values the template has for the store. An empty website field still falls back to the store’s website when Squid can work it out. A new lookup replaces everything in these fields, including what you typed.

Values that a template takes from its spreadsheet lookup have no field here and are not filled in for a single send, because there is no file row to match. A value saved for the template and store can still fill them in; the spreadsheet itself is only looked up for a batch.

What the lookup can answer:

  • The order is found and has an email address: the fields are filled in.
  • The order is found without an email address: you type the recipient.
  • The store is not connected to Shopify, or Shopify gives nothing back: only the store's name and, when Squid can work it out, its website are filled in, and you type the rest yourself.
  • The order is not found: the page says so, and the values of an earlier lookup are removed.

Choosing another store drops the previous lookup, because an order in one store says nothing about another; a recipient you typed yourself stays. After you change the order number, leaving the field looks the new number up. If it has not been looked up yet when you click "Send Email", Squid looks it up first and sends to that order's email address when it has one; if that lookup fails, nothing is sent.

Preview & Send

"Preview" shows the email's "Subject:" and text with the variables filled in, and above them the "From:" address when the store has a sending address. It needs a store, a template and a language. A lookup refreshes the preview by itself; after typing in "Manual Variable Overrides", click "Preview" to see the change. Any variable that still has no value is listed under "Unresolved variables:". The store's email signature is added when the email is made and is not in the preview.

"Send Email" schedules the email. It needs a store, a template, a language and a recipient email address; the button names what is missing.

Before it sends, Squid builds the email once more and checks it. If variables are still empty, it stops and shows "Some variables have no value". The customer would see the name of each such variable in square brackets, for example [order.number]. "Go back" returns to the form so you can fill them in under "Manual Variable Overrides"; "Send anyway" sends the email as it is.

After sending, the page confirms that the email is scheduled, names the address it is sent from and says it sends in 5 minutes, with "View Pending". Until then it can be cancelled on the "Pending" tab. The order number, the recipient, the variables and the preview are emptied for the next email; the store, the template and the language stay.

Upload CSV

In "Bulk" mode you upload a CSV file with one row per email.

  • "Required columns:" lists the columns the file must have for the chosen template. Two are always required: "shopify_store_code", which decides which store a row belongs to, and "order_number". A template can require more columns; those are set on the template. Capital letters in a column name make no difference.
  • Extra columns are fine. They are kept with the row and are only used where the template's spreadsheet lookup or spreadsheet actions refer to them.
  • The store code is the store's Shopify address, written with or without ".myshopify.com". A row is matched to the store that is connected to that Shopify address.
  • "Optional column:" "sender_email" sends that row from the address in it. The address must be one of the store's verified sending addresses; a row with another address gets an error when the rows are looked up and is not sent.
  • No email column is needed: the recipient of each row comes from the order in Shopify. An email column in the file is not used as the recipient.

Limits: the file must be a .csv file, must have at least one data row, and can have at most 200 rows. A file that misses a required column is refused, and the message names the missing columns. This check is made when you choose the file, against the template selected at that moment. A row in which the store code or the order number is empty gets an error when the rows are looked up. Choosing a new file replaces the previous one and removes its lookup results.

Look up rows and send a batch

"Look Up All Rows" needs a template and an uploaded file; the button says which is missing. For every row Squid finds the store, picks the language, looks the order up in Shopify, takes the recipient from the order and runs the template's spreadsheet lookup. The "Preview" table then shows one line per row with "Order", "Store", "Email", "From", "Lang" and "Status": "Ready", or the reason the row cannot be sent. The reasons are:

  • the store code or the order number is empty;
  • no store that is connected to Shopify matches the store code;
  • the template has no version in the store's language and none in its default language;
  • the sender address in the row is not a verified sending address of the store;
  • the order was not found, or it has no customer email address in Shopify;
  • the text uses values from the template's spreadsheet lookup and no row of that spreadsheet matches;
  • the lookup failed for another reason.

Above the table: how many rows resolved, and, when there are any, how many have errors and how many you removed.

"Ready" means the lookup succeeded. The checks for a repeat, an out-of-stock email and an address that refused mail, described under "What a send does", are made later, when the batch is sent.

  • The bin on a ready row removes it from the batch. Rows with an error have no bin; they are never sent. Looking the rows up again brings removed rows back.
  • "Clear" removes the lookup results and the table. The uploaded file stays, so you can look the rows up again.
  • "From": when a store among the ready rows has more than one sending address, choose the address that store's rows are sent from. The address the template names for the store is selected to start with, otherwise the store's primary address. A row's own sender column overrides this choice.

"Send N Emails (5-min delay)" schedules every ready row that you did not remove; N is their number. Rows with errors are left out. The button is disabled, and says why, when no row is ready.

The batch is sent by the server, not by your browser. The button shows "Sending" with how many rows are done, and a progress line shows how many are sent and how many failed. You can leave the page while it runs; the emails then show up on the "Pending" tab. Each email goes to the address the lookup found, and the order's details are read from Shopify again when the email is made.

A batch has no check for empty variables: a variable without a value reaches the customer as its name in square brackets.

All emails of one batch share a scheduled time, normally five minutes after you started the batch. If the background job starts after that time has passed, it sets a new time five minutes ahead. Delivery can happen later than the scheduled time. A row that is made late in a long batch therefore has less than five minutes left in which it can be cancelled.

When the batch is done, the page says how many emails are scheduled and drops the upload. If every row succeeded, it offers "View Pending". If rows failed, it says how many and gives the reason of the first one only. A failed row gets no ticket and does not appear in History.

What a send does

For every email, Squid:

  • finds the customer by email address, or creates them;
  • creates an email ticket for the store, already closed, with the email's subject as its subject and the email as its first message. In the Inbox thread the message is marked "Templated outbound";
  • sends the email five minutes later from the chosen address;
  • once the email is sent successfully, adds the template's tags to the ticket. For an email from a batch it also runs the template's spreadsheet actions; a single send has no file row and runs none.

Because the ticket is closed, it does not show up in the open views of the Inbox. When the customer answers the email, the ticket reopens and is handled like any other.

Squid refuses a send in these cases:

  • A repeat. The same template for the same order of the same store is refused when an earlier one was scheduled or sent in the last 60 minutes, to catch a double click or a file uploaded twice. The message says how long ago that was and when it can be sent again. An earlier email that was cancelled or that failed does not block a new one. Batch rows with different content for one order, such as one row per item, are each sent. An email without an order number is not checked for repeats.
  • Out-of-stock emails. A template that uses the out-of-stock sheet is not sent again to an order whose out-of-stock case is already settled, in progress or emailed. The message names the order and the ticket.
  • An address that refused mail before. An address whose mail server permanently rejected an email from your organization in the last 180 days is not sent to. The message names the address.

In a single send the refusal is shown as an error and nothing is created: no customer, no ticket. In a batch the row is skipped and counted as failed; the closing message gives the number of failed rows and the reason of the first one only.

A sent email cannot be recalled. Sending needs the 'Create Conversations' permission.

Pending

"Pending" lists the organization’s emails whose scheduled time is still ahead, from all teammates. An overdue email waiting for delivery is no longer listed here; check "History" for its status. The list refreshes every 30 seconds while you look at it, and the time left counts down every second.

Each line shows the template, the recipient, the order and "Sends in" with the time left. Emails of one batch are grouped under "Batch · N emails".

  • "Cancel" stops one email. It is not sent, and the send is kept in History as cancelled. The closed ticket that Squid made for the email when it was scheduled is not removed: it stays in the Inbox among the closed conversations, with the email's text in it. Nothing in that conversation says the email was cancelled; only the History tab here does. Check History before you assume a customer received an outbound email.
  • "Cancel Batch" stops every email of that batch that has not left yet, and says how many were cancelled. Their closed tickets stay in the Inbox in the same way.

Cancelling only works before the five minutes are over; after that Squid refuses it. An email that has already left cannot be stopped. Cancelling needs the 'Create Conversations' permission. A teammate whose access is limited to certain stores can cancel a single email of one of their stores, and cannot use "Cancel Batch". "No pending sends" means no email is listed inside its cancellation window; an overdue email can still be waiting for delivery.

History

"History" lists the organization's outbound emails, newest first, 25 per page with "Previous" and "Next".

The columns: the template, the recipient, the order number, the language, the status and "Sent At" in your own timezone. "Sent At" stays "-" until the email has been sent. The status is one of:

  • pending: scheduled and not yet recorded as sent, failed or cancelled, possibly past its scheduled time;
  • sent: handed over for delivery;
  • failed: the email could not be sent;
  • cancelled: stopped from the Pending tab.

Clicking a line opens the ticket of that email in the Inbox. "No send history" means nothing has been sent from Outbound yet.