LeadLeak | Automations

Workflow library

Start from a governed, reusable follow-up pattern.

Templates are industry-neutral starting points. They are not published workflows, and enrollment counts remain unavailable until LeadLeak has an approved execution-history contract.

Templates only

Workflow	Category	Trigger	Readiness	Total enrolled	Active	Action

Enrollment and execution statistics are unavailable because no workflow-enrollment record is implemented.

New-lead acquisition

Prepare an immediate text and email as one governed kickoff.

Each channel is evaluated independently for consent, suppression, sender identity, approval, and delivery eligibility. Saving this recipe sends nothing.

Draft only

Recipe nameWhen an approved new lead is created, prepare both channel steps with a zero-minute target delay.

Text messageSMS requires recorded, purpose-specific text consent and an unsuppressed destination.Email subjectEmail messageEmail purpose, lawful basis, footer, and unsubscribe treatment require client and compliance approval before activation.

Require recorded SMS consent for this purpose Require an approved email basis for this purpose Require human approval before first execution Respect channel-specific hours and sender timezone Deduplicate the lead and make both steps idempotent Apply suppression separately to SMS and email Provider delivery remains disabled

Draft configuration only. No SMS or email will be sent.

Conversation appointment booking

Move from “yes” to a confirmed calendar event inside the conversation.

The future runtime will offer live availability, hold a selected slot, confirm timezone and attendee identity, write the event, and return the confirmation to the same conversation. This draft does not read or write a calendar.

Contract draft

Contract configuration only. No availability was read, no slot was held, and no appointment was created.

No-reply rule

Build the next action before the current email sends.

Draft rule

Rules can be configured; sending remains disabled.

Conversation handoff

Offer a quick call or continue by text.

Save a consent-aware routing recipe without sending an SMS or connecting a provider.

Draft only

Recipe nameWhen an approved new lead needs a human follow-up, prepare one channel-choice message.

Message templateSender and business identity plus STOP instructions are required. Template tokens are examples until messaging contracts are approved.

Call repliescreate a call task.Text repliesopen the text-conversation queue.

Require recorded SMS follow-up consent Require human approval before the first message Respect business hours and sender timezone STOP, UNSUBSCRIBE, CANCEL, END, and QUIT suppress SMS Unknown or ambiguous replies require human review Provider delivery remains disabled

Draft configuration only. No SMS provider, conversation delivery, or call task is activated.

Automation library

Active and draft rules

0 active

No automations configured.

Start with a transparent no-reply rule, then add client lifecycle and renewal routines.

Pipeline stage rules

A real stage change can create an internal follow-up or prepare an encrypted email draft. Sending, calling, calendar writes and publication remain disabled.

Current manager permission is required. No default rules are active.

Action history has not loaded.