Lead routing & ownership
Website and form leads route to a client brand and a closer — not a shared spreadsheet waiting for someone to claim them.
Ledrix CRM features start with the pain: mixed leads, a closer in the wrong book, a chargeback on the wrong Stripe account. Then the fix: brand isolation, merchant routing, a seller panel that only shows assigned records, and a portal so clients stop asking for updates.
If your current stack looks like the left column, a chargeback is already sitting on the wrong brand.
If a CRM mixes client companies, shares one merchant, or lets closers browse the whole shop — you will keep reconciling in a spreadsheet. Ledrix ships the split they need.
Website and form leads route to a client brand and a closer — not a shared spreadsheet waiting for someone to claim them.
Assigned book only. Follow-ups on the deal. Commission-only closers cannot browse the agency’s full lead database.
They say yes — you send Stripe or PayPal from the lead card under that client’s own account, not a shared default.
Stop stuffing every LLC into one CRM. Keep Client A’s leads and money away from Client B — same agency workspace, clean split.
Real agency workspace — no credit card. Isolate a brand, assign a closer, send Stripe or PayPal under that client’s keys.
Start 14-day free trial — no card
Full CRM access. Cancel anytime. No card.
Start 14-day free trial — no card Watch 60-sec demoLead routing, clear ownership, and a seller panel that only shows their book — the pipeline closers live in.
Website and form leads land on a specific closer and brand while they’re still hot. Notes and history stay on the lead — so you never ask “who owns this?”
Your assigned leads, follow-ups, and the payment link on that deal. No bloated admin CRM. Nobody cherry-picks someone else’s book.
No “I thought you had it.” Activity sits on the opportunity — not in someone’s head or a group chat.
Drop a lead script on your site or POST to the lead API. The lead still lands on a closer and a brand — not an inbox.
On eligible plans, intake can score a lead as real vs junk before a closer wastes a dial. It is a classifier — not a bot that writes emails. The same classifier is available as /api/v1/leads/classify when API access is on — see Integrations.
When a client is already on the books, open a renewal from the order instead of starting a new pile in a sheet.
Stripe or PayPal from the lead card — generated on that brand’s merchant, not a shared agency default.
Generate Stripe or PayPal inside the lead card under that client’s merchant keys. No hop to a shared billing login mid-close.
Quote to paid stays on the order. Closers and clients can see whether it landed.
Staged cash when a project needs more than one invoice. On eligible plans.
Generate the invoice on the deal you’re already in. On eligible plans.
Stripe and PayPal refund and dispute events land back on that client’s payment — so a chargeback is not a surprise Slack thread against the wrong brand. On eligible plans.
Paid and failed updates hit the CRM from Stripe or PayPal. Closers don’t refresh another dashboard to ask “did it land?”
This is why agencies stop stuffing every LLC into one CRM. Each client brand keeps its own pipeline and merchant. You still run one workspace — and another company on Ledrix cannot open it.
Client A’s leads stay with Client A. Client B’s money stays on Client B’s merchant. Closers don’t trip over another LLC’s book. Admins see every brand in this agency — not every tenant on Ledrix.
Every workspace is isolated from every other company on the platform. That scoping is live on day one. Agencies that need a dedicated CRM database for a workspace can request one — we provision it for that tenant.
How isolation works · Try Basic free
Their orders, invoices, tickets, and progress — so they stop chasing the agency, and you stop forwarding screenshots from the wrong brand.
Clients see their own invoices and payment history. They don’t see other buyers.
When your team opens a project, they can check status and tasks in the portal. They can also message the assigned seller — a human thread, not a bot.
Clients open support tickets from the portal. Your closer, project manager, and admins get the mail — plus deadline reminders. Chat stays on the order; it doesn’t duplicate as email.
For agencies reselling the workspace to their own clients. Buyers should feel they hired you, not Ledrix.
Resell the workspace under your agency’s name: clients and closers land on your hostname, not Ledrix. White-label the client portal under the agency’s own domain. You set the hostname and verify DNS in Organization. Eligible plans can also replace the Ledrix logo. Available on plans that include custom domains.
Pipeline stats, routing, and team seats stay here — so closers stay in the seller panel and keep dialing.
Leads, orders, cash collected, and closer performance for the brands in your workspace.
Brands, users, routing, and payment accounts. Finance logins can be limited to payouts — they don’t run the full CRM.
Leaderboard, performance views, and bonus tracking on eligible plans. Closers still don’t get the admin database.
Invite admins and finance from the workspace. Sellers and clients are created by your team — trial signup is the org owner.
Optional two-factor on admin and seller logins. Lead-view activity on the Admin dashboard (who opened which lead). Org audit log plus a ZIP export you request with a reason. Security page.
Self-serve plan change and Stripe customer portal for the workspace subscription. That’s how you pay Ledrix — not how your buyers pay you.
Sees
Does not see
Sees
Does not see
Sees
Does not see
Some teams also use a project-manager or finance login. Those stay narrower than admin — not a second full CRM.
Admin-only historical sales import. Map your CSV. Preview. Commit. Closers pick up real contacts, orders, and payments — not a blank pipeline.
Upload any sheet. Map headers to lead, order, payment-link, and payment fields. Save the map so the next import is faster.
One row can create the cascade a closer needs: contact, order, payment link, and payment — only from data that is actually on the sheet. Nothing is invented.
See duplicates, unmatched brands, and what will be created. Choose merge, skip, or create-new — then commit or roll back the batch.
Import one brand at a time, or map a brand column on plans that allow multi-brand import. Limits follow your subscription.
For the technical buyer: tokens, /api/v1, outbound events, and inbound payment webhooks — closers still get a named lead.
Embed a brand script on your site. Form fields map into Ledrix. The lead still routes to a closer.
/api/v1
On plans with API access, Organization → API tokens issues a Bearer / X-Api-Token.
Pull company, membership, invoices, and usage from /api/v1.
POST website leads to the public lead API — they still route to a closer and a brand.
/api/v1/leads/classify is the same real-vs-junk classifier as Lead scoring, callable from your stack.
Revoke a leaked token from the same screen.
Organization → Webhooks: add your HTTPS URL and secret. Ledrix POSTs HMAC-signed events (for example invoice paid, membership activated) so your ERP or Zapier does not poll. Separate from that: Stripe and PayPal payment webhooks write paid, failed, refund, and dispute back onto the order — see Payments.
Tell us your identity provider. We turn on OIDC sign-in for CRM admins and, if you want it, SCIM so the IdP can create and deactivate those accounts. Setup steps.
Open Ledrix and do what agencies do: isolate a brand, assign a closer, send a payment link under that merchant. Watch the demo first if you want the tour.
Open a free agency workspace — no credit card. Route a brand, send Stripe or PayPal under that client, and keep closers out of books they shouldn’t see.
How brands stay isolated, where payment links generate, and who sees which records.