Skip to product overview

A configurable service request & provider management platform

One platform.
Two sides of
every service.

Connect the people who need a service with the people who deliver it. Bring requests, availability, provider responses and service records into one configurable workflow.

Already built. Ready to test. Customized for your business.

FedoCare by ASC Business software solutions since 2007
THE SERVICE CONNECTIONExisting platform
↗RequesterNeeds a service
✓ProviderDelivers a service
FedoCareMatching · Scheduling · Coordination
  1. 01
    Service requirement createdLocation, schedule & requirements
    Request
  2. 02
    Suitable provider respondsReview & acceptance
    Connect
  3. 03
    Service outcome recordedDelivery, feedback & history
    Complete
Your terminology. Your business rules.↗

Illustrative workflow

AN EXISTING ASC PRODUCTEvaluate before you commitConfigure around your operationCustomize where it matters

01 / THE COMPLETE PICTURE

From first request to final feedback.

One connected service lifecycle. Select a stage to explore what happens; detailed approval and completion rules are agreed for your implementation.

01Register

Create requester and provider accounts, with the profile information needed for the service operation.

02Create a request

Capture service requirements, a location, dates, times, duration and relevant remarks.

03Identify providers

Use provider profiles, availability and configured criteria to identify suitable providers.

04Notify & match

Distribute requests and notify relevant providers according to the configured rules.

05Review the request

Providers review the location, schedule, requirements and other relevant details.

06Accept / assign

Record a provider's acceptance. Organization-specific approval or dispatch rules can be assessed during gap analysis.

07Schedule

Keep the accepted service's dates and times visible in the operational calendar.

08Deliver the service

Providers carry out the agreed service and share relevant service updates.

09Confirm completion

Review the delivered service through the completion and feedback process. A separate sign-off or approval workflow is subject to requirements.

10Rate & give feedback

Capture the requester's service rating and feedback against the provider's service history.

11Review & report

Use service histories, invoices and administrative reports to review operational activity.

Two perspectives. One shared operation.The requester knows what is arranged. The provider knows what is required. Management can review the record.

BUILT AROUND PEOPLE

Clear journeys on both sides.

Requester journey

For the person requesting a service

  1. 1

    Create a profile

    Register and maintain relevant contact and profile information.

  2. 2

    Describe what is needed

    Choose the service, location, date, time and duration. Add requirements, remarks and configured fields.

  3. 3

    Connect with providers

    The platform identifies or notifies providers using configured matching criteria.

  4. 4

    Confirm the arrangement

    Review provider responses and follow the accepted service in the schedule.

  5. 5

    Follow delivery

    Keep service updates and operational communication in context.

  6. 6

    Review the outcome

    Complete the service feedback process, rate the provider and review related records.

Provider journey

For the person delivering a service

  1. 1

    Build a service profile

    Record profession, skills, qualifications, experience, location, languages, rates and preferences as configured.

  2. 2

    Set availability

    Maintain the dates and times available for service.

  3. 3

    Receive opportunities

    Review suitable requests, including location, schedule, conditions and requirements.

  4. 4

    Accept a request

    Respond to an appropriate opportunity and track the accepted arrangement.

  5. 5

    Deliver & update

    Perform the service and communicate relevant updates.

  6. 6

    Build service history

    Retain completed service records, customer ratings and associated invoices.

02 / FUNCTIONAL CAPABILITIES

The operational details, connected.

A working foundation for coordinating services. Customer-specific rules, integrations and additional approvals are scoped during gap analysis.

User management

Requester and provider registration, profiles and role-specific access.

Service management

Capture service requirements, remarks and request details.

Provider availability

Maintain provider calendars and available service times.

Matching

Connect requests with suitable providers using configured criteria.

Acceptance & allocation

Manage provider responses and accepted service arrangements.

Scheduling

Coordinate required dates, times and service duration.

Location management

Maintain service locations and map details.

Skills & qualifications

Capture provider capabilities and supporting profile information.

Communication

Keep requester messages and provider service updates together.

Completion & history

Review service outcomes through records and feedback; bespoke sign-off is optional customization.

Ratings & feedback

Capture customer evaluations and provider rating history.

Notifications

Notify participants about requests, responses and service events.

Administration

