LinkedIn and Lodgestory
Your LinkedIn conversations, in the same inbox as every other channel. Member DMs and company Page inboxes arrive in seconds, with assignment, routing and one timeline per contact.
LinkedIn DMs and company Page inboxes in your shared team inbox
The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
BBingo HotelsBBingo HotelsBBingo HotelsBBingo HotelsHow LinkedIn fits into the inbox
LinkedIn is where most B2B conversations start, and its native inbox was not built for teams — there is no assignment, no routing, and no shared view. Lodgestory's LinkedIn integration brings both kinds of LinkedIn inbox into your shared inbox: a member's own direct messages, and the inbox of any company Page they administer. Each inbox becomes its own channel, so a Page's conversations can be routed to a different team than an individual's.
You connect a LinkedIn login and choose which of its inboxes to bring in — the member's own messages, and any company Pages that login administers. Each one you pick becomes a channel in Lodgestory. New messages arrive within seconds and appear in the shared inbox next to WhatsApp, Instagram, Messenger, email and voice, with the full history on one contact timeline. Replies you send from Lodgestory appear in LinkedIn as the member or as the Page, depending on which inbox the conversation belongs to.
- 01Open Connections. In Lodgestory, go to Settings > Connections and choose Connect a channel > LinkedIn.
- 02Sign In to LinkedIn. Enter the LinkedIn login whose inboxes you want to bring in. LinkedIn usually asks for a verification code the first time; enter it when prompted.
- 03Choose Which Inboxes. Lodgestory lists the member's own inbox plus every company Page that login administers. Pick the ones you want — nothing is connected automatically.
- 04Route and Assign. Each inbox is now a channel. Point it at a team, add routing rules, and set who is responsible for replies.
- 05Reply From the Inbox. New conversations appear in the shared inbox within seconds. Replies go out as the member or as the Page, depending on the inbox.
Member DMs and Page Inboxes
Both LinkedIn inbox types in one place. A single login often exposes several — a person's own messages plus every company Page they administer — and each becomes its own channel.
Member DMs and Page Inboxes
Both LinkedIn inbox types in one place. A single login often exposes several — a person's own messages plus every company Page they administer — and each becomes its own channel.
A Real Shared Inbox
Assignment, routing rules, internal notes and one timeline per contact. LinkedIn's own inbox has none of this, which is why teams lose track of who replied to whom.
A Real Shared Inbox
Assignment, routing rules, internal notes and one timeline per contact. LinkedIn's own inbox has none of this, which is why teams lose track of who replied to whom.
Beside Every Other Channel
LinkedIn sits next to WhatsApp, Instagram, Messenger, email, SMS and voice. One contact who messages on two channels is one conversation history, not two.
Beside Every Other Channel
LinkedIn sits next to WhatsApp, Instagram, Messenger, email, SMS and voice. One contact who messages on two channels is one conversation history, not two.
Replies in Seconds
Messages arrive by live push rather than a slow refresh, so a conversation in the inbox keeps pace with the one happening on LinkedIn.
Replies in Seconds
Messages arrive by live push rather than a slow refresh, so a conversation in the inbox keeps pace with the one happening on LinkedIn.
Page Reply Rules, Surfaced
LinkedIn only lets a Page reply to members who messaged it first. Lodgestory shows that state on the conversation instead of letting an agent write a reply that cannot be sent.
Page Reply Rules, Surfaced
LinkedIn only lets a Page reply to members who messaged it first. Lodgestory shows that state on the conversation instead of letting an agent write a reply that cannot be sent.
Works With Your Automations
LinkedIn conversations flow through the same bot journeys, routing rules and AI replies as every other channel — no separate setup.
Works With Your Automations
LinkedIn conversations flow through the same bot journeys, routing rules and AI replies as every other channel — no separate setup.
In practice
How teams use LinkedIn with Lodgestory
Company Page Inbox for a Team
Messages to your company Page reach a shared queue instead of sitting behind one admin's login. Route them to sales or support and see who replied.
Founder and Sales DMs
Inbound LinkedIn DMs to founders and account executives land in the same inbox as everything else, so nothing is missed between channels.
One Timeline Per Contact
Someone who messages your Page on LinkedIn and later writes on WhatsApp is one contact with one history, not two disconnected threads.
Ready to connect LinkedIn?
Connect it in Settings today, or ask us to set it up with you during onboarding.
Questions, answered
What teams ask before connecting LinkedIn.
Yes. A company Page inbox is fully supported and is the main reason most teams connect LinkedIn. When you connect a login, Lodgestory lists every Page that login administers and you choose which ones to bring in. Each Page becomes its own channel, so it can be routed and assigned separately from anyone's personal messages.
No, and this is LinkedIn's rule rather than a Lodgestory limitation. A company Page can only reply to members who have messaged the Page first. Lodgestory shows that state on the conversation, so an agent sees it before writing rather than after a send fails.
LinkedIn only exposes a Page inbox to its super admins and content admins. The login you connect has to hold one of those roles on the Page, otherwise the Page will not appear in the list of inboxes to connect.
Within seconds. Lodgestory holds a live connection to LinkedIn for each connected login, so a new message is picked up as it arrives rather than on a slow refresh cycle. A scheduled check runs underneath as a safety net.
Yes, and that is the point. LinkedIn's native inbox has no assignment, routing or internal notes, so teams sharing one lose track of who replied. In Lodgestory each connected inbox is a channel with a team, routing rules, notes and one timeline per contact.
No. Lodgestory is a shared inbox for conversations people start with you. There is no connection-request sending, no sequences and no bulk messaging on LinkedIn — broadcast campaigns are deliberately not available on this channel.
LinkedIn is one more channel in the same inbox as WhatsApp, Instagram, Messenger, email, SMS and voice. The same routing, assignment, bot journeys, AI replies and reporting apply, so there is nothing LinkedIn-specific to learn or configure twice.