I automate ops workflows with Make.com, Zapier, carrier/portal scripts, and Retell help-desk agents - from Metropolitan-style multi-carrier quoting to form-to-CRM-to-phone chains that do not die on the first timeout.
Automation fails quietly: a Zap times out, a portal changes a button, a Retell call never writes the CRM note. I build the happy path and the failure path - retries, alerts, and a human handoff.
Heavy ops (insurance quoting, multi-portal 2FA) usually need Python workers and a real backend. Light ops (form → CRM → Retell → Slack) often stay on Make or Zapier with clean field maps.
Help-desk agents on Retell plus Make are a common package: missed-call recovery, after-hours intake, and campaign outbound without standing up LiveKit on day one.
Who it is for
- Agencies drowning in manual portal work
- Teams whose Zapier scenarios break weekly
- Offices that want Retell help-desk agents wired to the CRM
What you get
Mapped workflow
Triggers, systems, owners, and what happens when step three fails.
Make / Zapier or custom workers
No-code when it holds; Python/API workers when portals, 2FA, or volume demand it.
Voice + CRM loop
Retell or similar agents that create and update the same records your humans use.
How I work
Shadow the process
Watch one real job end to end - including the ugly exceptions.
Automate the spine
One production path with logs before clever branches.
Harden
Retries, alerts, and a weekly review of failed runs.
What this looked like on CarrierBridge + RenewalSync
Address intake, BrightData/Zillow property pre-fill, parallel Playwright fills across ~10 carrier portals, and real-time SSE progress for quoting — plus RenewalSync for Progressive/National General Dec pull, structured compare, and automatic EZLynx activity + PDF upload. Same discipline applies to lighter Make/Zapier stacks.
Proof
- CarrierBridge multi-carrier quote automation
- RenewalSync Progressive/NatGen Dec compare + EZLynx write-back
- Lehigh HVAC Retell + Make.com front desk and outbound
- Realtor Zapier form → GHL/eSimply → Retell speed-to-lead
Case studies
- Make/Zapier + Retell help desk
- CarrierBridge quote automation
- CarrierBridge address → quotes use case
- RenewalSync renewal automation
- HVAC Retell + Make
Stack and docs
Related
Common questions
Make, Zapier, or custom code?
Make/Zapier for CRM and SaaS glue. Custom Python when you hit portals, 2FA, volume, or logic no-code cannot express cleanly.
Can you fix our broken Zaps?
Yes - usually by simplifying the scenario, adding error paths, and documenting ownership so the next edit does not break production.
Do you set up Retell with Make?
Yes. Common package: inbound/outbound Retell agents, Make scenarios for CRM writes, Slack alerts, and after-hours routing.