You can learn how Envelaro works without starting with the domain customers use every day. A separate domain that your business owns can provide a place to test setup, administration and a small set of everyday email workflows.
The purpose is to gather evidence for a decision. An evaluation should end with a list of what worked, what needs clarification and what a production migration would require. There is no requirement to move your primary email or provide a favourable testimonial.
1. Choose a genuinely non-critical domain
Use a secondary or test domain that you own and can administer. Check that it is not receiving orders, used for account recovery or connected to an application that depends on its current email service. “Secondary” does not automatically mean unused.
Record its existing DNS and confirm who can approve changes. Keep the primary business domain’s MX and authentication records unchanged throughout this evaluation. Do not forward production mail or import sensitive customer messages just to populate the test inbox.
A separate domain keeps its mail-routing changes distinct from your primary domain. It does not eliminate every risk: access permissions, shared DNS accounts and the people performing the changes still need care.
2. Prepare the people and the setup
Include the person responsible for domain administration and someone who can assess daily use and commercial fit. Agree a few tasks in advance, such as creating an alias, finding an older test message or helping another participant sign in.
For the guided evaluation, submit the evaluation request with your current provider, team size and what you want to learn. Coordinate onboarding before starting the timed trial so support and participants are available.
The trial requires a verified tenant-administrator account, a verified business domain and at least one configured mailbox. Envelaro’s trial dialog shows the missing domain and mailbox steps before activation. Domain ownership verification is a preparation step; complete the displayed mail-routing instructions separately when the service records are ready.
3. Understand the trial allowance
The standard card-free trial lasts seven business days after successful activation. Weekends remain accessible and do not count toward those seven days. The displayed expiry is the reference for your workspace.
The trial permits up to three mailboxes, with 1 GB per mailbox and 1 GB of shared file storage. External sending is limited to five recipient deliveries per mailbox per day. Plan a small set of consenting test recipients and leave room for replies; this allowance is not intended for outreach campaigns or load testing.
The trial does not automatically become a paid subscription. Review the current billing policy and plan details before choosing paid service. Migration assessment can be discussed during evaluation, but migration execution requires an active plan and an agreed paid migration package.
4. Test a small set of real workflows
Use harmless sample messages and documents. Once the test domain’s mail records are ready and published, send controlled messages to mailboxes you or participating colleagues can inspect. Test receiving, replying and a small attachment as well as simply pressing Send.
Write down the result of each task and the steps required. If an action fails, capture the time, the relevant error and the domain or mailbox involved; do not share passwords or private message contents in a support request.
- Administration: understand mailbox and alias setup, access controls and the distinction between administrator and mailbox sign-in.
- Everyday mail: check folders, search, replies and the devices or email clients your team needs.
- Delivery: verify an incoming message, an outgoing message and a reply; inspect authentication results on a controlled received message.
- Support: ask one concrete setup question and assess whether the answer explains the next action.
5. Review results before considering a migration
Meet with the participants and compare the results with the tasks you agreed at the start. Separate configuration questions from missing requirements. A feature demonstrated in another product, a public roadmap or a sales conversation is not a substitute for confirming the workflow you need.
A small trial cannot establish long-term availability, large-mailbox migration performance or every aspect of delivery reputation. If you intend to move production email, request a separate scope covering source access, eligible data, backups, downtime expectations, cutover responsibilities and recovery.
Proceed only when the decision-maker understands the remaining work and the applicable charges. A useful evaluation can also end with a decision to keep the current provider.
6. Close the test deliberately
Before the trial ends, save any test results or data you need and decide whether to continue with a paid plan. If you stop, review the data-lifecycle policy and ask support about closing the workspace and removing test data.
Review the secondary domain’s DNS as part of closeout. If it will receive mail elsewhere, prepare the intended service before changing routing. Remove obsolete sender authorisations only after confirming that no legitimate service still uses them. Your primary business email can remain with its existing provider throughout.
Primary sources
Provider interfaces and requirements change. Check the linked source before applying a production change.