Loading
Two failures, both embarrassing. Sending to a list exported weeks ago, so it includes people who have since become customers or asked not to be contacted. And continuing a sequence after somebody replied, which tells them they were talking to a machine.
Both happen because the list and the relationship live in different systems, and only one of them knows what happened.
A segment is a live query — "companies over fifty staff in this sector with no open deal" — evaluated when it is read rather than exported. Enrolment comes from it, so somebody who becomes a customer leaves the audience automatically.
Consent state is checked at send rather than only at enrolment, and a detected reply stops the sequence immediately.
It will not write the sequence, and a bad sequence sent reliably is still a bad sequence.
And it does not source contacts. Whoever you enrol has to already be on your record with a lawful basis for contacting them, which is deliberately a decision rather than a feature.
Replies land on the account record rather than in one mailbox, so a colleague picking it up sees the whole thread. A positive reply becomes an owned lead routed by the same rules as any other.
And source tracking carries the campaign through to the closed deal, so outbound can be judged on revenue rather than on open rates.
Immediately, checked at send rather than at enrolment.
Live segments over your own records. It does not source or buy contacts.
Yes — source tracking carries the campaign through to the closed deal.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.