About

About SafeConnect

Program leaders who want to know who builds and supports SafeConnect

Who built it

Who built SafeConnect and who uses it

SafeConnect is built by Majic Holdings, a sister company of Green Communications Contracting LLC. It was scoped from the SafeConnect technology RFP and its addendum for coordinated victim services, and it is built as one secure place for the work from first request to grant report.

Who uses SafeConnect

Each role sees only what the job needs, on a phone or a computer.

  • Advocates and case managers run cases, log services, write short notes, send referrals and meet survivors by secure message or video visit.
  • Supervisors see team queues, coverage gaps, duplicate reviews and incomplete records, and they approve merges and closures.
  • Partner agency staff receive only referrals sent to their agency, and they accept, decline with a reason, or ask for more information.
  • Program administrators set programs, roles, forms, lists, consent and report definitions, and they run the first-run setup checklist.
  • Reporters run de-identified dashboards and VAWA and VOCA grant counts, and they export counts with a data dictionary.
  • Survivors reach the program through a safe link with no full account needed unless they choose one. They can message, join a visit, complete a form and check a referral status.

Advocates, partners and survivors, connected to one case folder.

One case record

Enrollments, incidents, notes, consents, referrals and appointments stay in one folder.

Consent first

Scope, receiving agency and expiry are checked before any referral shares data.

Safe links

Single-purpose links and access codes let survivors act with no full account.

De-identified counts

Grant reports count from the same records advocates use each day, with no case detail.

Implementation

Implementation, training and support in plain steps

A program moves from demo to pilot in a set order. Demonstration alone is not acceptance. Pilot starts only after written go or no-go approval.

  1. Discovery and workflow mapping

    The team works with program leadership, direct service staff, IT staff and selected partners to map service entry, intake, consent, referrals, case management, case conferencing, follow-up, closure and data collection.

  2. Setup and configuration

    Programs, roles, service lists, intake and consent forms, referral statuses, backup coverage and report definitions are set up and previewed. Published forms are versioned and never edited in place.

  3. Testing before pilot

    Functional, security, accessibility and integration tests run with test scripts. A test intake, a test referral with current consent and a test report must pass, and launch-blocking defects are fixed first.

  4. Training and guides

    Administrators and staff are trained by role, with short step-by-step guides that match the words on screen. Training uses sample records only. Guides are updated in the same release when a screen or field name changes.

  5. Pilot readiness and approval

    The first-run checklist shows what is done, who owns each step and what remains. Written approval records the go or no-go decision before survivor access opens.

  6. Ongoing support and transition

    Support, updates and change requests follow agreed steps. At contract end, a complete export with the data dictionary and checklist is provided so the program can continue without vendor lock-in.

What the program provides

Program owners confirm workspace and program details, publish service hours, response expectations, emergency wording and after-hours options, and name the administrators who approve roles, templates and the pilot decision. Majic Holdings provides the hosted product, setup help, training materials and support through the contract.

All work is performed by personnel physically located in the United States, and all environments and program data are hosted in the United States with no access from outside the United States.

Next step

How to request a demo or ask a question

Use the demo form to ask for a guided demo or a question. Share only organization contact details. Do not send survivor details, case notes or message content.

What the form asks

Name, work email, phone, organization, organization type and program size. That is enough for the team to arrange a demo around your day-to-day tasks.

What happens next

The team reviews the request and arranges a guided demo with sample records, or replies to a question through the contact route you gave. Security and accessibility documents can be requested in the same form.

See SafeConnect with sample records

Request a demo and walk through a case, a referral and a grant report in one session.

Request a demo