Phone, email, web form, chat. Qualifies real buyers, books meetings, filters the noise.
Fast inbound teams get punished by bad leads. LUPO triages the noise before it hits sales.
Other companies selling into your demo forms, phone lines, and chatbot. Politely declined, logged, and never routed to sales.
Existing customers and account issues arriving through sales channels. Routed to the right team with the original conversation attached.
Visitors who start a chat, submit a form, or reply once and disappear. Followed up through the channel they used until qualified or closed out.
Real interest, wrong company size, use case, geography, or timing. Handled appropriately without taking AE time.
Inbound comes in via call, form, or chat. Qualified buyers land in your CRM, your team's Slack, and on a rep's calendar. Noise gets filtered before sales sees it.
Connects to your stack
LUPO works with any chat, form, or website workflow that can send a webhook. Intercom, Drift, HubSpot Chat, custom forms, and internal routing tools can all hand qualified conversations into LUPO.
Not every form is a demo request. LUPO matches the response to the channel based on your policy: instant callback, thoughtful email, or live chat.
Picks up on the second ring, qualifies the caller against your policy, captures buying intent, checks live availability, books real appointments, and escalates to a human when the policy says so.
Classifies the submission, enriches context where it can, and decides whether to email, call back, post to Slack, book a meeting, or hold the lead for human approval. No blanket callbacks to senior buyers.
Takes intent and consent from your existing chatbot (Intercom Fin, Drift, HubSpot Chat, or a custom widget), continues qualification, and books inside the same conversation when the buyer is ready.
For leads that need email rather than an immediate call. Per-org sender domains, audience filters, and reply handling are tuned to your stack.
Every interaction becomes a structured packet: buyer context, qualification, routing decision. Reps don't join blind. Managers get the audit trail.
acme-corp#inbound-qualified in SlackTranscript, message log, and the policy decision behind every step are attached for audit.
Conversica nurtures by email. Intercom is a chatbot. LUPO is the one agentic brain that handles every inbound channel, phone, email, web form, and chat, with consistent context across them. Most teams run LUPO alongside their existing chat tool, not instead of it.
What counts as qualified. When LUPO must escalate. Who signs off before a booking. Co-authored with you in week one; yours to own from there.
Co-authored with you in week one: what counts as qualified, wrong-fit, support, vendor, or human review. Yours to own, tuned from real inbound.
Applies your routing policy and alerts the right Slack channel for each lead. Per-rep round-robin, territory ownership, and account-owner routing are tuned to your sales motion.
Hold uncertain or high-value leads for manual review instead of letting LUPO commit to risky decisions.
Every call, form, and chat gets a summary, message log, decision, and the next action LUPO took.
When LUPO is unsure, it asks a clarifying question, escalates to a named rep, or holds for approval. It never forces a booking.
Sales policy, routing rules, CRM fields, and qualification criteria are tuned for your business in week one.
Pick a channel. See what LUPO does with it. Nothing booked, nothing in your CRM.
Have a real 60-second voice conversation with LUPO right from this page. Ask it to qualify a fake lead and book a meeting.
Three example form submissions and the action LUPO would take with each: a vendor pitch, a support request, and a qualified buyer.
name: Pat Vendor company: VendorTools message: "We have an AI tool to help your SDRs…"
→ Vendor pitch. Auto-declined. Logged. Never routed to sales.
name: Alex Existing message: "My calls are dropping at 4pm GMT…"
→ Support leakage. Routed to #cs-tier-1. Sales not notified.
name: Jane Roe · VP RevOps company: Acme Corp (850) message: "Replacing our existing triage vendor…"
→ Qualified. No surprise call. Meeting offered · HubSpot deal created. Slack alert posted to #inbound-qualified.
See what an Intercom Fin or custom chatbot posts to LUPO when it hands a qualified visitor across, and what LUPO does with it.
{
"external_session_id": "intercom-conv-789",
"source": "intercom-fin",
"consent_to_call": true,
"message_log": [
"Visitor: looking for an inbound SDR tool",
"Fin: 60 SDRs, US + UK, eval Q3",
"Visitor: yes, happy for a call"
]
}
{
"status": "qualified",
"chat_session_id": "4df9…",
"callback_status": "queued",
"policy_applied": "consumer_callback_with_consent"
}
Voice runs on production speech infrastructure (Deepgram transcription, ElevenLabs voices) and Vapi as the runtime.
Encryption in transit, controlled access to customer data, no training on your data. A signed GDPR Data Processing Agreement is available on request. Formal SOC 2 / HIPAA attestations will be sought as the product matures.
AI disclosure on every call. Every decision logged with reasoning. Uncertain calls escalate to a human. Built around the EU AI Act.
Pre-agreed success metric written into the contract. Runs alongside your existing flow, not as a replacement. Short term, easy exit, only continues if we earn it.
Plain answers. LUPO is the inbound qualification layer, not a chatbot, not a rep replacement.
No. LUPO is an inbound qualification layer across calls, web forms, chat handoffs, and email. Chat is one intake channel of four. LUPO does not replace your chat widget. Your existing chatbot (Intercom Fin, Drift, custom) hands off to LUPO when a visitor is ready.
Sub-2 minutes median time-to-first-action on qualified inbound, measured. Your own number is visible in the dashboard from week one, so you don't have to take our word for it. The research benchmark is 5 minutes (Oldroyd et al, Harvard Business Review 2011: response in 5 min = 21x more likely to convert). LUPO clears it on every qualified lead.
Vendor pitches are politely declined and logged, never routed to sales. Existing-customer support requests are routed to the right team with the original conversation attached. AEs see only the buyers worth their time.
Yes. We're London-based and set up to run pilots on your timezone, with contracts in USD or GBP. The GDPR posture is a feature, not a bug, if you have European customers or employees.
Live integrations today: HubSpot and Salesforce CRM sync, Slack alerts, Google Calendar booking, voice qualification, Web Form Qualification, and Agentic Email Qualification. Microsoft 365 / Outlook calendar ships Q3 2026. Any chat, form, or workflow that can post a webhook can hand off to LUPO; HubSpot Chat is supported with HMAC signing. Additional CRM and calendar connectors light up on request.
A short product walkthrough showing how LUPO captures inbound demand, qualifies it against your sales policy, routes the right leads, and gives reps clean context before a meeting ever hits their calendar.