Compense keeps the affiliate informed automatically: every time their request moves forward —it’s submitted, decided, disbursed— or their PQRS gets a response, they receive a notice. Your operators don’t have to send anything manually: notifications fire on their own with each business event.

Key ideaWhat it means
AutomaticThey’re generated at every step of the process, with no operator involvement.
Real timeThe affiliate sees them as soon as the event happens.
MultichannelThey appear inside the app and the portal, and as a push notification on the phone.
With a destinationTapping them goes straight to the screen for the related request.

Where the affiliate sees them #

  1. Notification center (app and portal). The bell icon at the top opens the list of notices, grouped by date (Today, Yesterday, Earlier).
  2. Read / unread status. Unread notices are highlighted; the affiliate can mark as read, mark all as read or delete a notice by swiping it.
  3. Push notification on the device. If the affiliate has the app installed and allowed notifications, they get the notice in the phone’s status bar even when the app is closed.
  4. Tap to open. Tapping a notice makes the app or the portal open the related detail directly (the application, the loan, the subsidy or the PQRS).

Note. To receive push notices, the affiliate must allow system notifications when installing the app. They can always check them in the notification center, even with push turned off.


Notification types #

TypeCovers
SubsidiesProgress on subsidy and monetary allowance requests.
LoansProgress on loan applications and active loans.
PaymentsDisbursement confirmations and credits to the wallet.
PQRSStatus changes and official responses on a case.
ProgramsNews and updates about programs and benefits.
GeneralInformational notices from your family compensation fund (caja de compensación).

Events that trigger a notification #

These are the events that send a notice to the affiliate. Each one, when tapped, takes them to the corresponding screen.

ModuleEventWhat the affiliate receives
SubsidiesRequest submitted“Your subsidy request was received.”
SubsidiesRequest under review“Your request is being evaluated.”
SubsidiesDecision (approved / rejected)“Your subsidy was approved” or the rejection reason.
SubsidiesSubsidy disbursed“Your subsidy was paid.”
Monetary allowanceAllowance generated“Your monetary allowance for the period was generated.”
Monetary allowanceAllowance paid“Your monetary allowance was credited.”
LoansApplication received“We received your loan application.”
LoansDecision (approved / rejected)“Your loan was approved” or the rejection reason.
LoansLoan disbursed“Your loan was disbursed.”
PQRSCase submitted“Your PQRS was submitted. Filing No.…”
PQRSInformation required“Your PQRS requires additional information.”
PQRSOfficial response“You have a response to your PQRS.”
PQRSCase escalated / closed“Your PQRS was escalated / closed.”

Note. The exact catalog of notices may vary depending on the modules your compensation fund has enabled. PQRS cases send a notification on every status change; deadlines and statuses are explained in the PQRS guide.


How a notification flows #

flowchart LR
    A[A business event happens] --> B[Compense generates the notification]
    B --> C[Notification center<br/>app and portal]
    B --> D[Push notification<br/>on the phone]
    C --> E[The affiliate taps the notice]
    D --> E
    E --> F[Opens the request detail]

For integrators: webhooks #

The same business events that notify the affiliate can also notify your compensation fund’s systems automatically, through webhooks: Compense sends a signed message to an endpoint that you register, every time a loan is decided, an allowance is disbursed or a subsidy changes status.

This lets you, for example, sync your CRM, trigger your own emails or update your accounting without constantly polling the API. The notification to the affiliate (in the app) and the webhook (to your system) are two sides of the same event.

Note. Endpoint configuration, the technical event catalog, signature verification and idempotency are documented in Webhooks.


Frequently asked questions #

  • Does the operator have to send the notifications? No. They’re automatic; they’re generated with each event in the process.
  • Can the affiliate turn off push? Yes, from their phone’s operating system settings. Even so, the notices are still available in the notification center of the app and the portal.
  • Do notifications replace the legal notice for a PQRS? The official response to a PQRS is delivered to the affiliate who authorized electronic notification when submitting it; see PQRS.