RYA DEV
TechnologyServicesWorkAboutContact
RYA DEV · Case study RemembrApp — automating customer communication

Customers have reasons to come back. The software remembers when.

A periodic service, a dental check-up or another shoe-care treatment: many services expect the customer to return. Tracking every date by hand, though, means repetitive work.

We built a simple interface connected to a scheduling and messaging system. Information is entered once, and configured rules set the moments of contact and how each message is personalised.

01 — REGISTRATION
Customername
Service datedd.mm.yyyy
Phonephone
02 — RETURN RULE
After 3 months After 6 months Yearly

Illustrative intervals, adaptable to the service.

03 — PERSONALISED MESSAGE

The template combines the customer's details with the moment that matters for the service.

04 — HISTORY

Processed messages remain available for reference.

Interface from the initial implementation for funeral services. The flow can be adapted to other activities.
Usage examples — adaptable to each business's process
SHOE CARE

Hi, Andrei! It's time to care for your shoes again. Drop by whenever it suits you.

DENTAL PRACTICE

Hi, Andrei! This is a reminder of your regular check-up. Contact the practice to book an appointment.

CAR SERVICE

Hi, Andrei! Your recommended service date is coming up. Contact us to book.

The simplicity of the interface starts with the logic behind it.

Behind a quiet screen is a set of rules that decides when and what is sent.

Detail: configurable milestones. Press for the full screenshot, with the message template.
01

We simplified operation

A clear interface for entering information and checking records, without keeping a reminder calendar by hand.

02

We automated the moments of contact

The configured milestones and intervals set when messages are processed, and templates personalise the content.

03

We kept it flexible

Settings and texts are kept apart from the sending mechanism. For another field, we adapt the rules and, where needed, the app's flow and fields.

Detail from the history: the same milestone, processed 14 and 7 days before.
Angular / Firebase / SMSO / Scheduled automations

What should software remember for your business?