A CRM that already knows your kind of organisation.

BizCARE CRM is a customer relationship management system built in Malaysia for membership and non-profit organisations — associations, alumni bodies, temples, foundations and charities. It gives you the CRM core every organisation needs (contacts, companies, custom fields, your own record types, pipelines, tasks, saved views, roles, workflows and an API) and adds ready-made modules for the registers these organisations actually keep: members and dues, donors and a merit wall, memorial tablets and niches, clan genealogy, group practice, and WhatsApp outreach. The interface is in English and Chinese, and five of the modules publish a public site on their own address.

Yes. BizCARE CRM is a general-purpose CRM — contacts, companies, custom fields, your own record types, pipelines, tasks, saved views, roles and an API — and it works with none of the vertical modules switched on. The modules are pre-built registers for work we see often; they are a head start, not a requirement. Alumni associations, sports clubs, professional bodies, schools, trusts, welfare societies and chambers of commerce all run on the same core.

A general-purpose CRM models a sales pipeline and leaves the rest to you: a temple's tablet register, an association's member roll and dues, a clan genealogy or a donor wall all become custom objects you have to design, build and maintain yourself. BizCARE CRM ships those registers already built — with the intake forms, the public sites and the lists that go with them — on top of a CRM core that still does contacts, custom fields, pipelines, roles, workflows and an API. You are not choosing between a real CRM and a vertical tool.

Yes. Membership holds the alumni roll — add graduating year, class, campus and course as your own fields — with an online registration form, dues status, committee terms and a members-only directory. The Merit Registry publishes a donor wall for a building or scholarship fund, and Outreach sends reunion and AGM notices on WhatsApp.

No. Modules are switched on per organisation. Most start with one — usually the register they keep on paper today — and add others when they are ready. An organisation running only the CRM core is a normal setup.

Define it yourself. A custom object is a new kind of record with its own fields, list views, permissions, activity log and API endpoints — scholarships, equipment loans, event bookings, cemetery plots, whatever you keep. No developer and no change to the product is needed.

Members join online. The association site carries a join form that walks an applicant through their details, their consent and the plan they are applying for, and the submission arrives as an application for your committee to approve or reject — nothing is retyped. Dues are then recorded per member and per period, with paid, outstanding and waived status. The payment itself is still taken the way you take it now; the system does not collect money online.

Memorial records import from a CSV template whose columns follow the paper registration form, and merit donors import from CSV with matching against your existing contacts. For the other modules, talk to us about your records and we will plan the move with you.

Yes. Memorial records and merit donors export to CSV, and every module is readable through the REST and GraphQL APIs with an API key scoped to your organisation. Signed webhooks push changes out as they happen, so another system can hold a copy. The records are yours and nothing here is built to make leaving difficult.

Each staff member switches the interface between English and Chinese — menus and pages, with some screens still in English while translation finishes. Public sites for devotees and members are Chinese-first, and names are stored exactly as you enter them.

Each public site gets its own address under bizcare.my — for example yourtemple.memorial.bizcare.my — working from the moment the module is switched on, nothing to set up. Already have a domain? Point it at your site and we handle the SSL certificate; your organisation's name and logo lead either way, and BizCARE stays in a quiet footer.

Not necessarily. Outreach can connect your organisation's own WhatsApp Business account, so notices go out from your number and replies come back to you rather than to us — or it can send through JomCARE Messaging if you would rather not manage an account directly. Sending is paced so a notice to the whole roll goes out steadily instead of in one burst, and each message is logged against the member it went to.

Yes. Roles decide which modules and records a person reaches, and field permissions go further — the treasurer sees the amount on a donation while a volunteer entering names does not. Who changed what, and when, is kept on the record itself.

Yes. The public sites — the memorial wall, the merit wall, the association site and the member portal — are built for a phone first, because that is where families and members open them. Staff can work from a phone browser too, and there is nothing to install from an app store.

In a managed PostgreSQL database in Singapore (AWS ap-southeast-1), served through Cloudflare. Each organisation's records are kept separate, and changes to records are kept in an activity log.

With the Personal Data Protection Act 2010 in mind. The online join form records consent at the moment of joining, roles and field permissions limit who sees what, living people are kept off the public genealogy, and members can opt out of the member search. Your organisation remains the data user under the Act; our Privacy Policy sets out how we process personal data on your behalf.

• Personal Data Protection Department (JPDP)

Not inside BizCARE CRM. The merit wall and the association site acknowledge donors you record, and payments are taken the way you take them now. Organisations that want online giving use DonorCARE, the family's donation app — a Memorial Registry light-up campaign can already raise its donations there.

Accounting and e-invoicing belong to BizCARE Books, the family's accounting app, which issues e-invoices through LHDN's MyInvois system. BizCARE CRM records the payments on members, tablets and donors; posting them into BizCARE Books as receipt-ready entries is on our roadmap. Donation receipts raised in DonorCARE are already filed to LHDN as e-invoices.

• BizCARE Books
• LHDN e-Invoice (MyInvois)

Yes — through the REST and GraphQL APIs and signed webhooks, and through workflows that call out when a record changes.

Questions go to us on WhatsApp and are answered by the people who build the product. Guided onboarding includes training for the staff who will keep each register, and Enterprise agreements add priority support.

BizCARE CRM is a per-organisation subscription. There is no public price list: the price depends on which modules you switch on and the size of the registers they hold, so we quote after a conversation about the records you keep today. Activation and third-party costs are covered in the next two answers.

Not if you set it up yourself. Switching a module on and entering or importing your own records is free. Most organisations, though, arrive with years of paper registers and spreadsheets, and prefer us to handle the move — mapping the old columns, resolving duplicates, importing the archive and training the staff who will keep it. For that guided onboarding we charge a modest one-time activation fee per module, stated in your quotation before any work begins.

A few features rely on outside services that charge for their own use. The main one is WhatsApp: Meta charges per template message sent through Outreach, at rates Meta sets by message category and country. Others of a similar nature are the SMS sign-in codes sent to devotees and members, which carry a per-message carrier cost, and your own domain name, which you renew with your registrar (the SSL certificate is included). In most cases we pass these costs through at cost, without markup; where we do not, the quotation says so.

• WhatsApp Business pricing (Meta)

Yes. CARE Enterprise suits organisations with several branches or related entities, large registers, or more than one CARE app — a temple with branch temples, for example, or a foundation with a company arm and a welfare society. Enterprise pricing is monthly and discussed separately, because it depends on your organisation's setup: the entities and branches involved, the modules and CARE apps in use, the volume of records, the level of support and any integrations to be built.