How do you turn Instagram DMs into actual bookings?
Answer inside Instagram's 24-hour messaging window, and answer with something that can take money rather than something that starts a conversation. Meta's own documentation is explicit that an app has 24 hours to respond to a message an Instagram user sends, after which a standard reply will not go out and a human agent tag is the documented way to reply later. That window is the whole game for an Indian tour operator: an enquiry that arrives at 11pm on a Tuesday and gets read on Thursday morning is not a slow lead, it is a lead your software is no longer allowed to chase automatically. The fix is one inbox that carries Instagram DMs, WhatsApp and website enquiries together, a pipeline that ranks who is close to paying, nudges that fire while the window is open, and a link in every reply that ends at a checkout instead of at another question.
Most Indian trek and tour businesses get their enquiries as Instagram DMs. Almost none of them treat the DM inbox as a sales pipeline, which is why the same operator can have 40 unread messages and an unsold May batch in the same week.
The 24-hour clock you are already on
Instagram puts a hard limit on how late a reply can be, and Meta writes it down. Meta's Instagram Platform documentation for the Messaging API states plainly: "Your app has 24 hours to respond to any message sent from an Instagram user to your app user." That is the standard messaging window. A traveller messages you, a 24-hour clock starts, and any software connected to your account is allowed to send during it.
After that the same doc gives one documented way out. "If your app user uses a human agent to respond to messages and therefore may need more time to respond, your app can tag the response to allow your app to send the message outside the 24 hour messaging window." A human agent tag, in other words, is for a real person catching up on a real backlog. It is not a licence to drip promotional messages at somebody for a fortnight.
So a Thursday reply to a Tuesday message costs you more than her patience. Your tooling can no longer send her the price and the seat count the way it would have on Tuesday evening. The follow-up that would have cost you nothing now costs you a person typing.
The other rules that decide what you can build
Meta's Instagram Platform overview carries the sending limits, and they are far higher than a trek business will ever reach.
| Rule | What Meta's docs state |
|---|---|
| Standard messaging window | 24 hours to respond to a message an Instagram user sends |
| Replying after it closes | Tag the response as a human agent reply |
| Account type | Your app users must have an Instagram professional account, business or creator |
| Send API, text, links, reactions, stickers | 100 calls per second per Instagram professional account |
| Send API, audio and video | 10 calls per second per Instagram professional account |
| Conversations API | 2 calls per second per Instagram professional account |
| Private replies to comments | 100 calls per second on live comments, 750 calls per hour on post and reel comments |
| App access level | Advanced Access is needed for an app serving professional accounts it does not own or manage |
At 100 sends a second, a 30,000-follower trek page will never hit a rate limit answering its DMs. The 24 hours is the thing you run out of.
What a slow reply actually costs
Picture the enquiry that arrives at 11:40pm: "Hi, is the Spiti May batch still open? Coming solo." She has sent the same message to four operators, because that is what a person planning a trip does. Whoever answers first gets to define what the trip costs and what solo means. The other three get to be compared against that answer.
Now add the window. If you reply at 9am the next morning you are inside it and only losing on order. If she messaged on Friday night and your team opens the inbox on Monday, the standard window has been shut since Saturday night, and the automatic nudge that would have said "two seats left on 18 May" cannot fire at all.
The second cost is quieter. A reply that says "Yes it's open, ₹18,000, DM me your details" starts another conversation. A reply that says "Yes, 6 seats on 18 to 24 May, ₹5,000 holds one, here is the page" ends one. The tap count for each of those is worked through in should a tour operator use Linktree in their Instagram bio, and the short version is that the second route finishes at midnight without you.
Why the DM inbox leaks
Discipline is rarely the problem. The inbox is a bad container for a sales pipeline, for four structural reasons.
- It sorts by recency, not by money. The person who has asked three questions and mentioned dates sits below a stranger who sent a fire emoji at 2pm.
- It is not one inbox. She DMs you on Instagram, then messages the WhatsApp number in your bio, then fills the form on your site. That is three threads, on two or three devices, and nobody knows they are one person.
- Nothing has a state. A DM is read or unread. It is not "quoted, awaiting deposit" or "asked about the June batch, tell her when it opens", which is what you actually needed to know.
- Two people answer the same traveller. With the phone shared between a founder and an intern, the traveller gets two prices in a week. This is how a discount you never approved becomes a discount you have to honour.
Trying harder at 11pm does not touch any of the four. What does is the enquiry becoming a record the moment it lands, rather than a message in a queue of messages.
How a trek business answers its DMs today
The setup is usually the same three parts: the DMs answered by hand on a personal phone in the evening, a saved reply with the price list pasted into every thread, and a "comment info below" habit on the reels that do well. At thirty enquiries a week that is warmer than anything automated, it converts, and it costs nothing. Four things in it give way, and the clock is what does the damage in three of them.
| How it works today | Where it breaks | What Thrivia does instead |
|---|---|---|
| You answer every DM yourself, by hand, on your own phone, after the day's calls are done. | The enquiry that lands at 11.40pm on Friday is read on Monday morning. The standard window has been shut since Saturday night, so no software connected to your account is allowed to send her anything at all, and the only routes left are a person typing or a human agent tagged reply. | The enquiry becomes a timestamped lead record when it lands, so the reply clock runs from her message rather than from the morning somebody opened the app. |
| A saved reply with the price list in it, pasted into every new thread. | It answers what a trip costs and nothing about whether her dates exist, so four more messages go back and forth on the batch she wanted, all of them burning a window that started when she typed. | Each departure sells from its own trip page with that batch's dates and seat count on it, so the reply is a link to the date she asked about. |
| "Comment info below and I'll DM you" under the reel that did 90,000 views. | Four hundred comments arrive over two days and nobody opens them in order, so the person who commented on Tuesday gets a DM on Thursday and does not remember the reel. Meta caps private replies to post and reel comments at 750 an hour anyway. | Thrivia does not fix that one. There are no comment-to-DM triggers here, replies work only on conversations that already exist, and how far a reel travels is not something the product touches. |
| The enquiries that look serious get copied into a notes app or a sheet when there is time. | There is time on Sunday. So on Sunday you cannot say how many of last week's forty DMs reached a paid seat, or which step they stopped at, and you plan next month's ad spend off a feeling. | Bookings are counted back to the lead they came from, and drop-off is reported per step between the enquiry and the payment. |
Switching costs you one evening and a fortnight of relapse. Somebody has to type the departures in with real seat counts and write the checkout questions down for the first time, and your team has to answer travellers in a browser rather than on the phone in their pocket, which they will forget for two weeks. The saved reply does not go away, it just ends at a link now. If you run four trips a year and answer the DMs yourself within the hour, the phone is already doing this job and a subscription will not beat it.
One inbox, and a pipeline behind it
Thrivia is India's booking and ticketing platform for tour operators, trek leaders, and retreat & fest hosts to sell tickets, take bookings, and manage guests. Instagram DMs arrive over the Graph API. WhatsApp arrives on your own WhatsApp Business Cloud API number. Website enquiries and Meta Lead Ads arrive alongside them, and the four are one thread list rather than four apps on two phones.
Each conversation is a lead, and leads are ordered by intent score rather than by who typed last, so the traveller who asked about dates, price and a solo booking sits above the person who said "nice reel". Where she needs chasing next week, that is a follow-up task against her record instead of something you were supposed to remember.
A lead that goes quiet gets an automated 3-touch nudge, timed to land inside the 24-hour window rather than after it. Three chances at a reply while software is still allowed to send, instead of one guilty message on Thursday.
Automating the reply without sounding like a bot
"Thanks for reaching out! Our team will get back to you shortly" burns a touch inside the window and answers nothing. Most DM automation sold to Indian travel businesses is that message with a delay on it.
Every trek enquiry is really four questions. How hard is it. Is there a batch on my dates. What does it cost and what is included. How do I hold a seat. An AI DM sales agent can answer those overnight in your own tone and hand the thread to a person when she is ready to book or asks something it should not guess at. It is a paid add-on rather than part of the base plan.
The limits, stated plainly
"DM automation" gets sold for two very different jobs, so here is the shape of this one.
- There is no WhatsApp broadcast and no bulk messaging. If your plan is to push a new Ladakh batch to 4,000 past travellers in one go, this is not the tool for that job.
- There is no email drip. Follow-up here is one-to-one against a lead record, in the channel the traveller chose.
- It is not a comment-to-DM trigger tool. Replies work on conversations that exist, not on turning "info" comments into DMs automatically.
The value is in the join. The traveller who DMed you at 11:40pm is the same record as the lead, the deposit, the guest list row and the QR code scanned at the trailhead, so nobody retypes her name at any point. The rest of that side is in booking software for tour operators.
Set it up this week
- Check the account type first. Meta requires an Instagram professional account, business or creator, for any of this to be possible at all.
- Build the trip page for the departure you are actually pushing, with dates, price, seats per batch and a deposit rather than the full amount. That page is what your DM replies will link to.
- Connect Instagram and your WhatsApp Business number so both land in one thread list instead of on two phones.
- Write the three nudges before you switch them on, and write them as a person. The first is an answer, the second is a seat count, the third is a deadline.
- Agree a response-time target with your team and hold it against the window. Anything under two hours in waking hours is fine. Anything that regularly crosses a night is where the money leaks.
- Add the AI DM agent only once you can point at the enquiries you are missing. It is a paid add-on and it should be paying for itself in booked seats.
Thrivia is a monthly subscription with an included booking allowance rather than a commission on each ticket, so a good season is not taxed for being good. Current plans are on pricing. If the DMs also need to land somewhere on a site you already own, do you need a website for your travel business covers the checkout side of that.
Common questions
How long do I have to reply to an Instagram DM?
Meta's Instagram Platform documentation for the Messaging API states that your app has 24 hours to respond to any message an Instagram user sends. That is the standard messaging window. If a human agent needs longer, the documentation says the response can be tagged so that the app is allowed to send outside the 24 hour window. Checked on Meta's own developer documentation on 10 September 2026.
What is the human agent tag on Instagram messaging?
It is a tag your app puts on a reply when a real person, rather than automation, needs more time than the 24 hour messaging window allows. Meta's documentation describes it as being for app users who use a human agent to respond and therefore may need more time. It is meant for genuine backlog, not for continuing to market to someone days after they stopped replying.
Can I automate Instagram DMs for my travel business?
Yes, through the Instagram Messaging API, and Meta's documented limits are generous. The Send API allows 100 calls per second per Instagram professional account for text, links, reactions and stickers, and 10 per second for audio and video. Your account must be an Instagram professional account, business or creator. The practical constraint is not the rate limit, it is the 24 hour messaging window.
Do I need a business account to connect Instagram DMs to a booking system?
Yes. Meta's Instagram Platform documentation states that app users must have an Instagram professional account, which means either a business or a creator account. A personal account cannot be connected. Apps that serve professional accounts they do not own or manage also need Advanced Access from Meta.
Can I sell a ticket inside an Instagram DM?
Not inside the chat itself. What you can do is reply with a link to a trip page that has a real checkout on it, so the traveller picks a departure, answers your registration questions and pays a deposit without leaving the browser Instagram opens. That is the difference between a DM that starts another conversation and one that finishes a booking.
How does Thrivia stop enquiries being lost in DMs?
Instagram DMs over the Graph API, WhatsApp on your own WhatsApp Business Cloud API number, website enquiries and Meta Lead Ads all land in one conversations inbox. Each becomes a lead in a pipeline with intent scoring and follow-up tasks, and quiet leads get an automated three-touch nudge inside Instagram's 24 hour messaging window. An AI DM sales agent is available as a paid add-on for the routine overnight questions. There is no WhatsApp broadcast, no bulk messaging and no email drip.
Is the AI DM agent included in the plan?
No, it is a paid add-on rather than part of the base subscription. The unified inbox, the lead pipeline with intent scoring, follow-up tasks and the three-touch nudges are the parts you get without it. Add the agent when the volume of routine overnight questions is genuinely costing you bookings.
Sources
- Meta, Instagram Platform, Messaging API: 24 hour window to respond, human agent tagging to send outside it checked 2026-09-10
- Meta, Instagram Platform overview: professional account requirement, Send API 100 calls per second (10 for audio and video), Conversations API 2 per second, private replies 750 per hour on post and reel comments checked 2026-09-10