Back-in-stock callbacks
Out-of-stock disappointment becomes a list, and restocking flips a field that calls everyone on it, in order.
Trigger
A Waiting for field on the contact matches an item you mark back in stock.
Built from
Why teams set this up
The customer who wanted the thing you were out of is the easiest sale you will ever lose. They asked, you said soon, and soon arrived without anyone telling them.
Restocks sell to the waitlist first
Interest captured instead of lost at the counter
A measurable list of what to reorder
How the automation runs
Fourteen people asked about a part you ran out of in March. The shipment lands, one field flips, and by close of business nine of the fourteen have reserved one. The reorder quantity for next time is no longer a guess.
- 1CRM update
Interested callers get tagged with what they wanted
- 2Ticket field
The restock flips the field that wakes the sequence
- 3Outbound call
Everyone waiting gets a call offering to reserve theirs
- 4Outbound SMS
Unreachable customers get the text version
- 5CRM update
Buyers clear off the list, the rest stay for next time
The same workflow in different businesses
Auto shops
Backordered parts call their own waitlists the day they land on the dock.
Retail
Sold-out items build callback lists at the counter and clear them on restock day.
Built from standard Frontdesk blocks
No custom development. Each step is a building block you can rearrange, retime, or extend, so this workflow can grow into the next one.
Retention journeys that include this workflow
This workflow is one step inside larger retention journeys that run the full customer lifecycle.
Customer retention
Combine behavior, sentiment, service history, and conversation data into proactive retention workflows.
See the journey →Churn risk intervention
Route each at-risk customer into a playbook based on value, issue, urgency, and preferred channel.
See the journey →Renewal journey automation
Coordinate education, value review, objections, approvals, offers, and signatures before the deadline.
See the journey →Common questions
How does the back-in-stock callbacks workflow start?
A Waiting for field on the contact matches an item you mark back in stock.
Which channels does this use?
This workflow runs over outbound voice, sms. Each step can use the channel that fits the customer and the urgency.
Can my team stay in control of when it fires?
Yes. The trigger can be a field a person flips on a ticket or contact, so a human makes the decision and Frontdesk does the follow-through. Any step can also route to a teammate with the transcript and collected data.
Does it keep our records up to date?
Every call, text, and email in the workflow is logged against the contact and ticket, with transcripts attached. Frontdesk can also sync contacts and fields to your CRM.
What happens when a customer needs a human?
The workflow hands off with context: the right teammate gets the full history, the transcript, and the collected answers, so the customer never repeats themselves.
Thinking bigger than one workflow?
The customer journey library maps full lifecycle automations across activation, onboarding, retention, and growth.
Explore customer journeys →More from orders and deliveries
Status questions answered around the clock and delays announced before customers ask.
Order status hotline
Callers asking where their order is get a live answer pulled from your order system mid-call, around the clock.
Shipping delay notifications
When an order slips, every affected customer hears it from you first, by text, with the new date and an honest apology.
Return authorization automation
An RMA approved field that, once flipped, sends the label, the instructions, and the refund timeline, then chases the package until it ships back.