How to Contact & Work with Our Support Team

How to Contact & Work with Our Support Team


This article walks you through everything you need to know about contacting support, what to expect, and how to get your issues resolved efficiently.

1.  Contact Support

How to Reach the Support Team

We offer three ways to get in touch with our support team. Choose the channel that best suits the urgency and nature of your issue:
  1. 📧  Email: 

    Drop an email to support@zohonotebook.com - Best for non-urgent issues, detailed bug reports, or when you need to attach files and logs.
  1. 💬  In-App Chat/ Feedback:

    Open the app and follow the steps mentioned here to initiate the chat/ send feedback based on your platform. Best for quick questions during business hours.
  1. 🌐  Community Forum:

    Ideal for general questions, tips, and peer-to-peer assistance. Monitored by the Support team.

Support Response Expectations:

Typical Response Times by Channel

 


Channel


Business Hours/ Days


Outside Hours


Email


Within 12 hours


Next business day


In-App Chat


Within –2 hours


Within 8 hours


Community Forum


Within 2 days


Within 1–2 days


What to Include When Submitting a Ticket:

To help us resolve your issue as quickly as possible, please include the following when contacting support:
  1. A clear, concise description of the problem
  2. Steps to reproduce the issue (in order)
  3. Expected behaviour vs. what actually happened
  4. Screenshots or screen recordings showing the issue
  5. Device details: operating system, browser/app version
  6. Any error messages or codes displayed
  7. Logs or crash reports, if available
  8. The date and time the issue first occurred

2.  Understanding Our Support Process

What Happens After You Submit a Ticket:

Once your ticket is received, it moves through the following stages:
  1. Ticket Creation & Acknowledgement -  Once a ticket is created, it is reviewed by a support engineer, who will respond within the specified timeframe with either a solution or the next steps to help resolve the issue.

  2. Follow-Up Questions (If Needed) - We may ask for additional details or request a call/ meeting session to diagnose complex issues.

  3. Escalation (If Required) - If the issue requires deeper investigation, your ticket is escalated to our engineering or product team. You will be notified when this happens.

  4. Resolution & Closure - Once resolved, we send a closure confirmation. You may reopen the ticket within 7 days if the issue recurs.

Bug Reporting Workflow:

How Bugs Are Logged Internally:

When you report a bug, our support team validates and reproduces the issue, then logs it in our internal issue tracker with full context. 

From Issue Analysis to Fix and Deployment:
  1. Support engineer validates and documents the bug
  2. Issue is assigned to the engineering team for root cause analysis
  3. A fix is developed and reviewed via our internal code review process
  4. The fix is tested in our test environment
  5. Deployment is scheduled and released
  6. You are notified once the fix is live

Communication During Bug Resolution:

We keep you informed throughout the process:
  1. An initial acknowledgement is sent upon bug confirmation
  2. If a workaround is available, we share it proactively while the fix is in development

Feature Requests

How We Collect and Evaluate Suggestions:

We welcome feature requests. Here is how the process works:
  1. Submit your request via the Community Forum, email, or in-app chat/feedback.
  2. Our product team reviews all suggestions on a monthly basis.
  3. Requests are evaluated based on user demand, strategic alignment, and technical feasibility.
  4. High-priority requests are added to our product roadmap.
How We Notify You About Feature Roll-Outs:
  1. Release notes published on our website and in-app notification centre.
  2. Email announcements for major feature launches.
  3. Community Forum posts with usage guides and tutorials.
  4. If you submitted a feature request, you receive a direct notification when it ships.

3.  Best Practices for Fast Resolution


Following these tips significantly reduces the time it takes to resolve your issue:
    ●  Provide a clear, detailed description - Avoid vague descriptions like "it doesn't work." Explain exactly what happened and under what circumstances.

    ●  Reproduce the issue before reporting - Walk through the steps that trigger the problem and document them precisely.

    ● Share logs or crash reports - These are invaluable for diagnosing root causes quickly. Ensure to enable these logs while submitting the feedback. 

    ● Keep communication within the same thread - Reply to the original ticket email rather than opening a new one for updates. This preserves context.

    ● Respond promptly to follow-up questions - Delayed responses pause the resolution clock.

4.  Additional Support Resources


Self-Service Options


Many issues can be resolved quickly using our self-service resources:
 

📚  Knowledge Base

Browse articles covering setup, troubleshooting, integrations, and account management.

❓  FAQs

 Answers to the most common questions, updated monthly.

🌐  Community Forum

Ask questions, share solutions, and connect with other users and our team.

Escalation Path

If your issue remains unresolved after going through standard support, use the following escalation path:
 
Step
Action
How to Trigger
1
Reopen existing ticket
Reply to your ticket confirmation email and request an update.
2
Engineering escalation
Your ticket is escalated automatically after 48h without resolution.


Info
Our goal is to resolve every issue efficiently and transparently. If you have feedback on our support process, we'd love to hear it - send your thoughts to support@zohonotebook.com. 

Happy Note-taking :)