A rider asks whether you can fix their gears before the weekend. The shop needs a few details before anyone can give a useful answer. An automated reply can collect those details while the mechanic keeps working.
That is a good first job for DM automation. Start with one recurring request, give the rider a clear next step, and leave decisions about repairs, compatibility, and completion dates with the people doing the work.
We recommend starting with service intake before building a large conversational catalog. You can make the first exchange useful without connecting every product, workshop slot, and supplier feed.
Choose a job the shop can finish
Look through a recent batch of messages and separate questions you can answer from approved shop information from questions that need a staff member. “Where do I drop it off?” belongs in the first group. “Will this derailleur work with my drivetrain?” belongs in the second.
A useful starting set is:
- Service: collect the bike type, the rider's description of the problem, and their preferred drop-off day. Send the request to the workshop.
- Shopping: send a relevant product category or collect the model and size someone wants a salesperson to check.
- Group rides: send the published route, start location, pace description, and registration link.
These are three different outcomes. A service request needs a workshop response. A shopping question may need a stock check. A ride registration needs an actual registration record. Give each its own destination instead of ending every exchange with “Thanks, we'll be in touch.”
Build a service flow that makes no promises for your mechanic
Before building, connect an Instagram professional account (Business or Creator) to your tool. Personal accounts cannot connect to Manychat. Follow its current connection guide and review the permissions for the connection method you choose; the prerequisites differ between methods.
The following is an illustrative flow for a fictional shop. Replace the wording and operating details with your own.
A short Instagram post shows how the shop assesses a bike and says: “Need a service? Comment SERVICE and we'll send you the drop-off details.” In Manychat, attach a SERVICE keyword trigger to that specific post. Its comments trigger documentation covers both the public response and the first private reply.
- Deliver what the post offered. The first DM gives the drop-off information or its link: “Here are our service drop-off details. Want to send the workshop a question first?” Add a regular button labeled “Ask the workshop.”
- Ask about the bike. After the person presses that button, offer “Regular bike” and “E-bike,” then ask for the make and model if they know it. Include “Not sure” as an acceptable answer.
- Ask for the problem in their words. “What's happening with the bike?” gives the mechanic more context than forcing every rider to choose a repair package.
- Clarify timing. Ask when they would like to bring it in. Say explicitly that this is a request, not a confirmed slot or completion date.
- Hand over the conversation. Summarize the bike, issue, and requested day for the assigned staff member. Show the rider your actual staffed reply hours and a phone number for time-sensitive questions.
Keep the mechanic's assessment separate from intake. Trek's published service process moves from listening to inspection, then recommendations and an itemized estimate. That is a useful operational reference: the inspection supplies information a DM cannot. Trek also publishes its own turnaround offer; do not copy that promise into an independent shop's flow unless your shop actually provides it.
If you already use a booking system, send its booking link after the initial question. Only describe a booking as confirmed once that system has accepted it. A preferred day typed into Instagram is still a preferred day.
The Instagram rule that changes your follow-up plan
A comment lets you send an initial private reply. It does not give you an ongoing marketing subscription. Meta's private-reply documentation allows one initial message within seven days of the comment and requires a response before further messages, which must fall within 24 hours of that response.
Manychat spells out a detail that matters when building the example above: a regular button or Quick Reply can open the 24-hour window; an “Open website” button does not. If the rider only opens your drop-off page, do not treat that click as permission to send the remaining questions.
This trips up real builders. In a Manychat community troubleshooting thread, a user tried tagging a commenter and triggering a second flow. Community expert Gustavo Boregio explained that the missing piece was the recipient's interaction. Tags organize your workflow; they do not create messaging permission.
Keep ordinary automated follow-ups inside the standard 24-hour window. If the workshop needs to contact someone later about their repair, use the shop's service system and the contact details the customer supplied for that purpose. Do not build next-week tune-up promotions around an old Instagram exchange.
Keep stock and ride details current
A handwritten product recommendation in a flow will stay there after the last bike in that size sells. Unless you have a tested live inventory connection, link to the product page and say a staff member can confirm availability. Avoid “We've got one ready for you” when no system has reserved it.
Ride information needs a similar owner. Store the current route and weather decision on one page, then link to it from the DM. Someone must update that page when the ride changes. Stop or revise the campaign after the event so a comment on an old post does not send people to last month's meeting point.
For a ride campaign, keep the registration step explicit. Our guide to turning comments into event registrations separates asking for details from reserving a place.
Give staff a queue they can actually use
Assign one person to incoming service requests during each staffed period. Agree what “needs a human” means: an unclear repair issue, a product compatibility question, a complaint, or a request the automation cannot answer.
Pause the automated conversation when staff take over, and test that the pause works. The rider should not receive a menu while the mechanic is answering their question. If nobody is available, an honest reply time is more useful than a fake typing delay.
When comparing tools, build this exact handoff in a trial. Manychat documents the comment-led entry flow; respond.io documents managing Instagram messages in a shared inbox and links that open a customer's Instagram conversation. Ask each vendor to show who owns an unanswered request and what happens when that person is off shift. Those details matter more here than the number of templates.
Check completed work, then expand
For a small pilot, record service conversations started, requests passed to staff, appointments confirmed, bikes checked in, and completed paid jobs. Track unanswered requests separately. A fast automated greeting can hide a slow workshop handoff.
Use a campaign label in your booking or service records where possible. If your systems cannot connect the records reliably, ask staff to mark the source and describe the result as reported attribution. Do not count every linked job as a sale the automation created; some riders already intended to visit.
Before launch, test a new commenter, someone who only clicks the website link, a repeat comment, an unknown answer, and an out-of-hours request. Manychat notes that its trigger runs only for the first comment a person leaves on a particular post or reel, so repeating your own comment is an unreliable test.
Start with the service request you already receive most often. Write its destination, responsible staff member, and completion event in the DM campaign field guide. Add another flow when the first one consistently reaches that destination.
First published . Updated with current research and practical examples.
