--- title: Linq Blue Best Practices description: Linq Blue, iMessage Best Practices, Linq Zero, Contact Card, Messaging --- [Skip to content](https://help.linqapp.com/imessage-best-practices-for-linq-blue#main-content) English Show submenu for translations [![Cube-Linq-w](https://help.linqapp.com/hs-fs/hubfs/Cube-Linq-w.png?width=200&height=89&name=Cube-Linq-w.png)](https://linqapp.com/?hsLang=en) Open main navigation Close main navigation - English Show submenu for translations - [Go to linqapp.com](https://linqapp.com/) [Go to linqapp.com](https://linqapp.com/?hsLang=en) How can we help? - There are no suggestions because the search field is empty. 1. [Help Center](https://help.linqapp.com/?hsLang=en) 2. [Linq Blue](https://help.linqapp.com/linq-blue?hsLang=en) 3. [Linq Blue Subscription](https://help.linqapp.com/linq-blue?hsLang=en#linq-blue-subscription) April 29, 2026 # Linq Blue Best Practices #### 🔹 Why iMessage Works Differently Unlike A2P (Application-to-Peer) SMS services, iMessage is P2P (Peer-to-Peer). That means a more personal, conversational approach—both for effective communication and to align with how iMessage is designed to be used. | A2P (Traditional SMS) | P2P (iMessage via Linq Blue) | | --- | --- | | Message blasts | **Conversion through conversation and engagement** | | Required opt-outs | **Peer-to-peer communication** | | Broad, impersonal | **Targeted, conversational** | | Limited features | **Rich media, voice, video, reactions, threaded replies** | | Pay by volume | **Pay by line** | | Regulation, delay | **Ready in 72 hours** | --- #### 🔹 Reply Rate Standards Reply rate is the clearest indicator of a healthy line. Strong reply rates build momentum and compound into better deliverability over time. 1:2 — Target ratio: 1 reply for every 2 sends 30–40% — Ideal reply rate on first messages 15% — Minimum reply rate to maintain line health --- #### 🔹 Crafting an Effective First Message The first message sets the tone for everything that follows. The best ones feel personal, read fast, and make it easy for the recipient to reply. 1. **Be Personable** - Use the recipient's first name - Introduce yourself as an individual from your company - Give context — let people know why you're reaching out and why it matters - Bonus: your name may show as "Maybe \[Name\]" on future calls once they save you 2. **Keep It Short** - Messages should sound like a conversation between friends, not a campaign - The entire message should be readable before the recipient decides to reply - Message previews are valuable real estate — keep it 2–3 lines max 3. **Make It Easy to Reply** - End with a question that's simple and natural to answer - Whether open-ended or a quick yes/no, the goal is a low-friction response - Skip links and attachments in the first message — let the conversation start first The Formula Hi NAME, it's NAME from COMPANY. Quick one — are you more focused on A or B right now? --- #### 🔹 Factors That Affect Line Performance These practices give each of your lines the best chance to perform well over time. | Factor | Best Practice | | --- | --- | | Velocity | Cap at 50 unique new conversations per line per day. Warm up new numbers gradually — don't max volume on day one. | | Content | Keep first messages text-only. Links won't be clickable until the recipient replies, so lead with conversation. | | Media Timing | Save voice memos, images, and videos for after the first reply. Earn the response, then share media. | | Tone | Conversational copy outperforms templated or scripted messages. Write like a person, not a campaign. | | Pacing | Give recipients time to reply before following up. Stacking messages to non-responders rarely helps performance. | | Call & Text Separation | Text from Linq Blue, call from a separate office or VoIP number. Using the same number for both can trigger a "Spam Likely" label at the carrier level. | ![Screenshot 2026-04-21 at 11.34.27 AM](https://help.linqapp.com/hs-fs/hubfs/Screenshot%202026-04-21%20at%2011.34.27%20AM.png?width=191&height=233&name=Screenshot%202026-04-21%20at%2011.34.27%20AM.png) #### 🔹 Sending a Contact Card Sharing a contact card helps recipients see a name instead of a random number, which builds trust and improves reply rates. Use the method that matches your platform. ![Screenshot 2026-04-21 at 11.32.37 AM](https://help.linqapp.com/hs-fs/hubfs/Screenshot%202026-04-21%20at%2011.32.37%20AM.png?width=234&height=277&name=Screenshot%202026-04-21%20at%2011.32.37%20AM.png) | Platform | Method | | --- | --- | | Linq Zero | Use the native **Share Contact** action built into the app. | | GHL (single phone number) | Use the **Share Contact Card** action inside your GHL workflow. | | HubSpot, Salesforce, or GHL (multiple numbers) | Use a **.VCF file** — send it in the text body of the message. This is the right path when the card needs to carry more than one number. | --- #### 🔹 What Not to Send via iMessage Some message types aren't built for a conversational channel. Send these via SMS, email, or other broadcast tools instead. - Long paragraphs that read like a cold email - Links in the opener (they won't be clickable until the recipient replies) - Images, PDFs, or videos as the first message - Mass-marketing-first language or "BIG NEWS!" style promotional blasts - Templated, automated-feeling copy - Generic openers that don't name the recipient ![Screenshot 2026-04-21 at 11.35.43 AM](https://help.linqapp.com/hs-fs/hubfs/Screenshot%202026-04-21%20at%2011.35.43%20AM.png?width=331&height=221&name=Screenshot%202026-04-21%20at%2011.35.43%20AM.png) ##### Good Examples: Good · CRM Confirmation: Hey ! It's Bradley from Linq. Are we good to connect tomorrow at 10:30am CDT? To make sure we have the right interface ready, what CRM do you use? Good · Insurance Qualifier: Hi ! It's Sarah from Apex Insurance. Are we still good for our call at 2pm tomorrow? Are you mainly looking for auto, home, or both? --- #### 🔹 Benefits of Following These Practices | Benefit | Impact | | --- | --- | | ✅ Protects line health | Keeps reply rates above the 15% minimum threshold | | ✅ Builds recipient trust | Displays a verified name in iMessage, not a random number | | ✅ Increases engagement | Higher open and reply rates through conversational tone | | ✅ Reduces Spam Likely risk | Proper call/text separation prevents carrier-level flags | | ✅ Better deliverability over time | Strong reply rates compound into sustained line performance | --- #### 🔹 Need Help? If you're finding challenges implementing these best practices, your Partner Success Manager will reach out and work alongside you to recalibrate — reviewing workflows, adjusting messaging, and getting your line back to strong performance. - [Linq Blue](https://help.linqapp.com/linq-blue?hsLang=en#main-content) - [Linq Blue Subscription](https://help.linqapp.com/linq-blue?hsLang=en#linq-blue-subscription) - [Linq Zero](https://help.linqapp.com/linq-blue?hsLang=en#linq-zero) - [Integration: GHL](https://help.linqapp.com/linq-blue?hsLang=en#integration-ghl) - [Integration: Salesforce](https://help.linqapp.com/linq-blue?hsLang=en#integration-salesforce) - [Integration: HubSpot](https://help.linqapp.com/linq-blue?hsLang=en#integration-hubspot) - [Linq One](https://help.linqapp.com/linq-one?hsLang=en#main-content) - [FAQs](https://help.linqapp.com/linq-one?hsLang=en#faqs) - [Linq App](https://help.linqapp.com/linq-one?hsLang=en#linq-app) - [Admin Dashboard](https://help.linqapp.com/linq-one?hsLang=en#admin-dashboard) - [Products](https://help.linqapp.com/linq-one?hsLang=en#products) - [Troubleshooting](https://help.linqapp.com/linq-one?hsLang=en#troubleshooting) - [API](https://help.linqapp.com/api?hsLang=en#main-content) - [Sandbox](https://help.linqapp.com/api?hsLang=en#sandbox) - [API Resources](https://help.linqapp.com/api?hsLang=en#api-resources) [![Cube-Linq-w](https://help.linqapp.com/hs-fs/hubfs/Cube-Linq-w.png?width=197&height=88&name=Cube-Linq-w.png "Cube-Linq-w")](https://linqapp.com/?hsLang=en) linqapp.com Help Center Copyright © 2025, Linq