Sparkles Module
🌟

Sparkles Module

❓

Sparkles are made up of 🕑 rules and 🔔notifications. When a sparkle 🏃‍♀️runs, it grabs visit data and evaluates it based on one or many rules. Once all rules are met then a sparkle is delivered based on notification settings. ✨ For more information read our technical review of Rubi Space.

Sparkle Types

icon

Upcoming Visit Reminders Employees and clients can be notified of an upcoming visit.

icon

Birthday / Anniversary Notifications Show your staff that you have remembered them.

icon

Late Clock In Alerts Employees get the notification first, then the office is notified.

icon

Late Clock Out Alerts Employees get the notification first, then the office is notified.

icon

Rules-driven engine

Each Sparkle can be targeted to work for (include / exclude) only certain branches, service codes, facilities, or client / employee groups.

For more details here
  • Branch(es) - a sparkle can be assigned to run for one, many, or all client branches.
  • Groups
    • Employees Includes / Excludes - a sparkles can be set to include only certain employees based on group membership or exclude employees based on group membership.
    • Client Group Includes / Excludes - a sparkles can be set to include only certain clients based on group membership or exclude clients based on group membership.
  • Service Codes - a sparkle can be set to include or exclude one or many service codes when evaluating visits
  • Facilities

⚠️

Limitations with Sparkles Although our rules-driven engine can handle countless scenarios and configurations, there are some limitations.

Sparkle configuration updates
  • We allow users to enable / disable sparkles and notifications attached to them
  • We do not allow users to change settings themselves, changes are requested via support tickets.
Visit schedule constraints

Sparkles run on a schedule, usually every 15 minutes. This means that all visits must be scheduled on the 00/15/30/45 minute markers of the hour.

Visit update or cancellation
  • Due to the limitation of Alayacare's API, we cannot create notifications when a visit is created, (re)assigned, updated, or canceled.
  • If you want to explore this ability, please read this articles in Alayacare's support portal related to SQS (https://alayacare.github.io/external-integration-docs/external-api-guide.html). We plan on incorporating this into our Rubi Space roadmap but do not have a time frame. We can however help you with as part of consulting services, if you need it sooner.

Notifications

icon

Employee SMS

Sends SMS to employee assigned to visits (phone_main field).

icon

Client SMS

Sends SMS to clients for upcoming visits (phone_main field).

icon

Office SMS

SMS can be sent to a specific number used by back office staff.

✉️

Office Email

Emails can be sent to one or many office email addresses.

✉️

Employee Email (coming soon)

Sends email to employee assigned to visit.

✉️

Client Email (coming soon)

Sends email to employee assigned to visit.

icon

Webhook

Any notification can also be sent to a HTTP end point. This is used for things like integrating with Slack, MS Teams, or other communication software.

Tokens

One or many notifications can be attached to a sparkle and can have a customized and dynamic message depending on visit information and who the message is sent to.

Employee Related Fields
  • {employee_status}
  • {employee_first_name}
  • {employee_last_name}
  • {employee_phone_main}
  • {employee_email}
  • {employee_group}
  • {employee_departments}
  • {employee_roles}
Client Related Fields
  • {client_first_name}
  • {client_last_name}
  • {client_initials}
  • {client_phone_main}
  • {client_status}
  • {client_branch_id}
  • {client_email}
Visit Related Fields
  • {facility_name}
  • {alayacare_service_id}
  • {service_code_id}
  • {service_code_name}
  • {alayacare_visit_id}
  • {status}
  • {tags}
  • {start_at}
  • {end_at}
🆗

Notifications are constructed in a matter that does not violate HIPAA / PHIPA.