--- title: "GHL: Workflows—Best Practices & Optimization" description: "GHL workflows + Linq Blue: triggers/actions, provider setup, custom iMessage actions, stop-on-reply logic" --- [Skip to content](https://help.linqapp.com/ghl-workflows-best-practices#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. [Integration: GHL](https://help.linqapp.com/linq-blue?hsLang=en#integration-ghl) July 9, 2026 # GHL: Workflows—Best Practices & Optimization #### Why Workflow Optimization Matters Linq Blue works best when workflows feel like real conversations — not automated campaigns. Proper workflow structure improves: - Response rates - Deliverability - Customer engagement - Long-term line health Poorly designed automations can lead to low engagement, throttling, or flagged numbers. --- ### The Golden Rule: Prioritize Replies The most important metric for Linq Blue is engagement. Healthy lines typically maintain: - 30–40% response rates = strong performance - Minimum 15% response rate recommended The goal of every workflow should be to encourage conversations, not just send messages. --- ### Use “Wait for Reply” Logic One of the best ways to improve workflow quality is by slowing automation down until the contact engages. #### Recommended Structure 1. Send iMessage 2. Wait for Reply 3. If Reply → stop automation or branch workflow 4. If No Reply → delayed follow-up This creates a much more natural messaging experience. --- ### Important: “Stop on Response” Does Not Automatically Apply When using Linq Blue iMessage actions, GHL’s native “Stop on Response” setting does not automatically stop future Linq Blue messages. To properly stop the workflow: #### Recommended Setup ### Trigger Customer Replied ### Action Remove From Workflow This ensures contacts stop receiving automated messages once a real conversation starts. --- ### Space Out Your Messages #### Avoid Rapid-Fire Messaging Sending too many messages too quickly can hurt deliverability and increase the chance of line flagging. Recommended spacing: | Message Type | Recommended Delay | | --- | --- | | First Follow-Up | 24 hours | | Second Follow-Up | 1–2 days | | Additional Follow-Ups | Gradual spacing | Avoid: - Multiple messages within minutes - Large workflow bursts - Long automated sequences without engagement --- ### Keep Workflows Conversational #### What Performs Best Messages that: - Feel personal - Use the recipient’s name - Sound natural - Ask simple questions ### Example > Hey Mike! Just wanted to check in — are you still looking for help with your insurance quote? --- #### What to Avoid Avoid workflows that: - Sound robotic - Use aggressive sales copy - Send long paragraphs - Include links in the first message - Feel mass-produced - Include gifs/photos/media ### Avoid This > LIMITED TIME OFFER! Click here now to claim your discount! That type of messaging performs poorly on iMessage and increases spam risk. --- ### Limit New Conversations Per Line Linq Blue is designed for conversational messaging — not mass outreach. #### Recommended Daily Volume - Around 50 new conversations per line per day - Gradual warm-up for newer numbers Large spikes in outbound messaging can negatively affect line health. --- ### Smart Workflow Design Tips #### Use Branching Logic Instead of sending every contact through the same sequence: - Branch based on replies - Branch based on tags - Branch based on appointment status - Branch based on engagement This creates more relevant conversations. --- #### Keep Follow-Ups Short Every message should be readable in a few seconds. Short messages consistently outperform long-form copy inside iMessage workflows. --- #### Use Contact Cards Strategically The “Share Contact” action helps recipients recognize your number and improves trust. Best practice: - Send after the first message - Do not use as the first workflow action --- ### Monitor Workflow Health Inside GHL → Linq → Phone Analytics, monitor: - Response rates - Conversation quality - Message volume - Limited activity - Line health If response rates begin dropping, review: - Message copy - Workflow pacing - Audience quality - Send volume --- ### Signs Your Workflow Needs Optimization ⚠️ Low reply rates ⚠️ Large send spikes ⚠️ Multiple follow-ups without responses ⚠️ Contacts receiving messages too frequently ⚠️ Increased failed deliveries or throttling These are signs the workflow may need adjustments. --- ### Summary The best Linq Blue workflows: - Focus on conversations, not campaigns - Space messages naturally - Stop automations when contacts reply - Use short, human messaging - Encourage engagement early Well-optimized workflows improve both deliverability and conversion while helping protect your Linq Blue number long term. - [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