Under the bonnet

Plug it in and it runs itself

aiever is deliberately boring where it matters. A webhook in, one customer identity, a queue, and a gateway out. Everything else is built on top of those four things.

Step 1

Ingest

Your billing system, ecommerce store and purchase-order app POST to authenticated webhooks. Each source has its own API key, so you always know what sent what.

  • POST /webhooks/billing
  • POST /webhooks/order
  • POST /webhooks/stock
  • Bill reversals

Step 2

Resolve

Every payload is upserted against a master customer identity keyed on mobile number, and products are matched to a central product UID.

  • Customer identity by mobile
  • Product master UID
  • Purchase history
  • Opt-out register

Step 3

Decide

Loyalty rules credit points and recalculate tiers. Scheduled jobs pick up birthdays, festivals, inactivity windows and review requests.

  • Loyalty engine
  • Segment filters
  • Task scheduler
  • Trigger automations

Step 4

Dispatch

Messages are chunked, queued in Redis and paced out through your WhatsApp, SMS or email gateway. Opt-outs are stripped before anything is queued.

  • Chunks of 50
  • Redis queue workers
  • Provider abstraction
  • Per-recipient tracking

The whole integration

One authenticated POST and you are connected

This is genuinely all your billing software has to do. aiever upserts the customer, records the purchase, credits loyalty points, recalculates the tier and queues the thank-you message — from this single call.

  • API key per connected system, revocable independently
  • Reversals claw back points and reduce the purchase amount
  • Every call logged with its payload and result for debugging
  • Any language, any POS — it is plain HTTP and JSON
More on billing integration
POST /api/v1/webhooks/billing
// headers
X-API-Key: "sk_live_••••••••••••"
Content-Type: "application/json"

// body
{
  "mobile": "9876543210",
  "name": "Meena Raghavan",
  "bill_no": "INV-20418",
  "amount": 12400,
  "billed_at": "2026-07-26T10:41:00+05:30",
  "items": [
    { "uid": "SAR-00142", "qty": 1, "amount": 12400 }
  ]
}

// 200 OK
{ "customer_id": 4821, "points_earned": 240,
  "balance": 1860, "tier": "Silver",
  "message_queued": true }

End to end

What that call sets in motion

Four steps, none of which need a person once it is configured.

01

A bill is raised

Your POS, Tally or ecommerce store posts the bill to aiever over a secure webhook. The customer is matched by mobile number and created if new.

02

Points and a thank-you go out

Loyalty points are credited against your rules, the tier is recalculated, and a WhatsApp thank-you with the running balance leaves within a minute.

03

aiever keeps the conversation alive

Birthday wishes, festival offers, new-stock alerts and win-back nudges fire on schedule — filtered against every opt-out, always.

04

They walk back in and redeem

The customer shows a voucher or asks to burn points. Your billing counter checks the balance through the aiever API and closes the loop.

98%

WhatsApp open rate

industry average, vs ~20% for email

13

Modules included

switch on only what you use

<60s

Bill to WhatsApp

from POS to customer

99.9%

Platform uptime

monitored round the clock

Security & control

Your customer list is the asset. We treat it like one.

Your own database

Each client runs a dedicated database. Your customer data is never pooled with another business.

Role-based access

Root admin, super admin and staff roles, with module-level permissions enforced at the API, not just hidden in the UI.

Full audit trail

Activity logs record who changed what and when. Developer logs capture every inbound webhook and outbound API call.

Nightly backups

Automated database backups run on a schedule, with restore points retained and monitored.

Host it your way

Managed on our infrastructure, or deployed to a server you control. It is a standard Laravel and MySQL stack — nothing exotic.

Export anything

Every list and report exports to spreadsheet. Your data is yours, and getting it out takes one click.

The stack

Nothing exotic, on purpose

Any competent Laravel developer can read this codebase. That matters more than being clever when you are running a business on it.

APILaravel 12 · PHP 8.2
Admin panelVue 3 SPA
DatabaseMySQL / MariaDB
Queue & cacheRedis
SchedulerLaravel task scheduler
AuthSanctum + role-based access

Want the technical walkthrough?

We will screen-share the webhook logs, the queue workers and a live campaign report. Bring your developer.

Or call +91 97904 03333 — Monday to Saturday, 9:00 to 18:30 IST