Healthcare · Managed platform (Envoy)

Visitor Management

Envoy visitor sign-in, screening and badging for hospital entrances, configured and run for you

Book a demonstrationRequest a technical briefingFactsheet

Overview

What you are buying

Moraph resells, implements and runs Envoy visitor management for hospitals, clinics and other care sites. We configure sign-in flows for patients' visitors, vendors, contractors and other guests, with the screening questions, watchlist checks, document signing and badges your security and infection prevention teams approve, then operate the service across your entrances: changes, kiosks and printers, monitoring and support. Your organization decides who may enter and on what terms, and every change to those rules is recorded with its approver.

The problem it solves

Hospital entrances see a constant flow of visitors, vendor representatives, contractors and couriers, often across many doors and sites. Paper logs and handwritten stickers do not show who is in the building, screening questions change with every outbreak and are applied unevenly, and security officers rely on memory for people who should not be let in. When an incident or audit happens, finding who was on a unit at a given time means searching through clipboards.

  • Paper logs do not show who is in the building or on a unit right now
  • Screening rules change often and are applied differently at each entrance
  • Restricted-visitor and watchlist checks depend on staff memory
  • Visit records are hard to search after an incident or for an audit

Who uses it

  • Directors of security and public safety at hospitals and health systems
  • Front desk, information desk and security officers at entrances
  • Infection prevention teams who set health screening rules
  • Facilities, supply chain and vendor management teams who host contractors and vendor representatives
  • Privacy and compliance officers responsible for patient and visitor information

Requirements it supports

HIPAA Privacy Rule (45 CFR Part 160 and Part 164, Subparts A and E)HIPAA Security Rule (45 CFR Part 164, Subpart C)CMS Conditions of Participation, patient visitation rights (42 CFR 482.13(h))The Joint Commission Environment of Care standard EC.02.01.01 and workplace violence prevention requirementsOSHA General Duty Clause (Section 5(a)(1) of the Occupational Safety and Health Act)

The product supports these requirements; meeting them remains your organization’s responsibility.

Responsibilities

Who is responsible for what

Envoy runs the platform, Moraph configures and operates your entrances on it, and your organization owns the decisions about who may enter and what is recorded.

AreaMoraphEnvoyYour organization
LicensingResells Envoy subscriptions, or works with licences you already hold, and tracks use against themSets licence terms and what each plan includesAgrees to Envoy's terms and decides sites and plans
Platform availabilityTracks Envoy service notices and tells you when an incident affects entrancesRuns, hosts and maintains the Envoy service and its availability commitmentsKeeps a paper or manual sign-in fallback at each entrance
ConfigurationDesigns the baseline and builds and maintains flows, questions and badgesProvides the configuration options the platform supportsApproves the baseline and every change to it
WatchlistApplies entries on request and keeps the change recordChecks visitors against the watchlist as configuredDecides who is on the watchlist and how matches are handled
DevicesSets up and supports kiosks, printers and scanners and coordinates replacementSupports the devices its platform works withProvides power, network, mounting and physical security at each entrance
Access and identityCreates administrator and staff accounts from your requests and connects single sign-onAuthenticates users as configuredDecides who should have access and tells Moraph about leavers
MonitoringMonitors device status, failed integrations and administrator activityMonitors its own platformMonitors your entrances and runs your security operations
Incident responseTriages incidents affecting the service, supports investigations with visit records and contains issues under the agreed procedureResponds to incidents in the Envoy platform itselfLeads security and privacy incident response and makes notification decisions
Policy decisionsRecommends settings with reference to your policies and accreditation requirementsNoneOwns visitor, screening, privacy and retention policy
User supportSecond-line support for staff and devicesSupport to Moraph for platform defectsFirst-line support at entrances, unless you hand it to Moraph

See how it works

A short walkthrough

