Contact
Route your enquiry properly the first time. This contact page is structured for application routing, verification questions, register concerns, resource requests, and general operational enquiries — because random inbox chaos helps nobody.
Best practice
Use the enquiry category selector and include reference numbers where relevant. “Hi please help urgent” is not a workflow.
For register issues
Always include the entity name, reference number, claimed category, and what exactly does not match.
For application routing
State whether you are an Operator, Supplier, or still unsure. That alone cuts pointless back-and-forth.
Contact Routes
Choose the correct route so the enquiry lands in the right workflow instead of wandering around like a lost attachment.
Application Enquiry
Use for scope selection, application readiness, process questions, and submission routing support.
Verification / Register Issue
Use for mismatched register entries, verification questions, status concerns, or reference-number issues.
Counterparty / Vendor Query
Use for vendor due diligence, onboarding checks, or counterparties seeking clarification before proceeding.
Resources / Templates Request
Use for missing downloads, template requests, or suggestions for new guidance materials.
Contact Snapshot
Sidebar block for simple trust and routing cues.
Don’t send mystery messages
If the enquiry is about a specific record or application, include the exact reference. Saves time. Saves sanity. Saves everyone.
Reference details to include
This section quietly prevents garbage enquiries.
Example reference format: NGL-2026-00418
Send an Enquiry
Frontend-ready form layout. Wire this to your preferred form handler or CRM later.
Suggested frontend behaviour: required validation on name, email, category, and message; conditional prompt for reference number on register/verification enquiries.