🤖 AI & Transcription
Powers lead scoring, call summaries, funnel analysis📱 RingCentral
Calls, recordings, SMS, click-to-call, live presenceRegisters the webhook so RingCentral pushes calls + SMS to the dashboard in real-time.
Pulls past calls from RingCentral so the dashboard has data immediately.
✉️ PlusVibe
Lead intake — incoming leads are verified with this secretWebhook URL: https://mcp.lorphic.app/api/webhooks/plusvibe
Status: Checking…
📧 Email Delivery (SMTP)
For alerts: new interested leads, daily digest💬 Auto-SMS Playbooks
Text interested leads a message matched to their campaign
When PlusVibe marks a lead interested, the CRM picks the first matching playbook and
queues a text. Matching runs campaign ID → campaign name → default, so
relaunching the same offer under a new campaign keeps working as long as the name still
contains the pattern (e.g. 99$).
Messages are held outside quiet hours and sent once per lead, ever.
Used for every automated text unless a playbook overrides it.
Local time for the lead — worked out from their area code, falling back to the default timezone. A lead who replies at 2am is texted at 8am their time, not yours.
You run many PlusVibe campaigns but sell a small number of things. A product owns one message and one rep, and picks up every campaign whose name contains one of its terms — so relaunching “99$ … August” next month needs no setup. The rep who texts a lead also becomes its owner.
Computed by the same logic that runs at intake — if it says a campaign is uncovered, it genuinely is.
Per-campaign overrides
Only needed when one specific campaign must differ from its product. These win over the product's message.
Used for any campaign without its own message above — including brand-new ones. Set this first so no interested lead is ever missed.
Advanced — pattern rules & raw playbooks
A pattern rule matches on campaign name, so a relaunch under a new campaign ID is
covered automatically — e.g. a rule containing 99$ catches both
“99$offer … 18June” and “99$ … 20 July”. Campaign-specific messages above always win over a pattern rule.
🎙️ AI Voice Answering
Answers calls a rep couldn't takeRingCentral forwards unanswered and after-hours calls to a voice-AI platform. That platform holds the conversation and calls this CRM to find out who's ringing, what they bought interest in, and to book a callback. Nothing here places calls itself — it supplies the knowledge and records the outcome.
Neither RingCentral nor this CRM had any hours defined — the AI needs them to know when you're closed.
Create a shared secret, then paste it and these URLs into Vapi / Retell / Bland (or whichever you pick). The endpoints reject every request until a secret exists.
The agent is given these entries on every call. Tag an entry with a product term
(e.g. 99$) and it's marked as most relevant when that lead calls.
Be specific about pricing — a thin knowledge base is what makes an AI improvise.
🤖 Lead Automation
Auto-create leads + rep assignmentAuto-create Leads — captures unknown callers as leads automatically.
Lead Assignment — shows assignee dropdowns, "My Leads" filter, and bulk-assign. Disable when you have a single rep (simpler UI). Re-enable when you add more reps.
🗄️ Call Recording Retention
How long call audio is kept on the server
Only the audio file is deleted. The call record, its transcript and any AI
summary are kept permanently — so the lead's history stays intact and searchable, you just
stop storing the raw recording.
Cleanup runs once a day. Retaining customer call audio indefinitely is a privacy decision as
much as a storage one.
📥 Import Leads (CSV)
Bulk add leads from a spreadsheet exportPaste CSV with a header row. Columns are auto-detected (First Name, Last Name, Phone, Email, Company).
🔧 Data Tools
Transcribe, backup, export👤 My Account
📥 Inbound Email Replies (IMAP)
Files lead replies into the timeline
Leave these blank to derive them from your SMTP settings (smtp. → imap., port 993).
Gmail: use imap.gmail.com port 993 with a 16-character App Password,
and make sure IMAP is switched on under Gmail → Settings → Forwarding and POP/IMAP.
🔑 Google Sign-In
Let your team log in with their Google account
Only people who already have a Lorphic account can sign in with Google —
it verifies who someone is, it doesn't create accounts. Add users under User Management first.
Email + password login keeps working either way.
In Google Cloud Console → Credentials,
create an OAuth client ID of type Web application, then add this exact
Authorized redirect URI:
…
🔐 MCP Endpoint Security
Who can reach /mcp
The MCP endpoint is read-only — it can look up leads, calls and transcripts,
but it cannot send SMS or email or change a lead. Sending stays in this dashboard.
Turning enforcement on requires every MCP client to log in through this dashboard first.
Your connected Claude client will need to re-authorize once when you flip it.
While it is off, the server logs whether each caller would have been allowed —
check those logs before switching over.