Illustrative screens of how Moraph runs the service, with fictional sample data. They are not screens of Envoy itself, which belongs to its vendor.

  1. Step 1

    The entrance rollout tracker

    During implementation, every entrance has a row: its devices, the visitor types it handles and where setup stands.

    EntranceSiteDevicesVisitor typesSecurity sign-offStatus
    Main lobbyExample Medical Center (fictional)2 kiosks, 1 printer, 1 scannerAllSigned offLive
    Emergency departmentExample Medical Center (fictional)Desk sign-in, 1 printerPatients' visitorsSigned offLive
    Loading dockExample Medical Center (fictional)1 kiosk, 1 printerVendors, contractors, couriersSigned offTesting
    Women's and infants' entranceExample Medical Center (fictional)Desk sign-in, 1 printer, 1 scannerPatients' visitorsPendingUnit restriction rule not approved
    Outpatient clinicExample Clinic (fictional)1 kioskPatients' visitors, vendorsNot startedPlanned
    During implementation, every entrance has a row: its devices, the visitor types it handles and where setup stands.

  2. Step 2

    The configuration baseline

    Sign-in flows, screening questions, watchlist handling and retention are written down and approved before they go live.

    Baseline v2 · Example Health System (fictional)

    Status
    Awaiting approval
    Prepared by
    Moraph visitor platform engineer
    Approvers
    Security director, privacy officer
    Changes from v1
    4
    Retention for ID data
    Not yet set

    Key rules

    • Vendor representatives sign the vendor access policy at each visit
    • Patients' visitors answer the current health screening questions
    • Patient names not recorded at sign-in
    • Watchlist matches alert the security supervisor only
    Sign-in flows, screening questions, watchlist handling and retention are written down and approved before they go live.

  3. Step 3

    A screening change

    When conditions change, infection prevention requests new questions and the change goes live with an approval and a record.

    Change CR-0261 · Respiratory illness screening question

    1. Change requested for all entrancesInfection prevention lead
    2. Wording and outcome procedure agreedSecurity director
    3. Change approvedInfection prevention lead
    4. Question added and tested on a pilot kioskMoraph engineer
    5. Change applied to all entrances and desk staff toldMoraph engineer
    When conditions change, infection prevention requests new questions and the change goes live with an approval and a record.

  4. Step 4

    A watchlist match

    A possible match is shown privately to security, and the outcome is recorded.

    Watchlist alert WL-0093 · Main lobby

    Visitor
    Visitor 55102 (fictional)
    Visitor type
    Patient's visitor
    Match
    Possible match to watchlist entry
    Officer
    Desk officer on duty
    Status
    Security supervisor called

    Procedure

    • Do not tell the visitor about the watchlist
    • Call the security supervisor
    • Supervisor confirms identity and decides
    • Outcome recorded on the alert
    A possible match is shown privately to security, and the outcome is recorded.

  5. Step 5

    The device check

    Kiosks, printers and scanners are checked so entrances do not fall back to paper.

    EntranceDeviceLast seenIssueAction
    Main lobbyKiosk 1TodayNoneNone
    Main lobbyBadge printerTodayLow label stockFacilities told
    Loading dockKiosk 12 days agoOfflineTicket raised with IT network team
    Emergency departmentBadge printerTodayNoneNone
    Kiosks, printers and scanners are checked so entrances do not fall back to paper.

  6. Step 6

    The monthly service review

    Visits, changes, devices and support for the month, reviewed with your leads and turned into actions.

    Monthly service review · Example Health System (fictional)

    Period
    Sample month
    Visits recorded
    9,214
    Watchlist matches
    3, all handled under procedure
    Changes applied
    2
    Device tickets
    5

    Actions agreed

    • Approve retention period for ID data
    • Finish unit restriction rule for women's and infants' entrance
    • Add a kiosk at the outpatient clinic
    • Review vendor visits without an invitation
    Visits, changes, devices and support for the month, reviewed with your leads and turned into actions.

Workflows

