Welcome to the NZRT Wiki Podcast. Today we’re looking at NCS Intake Form.

The NCS Intake Form is the public-facing form on the NZRT website that charitable services applicants use to get in touch. It’s powered by the nzrt-dolibarr-bridge WordPress plugin, and the whole point of it is to save time — when someone submits the form, everything gets created in Dolibarr automatically. No one on the NZRT side has to manually enter anything.

So how do you get the form onto a WordPress page? You use a shortcode. Shortcodes in WordPress are small pieces of text you drop into a page or post, and WordPress replaces them with actual content when the page loads. The shortcode for this form is simply the words nzrt intake form wrapped in square brackets. Place that on any WordPress page and the form appears, ready to go.

Now, one thing worth knowing about how this form works under the hood — it uses something called AJAX. That means when a visitor hits Submit, the page does not reload. The form submits silently in the background and the user just sees a thank-you message appear right there on the page. It’s also nonce-protected, which is a WordPress security mechanism that prevents certain types of cross-site request forgery attacks.

Let’s walk through the full technical flow from the moment someone clicks Submit. First, the visitor fills in the form and submits it. Second, JavaScript sends the form data behind the scenes to a WordPress endpoint, triggering an action called nzrt intake submit. Third, on the PHP side, the nonce gets validated to confirm the request is legitimate, and then the form data is sent to the Dolibarr API to create a new thirdparty record — that’s Dolibarr’s term for a contact or organisation. Fourth, Dolibarr responds with an ID for that newly created thirdparty. Fifth, a second API call goes out to create a support ticket in Dolibarr, filed under the NCS charitable services category and linked to that thirdparty. Sixth, PHP sends an email to Nathan with a summary of the application. And seventh, the user sees a thank-you message on the page — no redirect, no wait.

Now let’s talk about what the form actually collects. There are four fields. The first is Organisation Name, which maps to the name field in Dolibarr. The second is Email, which maps to the email field. The third is Phone, which maps to the phone field. And the fourth is Message, which gets stored as a private note on the thirdparty record in Dolibarr. Private notes in Dolibarr are internal-only — they’re not visible to the applicant.

In terms of setup, the plugin file is called nzrt-dolibarr-bridge dot php and it lives in the 000WOR repository. To configure it, you go to WP Admin, then Settings, then Dolibarr Bridge. There you set two things: the API URL, which points to the Dolibarr installation, and the API key that authorises the connection. There’s also a product sync option in there, but that’s optional and not required for the intake form to work.

What happens after someone submits? Nathan receives the email summary and reviews the application manually. If he wants to approve it, he replies to that email with the words APPROVED colon services. That reply triggers the automated delivery pipeline — specifically two scripts called mail handler dot py and cas ncs delivery dot py — which handle the next steps in fulfilling the charitable services request. The full details of that post-submission process are documented separately in the standard operating procedure called SOP-NCS-001, so if you need to follow that through end to end, that’s where to look.

To summarise what you’ve learned today: the NCS Intake Form is a WordPress shortcode-driven form that collects basic organisation details from charitable applicants. It submits via AJAX with CSRF protection, automatically creates a Dolibarr thirdparty and support ticket, and fires off a notification email to Nathan. Configuration lives in WP Admin under the Dolibarr Bridge settings, and the plugin is managed in the 000WOR repo. The form is designed so that nothing falls through the cracks — every submission leaves a clean record in the ERP system without any manual data entry.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.