Integrations: What VizPass Connects To, and What It Does Not
This page covers VizPass visitor management integration options — WhatsApp (BeyondBox or your own gateway), custom SMTP email, .ics calendar invites, and permission-controlled CSV/Excel exports — plus what's not yet supported, so you know the scope before committing.
A visitor at the gate rarely stays a "visitor" problem for long — the security guard needs to message the host, the host wants it on their calendar, the safety officer wants an export for the auditor, and the HR head wants to know if the same tablet can also catch the staff punching in through the back gate. Most of that works out of the box. Some of it, honestly, doesn't yet, and it's better you know which is which before you sign a PO than after.
Messaging: WhatsApp and email
Approvals, invites, OTPs and gate notifications go out on WhatsApp by default, routed through VizPass's own BeyondBox gateway on the Meta Cloud API. These are approved message templates — nothing to configure, nothing to register with Meta yourself. For a plant that just wants the guard's tablet to ping the shift engineer the moment a vendor walks in, this is the entire setup: none.
If your company already runs its own WhatsApp Business number — for dispatch alerts, HR broadcasts, whatever — you can point VizPass at it instead. From Settings, connect one of:
- UltraMsg
- AiSensy
- Twilio
- Interakt
using your own number and token. Messages then carry your number, not a shared one, which matters if your visitors already have that number saved as "Factory Security."
Email works the same way in reverse: instead of a shared sender, you connect your own SMTP — Gmail Workspace, Microsoft 365, Zoho, or any other SMTP host — from Settings, and invites go out from your company's actual email address. A test-send button confirms the connection before you rely on it, which is worth doing once and forgetting about.
Calendar invites, without a calendar integration
When a visit is pre-registered — a vendor audit next Tuesday, a corporate office visit next month — VizPass generates a standard .ics file that both the host and the visitor can add to Google Calendar or Outlook. There's no live sync, no two-way calendar API, no need for one. It's a file that behaves the way calendar files have behaved for twenty years, which is exactly what you want from something this simple: it should just work on whatever calendar the visitor's IT department gave them.
Getting data out: exports, not APIs
This is where we should be precise about what "integration" means, because the word gets stretched. VizPass does not currently expose a public API for visitor data — the mobile API that exists covers staff attendance, leave, expenses and field work, not visitor records. If your ERP or business intelligence tool needs live visitor data pulled automatically, that connector doesn't exist today. An integration request for a specific case can be raised with support, but there's no roadmap promise to make here beyond that.
What does exist, and covers most of what a plant actually needs, is straightforward export:
- The visitor register, issued passes, and reports all export to CSV or Excel
- Exports are permission-controlled, so a shift supervisor doesn't necessarily see what a compliance auditor sees
- The exported file goes wherever your existing systems already read CSV or Excel from — which, for most Indian plants, is still the honest answer to "how does this talk to my ERP"
If you're evaluating VizPass against tools that promise deep two-way ERP or HRMS sync, it's worth asking them to demo it live rather than take the brochure's word for it. VizPass doesn't make that promise, and would rather you know that going in than discover it during rollout.
Biometric attendance, for staff — not visitors
A separate and genuinely useful integration exists for companies on the Gate & Attendance plan: eSSL and ZKTeco biometric readers that speak the ADMS "iclock" push protocol can send attendance punches to VizPass directly over the internet. No middleware PC sitting in a cabin next to the reader, no local software that stops working the moment that PC's hard disk dies or someone unplugs it during a power cut. The reader pushes punches straight to VizPass.
Two things worth being clear about here. First, this is for staff attendance — contract labour, shift workers, permanent employees clocking in — not for visitor check-in, which runs through the tablet and QR flow described elsewhere. Second, it only covers readers that speak the ADMS iclock protocol; if your existing eSSL or ZKTeco device is an older model that doesn't push over IP, it won't connect this way, and that's a hardware limitation, not a VizPass one. Worth checking the specific model before assuming compatibility. This attendance side is covered in more depth on /use-cases if multi-shift, multi-contractor attendance is your actual pain point rather than visitor management.
What VizPass does not connect to today
Better to say this plainly than let a site visit surface it as a surprise. VizPass does not integrate with:
- ANPR cameras (automatic number-plate recognition at the boom barrier)
- Boom barriers or turnstiles themselves
- Weighbridges
- ERP systems
- HRMS systems
- Zapier or similar no-code connector platforms
If your gate process depends on a boom barrier lifting automatically when an ANPR camera reads a truck's number plate, VizPass isn't that system today, and no amount of configuration will make it one. What VizPass does well — logging the visitor or vehicle, running the approval, printing the pass, keeping the register — it does without pretending to be a physical access control platform. Some of our other pages go deeper on where that boundary sits for trucks and transporters specifically; worth reading if that's your actual gate.
Hardware and single sign-on
On the hardware side, VizPass runs on any Android tablet with a camera — no proprietary kiosk hardware to buy or import, no spares lead time to worry about beyond whatever standard tablet you chose. Passes and labels print through the tablet's own print dialog to whatever label or pass printer you already connect it to. For visitors who'd rather not queue at the guard's tablet, a QR poster generated from the app lets them self-check-in from their own phone.
For plants already running other BeyondBox products, single sign-on lets a user move into VizPass with a short-lived signed ticket rather than a separate login — useful for a plant head who's already logged into a BeyondBox HR or ops tool and shouldn't need a third password. It's worth being precise about what this is not: SSO doesn't create visitor accounts, doesn't sync visitor data between products, and doesn't replace the visitor workflow itself. It only saves the login step for your own staff.
Scheduling without depending on a person
Some scheduled jobs in VizPass — a recurring report, a routine notification — are meant to fire on a timetable rather than wait for a host to trigger them. Where that host-dependent trigger isn't reliable enough (someone's on leave, someone's on the shop floor with no signal), a webhook URL lets an external cron job drive that scheduled task instead. It's a small mechanism, but on a site where the person who'd normally click the button is standing next to a furnace at the time, it matters.
If you're weighing all this against what a full evaluation actually needs — pricing, hosting, data residency, or just what the gate-to-register flow looks like day to day — those are covered in more detail on /features and /pricing. And if a specific integration question sits outside everything above, a short call is faster than guessing from a brochure — you can book one on /contact. For anything touching how visitor data itself is stored and handled, MeitY's guidance is the reference worth checking against, independent of what any vendor tells you.
Integrations: What VizPass Connects To, and What It Does Not FAQs
Does VizPass sync visitor appointments with Google Calendar or Outlook?
No, VizPass does not push meeting invites directly into Google Calendar or Outlook. When a visitor is pre-registered, the host gets a WhatsApp or email notification with the visitor's name, purpose and scheduled time, but that notification is a message, not a calendar event — nothing appears automatically on the host's calendar. If the host wants it tracked there, they'd need to add it manually from the invite. This is worth knowing before rollout if your building already relies on calendar-based room bookings or reception handoffs, since VizPass and the calendar remain two separate systems rather than one synced view. What VizPass does handle end-to-end is the visitor pre-registration flow itself — the invite, the OTP, the gate notification — so the gap is specifically about calendar sync, not about getting the host notified in the first place.
Can VizPass connect to biometric attendance devices like eSSL, Matrix or ZKTeco for staff punch-in?
No, VizPass doesn't talk to third-party biometric attendance hardware directly. Instead of pulling data from a separate biometric device, VizPass captures staff attendance on the same gate tablet used for visitor check-in — staff tap into a distinct attendance mode rather than the visitor flow, and that in/out record is logged inside VizPass alongside the visitor log. It's a software-side answer to "can one tablet do both jobs," not an integration with your existing eSSL or Matrix box. If your HR team already reports out of a biometric system, the two records will sit in separate places until someone reconciles them manually — there's no live API bridge between VizPass and biometric hardware today. This matters most in factories and warehouses where the gate tablet is trying to replace, or sit next to, an existing punch machine — worth checking against the use cases VizPass is built for before assuming one device fully absorbs the other.
Does VizPass control turnstiles or boom barriers at the gate?
No, VizPass doesn't operate turnstiles, boom barriers or electronic door locks — it handles the approval and pass layer, not the physical hardware layer. In practice, a guard checks the visitor's approved pass or the staff attendance record on the tablet, and then opens the barrier or turnstile manually, the same way they would with a paper register. VizPass isn't wired into the barrier's motor or the turnstile's access controller, so there's no automatic "pass approved, gate opens" trigger. For sites that already run automated boom barriers tied to RFID or access cards, VizPass sits alongside that system rather than replacing or driving it. This is a common point of confusion for warehouses and campuses that assume "gate management software" means the barrier itself moves — it doesn't; it means the record and approval behind why the barrier should move, which is spelled out in more detail under industries for warehouse and campus setups specifically.
Can I export VizPass visitor logs for a DGFASLI safety audit?
Yes, VizPass keeps a log of visitor and vendor entries — name, host, purpose, entry and exit time — that can be exported so a safety officer has something to hand an auditor. The export pulls from the same record created at check-in, so there's no separate data-entry step for compliance purposes; whatever was captured at the gate is what sh
Before you connect anything, decide who owns Settings
The messaging and SMTP swap-in above take five minutes to configure but only if one person is responsible for doing it — not the guard, not the shift-in-charge, and rarely IT if your plant runs lean. On a 40-machine unit where the safety officer, the HR head and the front-office admin all touch VizPass, decide upfront who holds the Settings login, because that's also who controls exports. Exports of the visitor register, passes and reports to CSV/Excel are permission-controlled by design — useful when an auditor from a client's quality team wants six months of contractor entries and you don't want every security guard able to pull that file.
The integration that gets forgotten until the audit
A pre-registered visit throws off a calendar .ics invite for both host and visitor, addable to Google Calendar or Outlook — small thing, but it means a visit doesn't live only inside VizPass's memory. Plants that skip this and rely purely on the tablet log usually rediscover it the week a DGFASLI inspection or an ISO surveillance audit asks for proof a visit was scheduled, not just logged at the gate.
Where attendance and identity cross into VizPass, and where they stop
- Biometric punches, not visitor swipes: eSSL and ZKTeco readers that speak the ADMS 'iclock' push protocol send staff punches to VizPass over the internet, no middleware PC in between — but this is for companies on the Gate & Attendance plan, and it's staff attendance, not a visitor credential. Don't expect the same reader to double as a visitor gate.
- SSO inside BeyondBox only: if your teams already use another BeyondBox product, a user can be dropped into VizPass with a short-lived signed ticket. No new accounts get created by this — it's a door, not a directory sync, so it won't onboard your ERP's employee master.
- Scheduling by webhook: when the host is the reason a job doesn't fire — on leave, on a shop floor with patchy signal — a webhook URL lets an external cron drive VizPass's scheduled jobs instead. This is a workaround, not a general automation layer; there's no Zapier-style connector to wire VizPass into fifty other apps.
What VizPass will not do at the gate today
Say this plainly, because it saves a wasted sales call: VizPass does not talk to ANPR cameras, boom barriers, turnstiles, weighbridges, ERPs or HRMS systems. If your gate process today depends on a barrier that lifts automatically when a truck's number plate is read, that integration doesn't exist yet. There's also no public visitor API — the mobile API that does exist covers staff attendance, leave, expenses and field work, not visitor data. If your workflow genuinely needs one of these, raise it through support; it goes on record as a request, not a promise.
What to measure once it's live
Skip the temptation to judge integrations by how clever they look in a demo. Track instead: how many gate entries needed a manual WhatsApp because the automatic one failed (power cut, SMTP hiccup), how often exports actually got pulled versus requested verbally, and whether the calendar invite reduced no-shows for scheduled vendor visits. None of that is a number VizPass can promise you in advance — it depends on your gate, your contract labour turnover, your technicians' comfort with a tablet in Hindi, Marathi or Tamil. Compare what you actually need against what's on /features and /pricing before the PO, not after — and if your situation looks close to another plant's, /industries and /use-cases are a faster read than a sales call.