Skip to content

Trillet Workflows

Orchestrate calls, texts and email in one workflow

A visual canvas where a single trigger sets off AI calls, SMS and email — with routing, delays and your systems in the loop, from draft to production.

1

canvas for AI calls, SMS and email steps

AI

Build with AI — drafting built into the editor

Draft

to production in one click, with watch runs in between

24/7

runs start the moment a trigger fires

Why teams choose Trillet Workflows

One run, every channel

Calls, texts and emails aren’t separate automations — they’re steps in the same workflow, sharing the same trigger data and variables from start to finish.

Branching that mirrors your operations

Filters and switches route every run — business hours, lead budget, or any rule you define.

Build with AI

Start from a description with Build with AI, then refine every step on the canvas — or drag the steps in yourself.

Timing built in

Delays, warm-up waits and business-hours windows — every touch lands at the moment it should.

Draft to production, safely

Test in draft, watch live runs as they happen, and push to production when it’s right — with every run kept in history.

Inside the platform

From webhook to won lead, in one build

This canvas is a complete speed-to-lead play: a webhook fires, the lead gets an instant text, business hours decide the path, an enterprise lead gets an AI call while an SMB lead enters a warm-up drip. Everything an agency sells — response, routing, follow-through — assembled visually and pushed to production.

Trillet workflow editor — a speed-to-lead workflow with a webhook trigger, lead enrichment, instant acknowledgment SMS, business-hours filter, Enterprise/SMB switch, AI call step, warm-up delay and nurture email, with Build with AI and Push to production controls
Workflow editor · demo content · the platform is constantly evolving — the live interface may vary slightly

From trigger to outcome, every run

01

A trigger starts the run

A webhook fires — a form fill, a new lead, any event your systems can send — and the run starts with that event’s real data.

Webhook — start

Listens on a dedicated URL

trigger.nameJordan P.
trigger.phone+1 (415) 555-01…
trigger.sourceWebsite form

Run started with live event data

02

Rules shape the path

Variables are set, then filters and switches route the run — business hours, lead budget, any rule you define.

Filter — business hours?

Yes — continue

No — after-hours email

Switch — lead budget

Enterprise
SMB
Otherwise

03

AI acts across channels

Instant texts, AI calls, emails and timed delays run as sequenced steps — each carrying the full context of the run.

During the run

SMS — instant acknowledgment
AI call — enterprise lead
Email — nurture drip

Sequenced steps, one shared context

04

Shipped and audited

Draft the change, watch a live run, then push to production. Every run is logged step-by-step in history.

Draft → production

Draft saved
Watch — live run verified
Pushed to production

Every run logged in history

Key capabilities

Respond

Answer the moment a lead appears.

  • Instant acknowledgment texts on new inquiries

  • Speed-to-lead AI calls, minutes after a form fill

  • After-hours branches that keep the lead warm

  • Business-hours aware responses

Route

Every conversation to the right path.

  • Filters that gate a run on any rule

  • Switch branches — Enterprise, SMB, or your own segments

  • Business-hours and after-hours routing

  • Escalation to your team with full context

Follow through

Sequences that never drop a lead.

  • Nurture drips across email and SMS

  • Appointment reminders that cut no-shows

  • Database reactivation for dormant lists

  • Payment and collections follow-ups

  • Timed delays and warm-up waits

Triggers & systems

Triggered by your stack, acting on your stack

Every workflow starts from a webhook — any system that can send an event can start a run, with the event’s data available to every step as variables.

Outcomes are written back into your live tools through the same integrations as every Trillet channel. No parallel systems. No double entry.

During a run

Lead enriched — variables set from the event

Acknowledgment SMS sent in seconds

AI call placed on the enterprise branch

Outcome written back to your CRM

CRM & scheduling integrations

GoHighLevelZoho CRMSalesforceGoogle CalendarCal.comStripe+ more

Actions written into

CRMCalendarsPayment systemsInternal systems+ more

Compliance & control

Automation you can audit

  • HIPAA, GDPR and ACMA compliant, with TCPA and DNC support on outbound calling steps.

  • Full audit logs and role-based access.

  • Complete run history — every step of every run, logged.

  • Draft and production kept separate — changes ship only when you push them.

HIPAASOC 2 Type IIISO 27001

Frequently asked questions

  • A trigger — every workflow begins with a webhook that any of your systems can call: a website form fill, a new lead in your CRM, or any other event. The run starts with that event’s real data, available to every step as variables, and filters decide whether and where the run continues.

  • AI calls, SMS and email run as sequenced steps on the same canvas, alongside timed delays, filters and switch branches. Because they belong to one run, every step shares the same trigger data and context — the AI call on the enterprise branch knows exactly what the acknowledgment text said.

  • Runs are triggered by webhooks from your systems, and outcomes are written back through the same integrations as every Trillet channel — GoHighLevel, Zoho CRM, Salesforce, Google Calendar, Cal.com and Stripe among them. Additional systems are connected through your system’s API during onboarding.

  • Workflows are built and edited in draft, so nothing changes in production while you work. You can watch runs live as they execute, review the complete step-by-step run history, and push to production only when the build is right.

Ready to orchestrate every conversation from one canvas?

Speak to sales to see how Trillet Workflows connects your triggers, channels and systems into production automations.

A working session with the team that builds the platform — not a scripted demo.