Manage master data, parameters, profiles and operational settings.

Reporting & invoices

Review service activity, management reports and service invoices.

Multilingual Support

Built with multilingual capability. Currently available in English, Sinhala and Tamil, with additional languages configurable based on customer requirements.

Platform Operations

Notification processing · Service reminders · Multilingual communications · Backup automation · Database monitoring · Operational alerts · Controlled recovery

Explore platform automation

MORE THAN A MOBILE APPLICATION

Platform Automation & Reliability

FedoCare includes server-side services designed to support reliable day-to-day operation. Automated communications, service reminders, data protection, monitoring and controlled recovery work behind the application to support ongoing service operations.

Automated Notifications

FedoCare supports in-app alerts and configurable email, SMS and push notifications. Server-side retry processing helps manage temporary communication failures.

Service Reminders

Automated reminders can notify relevant users about upcoming accepted services, helping them prepare before scheduled service delivery.

Multilingual Communications

Service reminders and communications can follow user language preferences, with English, Sinhala and Tamil supported. Further localization is scoped to customer requirements.

Encrypted Data Backups

Scheduled encrypted database backup capability includes configurable retention and off-server backup options, adding protection for operational data.

System Monitoring & Alerts

Backend services can monitor database availability and expected backup activity, with operational alerts for configured administrators when attention is required.

Controlled Recovery

Authorized administrators can inspect backups and follow controlled recovery procedures, with validation and safety measures before selected data is restored.

Behind Every Service

The customer-facing workflow is supported by background platform services throughout the service lifecycle.

Customer-facing workflow

  1. Register
  2. Request
  3. Match
  4. Accept
  5. Schedule
  6. Deliver
  7. Complete
  8. Rate

Background platform services

  • Notifications
  • Reminders
  • Monitoring
  • Backups
  • Recovery

Communications follow service activity; scheduled monitoring and backups also run independently in the background.

Built to Support Ongoing Operations

A service platform must continue working beyond the moment a booking is created. FedoCare supports communications, reminders, data protection and operational supervision throughout the service lifecycle.

Stay Informed

Automated communications help keep users updated.

Protect Operational Data

Encrypted backups support data-protection procedures.

Detect Operational Issues

Monitoring helps identify database and backup problems requiring attention.

Support Recovery

Controlled tools give administrators structured recovery procedures.

Deployment Note: Availability of external services such as email, SMS, push notifications, off-site storage and monitoring integrations depends on the selected deployment configuration and third-party service providers.

See the Complete Platform in Action

Explore how FedoCare combines service-management workflows with supporting platform services for day-to-day operation.

03 / YOUR INDUSTRY. YOUR TERMINOLOGY.

Same foundation. Different possibilities.

Requester and Provider are configurable roles—not permanent labels. Select an industry to see how the service relationship can be expressed.

AN EXAMPLE CONFIGURATION

Home & Care Services

RequesterClient
ProviderCaregiver
RequestCare Request

FedoCare adapts to the business—the business does not have to adapt to FedoCare.

Illustrative industry configurations. Specialized dispatch, routing, compliance or industry workflows are subject to requirements and may need customization.

Have a different service model? Discuss it with ASC

04 / DESIGNED TO ADAPT

Configuration first. Customization with purpose.

Many requirements can be handled through master data and parameters rather than source-code changes. ASC identifies the right approach during gap analysis.

Make the platform speak your language.

Role terminologyService typesProfessions & skillsLocationsLanguagesPreferencesService categoriesLabels & captionsOperational settingsWorkflow-related parameters

Specialized status transitions and additional workflow rules are assessed against the existing product.

Language & Localization

Additional languages, terminology and localized content can be incorporated according to deployment requirements.

01

Start with FedoCare

Evaluate the working platform.

02

Map the differences

Identify configuration, customization, integration and reporting requirements.

03

Make it yours

Configure, customize and validate the agreed solution.

A DIFFERENT STARTING POINT

See the product before defining the project.

TRADITIONAL DEVELOPMENT

Start with a specification

Requirements → Design → Development → Testing → Corrections → Deployment

THE FEDOCARE APPROACH

Start with a working platform

Customer evaluation → Gap analysis → Configuration → Required customization → Deployment

