Ring an agent and bridge the customer, dial a number and speak a personalised message with an AI voice, or connect two outside numbers so neither sees the other's real number. Every call is recorded, transcribed and pushed to your systems as webhooks.
Click-to-call, broadcast, connect ✦ IVR Studio with mid-call API lookups ✦ Recordings and transcripts by webhook
The most guest-obsessed brands trust Lodgestory to power 50M+ conversations a year
POST /voice/{organisationId}/calls/connect rings customer 1, rings customer 2 the moment customer 1 answers, and joins them on one of your Lodgestory Voice numbers. Both see your business number, never each other's. Pick the caller id per call: your default, one from a list in turn or at random, or the number customer 2 saw last time.


Click-to-call from an agent to a customer, or a voice broadcast that speaks a message in the voice you pick.
IVR Studio: play, collect digits, condition, business hours, caller lookup, Fetch data from your own system, send WhatsApp, route anywhere. Versions and a simulator.
call.answered, call.completed, call.missed, call.recording_available and call.transcript_available, with queues, transfers, hold time and whether it arrived in hours.
A flow is a diagram of steps: play a prompt, collect digits, check a condition, look the caller up, fetch data from your API while they wait, send a WhatsApp, then route to a department, an agent, a classic menu, voicemail, an AI agent or another flow. Every publish is a numbered version; the live version keeps answering while you edit, and a built-in simulator runs the draft against a pretend caller with your API calls live or mocked.
Create an organisation, enable Developer Access and run your first request against your own workspace today.
What engineering teams ask before they integrate.
POST /api/wp-crm/voice/{organisationId}/calls with an agentUserId from GET /voice/:org/agents and the destinationNumber. The agent rings first; the customer is bridged when they answer.
Yes. POST /voice/{organisationId}/calls/voice-broadcast with the destination number, a voiceId from GET /voice/:org/voices and the message text. It dials, speaks the message with an AI voice and hangs up.
POST /voice/{organisationId}/calls/connect joins two outside numbers: customer 1 is rung first, customer 2 the moment they answer, on one of your business numbers so neither sees the other's real number. It is switched on per organisation by your account team and placed only from the API or an AI assistant.
Yes. IVR Studio's Fetch data step calls your endpoint while the caller waits and the flow uses the answer: read it back in a real voice, branch on it, or route the caller already identified. The simulator runs your API live or mocked.