NeuraCore CRM — conversational CRM for WhatsApp

Template manager

Approved messages, built and tracked in one place

Business-initiated WhatsApp messages have to be pre-approved. NeuraCore gives you the editor, the preview and the paperwork in one screen, then keeps every number’s approval status in sync for you.

Build the whole message. Header as text, image, video or document; body with numbered variables; footer; quick-reply and call-to-action buttons.
Preview as you type. The phone panel renders exactly what the customer will receive, buttons included.
Marketing, utility or authentication. Pick the category and language, and the list keeps a running count of approved, draft, in-review and rejected against every sender.
Push to many numbers at once. Select the templates you want and sync them to whichever senders should carry them.
Cooldown-aware. The editor knows the platform’s edit window, so you don’t burn an approval by saving too soon.
Sync runs itself. A background service pulls status changes back — nothing to refresh, nothing to chase.

order_shipped_v3 Utilityen_ZA

Header · image

tracking-banner.png

Body

Hi {{1}}, order {{2}} is on its way and should reach you by {{3}}.

Footer

Reply STOP to opt out

Buttons

Quick reply · Track order URL · View invoice

Status across senders

Approved 3 Draft 1 In review 1 Rejected 0

AC Acme DeliveriesBusiness account

TRACKING BANNER

Hi Thandi, order AC-40912 is on its way and should reach you by Thursday.

Track order View invoice

09:14 ✓✓

Live preview — variables resolve per recipient at send time.

Form Studio

Forms that open inside the chat

No link, no landing page, no drop-off. Build the form in a three-pane studio — screens on the left, fields in the middle, a live phone preview on the right — and it opens as a native sheet in the customer’s WhatsApp.

Twelve element types. Text input, long text, dropdown, radio group, checkbox group, date picker, photo picker, document picker, opt-in, headings, body copy and footer.
Screens that branch. Each screen’s button names the screen that follows it, so the form can take different paths instead of marching through one long list.
Required where it matters. Toggle any field, name it once, and that name is the key you get the answer back under.
Live option data. Dropdowns can be filled from your own data source at the moment the form opens, so nothing goes stale.
Drop it into a conversation. A published form is a node in the automation designer, so it can be one step of a longer flow — and answers land on the form responses report.

Service booking Appointment bookingPublished2 screens

☰ Book a serviceScreen 1 of 2 → screen_b

Tell us about the vehicle

Registration *

CA 481 · 907

Branch *

Choose a branch▾

Service type

Major service Minor service Diagnostic only

Preferred date

12 Sep 2026📅

Send me reminders about this booking

Continue

Element library

AaHeading & subheading

¶Body text

[ ]Text input

[≡]Text area

▾Dropdown

◎Radio group

☑Checkbox group

📅Date picker

📷Photo picker

📄Document picker

✓Opt-in

―Footer button

Rendered natively by WhatsApp — the customer never leaves the conversation.

Automation designer

A canvas for the whole conversation

Drag nodes onto a canvas and wire them together. What you draw is what the customer experiences — including the branches, the loops and the calls out to your own systems mid-conversation.

Nine message nodes. Message, quick reply, list message, location request, WA template, API callback, URL button, WhatsApp form and media message — dragged from the palette onto the canvas.
Two logic nodes. Condition (if) branches on what you know about the contact; For each walks a list — order lines, branches, appointments.
Starts on a keyword. Point a trigger word at one sender or at every sender you own.
A nudge, then a deadline. A follow-up message fires after your delay timer without ending the conversation; an expiry message fires after the timeout and closes it. Both are just fields on the flow.
Call your systems mid-chat. An API callback node hits your endpoint and uses the response in the next message, so answers are live rather than cached.
Tell your app what happened. Every step and every ending posts to your webhook, with retries, so your CRM stays in step.

Delivery follow-up #track → all sendersfollow-up 04:00expiry 24:00Active

WA template

order_shipped_v3

API callback

GET /tracking/{ref}

Condition (if)

Replied within 24h?

truefalse

For each

Order line → media message

WhatsApp form

Rate the delivery

List message

Anything else?

RescheduleInvoiceAgent

Message

Thanks — we’re done here.

MessageQuick ReplyList Message Location RequestWA TemplateAPI Callback URL ButtonWhatsApp FormMedia Message Condition (if)For each

Drag nodes to canvas — the two amber ones are the Programability group: logic, not messages.

Campaign manager

Send to a segment, watch it land

Pick the template and the sender, build the audience, and see what it costs before you commit. Once it goes out, the campaign screen fills in live as receipts come back from the network.

Build the audience where the data is. Start from client groups and filter on any custom field you’ve defined — no exporting to a spreadsheet first.
Fill the variables properly. Set a value once for the whole send, or map it per recipient from their own record.
Costed before it sends. The estimate is priced off your own rate card, so there are no surprises on the invoice.
Scheduled to the minute. A live countdown on the list, and a scheduler service that does the sending whether or not anyone is logged in.
A funnel that moves. Total, sending, delivered, read and failed update in real time — and the recipient list underneath shows you exactly who is at which stage.

Spring service reminder Sending in 00:04:12

Total4 812

Sending4 806

Delivered4 691

Failed115

Audience Service dueandRegion = Western CapeandLast visit > 180d 4 812 contacts

Variables {{1}} first name · {{2}} vehicle · {{3}} branch per recipient

Estimated cost R 1 876.68

Receipts stream into this screen as the network confirms them.

The rest of the platform

Everything a conversation needs around it

Shared inbox

One thread per customer

Your team works the same conversation list, with the contact’s custom fields, groups, mailing lists and notes in a panel beside the chat. Replies are attributed to the agent who sent them.

Contacts

Segments that mean something

Define your own fields per client group, then filter on them anywhere. Bulk-load from Excel with column mapping and a live progress readout instead of a silent import that may or may not have worked.

Reporting

Dashboards and the detail behind them

Delivery performance, response rate, average response time, failure analysis and message-type breakdown on the dashboard; campaign performance, itemised billing, wallet statements and form responses as full reports.

Billing

Prepaid wallets, audited

Each company has a wallet and a rate card. Every message is charged against it and audited independently, so what you were billed and what you actually sent always reconcile. Top up by card or EFT.

Developers

An API, webhooks and an SDK

Send from your own system with a company API key, and receive callbacks for messages received, messages sent, status changes and automation events. There is an interactive callback reference with a throwaway inbox for testing, plus a .NET client library.

Browser extension

Chat from any system you already use

A Chrome extension puts a chat button next to phone numbers on any page — your ERP, your helpdesk, a supplier portal — and opens the conversation in the side panel without switching tabs.

Multi-site

Branches, brands and resellers

One company can run many sites, each with its own users and its own WhatsApp senders. Resellers create client companies under their own branding and rate cards, and manage them from a single login.

Documents

Paperwork, filled in and sent

Upload a fillable PDF, map its fields, and let a conversation generate the finished document — a quote, a booking confirmation, a policy schedule — and deliver it in the chat.

Email & SMS today

The other channels you already send

Email templates with a visual editor, newsletters with an approval step, mailing lists with unsubscribe handling, and SMS templates — already in the portal, and moving onto the same routing layer as the channel work lands.

Design the conversation once. Let it run itself.