Projects

Content

Creations

The workflow contains two parallel pipelines:

• Pipeline 1 (Lead In → Call Out): Webhook → normalize data → route by industry → build Retell payload → place call → log to Sheets → respond 200

• Pipeline 2 (Call Done → Act): Retell callback → route by call status → fetch transcript → Claude classifies HOT/WARM/COLD → update Sheets → Slack alert. If no answer, a 5-minute wait fires a Twilio SMS instead

Two independent pipelines in one workflow:

Pipeline 1 — Outreach Sequencer (runs daily 9 AM): Reads all contacts → cross-references two suppression checks (DNC sheet + contact-level flags) simultaneously → scores and sorts by segment priority and recency → enforces the daily send cap by reading a rolling counter in Sheets. For each eligible contact it builds a Claude prompt with segment, industry, days-since, and specific offer context → generates a unique email → sends via SendGrid → logs → waits exactly 48 hours in-execution → re-reads the contact row to see if they replied → sends Twilio SMS if still silent → waits 5 more days → sends one final SMS → closes the sequence. The Wait nodes persist execution state, so restarts or crashes don't duplicate sends.

Pipeline 2 — Reply Handler (/webhook/reactivation-reply): A single webhook handles both email (SendGrid Inbound Parse) and SMS (Twilio reply webhook) by detecting which format the payload is in. Claude classifies intent into 5 buckets. Interested contacts get tagged warm_lead, appended to a dedicated Warm Leads sheet, and trigger an immediate Slack alert with the reply text and Claude's suggested response. Unsubscribes auto-write to DNC and update the contact row in one shot — they will never be contacted again.

Three independent pipelines that run in parallel:

Pipeline 1 — Inbound Call Handler (/webhook/inbound-call): Twilio posts caller data here. n8n builds a TwiML response with a <Dial><Sip> tag pointing to Retell's SIP endpoint for the right industry agent, returns XML to Twilio in under 200ms, and logs the call to Sheets.

Pipeline 2 — Real-time Function Handler (/webhook/retell-function): The heart of the system. When the AI agent needs to do something mid-conversation — check availability, book, send an SMS, transfer, or detect spam — Retell posts here. A Switch node routes to 6 different handlers and returns structured JSON. Retell resumes the conversation with the result. This has to respond within ~2 seconds or Retell times out, so there's no heavy processing here.

Pipeline 3 — Post-Call Processor (/webhook/retell-callback): Fires when any call ends. Claude reads the full transcript and returns structured analysis (intent, outcome, urgency, action items), which gets written to Google Sheets and posted to Slack. Emergency and follow-up calls go to a separate urgent channel.

An E-Mail Agent

use to classify, summarise and reply to mails

Resume Screening System

WhatsApp Voice(chatbot)

This replies to both text and voice messages

1.

2.

3.

4.

5.

1.

2.

3.

4.

5.

6.

Feedback

What clients say about automindia's work

Outstanding Landing Page & Professional Experience I had my website landing page built for my recovery coaching business, and I couldn’t be happier with the result. The entire page looks extremely professional, clean, and well-structured. Everything flows perfectly, I would highly recom

bfogeltanz

USA

Grâce à son chatbot, notre service client fonctionne plus facilement que jamais, ce qui nous permet de consacrer plus de temps à la croissance et à la stratégie.

Tom S.

Paris

★★★★★

★★★★★

Get in Touch

Ready to automate your business? Let's connect.