001 Pronto Automations · Workflow Engine
Onboarding, reminders, review requests and the three-to-nine-month follow-up a three-person shop never runs by hand. Every sequence fires on a milestone, not on a date — and every trigger tells you what it costs to run.
✓Six standard triggers · $0.00 per execution · premium ones are labeled
002 The instrument
Every row is a real chain: a trigger, the branches it takes, and what it costs each time it runs. Pick one — or let it run through them.
Nothing here is a mockup of someone else's product — these are the chains Pronto runs, with the cost of each execution shown as it is built.
003 The rule
This is the whole difference between a sequence and an autoresponder. The same message, sent for a different reason, stops being noise and starts being useful.
Sent to someone who never forwarded their number. Nothing is going. It is noise.
Sent because a specific thing has not happened yet. That is the message that moves the account.
A tag added, an opportunity that changed stage, an appointment that got confirmed, a contact that was created. The sequence reads the state of the job, not the page of a calendar.
The moment the customer does the thing, the chase ends. Nobody gets a reminder for something they already did — that is the fastest way to make a contractor mute you.
If a contractor has not activated in 72 hours, they are not going to convert. Chasing them for 30 days wastes your time and burns your brand.
A weekly report that says “47 calls answered” is a statistic. One that says “3 appointments booked × your $5,442 average ticket = $16,326 in work captured” is a decision.
004 The sequence that already runs
This is the onboarding sequence, not a template. The bottleneck is never the software — it is a phone company and a form. The workflow exists so five minutes of success are not buried under three days of paperwork.
The two orange marks are human on purpose: the six-hour activation call and the day-21 call. A workflow can carry everything up to them and everything after them — it should not pretend to be them.
005 The three workflows
Three chains that call each other: the call gets logged, the pro gets asked, and the decision gets applied. Silence is never an allowed outcome.
An inbound call on the dedicated number tags the contact, writes the decision field as Pending, and opens the opportunity at Call received. Before anyone has typed anything, the job exists.
If an appointment was booked, the opportunity moves to Tentative at the high end of the quote — the pipeline should reflect the potential, not the floor — and the pro gets one message with two links.
Accept and the job is theirs. Fifteen minutes of silence and it is an automatic decline: the appointment is cancelled, the opportunity moves to Lost, and the customer hears about it from us, not from nobody.
The wait is a plain fifteen-minute delay with no advance window. In a fifteen-minute flow, a window that pushes the wait to another hour breaks everything.
One message. Everything needed to say yes or no, and a clock that answers for them if they say nothing.
A declined job is not a dead end and it is never a silence. The customer is told, the tentative hold is released, and they are handed somewhere else to go.
That contact is a real customer with a real need that one member turned down. It is worth more offered to another contractor than deleted.
006 The structural limit
It cannot walk a filtered list of other people and alert them. So “we notify every qualified pro and the first to accept takes it” is not something a workflow does — and we would rather show you the line than blur it.
Ranked by rating, acceptance rate, distance and seniority. Five candidates, in order, with a call in the middle and a human at the end.
Zero rows returned means somebody else took it. That is the whole race condition, handled at the only layer where it can be handled.
The contractors in the local directory came from public listings. They never signed up and never agreed to receive jobs. Texting them in bulk is cold outreach — which in the United States needs A2P 10DLC registration, and even with it, a mass send to numbers that never opted in gets the number blocked by the carriers within days.
Phase 1 — the part that does run on workflows — works today, and it is already genuinely useful.
007 Re-engagement
Lead flow and build flow are offset by one to two quarters. A remodeler who lets fall leads go cold has an empty April — and a three-person shop is never going to run a nine-month follow-up by hand.
In your April trial, Pronto answered 12 calls you were about to lose. It's July. Shall we turn it back on?
It works because the account never died. A trial that ends in a step down instead of a wall keeps the contacts, the calendar, the profile and the reviews — which turns the 84–92% who did not buy into a nurture list with real data on it.
June 1: the season starts. January 1: the cold is coming. Within 24 hours of a hailstorm: the roofers. Every month: how many times their profile came up in the directory.
A sequence that knows the year the house was built and the amperage of the service knows which rung to offer next: the EV charger is the wedge, the panel upgrade is the revenue, and the generator is the year.
008 What a trigger costs
Nobody tells you this part, and it is exactly what you need to know before you build anything. Standard triggers and actions are free to run. Premium ones bill a cent each time — forever, quietly, on every account you provision.
All standard. All free to run, whatever the volume. Every sequence on this page starts with one of them — that is not a coincidence, it is the design.
Premium triggers and actions — the Inbound Webhook first among them. A hundred free executions per account, and then a cent apiece. One workflow you forgot to delete keeps charging on every account you spin up.
This is the kind of thing a vendor keeps quiet. We would rather you build the cheap version: your backend creates or updates the contact through the API and adds a tag, and the sequence starts on the free trigger. Same behaviour, no cost per run.
After hours
The weeks that make the year's margin are exactly the weeks nobody picks up the phone.
009 The guards
Each one exists because of a specific way an automation fails in the field. None of them is theoretical.
010 Where it stops
A workflow that automates everything is not more powerful. It is one legal exposure away from costing its owner more than it ever made them.
North Carolina S.L. 2024-11 has been in force since 1 October 2024. It applies to roofing work tied to an insurance claim, and it does not care that the request for payment was sent by a machine.
So the engine refuses. Chain a payment request behind a denied claim and it will not build the branch: it shows you the statute, the date it took effect and the window you are inside of. Being told “Pronto will not let you request payment inside the statutory window” is a selling point to a roofer who has been burned once.
Calling hours run 8:00 to 21:00 in the recipient's local time under the TCPA; the voice engine holds itself to 8:00–20:00, which is stricter. An AI voice counts as an artificial voice under the FCC's February 2024 ruling, marketing calls to mobiles need prior express written consent, and the exposure runs $500–$1,500 per call. Do-not-contact propagates across voice, SMS, email and messaging — not only the channel it was asked on.
012 Plans
This is the page that explains the jump from $249 to $499. Onboarding, reminders and review requests already use up three. The fourth — seasonal re-engagement, the one that fills April — needs Pipeline, and Pipeline is where the sequences learn to place the call themselves.
Build your digital presence.
Your AI employee for everyday conversations.
Turn conversations into more work.
Full power for growing businesses.
Setup is $0. Workflows built on standard triggers and actions carry no variable cost. Voice minutes now come inside the plan — 300 with Answer, 1,000 with Pipeline, 2,500 with Engine — and anything beyond runs $0.15, $0.12 and $0.10 a minute. What still bills separately is SMS, messaging and bulk email — plus a cent per execution for any premium node you deliberately add. Pay yearly on a monthly plan and two months are included; Pronto Presence is $1 once, includes no voice minutes, and never renews. Pronto never takes a commission on your jobs.
013 Questions
014 Pronto Automations · Workflow Engine
Bring us the sequence you already know you should be running and are not. We will show you the trigger it starts on, the guards it needs, and what each run costs.
