Skip to content

Daily

Text quiet leads a follow-up and nudge sales in Slack

Leads who haven't replied in a few days get a short, friendly follow-up text, and sales gets a Slack summary of who was nudged.

Runs
Daily
Apps
Slack, Twilio
AI
Yes, uses the built-in AI allowance
Access
Twilio send/read; chat:write

Send this to your assistant

Create a ClickRuntime automation: every morning, find leads we texted more than 3 days ago who haven't replied, send each a short personal follow-up text, and post a summary to #sales.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Most leads don't reply to the first message, and most sales teams never send a second. Following up is the single easiest way to win more deals, and the step most often skipped.

Checking for quiet leads every morning and sending a short, personal follow-up keeps conversations alive, while the Slack summary tells the team which leads were nudged and might reply today.

What you get out of it

  • No lead left hanging

    Every quiet lead gets a follow-up.

  • Personal, not robotic

    AI writes each text around what the lead originally asked.

  • The team knows who was nudged

    A daily Slack summary shows who might reply.

  • Replies spotted

    Leads who already replied are never followed up.

How it works

What happens, step by step

  1. Every morning it checks the leads it has texted before.

  2. Leads who were texted more than three days ago are checked for any reply to your Twilio number.

  3. Those who haven't replied get a short follow-up text written by AI.

  4. A summary of who was followed up is posted to your sales channel in Slack.

  5. Each lead is followed up only once.

Before it runs live

  • Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
  • Connect Twilio

What you get

RunsDaily
Text quiet leads a follow-up and nudge sales in Slacktoday, 9:00Succeeded
Slack · #sales:wave: Followed up 3 quiet lead(s): Pat at Acme Dental, Northwind Cafe, Lee Morgan

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Run it at a different time, more or less often, or only on weekdays
  • Change what the AI looks for, or how it writes the result
  • Add another app, for example also send it to Google Sheets
  • Combine it with other Slack and Twilio steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
text_quiet_leads_a_follow_up_and_flag_them_in_slack.pyexample
from twilio.rest import Client
import time
from clickruntime import on_trigger, credentials, http, notify, state, ai

FROM = "+15005550006"

def sms(to, body):
    return Client(credentials.secret("TWILIO_ACCOUNT_SID"), credentials.secret("TWILIO_AUTH_TOKEN")).messages.create(to=to, from_=FROM, body=body)

@on_trigger
def run(event):
    client = Client(credentials.secret("TWILIO_ACCOUNT_SID"), credentials.secret("TWILIO_AUTH_TOKEN"))
    leads, nudged = state.get("leads") or {}, []
    for phone, lead in leads.items():
        if lead.get("followed") or time.time() - lead["at"] < 3 * 86400:
            continue
        if client.messages.list(from_=phone, to=FROM, limit=1):
            lead["followed"] = True; continue
        text = ai.generate(f"Lead {lead['name']} asked: {lead.get('message', '')[:500]}", max_output_tokens=60,
                           system="Write a friendly one-sentence follow-up text. No pressure.").text.strip()
        sms(phone, text)
        lead["followed"] = True
        nudged.append(lead["name"])
    state.set("leads", leads)
    if nudged:
        notify.slack(f":wave: Followed up {len(nudged)} quiet lead(s): {', '.join(nudged)}", channel="#sales")
    return {"nudged": len(nudged)}

FAQ

Common questions

How does it know who replied?
It checks your Twilio messages for any text from the lead's number since the first contact.
How many follow-ups are sent?
One per lead by default, so nobody is pestered.
Where are leads stored?
They're remembered when first contacted, from your form or another automation.
What permissions does it need?
Twilio send/read; chat:write. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Text quiet leads a follow-up and nudge sales in Slack” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.