Tickets that stay in step with your CRM
A ticket moves in Lodgestory and the deal, case or contact moves in HubSpot or Salesforce. Every message and call logs as an activity on the record, and signed webhooks carry the same events to any system you run.
HubSpot and Salesforce ✦ 40 signed webhook events ✦ API and MCP both ways
Riya SharmaThe most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
BBingo Hotels
Every ticket event, signed and delivered
Register an HTTPS endpoint, choose the events you care about, and Lodgestory sends a signed notification within seconds of each one. Tickets fire ticket.created, ticket.status_changed and ticket.assigned; the same envelope carries messages, contacts, chat lifecycle, campaigns, calls, leads and the AI agent's requests to your team. Deliveries are retried and logged, and you can replay any of them.
- HMAC-SHA256 signatures on every delivery, with an X-Webhook-Event header so you can route before parsing.
- Up to 30 endpoints per organisation, 30 custom headers each; failing endpoints pause automatically.
- Zapier's instant triggers connect through the same endpoints.
Three ways the CRM and the inbox stay aligned
Match the contact, not just the number
Contacts from WhatsApp, email and SMS are matched or created in the CRM with channel, source and conversation tags, so a returning guest is one record there too.
Map stages to stages
Ticket stages map to HubSpot deal stages or Salesforce cases. Move a ticket to Qualified and the deal updates; resolve a case and the ticket follows.
Log the whole conversation
Every message, call note and email becomes an activity on the contact timeline, with channel, timestamp and agent, so sales reads what support said.
Your fields, their properties
Map Lodgestory fields to CRM properties once: ticket category to deal type, CSAT score and first response time to custom properties, campaign tags to contact properties for attribution. Choose one-way or bi-directional sync and how conflicts resolve, then send a test message and watch the contact and activity appear.
- Salesforce Service Cloud. Cases from WhatsApp and email, worked in either tool, kept in sync.
- Custom objects. Industry-specific records in Salesforce mapped from Lodgestory data.
- Zapier and the API for every CRM without a native connector.
Ready to stop copying tickets into the CRM?
Connect HubSpot or Salesforce, or point a webhook at your own system, and watch the first ticket land.
Questions, answered
HubSpot and Salesforce have integrations: contacts are matched or created with the channel and source, conversations and calls log as activities on the contact, tickets map to HubSpot deals and tickets or Salesforce cases, and custom properties such as CSAT or first response time can be mapped for reporting. Anything else connects through signed webhooks, the partner API or Zapier.
A signed POST with one envelope for every event. For tickets: ticket.created when a ticket is filed by hand, by a bot journey or through the API; ticket.status_changed on a genuine open to resolved transition with the previous status; ticket.assigned when the assignee changes, including unassignment. Forty event types cover messages, contacts, chat lifecycle, campaigns, calls and more.
Every delivery is signed with HMAC-SHA256, retried automatically, and recorded in a delivery log you can inspect and replay. An endpoint that keeps failing is paused rather than hammered. You can register up to thirty endpoints per organisation with up to thirty custom headers each.
Yes. The partner API creates, lists, updates and bulk-operates tickets, so your CRM can open a ticket in Lodgestory when a case is raised there, and the same operations are available to AI assistants through MCP.