L
LoyaltyDocs

Managing Customers

Idempotent customer creation and lookup by phone, the Patient Profile page, and manual bonuses, penalties and adjustments

A customer joins your program once, identified by their phone number, and stays for life. Registration is the only step — there is nothing to maintain afterwards.

Adding a Customer

Register them by phone (add customer). You can capture, all optional:

Detail

Notes

Phone number (required)

Their identity — including the country code, in whatever format your business uses; the platform never reformats it

Name

Shown back in lookups and available to your staff

Email

Stored on the profile

  • Registering an existing phone simply returns the existing customer — front-desk staff can register freely at every visit without ever creating duplicates.
  • There is no approval step and no delay: a customer can earn points on the same purchase that registered them.
  • A referee captured through a referral program becomes a customer the same way, automatically, when their referral is accepted.

Looking One Up

Any of your systems can fetch a profile by phone (look up customer). The profile carries:

What you see

Use it for

A stable identifier

Linking the customer in your own systems — it never changes

Phone and email

Contact and verification at the counter

Stored details

Name and any attributes captured at registration

Join date

Tenure-based service decisions

Patient Profile in the App

Staff open a member from Patient Profile by country and mobile number. The page shows their mobile, email, member ID, member since, referral code and favourite centre, with Points Earned, Member For and Available Points on top, then:

Tab

What it shows

Accrual logs

Every credit — with its source: purchase, referral milestones or referee welcome — bill number, centre and points

Redemption logs

Every redemption, with a Reverse action on rows that carry a bill number

Expiry logs

Points that lapsed

Messages

Every WhatsApp and API message sent to them, with its status — sent, delivered, read, failed

From here Reward credits a bill and Redeem points spends points — see Accrual Flow and Redemption Flow. Export on any tab emails the data. The referral side of a member — who referred them and whom they referred — is on their profile reached from the Referrals pages; see Working the Referral Desk.

Bonuses, Penalties and Adjustments

Sometimes a balance needs a human touch — a goodwill gesture after a complaint, a correction for a mis-keyed bill. Three operations exist for this over the API, each recorded with a reason and an operation code that makes repeats harmless:

Operation

What it does

Policy it follows

Bonus

Adds points as a standalone credit; settles any negative balance first

—

Penalty

Removes points

Removing points by hand under Settings → Redemption — refuse, take what is available, or allow a negative balance

Adjustment

A correction in either direction

Credits behave like a bonus; debits like a penalty

Bonus and adjustment credits can carry their own use-by date; otherwise the tenant default applies.

For developers

[Grant bonus](https://prod.freecustomer.in/api/v2/docs#tag/loyalty/POST/api/v2/loyalty/points/bonus), [apply penalty](https://prod.freecustomer.in/api/v2/docs#tag/loyalty/POST/api/v2/loyalty/points/penalty) and [adjust points](https://prod.freecustomer.in/api/v2/docs#tag/loyalty/POST/api/v2/loyalty/points/adjust) all take the phone, the points as a positive number, a `reason` and an `operation_code`; a repeated code answers “already done”. With centres separated, every customer call also names the `store_code`.

Why the phone number?

Loyalty begins at a physical counter, where the phone number is the one thing a customer can always give. Every operation in the platform therefore works from the phone.

Was this page helpful?

Last updated on

On this page