> ## Documentation Index
> Fetch the complete documentation index at: https://support.blujay.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Following up

> How often to follow up, when to stop, and how to restart a quiet conversation.

Following up is how most conversations get going, but too many unanswered texts get you reported as junk and can get your number blocked. These limits keep you persistent without crossing that line.

## Dos and don'ts

| Do | Don't |
| - | - |
| ✅ Follow up at most 2 times a week | ❌ Send several texts in a day to someone who hasn't replied |
| ✅ Stop after 2 follow-ups with no reply | ❌ Keep following up until they answer |
| ✅ Keep unanswered texts to 5 or fewer (Blujay stops everyone at 6) | ❌ Let automations and manual texts stack up |
| ✅ Use a short, easy question to restart a conversation | ❌ Repeat your original pitch |
| ✅ Opt out anyone who asks you to stop | ❌ Keep texting after they've said no |

## How often to follow up

* **At most 2 follow-ups a week** to any one person.
* **At most 2 follow-ups after your first message.** If they still haven't replied, stop. Come back later with something new, not the same message again.

If two follow-ups didn't get a reply, a third rarely changes the answer. It just adds another unanswered text, and each one makes a junk report more likely.

### A simple follow-up schedule

1. **Your first text.**
2. **About a day later:** your first follow-up.
3. **A few days after that:** your second and last follow-up. Give them an easy way out, so a "no" is as easy to send as a "yes".
   * ✅ *"Should I close this out for now?"*
4. **Then stop.** Don't text again until they reply.

## Count every unanswered message

**Aim for 5 or fewer texts in a row without a reply.** Blujay enforces a hard stop at 6: nobody in your workspace can send a 7th text to someone who hasn't responded, counting your own texts, your teammates', scheduled messages, automations and integrations, from any of your numbers. At the 6th, the message box tells you it will be your last text until they reply. After that it waits for them. A text or a tapback from them restarts the count; a call doesn't.

If you use Blujay Automations, add a **Wait for Reply** step between messages. It waits for a reply for a set time, then continues down a different path depending on whether they answered, so a contact who goes quiet doesn't keep getting messages. An automation or scheduled text that would be the 7th isn't sent; it shows as **Not Sent** in the conversation with the reason.

## Restarting a quiet conversation

When a conversation stalls, send something short and low-pressure that's easy to answer from a lock screen:

* ✅ *"Did my last message come through?"*
* ✅ *"Still worth keeping this open, or should I close it out?"*
* ✅ *"No rush on this. Want me to check back next month?"*
* ❌ *"Just following up again on my previous messages about our offer…"*

## Why it matters

Every unanswered text is another chance for someone to tap **Report Junk**. Enough reports and Apple and the carriers start filtering or blocking your number, so fewer of your messages arrive, including to people who want to hear from you.

## When someone asks you to stop

If a contact replies with just the word **STOP**, Blujay opts them out automatically.

If they ask you to stop in any other way, opt them out yourself right away:

1. Open the conversation in the Blujay web app.
2. Open the **…** menu at the top of the conversation.
3. Click **Opt out contact**.

The conversation shows **Opted out**, and Blujay blocks all messages and calls to that contact, including scheduled messages and automations. You'll still see any messages they send you. If they later clearly ask to hear from you again, choose **Restore messaging** from the same menu.

## Next

> [card] [Your first text to a new lead](https://support.blujay.io/messaging/first-text.md)
>
> Open a conversation that gets a reply.

> [card] [Keeping the conversation going](https://support.blujay.io/messaging/keep-it-going.md)
>
> What to do once they reply.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.