Before you buy
Test the work you need your software to do.
Build a practical test plan, try it in your shortlisted tools, and compare what actually worked.
No account needed. The sample contacts cannot receive email: nothing is ever sent to them.
- Six fictional contactsOne exact duplicate, one unsubscribed, one with unknown permission.
- Nothing goes outPreviews and dry runs only. Without a safe preview, the test stops.
- Permission keptThe export test checks that permission status keeps its meaning.
Your plan lives only in this page. Reloading or closing the page clears it: download your results to continue later.
- 1 Shortlist
- 2 Requirements
- 3 Test plan
- 4 Decision sheet
How the test drive works
Contact data goes wrong quietly: a field dropped on import, a duplicate merged the wrong way, a segment that includes one person too many. This test drive uses six fictional contacts to check those points before any real list is involved.
Work in a separate test account. The addresses end in example.invalid, a domain reserved so that it can never receive email. Even so, send nothing: tests 4 and 5 use previews and dry runs only, and stop if the tool has none.
The decision sheet shows each product on its own. A failed essential test stays at the top, and suppression results are your own observation, never a legal assessment.
The six tests for CRM and email software
Find out whether CRM or marketing software handles contacts correctly and keeps unwanted messages from going out. Test version 1.0, test data version 1.0.
Test 1: Import without losing fields
Check that an import keeps your fields and handles an exact duplicate openly.
- Import the CSV.
- Map first_name, segment and permission_status to fields.
- Count the contacts after the import and look for Ana.
Passes when: Five unique addresses remain, or the duplicate is clearly marked for you to review. first_name, segment and permission_status are filled for every contact.
Test 2: Handle the duplicate
Check which update rule the tool applies when a known contact is imported again.
- Change Ana's company in the CSV.
- Import the file again.
- Open Ana's contact.
Passes when: The tool followed the rule you chose, and Ana's contact is still recognisable as the same person.
Test 3: Create an exact segment
Check that a segment selects exactly the contacts it should.
- Create a segment with both conditions.
- Open the list of matching contacts.
Passes when: Exactly two contacts match: Ana and Bo.
Test 4: Preview an automation
Check that you can see what an automation would do before it does anything.
- Build a flow for the segment with one branch.
- Run the preview or dry run.
- Check which contacts and which branch it shows.
Passes when: The preview shows Ana and Bo and the branch they take, and nothing is sent or changed.
Test 5: Check suppression
Check that contacts without permission are left out.
- Select all trial contacts as recipients.
- Open the recipient preview.
Passes when: Cy and Eli are both left out.
Test 6: Export and recheck
Check that an export keeps identity, segment and permission status recognisable.
- Export the contacts.
- Open the file and check email, segment and permission_status.
Passes when: Every contact keeps its email, segment and permission_status, and the meaning of the permission status is still clear.
Test data: six fictional contacts
Five unique addresses after the duplicate, and exactly two contacts in the segment trial plus subscribed: Ana and Bo. All of it is fictional.
| first_name | segment | permission_status | company | |
|---|---|---|---|---|
| Ana | ana@example.invalid | trial | subscribed | Demo company |
| Bo | bo@example.invalid | trial | subscribed | Demo company |
| Cy | cy@example.invalid | trial | unsubscribed | Demo company |
| Dee | dee@example.invalid | customer | subscribed | Demo company |
| Eli | eli@example.invalid | trial | unknown | Demo company |
| Ana | ana@example.invalid | trial | subscribed | Demo company |
CRM and email tools we are researching for this test drive
EngageBay
Product-specific steps: not ready. A source check on 28 September 2026 left open questions about plan limits and documented steps, so the general tests above apply to EngageBay as to any other product.
What the test drive does not do
- It does not operate your software. You carry out every step yourself, in your own test set-up.
- It does not rate or rank products, and it adds no score. Each product keeps its own results.
- It does not send anything. The sample contacts use example.invalid addresses, which cannot receive email.
- It keeps your plan only in this page. Download your results to continue later; nothing is stored elsewhere.
- A passed test drive is not a verdict on reliability, security, scale or legal compliance.
Questions about the test drive
Can I import these contacts into my live account?
Please do not. Use a separate test account or workspace, so no automation or list touches them.
The tool has no preview for automations. What now?
Stop test 4 and record it as blocked. Switching the flow on to see what happens is not a test step.
Does passing test 5 mean we comply with privacy law?
No. It shows that this tool left out two contacts under the rule of this test. Compliance depends on your consent records and processes.
Tests written and maintained by Daniel Haket. Version 1.0 of 2026-09-29: First version, from the build plan of 28 September 2026.