π₯
Total Visitors Today
0
β live tracking
π’
Project Enquiries
0
β today
π€
Meetings (AVP / MD)
0
β today
π
Vendors / Others
0
β today
π Live Queue Pipeline
0
Checked In
just arrived
0
Waiting
in lobby
0
In Meeting
with host
0
Checked Out
visit complete
β¨ Today's Snapshot
π¬ WhatsApp Delivery Today
π₯ Live Visitors (click a new visitor from the sidebar to check someone in)
| Name | Purpose | Meet | In Time | Status | Action |
|---|
π Last 7 Days Visitor Trend
π New Visit Entry
π₯ Visitors List
| Date | Name | Contact | Type | Location/Project | Purpose | Assigned | In | Out | Status | Action |
|---|
π·οΈ Visitor Type
π’ Location / Project
π― Visiting Purpose
π§βπΌ Person to Meet / Assigned To
π Live Queue Pipeline
0
Checked In
just arrived
0
Waiting
in lobby
0
In Meeting
with host
0
Checked Out
visit complete
ποΈ Queue Board
Checked In
0
Waiting
0
In Meeting
0
Checked Out
0
π Full Queue List
| Token | Name | Purpose | Assigned To | Waiting Since | Status | Action |
|---|
π’
All Project Visits
0
π
Project Enquiries Today
0
β³
Currently Waiting
0
π€
Converted to Meeting
0
π’ Project-wise Visits
π Purpose-wise Summary
π§βπΌ Person-wise Summary
π¬ WhatsApp Delivery Report
0Sent
0Delivered
0Failed
0Pending
β±οΈ Average Time in Building
β
Based on check-in to check-out time, checked-out visitors only.
π Repeat Visitors
Contacts with more than one visit on record, most frequent first.
| Name | Contact | Visits | Last Visit | Last Purpose |
|---|
π₯ Firebase Live Database
π Google Sheets Backup
π Data Synchronization
0Records In This Session
βFirebase Records
βGoogle Sheet Records
π¬ WhatsApp API Configuration
πΊοΈ Stage-wise Approved Template Mapping
Only SmartiConnect / Meta-approved templates are used. The five TNCD stage templates are pre-mapped. Future approved templates can be added below without changing the code.
οΌ Add Future Approved Template
𧩠Template Parameter Configuration
Each approved WhatsApp template has a fixed number of {{1}}, {{2}}... body variables, and may also have a media header (e.g. Image), as set on Meta / SmartiConnect's side. Both must exactly match what was approved β a wrong parameter count causes error #132000, and a missing/incorrect header causes error #132012 "Format mismatch". Check the template's approved content in your SmartiConnect / Meta Business dashboard to confirm both.
β WhatsApp Send & Delivery Status
βAPI Acceptedβ means SmartiConnect accepted the request. Delivered/Read confirmation shows once SmartiConnect returns that status, a delivery webhook updates the app, or an advanced status check is run. Full history per visitor is available from the circular WhatsApp icon next to their name on any visitor list β click it to open, send, and check status.
βοΈ Cloudflare Worker Proxy Code
Create a Cloudflare Worker, add a secret named SMARTICONNECT_TOKEN, paste this code, deploy it, then enter the Worker URL above.
export default {
async fetch(request, env) {
const cors = {
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Headers": "Content-Type, Authorization",
"Access-Control-Allow-Methods": "POST, OPTIONS"
};
if (request.method === "OPTIONS") return new Response(null, { headers: cors });
if (request.method !== "POST") return new Response("Method not allowed", { status: 405, headers: cors });
const body = await request.text();
const response = await fetch("https://app.smarticonnect.com/api/send/template", {
method: "POST",
headers: {
"Accept": "application/json",
"Content-Type": "application/json",
"Authorization": `Bearer ${env.SMARTICONNECT_TOKEN}`
},
body
});
return new Response(await response.text(), {
status: response.status,
headers: { ...cors, "Content-Type": response.headers.get("Content-Type") || "application/json" }
});
}
};
π©Ί Last Send Diagnostics
The exact request this app sent and the exact response SmartiConnect returned for the most recent WhatsApp send attempt β useful to paste into a SmartiConnect support ticket if a send keeps failing.
β Create Login Credential
π Login Users
| Name | Username | Role | Status | Last Login | Last Location | Action |
|---|
π Login Activity
Every sign-in, with device and an approximate location looked up from the signing-in device's IP address. Location is best-effort β it will show "Unavailable" if the lookup is blocked or there's no internet at that moment.
| Time | Name | Username | Role | Device | Approx. Location |
|---|