Scheduling Messages

A scheduled message that never reached anyone usually stalled at one of three points: it never queued, it queued and waited, or it sent and got filtered. Each one looks identical from your inbox, so work down the list. The Message Is Sitting in t...

Pipeline generates scheduled messages once a day and then waits for you. Answers to the common questions about when messages queue, what they queue on, and why they don't leave on their own. Why didn't my scheduled message send by itself? Beca...

Between the rule you set and the message you send sits the queue: once a day, Pipeline reads your schedules and lines up one message for every transaction that matches. Introduction You wrote the rule weeks ago, and today the message exists. So...

A schedule is a trigger plus a recipient list, and where you set it decides what you get. Answers to the common questions about triggers, recipients, send times, and what a schedule can't do. Can I schedule a Message Template to send on a specifi...

Set a message to send itself later — on a date the transaction supplies, when a task gets checked off, or at a time you pick. Introduction The message you need to send is one you already know how to write. What you don't know yet is the date, b...

A queue is where a scheduled message waits, and Pipeline keeps two of them. Answers to the common questions about finding yours, who else can see it, and what you can change before a message goes. Where do I find my scheduled messages? Click t...

Scheduled messages wait in a queue where you can preview them, fix what's wrong, send them, or delete them before they reach anyone. Introduction A schedule comes due and Pipeline writes the message. Before it reaches a client, an agent, or the...

The messages that keep a deal moving are the same ones every time. Write each one once, tell Pipeline what to wait for, and it goes out on its own — to your agents, to your clients, or to the accountant who never had a Pipeline login. Introductio...