+3Our team is still in the early stages of setting up Freshdesk and we are looking for a permanent test environment beyond the temporary Sandbox feature. We aim to create and retain dummy tickets without data loss and integrate seamlessly with this test environment, ensuring no interference with our live system.
What are some ways you all would go about accomplishing something like this?
Best answer by mahendarsingh
Hi
Thank you for bringing this up.
To create a permanent test environment beyond the temporary Sandbox feature in Freshdesk, the best option would be to set up a separate Freshdesk instance exclusively for testing purposes. Here's how you can meet your requirements:
Creating and Testing Dummy Tickets without Data Loss: Utilize the dedicated test environment to create dummy tickets. Ensure that agent actions, automation rules, and workflows are thoroughly tested in this space. You can replicate your live workflows, automations, and configurations to ensure better alignment.
Seamless Integration with External Tools and Systems: Integrate external systems into the test instance using test or sandbox environments of those tools. This avoids any impact on your live data or operations.
Isolation from Live Operations: Keep the test environment completely separate from your production setup. Use different domain names or manage access carefully so agents and external tools understand which is for testing.
Thank you
+8Hi
Thank you for bringing this up.
To create a permanent test environment beyond the temporary Sandbox feature in Freshdesk, the best option would be to set up a separate Freshdesk instance exclusively for testing purposes. Here's how you can meet your requirements:
Creating and Testing Dummy Tickets without Data Loss: Utilize the dedicated test environment to create dummy tickets. Ensure that agent actions, automation rules, and workflows are thoroughly tested in this space. You can replicate your live workflows, automations, and configurations to ensure better alignment.
Seamless Integration with External Tools and Systems: Integrate external systems into the test instance using test or sandbox environments of those tools. This avoids any impact on your live data or operations.
Isolation from Live Operations: Keep the test environment completely separate from your production setup. Use different domain names or manage access carefully so agents and external tools understand which is for testing.
Thank you
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
