Enterprise DNA

Instead of Envoy Visitors

Stop renting Envoy Visitors. Own your visitor system.

We build your version around how your reception teams work, bring your Envoy visitor history across and run it for you. Your sites, hosts and retention rules belong in your system.

Envoy Visitors Premium lists at US$362 per location per month, billed annually. That is US$4,344 per location each year.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

A recurring charge at every reception desk

Envoy prices Visitors by location. Compare the reception work you need with a system built around your own sites.

paid

A licence for each location

Premium is US$362 per location per month on annual billing. Adding sites adds subscriptions.

login

Visitor sign-in records

Envoy combines check-in and check-out records with a searchable visitor log.

group

Host review workflows

Its plans include visitor workflows and host approvals. Your version follows your own approval rules.

description

Document collection

Envoy offers legal-document features. We scope the documents and evidence your reception team needs.

download

History and exports

Envoy supports visitor-log exports. Keep useful history when you change the system around it.

domain

A quoted enterprise tier

Enterprise pricing is custom. Review the features in your agreement alongside the work your sites actually do.

What your version does

Run the reception week from your own records

ARRIVALS

Prepare hosts before visitors arrive

Keep expected arrivals and host decisions together, with overdue approvals visible.

  • check Register an expected visit with its site, host and purpose
  • check See the next seven days of arrivals across sites
  • check Record a host approval or decline before arrival
  • check Find expected visits assigned to unavailable hosts

RECEPTION

Reconcile the people recorded onsite

Staff record arrivals and departures. Historical imports stay separate from current visits.

  • check Require approval and current notice and induction evidence before sign-in
  • check Record a confirmed departure against the same visit
  • check Find overdue departures by host and site
  • check Generate visitor passes and reception arrival packs in your brand

RETENTION

Give old visitor records a review date

Each site has its own review period. Holds and unresolved presence prevent premature redaction.

  • check See old records due for a retention decision
  • check Keep held records visible until someone reviews the reason
  • check Redact identifying visit fields after an approved decision
  • check Flag notice and induction evidence that is missing or needs review

HANDOVER

Ask questions across the whole reception week

Combine host availability, visit history and evidence gaps in a review shaped around your business.

  • check Rank hosts by overdue departures
  • check Compare completed visit duration across sites
  • check Find companies with visits across several locations
  • check Draft the weekly reception handover from arrivals, exceptions and evidence checks

Make it yours

Design your own Envoy Visitors replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Envoy Visitors. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Envoy Visitors replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Envoy Visitors data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Visitor Management for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Visitor Management for Claude Code

Connected to your own database

Which visits need attention before the next handover?

VIS-002

Site
AKL
Visitor_name
Alex Moore
Host
Ari Chen
Status
onsite
Reason
Departure overdue

VIS-004

Site
SYD
Visitor_name
Sam Lee
Host
Ari Chen
Status
pending
Reason
Host unavailable

Ask it anything

Ten questions to ask your visitor records

These answers combine visit history, site policies and host availability. They run on the records you own.

chat_bubble Which hosts have the most overdue departures?
chat_bubble Which sites have visitors without current notice evidence?
chat_bubble Which companies have visits across several sites?
chat_bubble Which hosts have arrivals waiting for approval?
chat_bubble Which historical records have passed our retention date?
chat_bubble Which visitors arrived without the current induction record?
chat_bubble Which expected visitors have an unavailable host?
chat_bubble How long do completed visits last at each site?
chat_bubble Which held records need a retention decision?
chat_bubble Which sites need the most work before the next reception handover?

Switching

How to switch from Envoy Visitors

