A test Account or test User lets you try out Playbooks, traits, conversation sync, and other setup against realistic data in your live Vitally environment, without skewing your reporting or reaching a real customer. This is different from a sandbox, which is a separate Vitally environment. If that is what you need, see How to Effectively Set Up and Manage Your Vitally Sandbox Environment.
The step most people miss: an Ignored account does not go through Playbooks, does not calculate formula traits, and does not appear in Table Views or Dashboards. Keep your test account Ignored while you set it up, then un-ignore it when you are ready to run your test.
Setting Up a Test Account
Use a distinctive name marker, for example
[TESTING-ONLY] Acme. Avoid relying on just "Test": a rule like Name contains test also catches real accounts such as "Greatest Co" or "Contest Ltd". A unique marker keeps your track rules, filters, and AI instructions accurate.Do not attach MRR, ARR, or other revenue data, so the account does not skew your reporting or get categorized as a paying customer.
Set up a track rule to ignore the account, under Settings > Accounts > Track Rules, for example Name contains TESTING-ONLY. See Configure Track Rules.
Create it through CSV upload or the REST API, not linked to a CRM record, once your track rule is in place. Accounts created this way are checked against your track rules as they are created, so the account is Ignored before any Playbook can pick it up. If you create it manually in Vitally instead, it is not checked against your track rules when it is created. It starts tracked, can enrol in Playbooks triggered on creation, and stays tracked until it is next updated, for example when you edit one of its traits. Ignoring an account does not make it a full integration sandbox: while it is tracked, edits to synced fields can push back to your CRM.
Check that the account shows as Ignored before you generate any test activity. While it is Ignored, it does not go through Playbooks, does not appear in Table Views or Dashboards (only via search), formula traits do not calculate, and health scores and success metrics are frozen. See Categorizing Ignored Accounts for everything that changes while a record is Ignored.
Running Your Test
Un-ignore the account to test it. Edit or remove the track rule so the account no longer matches. Saving your track rules re-checks your accounts straight away, though it can take a little longer on larger workspaces. If your track rules use Include, the account is only tracked once it matches one of your include rules. Changing its subscription status manually does not un-ignore an account that a track rule ignored. Check that its status has actually changed before you start testing.
Expect Playbooks to pick it up straight away. As soon as the account is tracked, it is eligible for Playbooks, including any triggered on creation. A Playbook whose only trigger is Created At enrolls the account as soon as it is tracked.
Give formula traits time to recalculate. Formula traits resume calculating once the account is tracked, which can take up to an hour, or up to a day for churned accounts. Confirm the values you are relying on before you start testing. See Formula Traits.
Re-ignore it when you are done. Re-ignoring the account does not undo anything already sent or written to another tool.
Setting Up a Test User
Use an email address that does not belong to an existing team member, whether that team member holds a full seat or was auto-created. If an address exists as both, Vitally treats it as a team member, so messages from it are seen as outbound and the test User does not receive the conversations or meetings you expect. See There's missing email(s) in Vitally.
Plus-addressing is a simple option, for example
yourname+test@gmail.com. Vitally sees it as a separate address, but the mail still lands in your inbox, if your email provider supports it.Add your company's domain to Excluded Domains, under Settings > Security > Excluded Domains, so internal meetings and conversations do not sync in, even when a team member also exists as an end user. This applies only to meetings and conversations that sync in from that point on. Anything already in Vitally stays, so delete those manually.
If you are testing conversation or meeting sync, use an email on a domain that is not your company's and is not in your excluded domains list, otherwise those participants are filtered out.
Keeping Test Data Out of Quin
If you use Quin, an Admin or Leader can add a Global AI Memory such as "Ignore any account with TESTING-ONLY in the name when answering questions or generating summaries", so the test account does not show up in AI answers while it is tracked.
This list is not exhaustive. Depending on your setup, there may be other things to watch for.
