Sample accounts
Magic-link customer session
Resolve your account securely.
Preview account
SC-482911
Account lookup
Search or select an account before taking action
Loaded account
Keisha J. - demo account
456 Demo Crescent St, Buffalo, NY 14204
Current balance
$1,845.00
Account overview
Balance, offer, and next best actions
Recommended
Choose how to resolve this account
Account timeline
Recent customer events
Make payment
Hosted payment handoff preview
Hosted/tokenized rail
Authorize.Net window appears here later
Card/bank data never enters JSFC.
The live version will open Authorize.Net Accept Hosted or an approved hosted/tokenized flow.
Choose a payment amount to preview the handoff.
Payment arrangement
Preview a scheduled plan
Schedule preview
Installments and remaining balance
Payment source
Update stored method safely
Current source
Saved method preview
Visa ending 4242
Status: active preview method
Used for arrangement draft only.
Security boundary
No card fields in JSFC
Live rule:
Payment source updates must happen inside Authorize.Net hosted/customer-profile flow. JSFC stores only profile IDs, transaction IDs, brand, last 4, and audit metadata.
Hosted profile manager is not connected in this preview.
Messages
Email/SMS templates, message history, and link timeline
Template library
Upload or manage campaign templates
Templates selected here become available in Campaign Builder.
Communication history
Customer-level timeline
Campaign connection
How templates feed Campaign Builder
Email templates route to SendGrid campaigns after approval.
SMS templates route to the verified SMS provider after 10DLC/opt-out/webhook checks.
Every template stores channel, campaign use, approval status, version, and required payment-link merge field.
Replies and send results write back to the same customer timeline and Digital Collections analytics.
Analytics emitted
Events this portal will write
Receipts
Payment confirmations and letters
Documents
Available after payment or settlement
Payment receipt
Generated after successful payment.
Paid-in-full letter
Generated when balance is resolved under approved policy.
Settlement confirmation
Generated when a settlement offer is accepted.
Delivery
Email and SMS confirmation rules
Receipt email via SendGrid after confirmed payment event.
SMS receipt link only when SMS consent/opt-out status allows it.
All letters require approved templates before live send.
Help / dispute
Give customers a safe non-payment path
Follow-up queue
CRM routing preview
Disputes route to compliance/review queue.
Wrong party updates suppress future campaigns until reviewed.
High-value abandoned portals route to collector callback.
Help requests create CRM tasks and timeline events.
No request submitted in this preview session.
Internal CRM console
Digital Collections command dashboard
Campaign funnel
From file upload to dollars collected
Digital agents
Production by automation lane
Campaign builder
Create SMS and email campaigns with tracked payment links
Rules before send
Campaign guardrails
Suppress opt-outs, wrong-party records, disputes, and bad contact rows before send.
Generate unique tracked payment links per customer/account/campaign/template/channel.
SendGrid handles email delivery/open/click events; SMS provider must handle 10DLC, STOP, delivery, replies, and webhooks.
Every sent, opened, clicked, replied, paid, failed, abandoned, and no-close event writes back to CRM.
No campaign draft previewed yet.
Upload center
Load campaign files into Supreme Collect CRM
Campaign file
Import accounts for broadcast
Import checks
Required columns and safety checks
Waiting for preview validation.
Response center
Live SMS and email response boards
SMS live feed
Inbound SMS replies
Email live feed
Inbound email responses
Activity analytics
Response and escalation health
Payment activity
Staff view of payments, arrangements, failures, and receipts
Live ledger preview
Recent portal activity
Payment rules
Policy engine preview
Minimum payment, maximum payment, settlement percent, and down-payment rules are configurable by campaign/account segment.
Arrangement modifications can require approval based on balance, date, payment history, or failed-payment count.
Failed/NSF payments create recovery events, messages, and collector follow-up tasks.
Receipts, paid-in-full letters, settlement letters, and account timelines are generated from confirmed events only.