Halloween deal is live: flat 30% off Fluent Support. 🎃
Unlimited agents for one price. Your whole team handles tickets and automations inside WordPress, and you pay 30% less this season.
Discount link is in the reply 👻
#FluentSupport#HalloweenSale#Helpdesk
Same results. One site showed them instantly. The other took up to a minute and showed each airline being checked.
People sometimes preferred the slower one (Buell & Norton, HBS, 2011).
Show what you checked in your next ticket reply, not just the result.
Halloween deal is live: flat 30% off Fluent Support. 🎃
Unlimited agents for one price. Your whole team handles tickets and automations inside WordPress, and you pay 30% less this season.
Discount link is in the reply 👻
#FluentSupport#HalloweenSale#Helpdesk
Two customers wait four hours for a first reply.
One was told “within four hours.” The other got “we’ll get back to you soon.”
Same clock, but the second wait feels longer. Maister (1985): uncertain waits feel longer than known ones.
Name a time window in your auto-reply.
@FluentSupportWP remote portal plugin, I wondered if it contained enough information for me to get it to work on a static site. I could; it's actually two WP installs here one for cart, one for support and shared user accounts.
Customers don't stay for the wow. They stay when it's easy.
A study of 75,000+ customers (Dixon, Freeman, Toman, HBR) found going above and beyond barely moved loyalty. Effort did.
Pull 10 recent tickets. Count how many times the customer had to repeat themselves.
Connect Fluent Support with FluentCRM to view CRM details inside tickets, manage contact tags and lists from the support dashboard, and see a customer's tickets from their FluentCRM profile.
To know more about this integration, check the link in the first reply.
Fixing a customer's problem well can make them more loyal than if nothing broke.
But only about 5% of the time (Michel & Meuter, 11K+ banking interactions).
Most teams treat this as a strategy. The data says it's closer to a lucky outcome.
Fix: flag any customer's 2nd contact for the same root issue (not the same symptom) and route it straight to a senior agent.
That's the ticket that actually decides whether they stay.
Here's the part most teams never check.
When a customer hits a 2nd failure, even one your team fixes perfectly, they stop reading it as an accident.
They start reading it as how your company actually operates.
A flawless recovery on ticket 2 doesn't undo that read.
The customer isn't grading the ticket anymore. They're grading the pattern.
Trust breaks on ticket 2, not ticket 1.
The 7 deadly sins of customer support:
1. Slow first response
2. Customers repeating themselves
3. Every ticket treated the same
4. Closing without confirmation
5. Answers that change by agent
6. Feedback never acted on
7. Fully reactive support
Full blog in the reply 👇
August Edition of "Checkout Thinking" went out this week!
Most software newsletters are release notes with a subject line on top.
Checkout Thinking is the version you'd want to read.
Monthly, short, and written for people running stores rather than reading about them.
Don't miss out on September Edition:
https://t.co/DFbF3eGZpw
What if your support tickets already knew a customer's order history?
Fluent Support integrates with WooCommerce. Agents see purchase history, order status, and product details right on the ticket. Customers pick their order when they submit one.
Check link in reply for more👇