$500 balance · Hot RPC · compliance clear · portal eligible
Supreme red/white direction selected
Supreme Collect
A clean collections CRM for agents who need speed, clarity, and next actions without a cluttered admin screen.
Agent-first screen
Start the day with only what matters.
Agents see their queue, callbacks, promises, and next best action. Managers can drill deeper, but the floor view stays simple.
Today
Due next
Active
Next best action ready
Paris recommends the freshest promise-to-pay follow-up first.
Account workspace
One account, clean tabs, no stacked clutter.
The final account screen opens with a summary first. Calls, notes, payments, SMS, email, portal activity, documents, updates, and audit history live behind their own tabs.
Summary tab: balance, status, compliance, next best action.
RingCentral and Evolution call history stay in a calls tab.
Agent notes and system events stay separated.
Letters and files use a clean card grid.
Account updates and TMS/SCS requests are tracked here.
Queues and desks
Build the work lanes agents actually use.
Evolution has queues, queue creation, agent desks, and desk assignment. Supreme Collect keeps those concepts but adds cleaner ownership, audit history, Paris recommendations, and manager guardrails.
Saved filters, compliance gates, priority rules, and next-best-action ordering.
Branch, client, placement, status, balance, contact state, and campaign filters.
Assigned accounts, queue pressure, desk capacity, and reassignment history.
Controlled desk assignment with who/when/why and rollback notes.
Agent activity, idle time, active calls, queue movement, and coaching alerts.
Clients, placements, portfolios
Drill from client to account without losing context.
Manage clients, placements, portfolios, buckets, liquidation, import quality, and payment processor routing in one structured lane.
Client, portfolio, account count, balance, liquidation, and assigned strategy.
Client profile, short name, card/check processor, and status.
Client -> placement -> portfolio -> account with source caveats visible.
Header validation, staged rows, rejects, duplicate checks, and import notes.
Gross placed, collected, payment plans, settlements, and recovery by placement.
Calendar and promises
Scheduled money and callbacks need their own command view.
Supreme Collect uses the Evolution calendar idea for scheduled payments, promises, callbacks, follow-ups, broken PTPs, and manager review.
Scheduled payments, promises, and callbacks prioritized by risk and value.
Promise date, amount, method, agent, account, and failure state.
Paris flags broken PTP patterns and queue coaching opportunities.
Agent reminders, callback requests, portal callbacks, and voicemail press-1 requests.
Team commitments, missed commitments, and payment-plan exceptions.
Imports, exports, and account updates
Manual files become controlled workflows.
If vendors do not provide APIs, Supreme Collect still scales through clean import staging, export history, account update queues, and source-labeled reconciliation. Paris helps map raw exterior sales sheets into Supreme headers before the file is accepted.
Evolution, RingCentral, JotForm, OnTheClock, merchant, email, SMS, and manual files.
Balance, status, desk, NSF, deleted payment, and TMS/SCS confirmation workflow.
Every export records user, filters, source, file, timestamp, and purpose.
Bad headers, missing IDs, duplicate rows, bad dates, and unmatched agents.
Source records stay separate before combined reporting views are created.
Paris file mapper
Drop in any sales sheet and Paris maps it.
Supreme Collect keeps a strict header template, but real files come messy. Paris reads exterior sheets, suggests header matches, fixes missing or off-name columns, validates required fields, and creates a clean import package.
Canonical account, consumer, debt, contact, placement, payment, and compliance columns.
Maps Debtor Name, Consumer, Account Holder, or Customer into the correct Supreme field.
Users can accept Paris suggestions or manually change any column before import.
Missing account ID, balance, name, phone, placement, status, and bad dates are flagged.
Save mappings by client/vendor so the next file imports faster and cleaner.
Skip trace inside the CRM
Batch when needed, single account when urgent.
Supreme Collect needs both batch skip tracing and one-off account lookup. If a user asks Paris to skip trace one account, Paris opens the skip trace workflow, gathers available identity fields, runs the approved lookup path, and returns structured results to the account.
One account, immediate request, results returned to the account workspace.
Upload placement or account group for controlled batch enrichment.
If no API exists, support guided user/session workflow and result capture without breaking audit.
Phones, addresses, emails, relatives, cars, properties, assets, confidence, source, date, and compliance state.
Every lookup stores who requested it, why, source, fields used, and what was added.
Property, vehicle, and asset findings can route to approved legal/manager review before lien or escalation language is used.
Consumer payment portal
Give the debtor a secure link, not a phone-card handoff.
Consumers can pay, make a settlement offer, or choose an approved payment plan. Authorize.Net runs through a locked merchant center, and admin rules control what every role and portal is allowed to do.
Choose one option
No live card data is collected in this mock.Minimum recurring payment from admin rule.
Maximum plan for this balance and placement.
Lowest self-service offer before manager approval.
Admins and authorized agents can take tokenized payments from any approved CRM screen.
Keys stay encrypted; routing, receipts, declines, settlement sync, and failover are controlled here.
Can take payments on assigned accounts after compliance and IP checks pass.
Payments and merchant center
Payments have their own workspace.
Admins, managers, and authorized agents can take or review payments from approved CRM screens. Post-dated payments should run automatically at 7 AM, then the team works the declines instead of manually charging every account.
Hosted or tokenized capture with encrypted backend credential references only.
Payments, promises, settlements, declines, refunds, and receipts.
Client, placement, method, balance, state, and failover controls.
Approved post-dated payments queue overnight and process together at 7 AM.
Declined payments route to recovery queues with reason, agent, payment code, and next action.
Every payment user gets a unique pay code tied to agent/supervisor identity and permissions.
Settlement batch health, posting status, webhook events, and payout reconciliation.
Payment actions are role, assignment, IP, payment-code, and compliance gated.
Digital SMS
Texting gets its own tab.
Vaspian or Twilio SMS sends, replies, script replies, opt-outs, unit usage, delivery failures, portal-link clicks, and conversion are not mixed into the dashboard. They live here with compliance checks before sending.
Eligible accounts after DNC, opt-out, dispute, C&D, bankruptcy, and time-window checks.
Primary SMS path if available; Twilio can be secondary/fallback if needed.
Consumer replies route to live-agent or review queues.
Template approval gates run before a blast can send.
Sent, clicked, portal-started, paid, offer, plan, abandoned.
Stop and DNC states stay visible and enforced.
Email campaigns stay clean and separate.
SendGrid email blasts, templates, layouts, unpublished email queue, sender performance, bounces, replies, opt-outs, and portal conversion live behind this tab.
Every email can carry payment, settlement, plan, callback, or contact-update links.
Use SendGrid for blasts, delivery events, bounces, suppression, and template performance.
Approved layouts, versions, and template event stats.
Review unpublished email records by account, template, agent, and date.
Bounces, failures, engagement, sender/from-email performance.
Inbound email and digital inbox activity tie back to accounts.
Communications hub
Teams, RingCentral, and internal chat belong in the CRM.
Supreme Collect should emulate the useful parts of Microsoft Teams: chat box, channels, group chats, direct messages, account-update threads, and alerts. Teams can remain an integration, but the CRM should have its own native communication center.
Use approved Teams keys for channels, account-update confirmations, alerts, and internal routing.
Calls, recordings, voicemail, SMS/phone events, users, and call outcomes tied to accounts.
Teams-style CRM chat with channels, group chat, direct messages, mentions, files, and tasks.
Every communication can attach to account, placement, user, payroll, or support case.
Paris routes blockers, approvals, compliance flags, and manager escalations.
Embedded dialer
Calling modes live inside Supreme Collect.
Agents and managers need voice broadcast, predictive dialing, preview dialing, manual dialing, power dialing, click-to-call, voicemail drops, SMS broadcast, and email blast workflows from the same account and campaign context.
Queue-based dialing with agent availability, compliance windows, and abandon-rate guardrails.
Agent sees account, balance, skip-trace result, and Paris recommendation before calling.
One-agent high-speed calling through assigned accounts with disposition control.
Manual dialing and click-to-call from account, queue, placement, and search screens.
Approved voice messages, press-1 live-agent routing, voicemail drops, and outcome tracking.
Campaigns built into the CRM
Blast the message, route the customer to the portal.
Email, SMS, and voicemail campaigns can carry secure portal links, payment links, settlement offers, payment-plan options, and live-agent routing.
Text a secure one-time portal link during a live call or campaign.
Embed payment, offer, plan, callback, and contact-update links.
Route to a live agent or follow with a personalized portal link.
Track delivery, replies, link clicks, portal starts, offers, plans, payments, abandons, and recovered money by campaign.
SMS broadcast, email blast, and voice campaigns can include secure payment, settlement, plan, callback, and live-agent links.
Audience ready: 842 eligible accounts. Exclusions: DNC, dispute, C&D, bankruptcy, time window.
Phone and dialer
Calls stay in their own lane.
RingCentral, Evolution call exports, recordings, caller IDs, dispositions, voicemail, press-1 transfers, and agent call stats stay separated until reporting views intentionally reconcile them.
Current account, timer, recording, disposition, callback, transfer, and pay-link action.
Recording links and QA review requests.
Caller ID health, routing, and campaign-level performance.
Voicemail campaign delivery and live-agent routing events.
Calls, RPCs, transfers, talk time, and outcomes.
Supreme On The Clock
Our clock is built in, even if OnTheClock stays closed.
Agents clock in from Supreme Collect. If OnTheClock integrates, it syncs. If not, Supreme On The Clock becomes the system of record for time, schedules, breaks, missed punches, monitoring status, payroll, and manager approval.
Clock in/out, breaks, schedules, missed punches, approvals, and payroll feed.
Approved and pending hours by agent, team, branch, and cycle.
Managers approve corrections with a full audit trail.
Queue status, active account, call state, idle time, IP/device, and manager review.
Sync if API works; native CRM clock if it does not.
Collab AI / agent monitoring
Work visibility belongs in the CRM, with consent and audit.
If Collab AI has an integration path, Supreme Collect links to it. If not, Paris keeps a fast embedded login/workflow so managers can reach the monitoring system quickly. Any camera, microphone, screen, or activity monitoring must be disclosed, role-controlled, and audited.
API if available; otherwise fast SSO/deep-link/manual workflow from the CRM.
Screen/activity visibility for approved work devices and approved roles only.
Visible consent, work-policy notice, manager permissions, and audit log required.
Clocked in, active app, active account, call state, idle state, and support needs.
Paris can open the correct monitoring view or setup screen for a new agent.
Payroll inside Supreme Collect
Hours, hourly pay, commission, and approvals in one place.
Payroll combines approved time, hourly rates, commission events, adjustments, bonuses, deductions, and payment status. Actual payout actions stay approval-gated and processor/provider controlled.
Review gross estimate, commissions, adjustments, approval, export, and paid status.
Store each agent's rate, role, team, and effective-date history.
Payment and transfer events feed commission review before approval.
No payroll change or payout happens without manager/admin approval.
Pay inside Supreme Collect only after provider, funding, approval, and audit controls are set.
Onboarding and training
Simple training, smooth onboarding, all inside one system.
Supreme Collect should be vertically integrated: hiring setup, onboarding, training, testing, system access, payroll setup, monitoring policy, and manager signoff happen inside the CRM.
Offer, profile, role, branch, team, payroll, access, clock, monitoring, and first-day checklist.
Short lessons, videos/docs, scripts, examples, and step-by-step workflows.
FDCPA, TCPA, payment handling, data security, account notes, and call standards.
Agent, senior, manager, admin, QA, payroll, and custom group training paths.
Employees cannot enter production queues until required training, tests, policy acknowledgements, and manager signoff are complete.
Paris new-agent setup template
New hires get created from one guided checklist.
Paris needs a reusable template for every new agent: job title, job description, team, pay setup, Supreme login, clock setup, phone system setup, Collab AI monitoring setup, training assignment, and permissions/group placement.
Reusable new-agent intake with required fields and role-specific defaults.
Title, job description, rate, payroll cycle, commission rules, and team.
Supreme login, permission group, phone/RingCentral user, clock, Collab AI, Teams, and training.
Who created it, what is complete, what failed, what needs manager approval.
If a vendor has no API, Paris opens the right setup page and tells the admin what to enter.
Integration or replacement strategy
If the vendor will not integrate, Supreme Collect replaces the workflow.
Evolution is the system being studied and replaced. For every other tool, Supreme Collect should integrate when access is practical, or build a native replacement module when it is not.
Our merchant account, hosted/tokenized capture, customer profiles, 7 AM runs, settlement, receipts, and audit.
Integrate exports/API if available; otherwise replace with native Supreme forms.
Use our own clock/monitoring/payroll feed first; sync OnTheClock only if useful.
API/SSO/deep-link if available; otherwise Paris keeps a fast manual login path.
Email blast provider for templates, delivery, bounces, suppressions, and portal-link conversion.
Primary SMS route through Vaspian if available, with Twilio as fallback if needed.
No API path becomes guided lookup, file/result capture, and Paris-assisted account update.
Manual interview/crawl only: rebuild the useful workflow inside Supreme Collect.
Collection Goat analytics, cleaner layout
The deep numbers stay one click away.
The landing page stays clear. Conversion, liquidation, agent ranking, placements, PTP, SMS, email, and portal activity live in this tab.
Reports and exports
Deep Evolution-style reports stay one click away.
The CRM needs a report builder for account, placement, agent, phone, SMS, email, payment, portal, digital inbox, import/export, payroll, QA, and compliance reports.
Feature keys from the Evolution deep crawl become structured report definitions.
Date, branch, status, direction, campaign, template, processor, and source fields.
Every export records user, filters, source, and timestamp.
Scheduled reports after permissions and data reconciliation are approved.
Evolution, RingCentral, JotForm, merchant, email, SMS, and OnTheClock stay labeled.
Users, groups, branches
Identity mapping is part of the CRM, not a spreadsheet.
Evolution has users, groups, branches, permissions, and IP access. Supreme Collect adds cross-system aliases so production, payroll, RingCentral, JotForm, and Evolution names match cleanly. Permissions are not limited to generic owner/admin/manager/agent roles: custom groups can be created and granted exact tab/action permissions.
Name, role, team, branch, active state, aliases, and last activity.
RingCentral username, JotForm submitter, Evolution username, payroll name, and nicknames.
Create any group and manually assign tab, report, export, payment, payroll, and admin permissions.
Branch-level access, reporting, queue ownership, and campaign segmentation.
Generic templates plus manual overrides for every tab, action, export, letter, payment, and payroll function.
System settings
Admin controls without the clutter.
Company settings, account settings, payment settings, statuses, email settings, permissions, promo codes, and feature flags are grouped behind a clean admin lane.
Parent status, desk allowance, admin-only states, and contact eligibility.
Processor aliases, active state, profiles, posted count, declines, and routing.
Templates, liquidations, sender rules, opt-out feedback, and approval gates.
Settlement/discount codes with authority, expiration, approval, and audit trail.
Admin-only switches for imports, reports, contact actions, AI, and payment features.
Safe by design
Every contact action passes the gate first.
Supreme Collect should feel simple to agents, but the backend still checks rules before calls, SMS, email, letters, settlement, and payment actions.
Login security made simple
Approved IPs only, except audited super admin access.
Each staff login checks the user’s IP before opening the CRM. Admins can add an office or remote IP with a clear label, scope, expiration, and one-click current-IP capture.
Add this IP for office, branch, role, team, or one user.
Scope: all active users. No expiration.
Scope: admin role. Auto-removes after 7 days.
Unknown IP requests access without exposing private system details.
Super admin access can recover the system, but every bypass records user, IP, device, time, and reason.
Support upload and internal help
Support files stay tracked, labeled, and recoverable.
Evolution has a support upload lane. Supreme Collect keeps the idea but adds file purpose, account/placement links, retention rules, and visible audit history.
Upload support files with account, placement, issue type, owner, and retention.
Internal issue status, assigned owner, notes, and resolution timeline.
Role access, document type, expiry, and sensitive-data handling.
Keep vendor/system support history tied to the affected workflow.
Paris explains which screen handles the issue and what evidence to collect.
Paris lives inside the CRM
A guide that explains, navigates, and keeps agents moving.
Paris appears as a calm in-product avatar: she can explain a screen, recommend the next step, summarize an account, and walk new agents through the CRM without crowding the workspace.
I can show this agent the next account and explain why it matters.