Email History

Receipts are meant to be reassuring, so an unexpected one is unsettling — especially a "Document upload failed" that names a file nobody recognises. Each of these has a plain cause. The Same Failure Notice Keeps Arriving One receipt equals one ...

The acknowledgement is a personal setting that reports what each submission did with your docs. Answers to the common questions about turning it on for a team, receipts that don't arrive, and messages that cover more than one transaction. Can I t...

Ask Pipeline to write back every time you email docs in, and you'll know what uploaded and what didn't without going to look. Introduction Email a doc to your maildrop address and it's gone for a moment. It's in a mail queue you can't see, on i...

Texts are part of the deal and they live on somebody's phone. Send the thread to the transaction's maildrop address and it lands on the file with everything else. Introduction The conversation that actually moved a deal is often a text. In some...

Half the story of a deal is in your inbox and none of it is on the file. Forward it to the transaction's own address and the whole conversation lands where the rest of the record already lives. Introduction Documents are the easy part — they we...

Pipeline doesn't tell you a reply came back. One saved search does — and it takes about a minute to set up. Introduction You email the lender from a transaction, and then you wait. There's no alert when they answer, no read receipt, no badge th...

Forward mail into a transaction and Pipeline keeps it there, visible to admins and to the person whose maildrop address took it in. Answers to the common questions about attachments, senders, visibility, and deleting an email. Can an agent see an...

Forward an email into a transaction and it stays there — the subject, the message, and a record of what came attached. Introduction The paperwork on a deal arrives in somebody's inbox. The lender's reply, the signed addendum, the title company ...