The principal workflows

  1. Invite

    Staff pre-register expected guests such as vendors, contractors and interview candidates, so they arrive with their details and documents already handled.

    • Host invites the guest from the web or their calendar
    • Guest receives arrival instructions and any documents to sign
    • Vendor representatives' credentialing status is checked where integrated
    • Security sees expected arrivals by entrance and day
    • Host is told when the guest arrives

  2. Sign in and screen

    At the entrance, visitors sign in on a kiosk or with a desk officer, answer the screening questions for their visitor type, and are checked against your watchlist.

    • Visitor chooses their visitor type on the kiosk or tells the desk officer
    • Photo and ID captured where your policy requires
    • Screening questions for that visitor type answered
    • Name checked against your watchlist; matches go to security privately
    • Badge printed showing the destination and date

  3. On site

    While visitors are in the building, security and front desk staff can see who is signed in, where they were going and when they arrived.

    • Live list of signed-in visitors by entrance and destination
    • Unit restrictions applied, such as limits on visitors to a restricted unit
    • Host notified and comes to meet the guest where required
    • Visitors who have not signed out flagged at the end of the day
    • Security can look up a visitor during an incident

  4. Review and adapt

    Visit records answer questions after an incident, and screening rules are changed through approved requests when conditions change.

    • Visit log searched by person, date, entrance or destination
    • Records exported for an investigation or audit
    • Infection prevention requests a change to screening questions
    • Change approved and applied across the chosen entrances
    • Change history kept for review

Roles and permissions

Who does what in the product

Each role below is a starting point. During implementation we set them up to match your teams, and every action anyone takes is recorded in the audit trail.

Security director

Director of security, public safety manager, emergency management lead

Owns who may enter and on what terms, and uses visit records to manage incidents and risk.

Sees

  • All sites, entrances and visit records
  • The watchlist and alerts raised against it
  • The configuration baseline and its change history

Does

  • Approves the configuration baseline and changes to it
  • Decides who is added to or removed from the watchlist
  • Decides how watchlist matches are handled at the desk
  • Searches and exports visit records for incidents and audits
  • Chairs the monthly service review with Moraph

Cannot

  • Apply configuration changes in the platform directly
  • Approve a change they requested themselves when a second approver is named
Approvals
Approves the baseline, watchlist rules and changes to them; their own requests go to a named second approver.
Notified about
Watchlist matches, changes awaiting approval, and platform incidents that affect entrances.

Front desk or security officer

Security officer, information desk staff, lobby ambassador

Signs visitors in at the entrance and applies the screening and watchlist rules.

Sees

  • Expected and signed-in visitors at their entrance
  • Screening outcomes for visitors they sign in
  • Watchlist alerts for visitors at their entrance

Does

  • Signs visitors in and prints badges
  • Captures photos and ID where policy requires
  • Handles a failed screening under the agreed procedure
  • Calls security leadership on a watchlist match
  • Signs out visitors and checks end-of-day lists

Cannot

  • Change screening questions or watchlist entries
  • Search visit records outside their site
  • Override a screening or watchlist outcome without the procedure the security director set
Approvals
Overrides of screening or watchlist outcomes need security leadership approval as your procedure sets.
Notified about
Watchlist alerts and failed screenings at their entrance, and expected arrivals.

Host

Staff member, department manager, supply chain or facilities coordinator

Invites the guests they expect and is responsible for them while on site.

Sees

  • Their own invitations and guests
  • Arrival notifications for their guests

Does

  • Invites guests in advance with date, entrance and destination
  • Adds documents a guest must sign where allowed
  • Meets guests on arrival
  • Cancels invitations that are no longer needed

Cannot

  • See other hosts' guests or the full visit log
  • Bypass screening or watchlist checks for their guest
Approvals
Invitations for restricted areas may need approval from security, as your policy sets.
Notified about
Their guest's arrival and any problem at sign-in.

Infection prevention lead

Infection preventionist, director of infection prevention, employee health lead

Sets health screening questions for visitors and changes them when conditions change.

