Enquiry.php ((full)): Tricorniotech.com

This feature breaks down the page’s purpose, user flow, technical structure, security considerations, and UX design—as if it were part of a live industrial tech platform.

Feature Deep-Dive: enquiry.php – TricornioTech’s Core Lead Intake Engine Product: TricornioTech Corporate Website Page: /enquiry.php Role: Primary B2B lead generation & RFQ (Request for Quotation) gateway. 1. Strategic Purpose Unlike a simple “Contact Us” form, enquiry.php is designed to handle complex, technical sales inquiries. TricornioTech sells industrial IoT sensors, edge computing hardware, and AI-driven analytics. This page is the bridge between a potential enterprise client and the sales engineering team. Primary Goals:

Capture structured technical requirements. Filter out spam/low-intent submissions. Route qualified leads to the correct vertical (e.g., Manufacturing, Energy, Logistics). Collect GDPR/CCPA consent for follow-up.

2. User Interface & Layout (Desktop First) Since B2B users often work from office desktops, the page follows a two-column, distraction-free layout . Left Column – Context & Trust tricorniotech.com enquiry.php

Hero Headline: “Request a Technical Consultation or Quotation” Subheadline: “Average response time for technical RFQs: < 4 business hours.” Trust badges: ISO 27001, GDPR compliant, SOC2 Type II. Live support teaser: “Chat with an engineer” (offline hours shown).

Right Column – The Form (Dynamic) A multi-step (or long, segmented) form with conditional logic. 3. Detailed Form Fields (Backend Mapping) | Field Name | Type | Validation | Purpose | |------------|------|------------|---------| | full_name | Text | Required, min 2 chars | CRM lead name | | work_email | Email | Required, MX record check | Send quote & follow-up | | company | Text | Required | Account segmentation | | phone | Tel | Optional, but flagged if empty | High-value lead scoring | | product_interest | Radio/Dropdown | Required | Maps to SKU categories (e.g., “TRI-Edge AI Box”) | | quantity | Number | Min 1 | Rough order magnitude | | technical_requirements | Textarea | Max 2000 chars | Core of the enquiry – free-text spec | | timeline | Select | Urgent (<2 weeks), Standard (1-3 mo), Planning (>6 mo) | Sales pipeline prioritization | | attachment | File upload | PDF/DWG/DOCX, max 20MB | Upload RFP, drawings, or specs | | existing_customer | Boolean (Yes/No) | Optional | Route to support vs. new sales | | gdp_consent | Checkbox | Required | Legal compliance | | recaptcha_token | Hidden | Server-side verified | Bot protection | 4. Technical Workflow ( enquiry.php backend logic) Step 1 – Initial Load (GET request)

PHP checks if session is started. Generates CSRF token, stores in $_SESSION['enquiry_token'] . Renders the form with method="POST" and enctype="multipart/form-data" . This feature breaks down the page’s purpose, user

Step 2 – Submission Handling (POST request) if ($_SERVER['REQUEST_METHOD'] === 'POST') { // 1. CSRF validation if (!hash_equals($_SESSION['enquiry_token'], $_POST['csrf_token'])) die("Invalid request"); // 2. reCAPTCHA v3 check $recaptcha = file_get_contents("https://www.google.com/recaptcha/api/siteverify?...");

// 3. Sanitize inputs (filter_var, htmlspecialchars) $email = filter_var($_POST['work_email'], FILTER_SANITIZE_EMAIL);

// 4. Validate file upload (check MIME, scan with ClamAV) // 5. Store in temp queue (not directly emailed) // 6. Insert into `enquiries` table (MySQL) // 7. Trigger webhook to CRM (HubSpot/Salesforce) // 8. Send auto-reply to user // 9. Redirect to /enquiry-success.php Strategic Purpose Unlike a simple “Contact Us” form,

}

Step 5 – Database Schema (simplified) CREATE TABLE enquiries ( id INT AUTO_INCREMENT PRIMARY KEY, full_name VARCHAR(100), work_email VARCHAR(255), company VARCHAR(150), product_interest VARCHAR(50), technical_text TEXT, attachment_path VARCHAR(255), submitted_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP, assigned_to INT, -- sales engineer ID status ENUM('new', 'reviewed', 'quoted', 'lost') DEFAULT 'new' );