# Start here: CMA platform overview

What would it mean for your organization if staff spent less time moving information between systems, and more time helping people? Welcome to the Client Management Application, or CMA. This overview is for organizations exploring debt management, housing counseling, or other client services. You'll see how the platform fits together, where it can simplify everyday work, and what to explore in a demonstration for your team. The CMA began with lead management in 2002 and grew into a connected platform for intake, enrollment, service and accounting. Its organizing idea is simple: keep the client and the work together. Start with this map. Online intake can collect information through the Website Management Application. Staff use the Lead Management Application to qualify, assign and enroll people. Eligible website records synchronize into the CMA workflow. Around the shared client record, different applications support different programs. Debt Management handles ongoing debt management plans. Debt Negotiation supports settlement workflows. Housing Management supports counseling and related agency activity. The Client Portal gives clients access to the steps your organization enables. You choose the applications and integrations that fit your services. In the workspace, familiar tabs bring together contact information, household members, creditors, housing, budgets, paperwork, tasks and notes. Staff can find a person, understand the current situation, and see the next action without assembling the story from separate files. Agencies and permissions help keep access appropriate. For a multi-service organization, that means a shared foundation with program-specific tools, rather than a new system to learn for every service.

Let's follow the client journey. Intake leads to counseling, then to the appropriate enrollment or service path. Staff confirm the person and agency, review the information, and establish the next step. This task-based approach gives each handoff an owner and a result to check. During counseling, the household budget brings income, expenses and debts into the conversation. With a configured credit-report connection, account information can be imported for review. This can reduce retyping while keeping the counselor responsible for checking the details. For debt management, enrollment connects approved paperwork with the ongoing client record. Staff manage creditor accounts, proposals, responses, program terms and hardship options, including applicable creditor programs. The integrated RPPS workflow supports proposals, disbursements and return files. Exceptions become work the team can follow through. A Housing Counseling Agency follows a different service path on the same foundation. Housing information, action plans, individual services, group education and follow-up stay connected to the household. Managers can review activity, funding and counselor records, and prepare supported HUD reporting outputs. Current HCDS tools support specific data exchange and gap-review workflows; the agency still reviews the data and its reporting requirements. For other services, configurable agencies, phases, tasks and forms help shape the workflow around your process. Now consider accounting. The daily accounting checklist gives staff a visible sequence for payments and disbursements. The platform supports multiple banks, scheduled or individual payments, bank-specific files, electronic creditor payments and checks. Payment returns, Fair Share, fees and client balances remain part of the accounting workflow. Cleared payments and cleared disbursements drive the client balance. Batch histories and reports help staff trace what happened and reconcile results. The operational benefit comes from connecting these steps: fewer disconnected handoffs, less duplicate entry, and a clearer queue of exceptions that need a person. Your exact process and available options depend on the programs and providers you configure.

The connections around that journey matter just as much as the main screens. Start with documents. Approved templates can use information already on the record to create letters, contracts and messages. Uploaded documents, generated paperwork and signed portal documents stay associated with the client. Reusable templates help your team produce consistent material without rebuilding it for each person. Through the Client Portal, eligible clients can complete assigned steps, review and sign documents, exchange secure messages and access configured account information. For debt management clients, that can include statements, payment and disbursement history, and counterproposal decisions. Self-service can reduce routine status calls and paperwork follow-up while giving clients a clearer view of their own progress. Communications connect to the record too. Available integrations include PBX calling and call history, email delivery, Twilio text messaging, fax services and credit-report providers. Click-to-dial and linked call records can save navigation and help the next staff member understand the conversation. Consent, contact preferences and provider setup still matter. Tasks and rules can move routine work forward. For example, a payment-return import may create a follow-up task; configured rules can assign work or prepare a notification. Automation follows your setup, and staff review exceptions and outcomes. Current AI-assisted tools add options for drafting, transcription and finding information, subject to permissions and configuration. People review the results before relying on them. Managers can use dashboards, reports, task activity and available time and payroll tools to understand workload and performance. Supported APIs and integrations can connect other systems. These capabilities can lower operating costs by reducing repetitive administration and time spent maintaining separate processes. The best way to evaluate the benefit is to bring your own workflow to a demonstration and identify which manual steps can be removed.

Behind the workspace is a browser-based application stack. Your team accesses the service through a web browser, which makes it practical to support staff in different locations without distributing a desktop application for each release. Here is what the layers do. The browser presents the workspace. Apache handles web requests, PHP runs application logic, and Smarty templates build the interface. MySQL stores structured operational data. Background jobs handle scheduled imports, messages, documents and other processing. Connected providers remain separate services, with their own configuration and accounts. The hosting foundation uses FreeBSD, workload isolation through jails, and ZFS storage. Those are infrastructure building blocks; staff work through the CMA interface. Keeping this foundation together supports centralized maintenance and updates as the product evolves. Security has several layers. Authenticated sessions, permissions, agency and company scope help control access. Multi-factor authentication and passkeys are available where configured. TLS protects information in transit. The hosting and backup arrangement provides storage protection, while masking and audit records support appropriate use and review within the application. Recovery has a different purpose from ordinary access control. Database replication maintains another current copy, and configured replicas can also support reporting. Retained snapshots and offsite backups preserve recovery points. A replica and a backup serve different needs: an unwanted change can reach a replica, while an earlier retained recovery point may help restore prior state. Confirm the hosting arrangement, retention and recovery expectations for your deployment. The platform continues to evolve with customer feedback and requested changes. Existing migration tools can help bring information from another system into a planned implementation. Scope, data quality and validation still need review. For your organization, the value is a maintained foundation for connected service delivery, with infrastructure and configuration discussed as part of a clear implementation plan.

What should you look for in your own demonstration? Begin with one real business journey, using example data: a new inquiry, a counseling session, the service handoff, and the reports your manager needs. Ask where the team re-enters information, chases paperwork, or checks the same status in several places. Those are useful candidates for reducing administrative effort. Then look at ease of use. Can a new employee recognize the client, find the relevant tab, and understand the next task? Can a supervisor see the exceptions and follow the history? The CMA combines shared records, reusable workflows and connected services to support that goal. To explore further, use the Learning Center's short topic videos. Debt Management teams can follow intake through client service and accounting. Housing Counseling Agencies can start with the dedicated Housing Management tour. Documentation and in-application Guided Tours provide additional help, and onsite or live online training can support your rollout. Bring your services, integrations and reporting needs to the conversation. We'll help you explore how the CMA can fit your organization and give your team more time for the people you serve.