Sees

  • Screening questions by visitor type and site
  • Screening outcomes in summary
  • Change history for screening rules

Does

  • Approves screening questions and what happens when a visitor does not pass
  • Requests changes when outbreak conditions change
  • Reviews screening outcomes in summary
  • Works with security on visitor restrictions for affected units

Cannot

  • Change watchlist entries or sign-in flows outside screening
  • See individual visit records unless your policy allows
Approvals
Approves changes to health screening; changes touching security rules also need the security director.
Notified about
Screening changes applied and summaries of screening outcomes.

Privacy officer

Privacy officer, compliance officer

Decides what information is collected and kept about visitors and patients, and decides on privacy events.

Sees

  • Data collected in each sign-in flow
  • Retention settings
  • Privacy events Moraph escalates

Does

  • Approves what each sign-in flow collects, including whether a patient's name is recorded
  • Approves retention periods for visit records, photos and ID data
  • Decides on privacy events and whether notification is needed
  • Reviews Moraph staff access to the service

Cannot

  • Change configuration directly
  • Delegate a breach notification decision to Moraph
Approvals
Approves data collected and retention settings in the baseline with the security director.
Notified about
Privacy events and changes to data collected or retained.

Moraph visitor platform engineer

Moraph workplace platform engineer

Configures and supports Envoy under change requests your organization has approved.

Sees

  • Envoy administration settings within the service's scope
  • Device status for kiosks, printers and scanners
  • Tickets and the change record

Does

  • Builds sign-in flows, questions and badges as approved
  • Configures sites, entrances and integrations
  • Sets up and supports kiosks, printers and ID scanners
  • Investigates second-line issues and escalates platform defects to Envoy
  • Applies watchlist entries only when security requests them

Cannot

  • Approve a change they will apply
  • Decide who goes on the watchlist
  • Grant themselves additional administrator rights
Approvals
Every change they apply has an approved request; emergency actions follow the agreed procedure and are reported straight away.
Notified about
New tickets and requests, approvals granted, device problems and Envoy service notices.

Moraph service manager

Moraph service delivery manager

Runs the service, reports on it and makes sure requests, changes and escalations reach the right people.

Sees

  • Service reporting, tickets, changes and escalations
  • Device inventory and licence use
  • Open actions from service reviews

Does

  • Prepares and runs the monthly service review
  • Tracks requests, changes and escalations to closure
  • Reports licence and device needs
  • Coordinates with Envoy on platform incidents and service notices

Cannot

  • Apply configuration changes
  • Make security, screening or privacy decisions
Approvals
Recommendations go to the security director for a decision.
Notified about
Escalations, overdue requests and platform incidents.

Permissions at a glance

ActionSecurity leadDesk officerHostInfection ctlPrivacyMoraph eng.Moraph service
Approve the configuration baselineApprovesNo accessNo accessView onlyApprovesNo accessView only
Request a configuration changeFullNo accessNo accessFullFullNo accessNo access
Apply a configuration changeApprovesNo accessNo accessNo accessNo accessFullNo access
Change health screening questionsView onlyNo accessNo accessApprovesView onlyFullNo access
Add or remove watchlist entriesApprovesNo accessNo accessNo accessNo accessFullNo access
Invite guestsFullFullOwn work onlyOwn work onlyNo accessNo accessNo access
Sign visitors in and print badgesFullFullNo accessNo accessNo accessNo accessNo access
Override a screening or watchlist outcomeApprovesOwn work onlyNo accessNo accessNo accessNo accessNo access
Search and export visit recordsFullOwn work onlyOwn work onlyNo accessView onlyNo accessNo access
Set retention for visit dataApprovesNo accessNo accessNo accessApprovesFullNo access
Grant Moraph administrator accessApprovesNo accessNo accessNo accessView onlyNo accessView only
View change historyView onlyNo accessNo accessView onlyView onlyView onlyView only
  • Full
  • Own work only
  • Approves
  • View only
  • No access

