Your LinkedIn page, answered by a team
Messages to your company page and your members' own DMs land in the same queue as everything else. Assign them, route them, brief a colleague in a note and see who replied, instead of sharing one admin login and hoping.
Page inbox and member DMs ✦ Same routing as every channel ✦ One contact, one timeline
Riya · Sales
Maya · SupportThe most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
BBingo Hotels
One login, several inboxes, each its own channel
A LinkedIn login usually exposes more than one inbox: the person's own messages plus every company page they administer. Connect the ones your team should answer. Each becomes a channel card on the Connections page with its own status, its own bot journey and its own routing.
- Company pages for a team. Page messages reach a shared queue instead of one admin's login.
- Founder and sales DMs. Inbound DMs to the people who sell land beside everything else, so nothing is missed between channels.
- Senders by URN. On the API and in webhooks a LinkedIn sender is a LinkedIn profile or company URN, not a phone number.
This login can see three inboxes. Choose the ones your team should answer.
Channels
What changes when LinkedIn joins the inbox
Share the page without sharing a login
Assignment, team routing and internal notes on every LinkedIn thread. Who replied, and to whom, is visible to the whole team.
Keep one history per contact
A prospect who messages the page and later writes on WhatsApp is one record with one timeline, not two threads in two tools.
Reuse what you already built
Bot journeys, routing rules, AI replies and reports run on LinkedIn exactly as on WhatsApp or email. Nothing is configured twice.
The page message and the WhatsApp message are the same person
A contact's LinkedIn thread sits on the same record as their WhatsApp, email and call history. Sales sees the first question from LinkedIn, support sees the booking that followed on WhatsApp, and nobody asks the guest to repeat themselves.
- Same guest panel, with the booking, labels, tickets and notes beside the LinkedIn thread.
- Same webhooks. message.received carries channel_type linkedin and the sender's URN.
- Same reports. LinkedIn threads count in response times, resolution and the Agents table.
RKRohan Kapoor · one record
Ready to take LinkedIn out of one person's login?
Connect the page, route it to the team and answer the next message from the inbox.
Questions, answered
Both inbox types a LinkedIn login exposes: a member's own messages and every company page they administer. Connect the ones you want and each becomes its own channel in the inbox, next to WhatsApp, Instagram, Messenger, email and web chat.
A page inbox sits behind one admin's login with no assignment, no routing and no internal notes, so teams lose track of who replied. In Lodgestory it is a channel with a team behind it: route it to sales or support, see who owns each thread and brief colleagues in notes.
Yes. Someone who writes to your page on LinkedIn and later messages on WhatsApp is one contact with one history. On the API and in webhooks the LinkedIn sender is identified by their LinkedIn URN rather than a phone number.
LinkedIn conversations flow through the same bot journeys, routing rules, AI replies and reports as every other channel. There is nothing LinkedIn-specific to configure twice.