Tidio Instagram Integration
Managing Instagram DMs through Tidio — setup, features, and what to expect.
Instagram has become a genuine customer service channel, especially for brands with a visual presence. Customers DM businesses with questions about products, orders, and availability -- and they expect quick replies. Tidio's Instagram integration routes those DMs into the shared inbox so your team handles them alongside chat, email, and other channels.
It is the newest and most limited of Tidio's social integrations, and setting expectations correctly matters.
What the integration does
When someone sends a direct message to your Instagram Business account, that message appears as a conversation in your Tidio inbox. Agents reply from Tidio, and the customer sees the response as a normal Instagram DM. The goal is the same as with Messenger -- consolidation into one workspace.
Beyond direct messages, Tidio also surfaces Instagram Story activity -- replies, mentions, and reactions added to your Stories show up in the inbox (each is toggleable in Settings). Comments on feed posts are handled separately and are not part of the core DM flow.
Setup
The setup routes through Facebook because Meta owns Instagram and requires the connection via your Facebook page:
- Ensure your Instagram account is a Business account. Personal accounts cannot use the Messaging API, and Creator accounts are not supported by the integration -- it has to be a Business account.
- Link your Instagram account to a Facebook page. This is done in Instagram settings or Meta Business Suite. If you already advertise on Instagram, this is likely already configured.
- In Tidio, go to Settings > Channels > Instagram.
- Connect via Facebook. Sign in with a Facebook account that has admin access to both the Facebook page and linked Instagram account.
- Authorize permissions. Tidio needs access to Instagram messaging.
The dependency on Facebook tripped some reviewers up. If your Instagram is not linked to a Facebook page, you need to do that first, which adds a step some users do not anticipate. Once the connection is established, new incoming DMs appear in Tidio within seconds.
Features
| Feature | Details |
|---|---|
| Reply to Instagram DMs | Two-way messaging from the Tidio inbox |
| Customer context | Instagram username and profile info in the conversation sidebar |
| Conversation assignment | Route Instagram conversations to specific agents or teams |
| Tagging | Tag and categorize Instagram conversations |
| Macros | Saved-reply Macros (Growth plan and above) work on Instagram conversations |
| Chatbot Flows | Basic text-based Flows can respond to Instagram DMs |
| Lyro AI | Available on supported plans for Instagram conversations |
Limitations
Instagram's Messaging API is more restrictive than Messenger's, and this shows in what Tidio can and cannot do:
- Voice messages and disappearing content. Instagram DMs support voice messages and disappearing (vanish-mode) content. These either do not appear in Tidio or show up as unsupported-content placeholders.
- 7-day messaging window. Following Meta's policy, you have up to 7 days to respond to an incoming Instagram message. After that window, you cannot message the customer until they re-initiate. (This matches Messenger; WhatsApp uses a shorter 24-hour window.)
- No post-comment management. Comments on feed posts are not part of the core DM integration. (Tidio does offer separate handling for Instagram and Facebook comment replies, but managing your full comment stream still belongs in Instagram's native tools or a social platform like Sprout Social.)
- More limited than web chat. The range of what you can do in an Instagram conversation from Tidio is narrower than web chat. No file attachments beyond images, no rich interactive elements, no pre-chat forms.
- API rate limits. Instagram's API has stricter rate limits than Messenger. During high-volume periods (a product launch, a viral post), there can be delays in messages appearing in Tidio.
Chatbot Flows on Instagram
Flows work on Instagram DMs but in a reduced capacity. Simple text-based automation -- greeting messages, FAQ responses, basic qualification questions with quick-reply buttons -- functions well. Customers see button options in the DM thread and can tap to respond.
What does not work well:
- Complex multi-step Flows with rich media (carousels, product cards) do not render properly in Instagram DMs.
- Triggers based on website behavior are irrelevant for Instagram conversations.
- Some Flow actions that work in web chat (opening a URL, embedding forms) are not supported in the Instagram DM context.
My recommendation: keep Instagram Flows simple. A greeting message, two or three FAQ buttons, and a handoff to a human agent is the sweet spot. Anything more complex risks a broken experience for the customer.
Who benefits
The Instagram integration is most useful for:
- Ecommerce brands with strong Instagram presence. If customers discover your products on Instagram and DM you about sizing, availability, or shipping, routing those conversations into Tidio keeps them in your support workflow.
- Small teams handling DMs manually. If someone on your team currently checks Instagram DMs separately, consolidating into Tidio saves time and reduces missed messages.
- Brands running Instagram ads with DM CTAs. Ads that encourage "Send a message" drive DM volume, and having those conversations land in Tidio means they get treated as real support tickets rather than social noise.
If Instagram is not a meaningful customer communication channel for your business, the integration is not worth connecting -- it adds clutter to your inbox without adding value.
Practical tips
Based on what I see working in reviews and case studies:
- Set up a greeting Flow. An automated "Thanks for reaching out, how can I help?" message with 2-3 common options (Order status, Product question, Other) sets expectations and routes conversations faster.
- Monitor response times closely. The 7-day messaging window is more forgiving than WhatsApp's 24 hours, but it is still a hard limit -- if Instagram DMs sit unanswered past it, you lose the ability to respond until the customer messages again.
- Train agents on context limitations. Instagram DMs lack the rich customer context available in web chat (no page history, no browsing data). Agents need to ask questions they might not need to ask in other channels.
- Do not over-automate. Instagram users expect a personal, conversational tone. Heavy-handed bot responses feel particularly off-putting in DMs compared to web chat. Keep automation light and hand off to humans quickly.
Review sentiment
Instagram integration gets less review coverage than Tidio's other channels, likely because it is newer and less widely used for support than chat or email. What I do see:
- Positive: Users who manage multiple social channels praise having everything in one inbox. "I don't have to check Instagram separately anymore" is the main win.
- Positive: Basic DM handling works reliably. Messages come in, replies go out, no drama.
- Negative: Users who expected full Instagram management (especially feed-post comment moderation) are disappointed to find the focus is DMs and Story activity rather than the whole account.
- Neutral: Most users treat it as a nice-to-have rather than a core feature. Few cite Instagram integration as a reason they chose Tidio.
Bottom line
The Instagram integration does the basics well -- it gets DMs into your shared inbox and lets agents reply without switching apps. For brands where Instagram DMs are a meaningful customer touchpoint, that consolidation has real value.
But go in with clear expectations. This is a DM-only, text-forward integration with the limitations that Instagram's API imposes. It is not Instagram management, it is not comment monitoring, and the automation options are narrower than web chat. For most Tidio users, it is a useful addition to an existing setup rather than a standalone reason to choose the platform.
For other channel integrations, see Messenger and WhatsApp; Tidio also routes Telegram into the same shared inbox. For the full integration list, see Integrations.