How access is controlled

  • Moraph engineers apply changes; your organization approves them. Nobody approves a change they requested themselves when a second approver is named.
  • Watchlist decisions belong to your security team. Moraph enters or removes names only on a request from security, and watchlist matches are shown privately to the officers your procedure names.
  • Desk officers and hosts are limited to their own site or guests. Roles can be limited by site and entrance, so a satellite clinic sees only its own visitors.
  • Moraph staff use named, individual administrator accounts with only the rights the service needs. Every administrator action is recorded, and auditors get read-only evidence with a defined scope and end date.

Features

What it does

Kiosk and desk sign-in

Envoy provides sign-in on a tablet kiosk or by front desk staff, with flows that differ by visitor type.

Visitor types

Separate flows for patients' visitors, vendor representatives, contractors, interview candidates, couriers and others, each with its own questions and documents.

Health screening questions

Questions set by your infection prevention team for each visitor type, changed through approved requests when conditions change.

Watchlist checks

Envoy checks visitors against the watchlist your security team keeps, and alerts security privately on a possible match.

Badges

Printed visitor badges showing name, photo where captured, destination and date, so staff can see who should be where.

Pre-registration

Hosts invite expected guests in advance, so arrival is quicker and security sees who is expected.

Document signing

Envoy has visitors sign the documents you require, such as confidentiality or safety acknowledgments, before entry.

Host notifications

Hosts are told when their guest arrives, by email, text or messaging tool.

Multi-site configuration

One baseline across sites and entrances, with local differences recorded and approved.

Visit log

A searchable record of who visited, when, where they went and what they answered, kept for the period your policy sets.

Kiosk and printer support

Moraph supports kiosk tablets, badge printers and ID scanners, and coordinates replacement when hardware fails.

Controlled changes

Every change to sign-in flows, questions, watchlist rules and retention has a request, an approver and a record.

Integrations

How it connects to your systems

Connects toHowWhat flows
Single sign-onStaff and administrators sign in through your identity provider.In: user identity and group membership.
Employee directoryStaff are synced from your directory so visitors can find their host and hosts can invite guests.In: staff names, email, department and site.
CalendarHosts can invite guests from their calendar where your calendar system is connected.In: meeting invitations that include external guests.
Access controlWhere Envoy supports your access control system, approved visitors can be given temporary access to specific doors.Out: visitor credentials limited to the doors and times approved.
Vendor credentialingWhere an integration is available, vendor representatives' credentialing status from your vendor credentialing system is checked at sign-in.In: credential status for vendor representatives.
Messaging and emailArrival notifications and security alerts go to hosts and officers by email, text or your messaging tool.Out: arrival notices and alerts.
Your service deskTickets pass between your IT service management tool and Moraph's.In and out: ticket details and status.

Each integration is confirmed in discovery and specified in the design. See how an engagement progresses.

Security and privacy

How your data is protected

Data you choose to collect

Each sign-in flow collects only what your privacy officer approves; by default the patient being visited is not recorded.

Business associate agreement

Where visit records include patient information, Moraph signs a business associate agreement and patient details are only recorded where Envoy's terms allow it.

Role-based access

Desk officers see their entrance, hosts see their guests, and the full visit log is limited to the roles you choose.

Complete audit trail

Envoy records sign-ins and administrator actions, and Moraph's change record links each change to its request and approval.

Encryption and keys

Service records Moraph holds are encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.

Audited company-wide

Moraph is audited to SOC 2 Type II and ISO/IEC 27001 across the company, including the teams that run this service. Envoy's own attestations cover the platform.

Company-wide controls, independent audits (SOC 2 Type II and ISO/IEC 27001) and data residency are described in our Trust Center, where you can request the evidence pack.

Reporting

What you can report on

11 standard reports, grouped by who uses them. Each shows who it is for, how it can be broken down, how it is delivered and what it is used for. The data behind them is also available to your own reporting tools.

Operational

Visitors on site

For security director and desk officers

Everyone signed in now, by site, entrance and destination, with arrival time.

