We use cookies to understand how the site is used and improve it. See our Cookie Policy.
Here's how Trailfire's rules engine turns events into action without you lifting a finger.
Anything that happens in Trailfire — a job marked complete, a review left, a referral booked, a customer hitting a date milestone — kicks off the engine.
Every rule has filters: trade, service value, review score, zip code, time of day, customer age. Only rules whose conditions actually match the event are eligible to run.
Actions are the work: send a review request, queue a neighborhood postcard, send a drip email, nudge for a referral, tag a customer for win-back later. One event can fire several actions at once.
Even when multiple rules try to fire, Trailfire enforces sensible caps — no double-texting, no two postcards in the same week, no review request to a customer who just left one.
Every rule has a switch and a test mode. Pause a rule for a week, change a threshold, or dry-run it against historical jobs to see exactly what it would have triggered before flipping it on.
Our support team typically responds within one business day.