Plan from the Case
Schedule the future services that belong to the person’s active case.
SCHEDULED SERVICES
Plan future services once. Let configuration create the work.
Inside a case, SecureCare can schedule future services and create them automatically according to the program and service configuration — reducing repetitive setup while keeping every generated service tied to the customer, case, and program.
Automatic Service Creation
SecureCare creates the service instances as the schedule comes due.
Configuration-Driven Behavior
Generated services follow the program/service configuration instead of inventing a separate automation rule set.
Optional Appointment Creation
Where configured, service creation can also create the related appointment automatically.
Optional Payment Action
Where configured, the workflow may charge the customer’s default payment method as part of the service creation flow.
HOW IT WORKS
Choose the Case to Continue Through Service Delivery.
Scheduled Services does not create a second version of the service rules. It uses the configuration already established for the program and service so the automated result behaves like work created manually by staff.
Choose the Case
Work from the case where the future service plan belongs.
Schedule the Service
Define the future service timing according to the case plan.
Create Automatically
SecureCare creates the service when the scheduled point arrives.
Run Configured Downstream Actions
Appointment and payment behavior follow the service/program configuration where enabled.
Continue Through Service Delivery
The generated service follows the same lifecycle as any other SecureCare service.
A CLOSER LOOK
Automation should follow configuration, not bypass it.
Scheduled Services does not create a second version of the service rules. It uses the configuration already established for the program and service so the automated result behaves like work created manually by staff.
Scheduled Services is planned from within the customer’s case.
The feature creates future service instances automatically according to the schedule.
Generated services remain connected to the case, customer, and program.
Automatic appointment creation can occur when the configured service behavior requires it.
Charging the customer’s default payment method can occur when configured for that service workflow.
The resulting service continues through the normal SecureCare service lifecycle and reporting.
KEY CAPABILITIES
Scheduled Services built around the real workflow.
Case-Based Planning
Keep future service automation inside the case that defines the plan.
Future Service Schedule
Represent when the next service should be created.
Automatic Creation
Reduce repetitive staff creation of predictable future services.
Program Rules
Reuse the billing, approval, line-item, and related rules already configured.
Appointment Automation
Create the related appointment when configured.
Payment Automation
Use the configured default-payment behavior when applicable.
Connected Service Record
Create a normal SecureCare service, not a separate automation-only record.
Reporting Continuity
Keep automatically created services in the same reporting layer as manually created services.
CONNECTED ACROSS SECURECARE
Part of one connected platform.
Automate the repetitive setup while keeping the service governed by the same rules as the rest of the platform.
PEOPLE. PURPOSE. POSSIBILITIES.
Automate the repetitive setup while keeping the service governed by the same rules as the rest of the platform.