Break down by
Site, Entrance, Destination, Visitor type
Delivered as
Live view
Used for
Knowing who is in the building during normal operations and incidents.

Not signed out

For desk officers and security supervisors

Visitors still signed in at the end of the day or past the time set for their visitor type.

Break down by
Site, Entrance, Visitor type
Delivered as
Live view; daily email
Used for
Closing out the day's records and checking for anyone still on site.

Expected arrivals

For desk officers and hosts

Guests invited for the day by entrance, with their host and documents still to sign.

Break down by
Site, Entrance, Host, Visitor type
Delivered as
Live view; morning email
Used for
Preparing entrances for expected vendors, contractors and guests.

Security

Watchlist matches

For security director

Possible watchlist matches, the officer who handled each and the outcome.

Break down by
Site, Outcome, Date
Delivered as
Live view; email at the time of the match
Used for
Reviewing how matches were handled and whether the watchlist needs updating.

Visit history search

For security director and investigators

All visits for a person, unit, entrance or time period, with screening answers and badges printed.

Break down by
Person, Destination, Entrance, Date range
Delivered as
On request; CSV and PDF export
Used for
Answering who was where during an incident or investigation.

Screening outcomes

For infection prevention lead and security director

Visitors who did not pass screening, by visitor type and site, and what happened next.

Break down by
Site, Visitor type, Question, Outcome
Delivered as
Weekly summary; CSV export
Used for
Seeing whether screening rules are working and applied the same at every entrance.

Volume

Visits by site and type

For security director and facilities

Visit counts by site, entrance, visitor type and time of day.

Break down by
Site, Entrance, Visitor type, Hour of day, Period
Delivered as
Monthly report; CSV export
Used for
Staffing entrances to match the flow of visitors.

Vendor and contractor visits

For supply chain and facilities

Vendor representatives and contractors who visited, their host and destination.

Break down by
Company, Host department, Destination, Period
Delivered as
Monthly report; CSV export
Used for
Checking vendor activity against your vendor access policy.

Governance

Configuration change history

For security director, privacy officer, auditors

Every change to flows, screening questions, watchlist rules and retention, with requester, approver and date.

Break down by
Change type, Site, Approver, Date
Delivered as
Live view; PDF and CSV export
Used for
Evidencing that entrance rules were approved before they changed.

Monthly service review

For security director, infection prevention and IT lead

Visits, changes, devices, tickets and incidents for the month, with open actions.

Break down by
Month, Topic, Action owner
Delivered as
PDF; presented in the review meeting
Used for
Running the service with your organization and agreeing what to do next.

Retention and deletion

For privacy officer

Visit records, photos and ID data held, their retention period and records deleted on schedule.

Break down by
Data type, Site, Retention period
Delivered as
Quarterly report; PDF export
Used for
Showing that visitor data is not kept longer than your policy allows.

Exports, access and evidence

  • Live views come from Envoy; summary reports are produced by Moraph from Envoy's data and Moraph's ticket and change records, and reviewed with you each month.
  • Reports respect each viewer's role: desk officers see their entrance, hosts see their guests, and full visit history is limited to the roles you choose.
  • Visit history can be exported to CSV or PDF for an investigation or audit, and each export is recorded.
  • Report contents, recipients and frequency are agreed during implementation; additional views can be requested through the service review.
  • Reports only include what each sign-in flow collects, so they never show information your privacy officer chose not to collect.

Deployment

Where and how it runs

Licences through Moraph

Moraph resells the Envoy subscription and runs it as one service, subject to Envoy's terms.

Your existing Envoy account

If you already license Envoy, Moraph reviews the current setup against a new baseline and takes over its operation.

Co-managed

Your team keeps some tasks, such as watchlist entry or first-line device support, and Moraph runs the rest; the split is written into the responsibilities for the service.

Security controls, independent audits and data residency are set out in our Trust Center. Engagement models and what drives a quotation are on Working with Moraph.