Less development from scratchEarlier visibility of the workflowClearer requirements and project risksFaster implementation potential

Implementation effort and timing depend on the agreed scope. Evaluate the existing workflow before committing.

YOUR IMPLEMENTATION

From demonstration to deployment.

A practical implementation process, with scope and responsibilities agreed before delivery.

  1. 01

    Demonstration

    Evaluate the existing working platform.

  2. 02

    Requirements

    Describe your service operation and objectives.

  3. 03

    Gap analysis

    Map existing features, configuration and development needs.

  4. 04

    Proposal

    Agree scope, infrastructure and commercial terms.

  5. 05

    Configure & customize

    Adapt the platform to the agreed requirements.

  6. 06

    Customer testing

    Validate the configured solution with your team.

  7. 07

    Deployment

    Release to the agreed production environment.

  8. 08

    Support

    Receive agreed maintenance and ongoing support.

05 / DEPLOYMENT & DATA

A solution that fits your environment.

Hosting, operational controls and support are agreed for each customer. Enterprise alternatives are subject to technical assessment.

ASC-managed cloud

ASC manages the hosting infrastructure within the agreed implementation and support scope.

Customer cloud

Plan deployment in your approved cloud environment, including assessment of AWS or Microsoft Azure requirements.

Enterprise environment

Design the deployment around your organization's infrastructure, access and security requirements.

BUILT FOR BUSINESS DATA

Relational at its core.

FedoCare uses a relational database for structured service-management transactions. MySQL is the standard deployment. Alternative databases require compatibility assessment and implementation work.

  • MySQLStandard architecture
  • PostgreSQLCompatibility assessment required
  • OracleCompatibility assessment required
  • Microsoft SQL ServerCompatibility assessment required

Security & data protection

Authenticated access

Sign-in and role-based functionality control access to application operations.

API & data access

The application communicates through an API; database access remains on the server.

Deployment controls

Agree environment separation, infrastructure safeguards and backup arrangements for your deployment.

Security and regulatory requirements are assessed for the intended deployment. No formal certification or blanket regulatory compliance is claimed.

06 / EXPERIENCE THE PRODUCT

Don't just read about it. Test it.

Evaluate the existing application with ASC, explore the workflow and discuss the configuration your organization needs.

COMMERCIAL OPTIONS

A proposal built around your requirements.

Agree the platform license, implementation scope and ongoing services with ASC. Branding and configuration do not imply transfer of FedoCare intellectual property.

Platform licensingConfiguration & customizationImplementationManaged hostingSupport & maintenanceEnterprise deployment
Request a Proposal

DEVELOPED & SUPPORTED BY ASC

Advanced Systems Consultants (Pvt) Ltd

Business software solutions since 2007.

ASC develops business software and provides implementation, configuration, customization and ongoing support. FedoCare brings that experience to the relationship between service demand and service delivery.

Visit the ASC corporate website

A FEW PRACTICAL QUESTIONS

Before we talk.

Is FedoCare already built?

Yes. FedoCare is an existing working platform available for demonstration and evaluation. ASC assesses your requirements against the product before agreeing configuration or additional development.

Is it only for healthcare or care services?

No. Its requester-provider model can be adapted to other service operations. Industry examples illustrate possible configurations; specialized workflows and integrations are assessed with ASC.

Can we use our own terminology and branding?

Yes. Role labels and selected terminology are configurable. Customer branding, screens, reports and further workflow changes are scoped during implementation.

Can organizations outside Sri Lanka use the platform?

International organizations can discuss a FedoCare implementation with ASC. Service coverage, supported languages, hosting, local requirements and integrations are agreed for each deployment. This is software for coordinating services, not a promise of a worldwide provider network.

Are payments and third-party integrations included?

Service invoices and advance-payment records exist in the platform. Online payment gateways and other integrations are assessed and scoped separately; no universal gateway support is promised.

How much does an implementation cost?

ASC prepares a proposal based on platform licensing, configuration, customization, hosting and support requirements. No standard source-code transfer is included or implied.

LET'S EXPLORE THE FIT

See how FedoCare can work
for your organization.

The platform already exists.
Let us configure it for your business.

ASC will use these details to respond to your enquiry. Please do not include passwords or sensitive personal information.