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
- Send iMessage
- Wait for Reply
- If Reply → stop automation or branch workflow
- 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.