Implementation

What a rollout involves

The general phases are on Working with Moraph. For this product, they involve the following.

Discovery

We review your sites, entrances, visitor types, current sign-in process, visitor policy and any visitor restrictions with your security, infection prevention and privacy leads.

Baseline design

We propose sign-in flows, screening questions, documents, badges, watchlist handling and retention, and agree the baseline with your approvers.

Entrance setup

Kiosks, badge printers and ID scanners are installed or configured at each entrance with your facilities and IT teams.

Integrations

Directory, single sign-on, notifications and any access control or vendor credentialing integrations are connected and tested.

Pilot entrance

One entrance goes live first with extra support, and flows and procedures are adjusted with your desk staff.

Rollout and handover

Remaining entrances go live in an agreed order, staff are trained, and the change process, escalation contacts and reporting move into day-to-day operation.

Limitations

What it does not do

Worth knowing before you evaluate it.

  • Moraph is not Envoy. Envoy operates the platform, and Envoy's own service commitments, roadmap, maintenance and outages apply.
  • Envoy licences are subject to Envoy's terms. Kiosk tablets, printers, scanners and some integrations are priced separately.
  • Moraph does not staff entrances or provide security officers. Your staff sign visitors in and respond to alerts.
  • Watchlist checks only find people on your watchlist. The service does not perform criminal background checks.
  • Health screening relies on the answers visitors give. It is not a clinical assessment, and your infection prevention team decides the questions.
  • Access control and vendor credentialing integrations depend on what Envoy supports with your systems.
  • Visitors who bypass a staffed or kiosk entrance are not recorded. Physical entrance control is your organization's responsibility.
  • Moraph does not make privacy or breach notification decisions; your privacy officer does.

Evaluation checklist

What to test in a demonstration or pilot

Questions worth putting to us, and to any other vendor you are considering.

  1. List your entrances and visitor types and check each has a proposed sign-in flow
  2. Walk a vendor representative and a patient's visitor through sign-in at a pilot kiosk
  3. Review what each flow collects with your privacy officer
  4. Rehearse a watchlist match with your desk officers and security supervisor
  5. Run a visit history search for a fictional incident and check the export
  6. Confirm the split of responsibilities between your security team, Moraph and Envoy

Questions

Frequently asked questions

Do we buy Envoy from Moraph or from Envoy?

Either. Moraph can resell the subscription, or run an account you already license. In both cases Envoy's terms apply to the licence.

Do you record which patient a visitor is seeing?

Only if your privacy officer decides you need to. By default the sign-in flows do not ask for the patient's name. Where patient information is recorded, Moraph signs a business associate agreement and it is only collected where Envoy's terms allow it.

Who decides who goes on the watchlist?

Your security team. Moraph applies entries only on their request, and matches are handled under the procedure your security director sets.

What happens if Envoy or a kiosk is down?

Envoy's own service commitments and incident process apply to the platform. Moraph tells you when an incident affects entrances and works on device problems, and each entrance keeps a manual sign-in fallback agreed during implementation.

How is it priced?

Envoy licences are priced under Envoy's terms, hardware separately, and the managed service and implementation are quoted separately. See Working with Moraph for what drives a quotation.

Can we take the service back in-house?

Yes. The account and its configuration are yours; at the end of the agreement Moraph hands over the baseline, documentation and change history and removes its administrator accounts.

Next steps

Evaluate Visitor Management

Book a demonstration

See the product working with sample data, focused on your workflows.

Request a demonstration

Request a technical briefing

Architecture, integrations, security and hosting, with our engineers and your technical team.

Request a briefing

Factsheet

This page on two sides, to share with colleagues or add to your evaluation file.

Open the factsheet

Buying through a formal procurement? See How to buy for purchasing routes, accessibility conformance reports and company information. Documentation: Visitor Management guides on docs.moraph.com (getting started and security guides are public; setup, administration and integration guides are for client accounts). Support: Visitor Management support guide.

Related products