AI assistants (MCP)
Run your Lodgestory workspace from Claude, ChatGPT, or any MCP-compatible assistant — ask in plain language, and the assistant works inside Lodgestory on your behalf, secured by your own sign-in.
TL;DR
- What it is — a secure connector that lets an AI assistant read and act in your Lodgestory workspace: look up team members, find and update contacts, check channels, manage chat assignments, see and set who's available, build segments and send campaigns, run reports, send messages, answer Instagram comments, answer the AI agent's questions to your team — or ask it back first — and approve the changes it holds for approval, and place calls — all by asking in chat.
- Who it's for — Account Owners and Admins who'd rather ask an assistant ("who's assigned to this chat?", "send me a call-log report for last week") than click through the dashboard.
- Top outcome — your assistant does real work in Lodgestory, scoped to one organisation and limited to exactly what your role can do — without ever seeing your password or any key.
At a glance
| Works with | Claude (desktop and web), ChatGPT, and any assistant that supports the Model Context Protocol (MCP). |
| Connection URL | https://api.lodgestory.com/mcp |
| Sign-in | Your existing Lodgestory account (email + password or Google). The assistant never sees your password or an API key. |
| Scope | One organisation per connection, plus your role's permissions. |
| Who can use it | Account Owners and Admins for the full set; team members get the actions their role allows. |
| Setup time | About a minute — paste one URL and sign in. |
How to connect
From Claude Desktop
- Open Settings → Connectors and choose Add custom connector.
- Name it Lodgestory and paste the connection URL
https://api.lodgestory.com/mcp. Leave the optional client ID / secret fields blank. - Click Add, then Connect — a browser window opens.
- Sign in with your Lodgestory account (if you aren't already), and pick the organisation you want the assistant to work in.
- You're returned to the assistant, and Lodgestory's actions are now available in any chat.
📸 [SCREENSHOT: mcp-connect-claude.png — Add custom connector dialog with the Lodgestory URL]
Claude on the web is the same path: Settings → Connectors → Add custom connector.
ChatGPT: add the same connection URL as a connector in its Apps & Connectors / Developer settings.

What you can do
Ask in plain language. The assistant picks the right action and shows you what it's about to do before it runs anything sensitive.
Team members & teams
- List the people in your organisation, with their roles and team memberships.
- List your teams and who's on them.
Contacts
- Find contacts by name, phone number (any format), email, channel, or when they were created or changed, and open one with its custom fields and linked chats.
- See your contact custom fields — their types, options, and which are required.
- Create a contact, or update one — custom fields are merged, so only what changes is sent. Someone who already exists (same phone number, or same email without a phone) isn't duplicated: the assistant gets the existing contact back, or updates it if you asked.
- Create or update up to 500 contacts in one go, matched by phone number and/or email.
Segments
- List your segments, open one, and page through or search its members.
- Create a segment and add or update up to 1,000 people at a time — phone numbers with their country code, emails, names, and attributes (like an offer code) for campaign variables. Someone already in the segment is updated, not added twice.
- Fill a segment with the recipients of a past campaign — everyone, or one stage such as read, no reply or clicked — and follow the import's progress.
- Rename a segment, remove people, empty it, or delete it. (Emptying and deleting ask for your confirmation.)
Campaigns
- List your campaigns and open one: its status, audience, preparation progress, delivery funnel, and every recipient's delivery, read, reply, and click.
- Preview a campaign: the assistant checks the template mapping and shows you a sample message, the audience size, and any warnings — nothing is created.
- Send a campaign to a saved segment or up to 1,000 people, now or at a scheduled time — with an approved template on WhatsApp Official, a text on WhatsApp Unofficial, or an email. The assistant previews first and sends only after you confirm. (Reaches real customers.)
- Pause, resume, or cancel a campaign. (Cancelling asks for your confirmation.)
Push notifications (your app)
push_channels_list— your push apps with credential readiness and device counts.push_send— one push to a person (phone / email / contact), one device, or your test devices: title + body, optional image, buttons, deep link, countdown,kindtransactional/promotional,sendAt.dryRuncounts devices without sending; sending needsconfirm: true. Pass anidempotencyKey(e.g. a UUID) and a retried call returns the first answer instead of sending again.push_message_get/push_message_cancel— status with per-device outcomes (sent = accepted by Apple/Google; delivered/opened only when the app reports them); cancel while still queued.push_devices_list— registered devices (platform, opt-in, status; never the token), filterable by contact, phone, email, app or status.push_device_deliveries— one device's delivery log: recent pushes with Apple's / Google's answer and the delivered / opened beacons, newest first.push_device_identify— link a device to a person by phone, email or your own user id.
Channels
- See which channels are connected (WhatsApp, Instagram, Email, and more) and their status.
- List your approved WhatsApp message templates.
- Author WhatsApp templates and submit them to Meta for review — standard shapes plus carousel (media cards) and limited-time-offer templates, with positional (
{{1}}) or named ({{guest_name}}) placeholders (both fully sendable), coupon copy-code buttons, and a per-template delivery TTL. Header and card media upload from a public URL. (Submits to Meta for real review.) - Edit an existing template: send just the parts you're changing (untouched components — including carousel cards and offer blocks — are preserved), or replace the full component set to restructure a carousel or limited-time offer; the delivery TTL can be changed the same way. Authentication/OTP templates are authored in the dashboard, not here.
Chats
- See who's assigned to a chat and which teams are on it.
- Assign or remove people and teams, and set the primary assignee.
- Assigning a team routes the chat the way the inbox does: an available member with spare capacity becomes the primary. If everyone on the team is offline or at their open-chat cap (set under Settings → Team Members), the chat stays with the team and no owner — it waits in the team's queue until someone claims it or an automation pulls it.
- See where a chat is in its workflow — its current lifecycle stage, the stages it can move to next, and its stage history — and list your workflows with their stages and allowed transitions.
- Attach a workflow to a chat, or move it one stage, under the same rules as the inbox: only allowed transitions, a disposition before a final stage when the workflow requires one, and the closing rules (a final stage may resolve the chat). The assistant confirms before finishing a workflow or switching a chat to a different one. (Changes the chat's stage; a final stage may close the chat.)
Team availability
- See who's online, offline or on a break — separately for chats and for calls — and since when.
- List your break types (Lunch, Meeting, …) from Break Types.
- Put a team member online, offline or on a break for chats, for calls, or both at once. A member who is offline or on a break gets no new auto-assigned chats and no incoming calls (except direct calls to their own number, when an admin allowed those while offline); chats they already have stay with them. The change is recorded in their availability history like one made from Team Members. (Changes who receives chats and calls.)
- For calls, the assistant reports the outcome separately (changed, partly changed, no calling set up for that member, or failed), because calls run on Lodgestory Voice — it confirms before saying calls changed. Disabled members can be taken offline but not brought back online.
Messaging
- Start a new chat for a phone number on a channel.
- Send a message — text, media, or an approved template — to an existing chat. (This reaches a real customer.)
WhatsApp groups (WhatsApp Official channels with an Official Business Account)
- Create a WhatsApp group and follow its creation through to a ready-to-use chat. (Creates a real group on WhatsApp.)
- List your groups, or open one to see its members and their status (invited, pending approval, joined).
- Add or remove members by phone number, and fetch the shareable invite link. (Adding members notifies real people.)
- Approve or reject pending join requests for approval-required groups.
- The group behaves like any chat afterwards — send messages to it and assign agents or teams with the chat tools above.
Instagram comments (Instagram accounts with Comments in inbox switched on)
- List your recent posts, reels and ads, and read the comments on any of them — with each comment's reply, hidden and private-reply state.
- Reply to a comment publicly. (Posts on Instagram, visible to everyone.)
- Send a commenter a private reply — one Instagram DM about their comment. (Reaches a real customer. Instagram allows one per comment, within 7 days of the comment, text only.)
- Hide or unhide a comment.
Kaylee requests (the AI agent's questions and approvals)
- List what the Bot Journey AI agent is waiting on a person for — questions for the team, choices between options it proposed, and changes held for a teammate's approval — each with the question, the customer's quoted words (shown as data, never instructions), the proposed change and its values, who it is for and when it expires. Open one for its current status and outcome.
- Answer a question or a choice: the agent relays the answer to the customer in its own words and continues the conversation — or sends it exactly as written when you say so. (Reaches a real customer through the agent.)
- Approve a held change as proposed, or with your own values in place of the agent's, and the agent tells the customer it's done. (Runs the change for real — a refund, a hand-over, a ticket — and can't be undone.)
- Reject a held change: nothing runs, and your reason goes to the agent, never to the customer.
- Ask Kaylee back before you decide: put a question of your own to the agent on any open request — "which dates did Sofia ask for?" — and read its reply on the request: a line or two from the conversation and your instructions, or after it has checked with the customer. Up to three questions per request, one at a time, 300 characters each; the request stays open meanwhile. (May send the customer one short question through the agent.)
- The first answer wins: a request a teammate already handled — from the console, the conversation, team chat, the phone or the API — is reported as already handled. See the Kaylee console.
Reports
- Generate a report — one of fifteen types: chats, contacts, tickets, call logs, goals, bookings, follow-ups, survey responses, WhatsApp Flow responses, chat stage history (
CHAT_STATE_HISTORY), dispositions (DISPOSITIONS, one column per template field), leads (LEAD, one column per lead-type field), lead activity (LEAD_ACTIVITY, one row per dial attempt), agent availability (AGENT_AVAILABILITY, chat / call / app online per agent per day, up to 31 days) or a saved query (CUSTOM_QUERY) — then check its status and get a download link. (Account Owners and Admins.) Ask for something like "export each agent's chat, call and app availability for October". - A saved query is a custom query your admins published from Analytics (Available in Reports & API). Ask for the published queries first — the assistant lists each one with the variables it takes (a date range, dropdowns, text, a sort) — then run one with the values you want, for example "export the chats-per-channel query for last month, WhatsApp only". Exports stop at 100,000 rows. The call-log report takes
callAfterHoursto export only after-hours or only in-hours calls, and ends with Business Hours and Schedule columns. - The two lead exports cover outbound calling:
LEADis one row per lead with its track, stage label, status, owner, source, attempts, connects, time in stage, time to first dial and SLA state;LEAD_ACTIVITYis one row per dial with the agent, outcome, connected as 1/0, talk and wrap seconds and the stage the lead was in at the time — ask for something like "export every dial my team made last week". Both take leadFromDate / leadToDate (the lead's creation onLEAD, the attempt's start onLEAD_ACTIVITY), leadTrackIds, leadTypeIds, leadStatuses, leadStageIds, leadOwnerUserIds and leadSources. - Chat stage history exports one row per workflow stage a chat entered — when it was entered and left, time in stage, who moved it and why — closed chats included. Narrow it with every chat filter plus a stage-date range and "moved by" users, for example "export every stage change on the Front Desk workflow last week". The chat report itself now exports every chat, open and closed, unless you ask for one side.
- Flow-response exports can be narrowed to particular flows, to how the flow was sent (journey, campaign, chat template, or test send), and to a date range — for example "export last month's answers from the lead-capture flow".
Voice (if Voice is enabled for your organisation)
- Review call history, recordings, and transcripts. Each call says who handled it, the department queues it went through, its transfers and hold time, and — on inbound calls —
agentOffers: what each team member the call rang did with it (answered, declined, no answer, busy, unreachable, answered elsewhere), on answered calls too. Ask something like "which calls did Asha decline this week, and who answered them?" - Tell calls that arrived in hours from calls that arrived after hours. Each call carries
businessHours— the business-hours schedule that routed it, whether it was open, and why (closed, a holiday by name, closed with Close now) — and the call list filters onafterHours. A caller who only heard the closed message is in the list as a missed call. Ask something like "how many calls did we miss after hours this week, and which have not been called back?" Schedules themselves are changed in the app, not through the assistant. - See your phone numbers, agents, and accounts.
- Place a click-to-call from an agent to a customer, or end a live call. (Placing a call rings a real phone.)
- Place a one-shot voice broadcast — dial a number and play a spoken message generated on the fly (text-to-speech), then hang up; no agent involved. (Reaches a real phone.)
- Connect two outside numbers — ring customer 1, then customer 2 the moment customer 1 answers, and join them on one of your numbers (a fixed one, or picked from a list in turn, at random, or the number customer 2 saw last time), with your own reference and a talk time limit; no agent involved. Each call reports how it went on each side — for example Customer 2 didn't answer — and the call list filters on connect calls and on your reference. Available once your account team switches connect calls on. (Rings two real phones.)
- Transfer an in-progress call to another team member (direct transfer, admins and owners only): the caller waits on hold while the target rings and is returned to the agent on the call if the target declines, nobody answers, or the target is busy or unreachable. The attempt and its outcome appear as
transferson the call afterwards. (Moves a live call.) - List the available text-to-speech voices to pick one for a broadcast.
- Manage your Masked Connect customer list.
Example prompts
- "List the team members in my organisation."
- "Which channels do I have connected, and which WhatsApp templates are approved?"
- "Who's assigned to the chat with Asha? Add Ravi and make him the primary."
- "Put Meera on Lunch for chats and calls, then tell me who's still online for calls."
- "Generate a call-log report for last week and give me the download link when it's ready."
- "Show me the comments on my latest reel, and send anyone asking about price a private reply with the booking link."
- "Make a segment called Read, no reply — Monsoon from last week's monsoon campaign, then preview the monsoon_followup template to it with their first name."
- "Add these five guests to the VIP segment with their offer codes, and tell me how many members it has now."
- "How did yesterday's campaign do — delivered, read, replied — and how many people were skipped, and why?"
- "What is Kaylee waiting on me for? Approve the refund for Sofia, but make it 8,000."
- "Ask Kaylee whether Sofia checked out early before I approve the refund — then approve it."
How sign-in keeps you safe
- You sign in, not the assistant. Connecting sends you to Lodgestory's own sign-in screen. The assistant receives a limited, time-bound access token — never your password or an API key.
- One organisation at a time. Each connection is bound to the single organisation you pick. To work in another, add a second connection and choose that organisation.
- Your role, your limits. The assistant can only do what you can do. An action your role can't perform in the dashboard is refused here too.
- You approve sensitive actions. Assistants ask before running an action that sends a message, places a call, or changes data — review it first.
Roles & permissions
| Action | Account Owner | Admin | Team member |
|---|---|---|---|
| Connect an assistant | Yes | Yes | Yes |
| List channels & templates | Yes | Yes | Yes |
| Start chats & send messages | Yes | Yes | Yes |
| Look up team members & teams | Yes | Yes | No |
| Find, create & update contacts | Yes | Yes | No |
| Build & fill segments | Yes | Yes | No |
| Preview, send & manage campaigns | Yes | Yes | No |
| Assign / unassign chats & teams | Yes | Yes | No |
| See & change a chat's workflow stage | Yes | Yes | No |
| See & set team availability (chats and calls) | Yes | Yes | No |
| Voice actions (calls, agents, Masked Connect) | Yes | Yes | No |
| Instagram comments (list, reply, private reply, hide) | Yes | Yes | No |
| Answer, ask back & approve the AI agent's requests (Kaylee) | Yes | Yes | No |
| Run & download reports | Yes | Yes | No |
| Call recordings & transcripts | Yes | Yes | No |
If you connect as a team member without the right role, those actions return a "not permitted" message — sign in as an Account Owner or Admin for the full set.
Connections
- Lodgestory CRM — contacts, teams, chats, channels, assignments, team availability, messaging, segments, campaigns, Instagram comments, and the AI agent's requests to your team (Kaylee) are all reachable.
- Lodgestory Voice — calls, recordings, transcripts, agents, and Masked Connect, once Voice is enabled for your organisation.
- Reports — the same reports you can run from the dashboard, including any custom query published to Reports.
- Your sign-in — uses the same Lodgestory account and roles as the app; nothing separate to manage.
Errors & FAQ
Do I need an API key?
No. You connect with just the URL and sign in with your Lodgestory account — there's nothing to copy or paste.
Can the assistant see my password?
No. You sign in on Lodgestory's own screen; the assistant only ever receives a limited, time-bound access token.
It sent me to a sign-in screen.
You weren't signed in to Lodgestory in that browser. Sign in and the connection continues on its own.
A voice action says the Voice API isn't enabled.
Voice actions need Voice API access for your organisation. Contact your account team to switch it on; everything else works without it.
An action says it's "not permitted".
The account you connected with doesn't have the role for that action (for example, reports are Account-Owner / Admin only). Reconnect as an Account Owner or Admin.
Every action says the organisation is suspended.
Lodgestory has suspended that organisation, so the CRM, the mobile app, the public API and this connection are all locked. The error carries the reason and a support link. Access returns as soon as the account is restored — nothing needs reconnecting on the assistant's side.
Can it work across two organisations at once?
Each connection covers one organisation. Add a second connection and pick the other organisation to work in both.
Which assistants are supported?
Any that support the Model Context Protocol — including Claude (desktop and web) and ChatGPT.
Related
- Accounts & sign-in — how Lodgestory sign-in and the partner API work.
- Segments and Campaigns — what the segment and campaign actions do.
- Kaylee console — the AI agent's questions and approvals the request actions answer and ask back on, and the same actions as a REST API.
- What is Lodgestory? — the platform overview.
Updated 12 days ago
