1
Canvas for Voice, SMS, and Email steps
Platform · Workflows
Orchestrate calls, texts, and email in one playbook
A visual journey where one trigger sets off Voice, SMS, and Email — with routing, delays, and your systems in the loop — from draft rules to live coverage.
AI
Draft assist built into the editor
Draft
To production when the shop is ready
24/7
Runs start the moment a trigger fires
Why Workflows replace duct-taped automations
One run, every channel
Calls, texts, and emails are steps in the same journey — sharing trigger data from start to finish.
Elyt · one desk
Webhook · new form
SMS · instant ack
Voice · enterprise path
Branching that mirrors the shop
Filters and switches route every run — business hours, ZIP, membership, or any rule you define.
Build with assist
Start from a description, then refine every step on the canvas — or drag the steps yourself.
ServiceTitanHousecall ProJobberGHL
Timing built in
Delays, warm-up waits, and business-hours windows — every touch lands when it should.
✓ZIP verified
✓Window offered
✓Confirmation queued
Draft to production, safely
Test in draft, watch a live run, push when it is right — with every run kept in history.
RulesAuditWarm transferQuiet hours
Shop playbook · human takeover ready
Inside the platform
From webhook to won lead, in one build
A form fires, the lead gets an instant text, business hours decide the path, a hot lead gets a Voice callback while a softer lead enters a warm drip. Everything a shop sells — response, routing, follow-through — assembled visually.
app.elyt.agents
Workflows /Speed-to-leadDraft
Auto layout ▾
Webhook
StartTrigger
Listens on: Dedicated URL
+
In business hours?
Condition
{{inTimeWindow("America/Phoenix")}}
SMS speed-to-lead
Message
To: {{lead.phone}}
Msg: Thanks for reaching Desert Air — reply 1 to book a window.
Update CRM
Action
Stage → Contacted · owner: front desk
Workflow canvas · demo layout · draft and production stay separate
From trigger to outcome, every run
01
A trigger starts the run
A webhook fires — form fill, new lead, any event your systems can send — and the run starts with that event’s real data.
EL
Webhook — start
nameJordan P.
phone(480) 555-0142
sourceWebsite form
Run started with live event data
02
Rules shape the path
Variables are set, then filters and switches route the run — hours, ZIP, membership, budget.
EL
Routing
Business hours?Yes
ZIP in area?Yes
PathVoice callback
Shop rules, not guesswork
03
AI acts across channels
Instant texts, Voice calls, emails, and timed delays run as sequenced steps with shared context.
EL
During the run
SMS · instant acknowledgment
Voice · speed-to-lead call
Email · nurture if needed
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.
EL
Draft → production
Draft saved
Watchlive run verified
Pushed to production
Every run logged in history
Quality
Respond, route, follow through
Sequences that never drop a home-service lead.
Instant acknowledgment texts on new inquiries
Speed-to-lead Voice calls minutes after a form fill
After-hours branches that keep the lead warm
Filters that gate a run on any shop rule
Switch branches for membership, ZIP, or ticket size
Nurture drips across email and SMS with timed delays
Key capabilities
Respond
Answer the moment a lead appears.
- Instant acknowledgment texts
- Speed-to-lead Voice callbacks
- After-hours branches that stay warm
- Business-hours aware responses
Route
Every conversation to the right path.
- Filters on any rule you define
- Switch branches — membership, ZIP, ticket size
- 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
- Dormant list reactivation
- Estimate and collections follow-ups
- Timed delays and warm-up waits
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. Outcomes write back through the same integrations as every Platform channel.
During the run
Lead enriched — variables set from the event
Acknowledgment SMS sent in seconds
Voice call placed on the hot path
Outcome written back to your CRM
Triggers
WebhooksFormsCRM eventsCalendar
Desk tools
ServiceTitanHousecall ProJobberGoHighLevelStripe
Writes into
CRMCalendarsPayment systemsInternal notes
Multi-channel
Automation you can audit
Draft and production stay separate. Every step of every run is logged so owners can see what happened — and why.
One thread
- 01 · TriggerForm fill · variables loaded
- 02 · BranchBusiness hours · Voice path
- 03 · OutcomeBooked · CRM updated · logged
Built for multi-trade home services
- Quiet hours and opt-out support on outbound steps
- Full run history — every step logged
- Draft and production kept separate
- Pairs with AI Workforce seats as you grow
- One front door for Voice, Messaging, and Email
Frequently asked questions
A trigger — typically a webhook from a form fill, CRM event, or other system signal. The run starts with that event’s real data, available to every step.
Ready to orchestrate every conversation from one playbook?
Book an assessment. We map your triggers, channels, and booking rules into production Workflows for the shop.
A working session with the team that builds the shop playbook — not a scripted demo.