# A recruitment inbox is not an employee address: reviewing Insacheck’s shared-address setup
Prepared on behalf of Insacheck. This is a document-based feature assessment, not an independent customer testimonial. The following are proposed checks, not completed tests. Imagine a small employer preparing a recruitment notice while two administrators take turns handling questions. Before publishing its contact details, the team needs to distinguish a shared recruitment address from the mailbox assigned to a named employee.
Contents
# Two address purposes in the published guide
Insacheck’s company-mail guide describes employee addresses on a connected company domain, with configuration and issuance available to representative and company administrators.
Individual employee mail addresses are created by selecting an eligible employee and reviewing the proposed address before issuance.
The guide directs administrators to the separate Shared addresses tab and Create shared address action for contact addresses used by multiple people, such as general or recruitment enquiries.
# A recruitment handoff to review before advertising the address
The first decision is about purpose, not the spelling of the address. A named employee address identifies an individual in the organisation; a recruitment contact represents a continuing point of contact for a task. The guide gives the latter a separate creation route. That distinction is useful to an evaluator even before considering how incoming messages will be handled.
For the fictional employer, a small proposed responsibility table would list the recruitment contact, the person covering today’s enquiries and the person taking over tomorrow. This is an operating checklist for discussion, not a claim that Insacheck includes an assignment board, shift rota or automatic case routing. A shared contact name does not by itself settle who must respond.
A demonstration request could use one invented enquiry with no applicant details. The evaluator would ask the supplier to show which authorised people can see the message and which address appears to the recipient when a reply is sent. This review has not opened a shared mailbox or sent such a message. It therefore does not assume permission granularity, a shared sent folder or a particular sender-selection control.
A second proposed check concerns the handoff. Suppose the first administrator has already replied when the next person starts covering the contact. How would the second person establish that a response was sent, and what information should the team record outside the mailbox if needed? These are questions for a demonstration and an internal working agreement; duplicate-reply prevention and read-state synchronisation are not established here.
The team should also ask how access is granted and withdrawn when the people covering recruitment change. The published creation instructions are not enough to prove how an existing shared address behaves after an individual employee leaves. This article does not extend the separate employee-address withdrawal policy to every shared-address permission or promise uninterrupted delivery during personnel changes.
This feature is worth a closer look for an employer that wants its recruitment contact to remain distinct from a particular employee’s identity. The readiness decision is narrower than declaring the mailbox fully operational: the team would need a confirmed address, a demonstrated access and reply path, and an agreed human handoff. Those conditions should be checked before the address is printed on a real vacancy notice.