A move involves exporting each location’s visitor log, testing the historical import, checking the records, then running both systems side by side before you retire Envoy.

  1. 1

    Export each location

    Export the visitor log as a CSV for each Envoy location. The migration uses one export per location, so keep each export tied to the site it came from. If you cannot find the export or need to confirm what your account allows, check with Envoy Visitors. Decide which history to bring before you start, since some records need separate handling.

  2. 2

    Test the import

    Load the exports into the new database using the import’s dry run first. The import brings in visitor names, companies, hosts, and arrival and departure times as historical records. A dry run lets you review the proposed import before accepting it. Do not treat imported history as a list of people currently in the building.

  3. 3

    Review flagged records

    Check the dry-run results and resolve any records the import flags before accepting the import. Confirm dates and timezones, and make sure each export is associated with the right location. The import covers the visitor log fields listed above. Photos, signed documents, custom fields, and future invitations need a separate migration plan.

  4. 4

    Run both systems briefly

    Keep Envoy Visitors and the new system in use side by side for a short period. Have reception staff check that the imported history is in the right location and that they can handle the current reception process in the new system. The free base is operated by a staff member, so check any unattended sign-in, badge, or door-control needs before changing that process.

  5. 5

    Switch off Envoy Visitors

    After you have checked the imported records and confirmed the replacement reception process works for your staff, decide when to stop using Envoy Visitors. Before you close out the old process, make sure you have a plan for any photos, signed documents, custom fields, or future invitations you still need. Keep any required records and reports according to your own retention process.

construction

Where the real effort goes

The main work is usually mapping your own fields and reception rules, then deciding how much history to bring across. The visitor log import covers names, companies, hosts, and arrival and departure times. Photos, signed documents, custom fields, and future invitations need separate planning. Enterprise DNA handles this mapping and migration work when you have them install and run your version.

Not ready for a call?

Get your Envoy Visitors switch plan by email

We will send you the step-by-step plan for moving your business off Envoy Visitors, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to make it yours

Start with the free version or have your reception system built

Open source

Do it yourself

Free code

  1. 1 Clone the repo, then run npm install, npm test and npm run demo.
  2. 2 Open the folder in Claude Code, Codex, OpenCode or Cursor.
  3. 3 Export the Envoy visitor log as CSV and run import envoy for each location with a dry run first.
  4. 4 Compare the imported history, test the staffed reception process and set your own retention policies.
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer

  • check Your sites, visitor fields and host approval rules
  • check Your Envoy history brought across and checked
  • check Your reception screens, document process and hardware integrations scoped together
  • check A different stack if that suits your business
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a monthly retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Access controls, backups and recovery checks for your team
  • check Reception exceptions and retention reviews brought into your weekly routine
  • check Your system maintained as sites, staff and policies change
Book a call with Sam

Questions

Instead of Envoy Visitors, answered

What does Envoy Visitors cost compared with this? expand_more

Premium lists at US$362 per location per month, billed annually. Enterprise is quoted. The free version here has no software licence fee; hosting and your chosen assistant can have their own costs. Enterprise DNA builds and runs your version for one setup fee, then a retainer.

Can we bring our visitor history across? expand_more

Yes. Export the visitor log as CSV for each location. The free version imports names, companies, hosts and arrival and departure times as historical records. Check dates and timezones before accepting the import. Photos, signed documents, custom fields and future invitations need a separate migration plan.

Will this replace the iPad and door integrations at reception? expand_more

We can build the reception screens and integrations your sites need as part of your version. The free base is operated by a member of staff. We scope unattended sign-in, badge hardware and door controls before you change the current process.

Does the onsite list prove who is in the building? expand_more

It shows who has been recorded as signed in and not yet signed out. It is a point-in-time reception record. Staff still reconcile physical presence and follow the site emergency plan. Imported history never appears as a current arrival.

How are privacy and retention handled? expand_more

Each site sets a review period and records notice and induction evidence. The system flags missing evidence and old records. Holds block redaction until reviewed. Your team decides the lawful purpose and disposal process, including saved reports and backups. A check result is not a compliance certification.

Show Sam your reception process and Envoy bill

In a 30-minute call, walk through one site, its visitor history and the reception equipment you need. Sam will scope your version, the migration and ongoing operation. One setup fee, then a retainer.

Book 30 minutes with Sam Get the free version

Visitor Management for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Envoy Visitors?

Get your version built