Live data from Postgres

Every tool call, conversation, booking, ticket and guardrail decision as it lands in the voicepilot schema. Chat with Layla in another window and watch rows appear.

Data source

Filled in automatically by ./start.sh. Otherwise paste the n8n "Live data feed" URL with your key.

Tool calls

Each row is one webhook from Layla through n8n into voicepilot.handle_tool(). blocked rows are server-side guardrails refusing a request.

Conversations

Written by the ElevenLabs post-call webhook 10 to 30 seconds after a chat or call ends. Open a row for the full transcript.

Callback queue

The single queue for every callback from every channel (voicepilot.callback_queue), with priority, SLA and an English summary. Work it from the Overnight page.

Leads, service requests and complaints

Sales leads (no verification needed), requests checked against the rules in SQL (refused rows are the resale NOC rule firing), and complaints, which can only be recorded and escalated.

Leads

Service requests

Complaints

Bookings

Maintenance tickets

Callbacks and transfers

WhatsApp and email outbox

Confirmations written by the tools for every booking, reschedule, cancellation, ticket and callback, in the customer's language. simulated means no provider is connected yet (see Setup → WhatsApp and email).

Documents sent

Website call-back requests

"Layla will call you" on the Crestline website: number checked (UAE and UK only, 3 per number and 10 per visitor per hour, a daily cap), one-time code by SMS, then an outbound call. Turn it off with VP_CALLBACK_ENABLED=false in .env.

Guardrail sessions

One row per conversation: which customer it is verified for and how (caller ID or name), failed lookups (locks at 3), tool calls (capped at 40) and blocked requests.

Customers

Demo CRM. Phone numbers and emails are masked in this feed.