Build Twilio Towing Call Flow
Budget: $250 – $750 USD
I want a lightweight yet reliable Twilio voice workflow that handles incoming roadside-assistance calls end-to-end. When a caller dials in, the IVR should prompt for their ZIP code, query an Airtable base that holds my driver roster, and instantly route the call to the primary driver listed for that ZIP. If the primary driver does not pick up, the system has to try the backup driver and, finally, a global fallback number before giving up. No voicemail collection or SMS follow-ups are needed—just the sequential dialing I described.
While the call is active I only need two fields captured in a simple log: Caller ID and total call duration. A Google Sheet, new Airtable table, or even a Twilio Sync document is fine as long as the data is easy for me to export later.
Here is how I picture the stack:
• Twilio Studio or a Serverless Function for the IVR and dialing logic
• Airtable API for ZIP-to-driver lookups
• Node.js helpers to keep everything tidy and easy to update
Deliverables
1. Deployable Twilio flow (Studio JSON or Serverless code) that I can import to my account
2. Airtable integration script with clear instructions on adding or modifying driver records
3. Minimal logging utility that writes Caller ID and duration for every attempt—success or fail
4. Quick read-me showing how to redeploy, edit drivers, and test the flow locally
Acceptance
I will call the number, enter a test ZIP, watch it cycle through the three numbers, and then verify that a log entry with the correct caller ID and duration appears. If that works, we are done.
While the call is active I only need two fields captured in a simple log: Caller ID and total call duration. A Google Sheet, new Airtable table, or even a Twilio Sync document is fine as long as the data is easy for me to export later.
Here is how I picture the stack:
• Twilio Studio or a Serverless Function for the IVR and dialing logic
• Airtable API for ZIP-to-driver lookups
• Node.js helpers to keep everything tidy and easy to update
Deliverables
1. Deployable Twilio flow (Studio JSON or Serverless code) that I can import to my account
2. Airtable integration script with clear instructions on adding or modifying driver records
3. Minimal logging utility that writes Caller ID and duration for every attempt—success or fail
4. Quick read-me showing how to redeploy, edit drivers, and test the flow locally
Acceptance
I will call the number, enter a test ZIP, watch it cycle through the three numbers, and then verify that a log entry with the correct caller ID and duration appears. If that works, we are done.