Features
Feature lanes
Metro2 review Client portal API bridge Social / Meta manager Managed websites
Migration Outsourcing Videos Pricing About Start Intake Login

Client portal on the outside. CreditSoft intranet on the inside.

Clients get a branded front door to log in, upload what you request, and follow progress. Your team keeps the real casework inside the local CreditSoft intranet where it belongs.

Client-facing lane

This page should explain the part customers actually touch.

The navigation is pointing to the outside layer of CreditSoft, so the page needs to show the branded public site, the client portal, and the split between customer access and the protected business workspace.

  • Branded public siteLeads hit your own front end first for consultations, offer pages, portal entry, and client-update calls to action.
  • Client portal accessExisting clients sign in to a clean, branded lane to check status, see requested next steps, and stay oriented.
  • Uploads and handoffRequested files can be collected through the portal lane instead of getting lost in random email threads and ad hoc form tools.
  • Protected company workspaceThe real casework, Metro2 review, notes, tasks, and internal operations stay inside CreditSoft on the business side.
Outside to inside

One branded customer experience. One protected business system.

The public site and portal are meant to feel polished and simple for the client. The local intranet is where the company works the file.

Public site Leads, consultations, and portal entry Use your brand, your offer copy, and your own domain instead of sending people into a disconnected vendor page.
Client portal Status, requested uploads, and client updates Give customers a clear place to log in, see what is happening, and send what your team requested.
Local intranet Casework stays on the company side Notes, disputes, workflows, and internal review stay in the protected CreditSoft workspace instead of living on the public website.

What customers actually see and upload

This is the lane the menu should be describing: the polished, client-facing side of the product.

  • Portal loginA branded sign-in page that looks like your company, not like a bolted-on third-party tool.
  • Progress viewClients can follow milestones, status notes, and next-step prompts without seeing the back-office clutter.
  • Requested filesUpload lanes can be tied to the portal flow so the client has one obvious place to send what the company asked for.
  • Public updatesLead forms, consultation routing, and client update prompts can all live in the same branded experience.

What stays on the business side

The portal is not the casework system. The company still works inside the protected CreditSoft environment.

  • Internal case notesTeam-only notes, research, decisions, and workflow context stay off the public-facing layer.
  • Metro2 review and disputesThe actual operating system for the file remains inside the intranet, not the website.
  • CRM and intake controlLead handling, fit checks, and internal routing stay with the company rather than turning into public portal clutter.
  • Operations and billingCompany-side actions stay in the secured workspace where staff can work without exposing the back office.
1

Lead hits the branded site

The public site explains the offer, handles intake, and gives customers a clear path into the portal without sending them somewhere generic.

2

Client uses the portal lane

They log in, review progress, see what the company needs next, and upload requested material through the branded front end.

3

The company works inside CreditSoft

The protected intranet remains the real operating layer for the business, so the portal stays simple and the casework stays organized.

Managed website + portal packaging keeps the customer side polished without turning the back office public.

That is the whole point of this lane. CreditSoft can support the branded public front end while the business continues to run the real file from the local-first intranet.

See pricing