Support Center
Get help with your Nonstop Automation setup. Our team is here to support you every step of the way.
Email Support
Send us an email and we'll get back to you within 24 hours.
customersupport@nonstopautomation.comLive Chat
Chat with our support team in real-time during business hours.
Support Hours
Monday - Friday
8:00 AM - 5:00 PM EST
Frequently Asked Questions
Get answers to the most common questions about our automation platform, implementation, and ongoing support.
Is this a lead generation service?
Can the AI actually book appointments in my CRM?
What happens during after-hours and weekends?
Will automation replace my team members?
How quickly can we get started?
What about data security and compliance?
How do I integrate with my CRM?
What's included in the setup process?
Best Practices for Testing Your Account
1. Always Use Unique Test Data
When creating a test contact, never use real user data, especially if that contact already exists in the system. Reusing existing email addresses or phone numbers can cause the system to associate your test with real, active records—leading to confusion, errors in automation, and inaccurate API results.
Example (What NOT to do):
Name: "Sammy Test or Test Test"
Email: samantha@realdomain.com (already exists in the system)
Result: This will cause conflicts because that email is already linked to another contact.
2. Naming Conventions for Test Contacts
To clearly identify a test contact while avoiding system flags for the word "test", follow this naming format:
Use this structure: FirstNameTest LastNameTest
- • Do not use the word "test" alone or in multiple instances (e.g., "Test Test").
- • Do not use spaces or special characters in the name.
Example (Correct Format):
Name: JohnTest TolentinoTest
Email: john.tolentino@gmail.com
3. Use Fake but Unique Phone Numbers
Avoid placeholder numbers like 1234567890 or 1111111111, as these are often flagged or already tied to other test accounts.
Format: Use a real area code with a made-up number that ends uniquely (e.g., last 4 digits = ZIP code).
Example: 619-555-7890
4. Use a Clearly Fake but Unique Email
Use a test email that looks valid but is obviously not a real user or business contact. This ensures the system treats it as new and avoids matching it to existing records.
Format: firstname.lastname.@gmail.com
Example: john.tolentino@gmail.com
5. API Considerations
The API relies heavily on email and phone number to match and pull records. If a test email or number is reused (or previously existed), the API may:
- • Retrieve the wrong contact
- • Delay test results
- • Overwrite existing records unintentionally
Be mindful to create completely new, isolated test data for every unique test case to ensure valid responses from the API.
Video Tutorials
GHL Conversations
Learn how to manage conversations in GoHighLevel
GHL Contacts
Master contact management in GoHighLevel
GHL Opportunities
Track and manage sales opportunities
GHL Connecting Calendars
Set up calendar integrations
GHL Adding a New User
Learn how to add team members