A lead texts your business line at 9:47 PM asking about pricing. You see it at 7 the next morning. By then they've already texted two competitors, and the one who answered first is the one they're talking to now. This isn't a hunch, it's measurable: a study of 2,241 US firms published in the Harvard Business Review found that companies contacting a lead within an hour were nearly seven times as likely to qualify that lead as companies that waited even one hour longer, and more than 60 times as likely as companies that waited a full day. The average firm in that study took 42 hours to respond at all.
You can't staff a human to answer texts at 2 AM, and you shouldn't have to. What you can do is make sure the lead gets something back in seconds: an acknowledgment that buys you the time to call back properly. That's what an auto-reply rule is for, and it's a feature most operators in high-risk verticals never turn on because they're focused on just getting the message delivered in the first place.
What speed to lead actually costs you
The mechanism behind the HBR numbers isn't mysterious. A person who just submitted a form or sent an inquiry text is, for a short window, actively comparing options. Real estate wholesalers text hundreds of homeowners a day and see reply rates around 2%, so on a 10,000-message batch that's 200 live conversations opening up in a short window. Lead-gen buyers selling those same leads to multiple end clients know the first responder usually wins the deal, not the best offer. In both cases, the value of the lead decays fast, and it decays before anyone on your team has read the message.
An auto-reply doesn't close the sale. It holds the door open long enough for a human to walk through it.
How auto-reply rules work
Android Texter's auto-reply rules live at /dashboard/auto-replies in the web dashboard. A rule triggers on a keyword or on the sender matching a pattern, and fires a canned response back automatically, the moment the inbound message lands, with no human in the loop. This is a different tool from quick replies (the /thx-style shortcuts you trigger manually from the composer): auto-reply fires without you touching anything.
Three things make this work at the SMS layer specifically, in a way a chatbot widget on your website can't replicate:
- It happens on the channel the lead already used. They texted you, they get texted back. No app to open, no email to check.
- It's instant regardless of your team's hours. The rule fires the same at 2 AM as it does at 2 PM.
- It's honest about what it is. A short "got it, calling you back shortly" message sets an expectation instead of pretending to be a person who isn't there.
Three auto-reply patterns worth setting up
Instant lead acknowledgment. Trigger on any first inbound message from a number not already in your contacts, and reply with something like "Thanks, got your message. Someone will call you back within 15 minutes during business hours." This is the single highest-value rule for lead-gen, real estate wholesaling, and any inbound sales line, because it directly answers the response-time problem above without requiring a human to be at a keyboard.
Business-hours responder. Trigger outside your staffed hours and set expectations honestly: "We're closed right now, back at 8 AM. We'll follow up first thing." This matters more than it sounds like it should. A lead who gets nothing back at all assumes they were ignored. A lead who gets an honest "not yet, but soon" stays warm.
Opt-out keyword handling. Trigger on STOP, UNSUBSCRIBE, CANCEL, END, or QUIT and reply with a suppression confirmation. Android Texter treats these as automatic suppression triggers regardless of whether you've built a custom rule for them, but a confirmation reply ("You've been unsubscribed and won't receive further messages") is good practice on top of that, because it gives the person proof the request was received. This rule is compliance infrastructure as much as it is a courtesy: TCPA enforcement turns partly on whether an operator actually honored an opt-out request, and an auto-reply that confirms suppression is a cleaner record than a silent unsubscribe with no trace.
Why this matters more if you're in a blocked vertical
If you're sending through a standard A2P 10DLC line, operators in payday lending, cannabis, debt collection, MLM, and gambling either can't register a campaign at all or get carriers to throttle content they've flagged under the SHAFT-C restricted categories, independent of whether the content itself is compliant. When a message from one of these verticals does land, it's often because it came through a channel the carrier didn't gate the same way, which is exactly what P2P SMS through a real handset is. That makes every inbound reply more valuable, not less: you already fought harder to get the conversation started, so the auto-reply that keeps it alive matters more than it would for a business whose texts flow freely through a registered A2P campaign.
This doesn't change what you owe the lead legally. TCPA consent requirements and opt-out handling apply the same way regardless of which channel carried the message. An auto-reply rule is operational, not legal cover: it makes sure a real reply follows quickly, and it makes sure STOP requests get recorded and honored.
Setting up your first rule
- Open
/dashboard/auto-repliesin the Android Texter web dashboard. - Choose a trigger: a keyword match, or "any first message from a new sender" for a general lead-acknowledgment rule.
- Write the reply. Keep it short and honest about what happens next, don't pretend a person wrote it if one didn't.
- Set a time window if the rule should only fire outside business hours.
- Save. The rule applies to every paired device on the account unless you've scoped it to one.
If you're running outbound across multiple paired phones to spread volume and avoid tripping a carrier's velocity filters, auto-reply rules apply account-wide, so a lead who replies to Phone B gets the same acknowledgment as one who replies to Phone A. You don't have to configure the rule per device.
What auto-reply doesn't do
It doesn't get you consent, and it doesn't make an uncontacted lead into a contacted one for TCPA purposes. If you don't already have prior express consent to text a number, an instant acknowledgment reply to their inbound message doesn't create it retroactively, and it doesn't excuse a marketing text you send them later without that consent on file. It also doesn't replace the actual follow-up call or text a human needs to send. The whole point of the rule is to buy time for that follow-up, not to stand in for it. A lead who gets an instant "we'll call you back" and then never gets called back is worse off than one who got nothing, because now they know they were seen and ignored.
Frequently Asked Questions
Is an auto-reply text the same as an autodialer under the TCPA?
No. Auto-reply rules respond to an inbound message the recipient already sent you, they don't originate unsolicited outbound contact. The TCPA's autodialer provisions concern unprompted outbound calls and texts, particularly marketing messages sent without consent. A reply triggered by the recipient's own inbound text is a different fact pattern, though you should still avoid sending marketing content in an auto-reply if you don't have consent to market to that number.
Can I use different auto-reply messages for different lead sources?
Yes, if you can distinguish the sources by keyword or sender pattern. Android Texter's rules trigger on keyword or sender matches, so if different campaigns route to different numbers or use different first-touch keywords, you can write a distinct rule for each.
Does an auto-reply count toward my message volume or affect delivery?
An auto-reply is an outbound SMS like any other message from the device, so it counts against whatever quota or rate limit applies to your account tier. It doesn't get special treatment from the carrier, but it also isn't singled out for extra scrutiny since it's routed the same way as every other message from that phone.
What happens if two auto-reply rules both match the same inbound message?
Only build overlapping triggers if you've thought through which one should win. Keep keyword triggers specific (an exact word or short phrase) rather than broad, and reserve the "any first message" trigger for a single catch-all acknowledgment rule rather than stacking it with keyword rules that might also match.
Should my auto-reply mention that it's automated?
It's the more honest option, and it sets a cleaner expectation than a reply that reads like a person typed it in real time. "Thanks, got your message, someone will follow up shortly" reads as a system confirmation without needing to say the word "automated," and it doesn't overpromise a response time you can't hit.
Android Texter's auto-reply rules run on the same P2P line as every other message the account sends, so the acknowledgment goes out from the same real phone number the lead already texted, no separate short code or chatbot number to look suspicious. If you're losing leads to slow response and you're already routing SMS through Android Texter, turning on a rule at /dashboard/auto-replies takes a few minutes to set up.