Novu Handbook
    Logo

    The Open Source Notifications infrastructure For Developers

    GitHubXDiscord
    📖

    Support handbook

    💡
    This support handbook provides guidelines and procedures for delivering quality support to our community members and users.

    Guidelines

    • Always be nice, polite, and informative.
    • While providing help we should always get to the root cause of the issue.
    • While providing help we try to learn what problems members are trying to solve, to better our product, support, and overall service.
    • When providing technical support, try and be as precise and useful as can be.
    • Always follow up on issues, questions, and tickets.
    • Only if needed escalate to other team members. Escalation process takes longer, and have more risk of delivering a lower support quality.
    • Whenever possible convert issues, question into new pieces of knowledge.
    • Our FAQ section and Documentation are always available.
    • Strive to go over to video call to supply better support, and better guidance.
    • Discord is for all of our community support.
    • Intercom is intended cloud users, thus information there is focused around cloud based.
    • Roadmap is available on Novu’s Github.
    • Novu is a commercial is a commercial company, with both an Open Source project as well as a SaaS offering.
    • If asked about pricing, pricing page is available here, further questions can be directed to @Tomer Barnea or @Dima Grossman.

    Procedures

    ‣

    While providing help we should always get to the root cause of the issue

    • Is it in our onboarding?
    • Is it in our documentation?
    • How it’s being implemented?
    • Why are things failing?
    • Cloud version or self-hosted?
    ‣

    While providing help we try to learn what problems members are trying to solve, to better our product, support and over whole service.

    • What is being build? What features are being used?
    • What is the desired outcome?
    ‣

    When providing technical support, try and be as precise and useful as can be.

    • Share links to documentation. (https://docs.novu.co/)
    • Share links to API. (https://docs.novu.co/api/overview/)
    • Share code snippets.
    • Share screenshots or Loom videos with explanation.
    • Share dashboard snippets. (https://web.novu.co)
    ‣

    Questions roadmap, features, and potential problems?

    These questions are better answered by hopping on a call with @, @Dima Grossman, or @Tomer Barnea.

    • https://calendly.com/omer-novu/30min
    • https://calendly.com/grossman-dima/30min
    • https://calendly.com/novuhq/tomer-barnea-30
    ‣

    Questions about enterprise, commercial stuff?

    These questions and conversations are better answered by hopping on a call with @Dima Grossman or @Tomer Barnea.

    • https://calendly.com/novuhq/tomer-barnea-30
    • https://calendly.com/grossman-dima/30min

    Community Support Locations and tools

    ‣

    Discord

    Used by our whole community, both as a support channel, as well as a contribution path.

    ‣

    Intercom

    Used by our cloud users, not intended for community support, mostly to be able and filter issues as types, as we do assume this is for the cloud version. Similar to Discord technical support, but only relevant for cloud users.

    ‣

    GitHub

    Used by our contributors and users to add issues, and submit PRs. Make sure issues and PRs are moving along, assigned or if needed getting help from other team members.

    ‣

    Notion Documentation and notes

    Conversions about feature requests, issues, lack of documentation, and similar cases should be documented on internally, and when resolved the member should receive an updated.

    Back to ⁉️FAQs

    Go to No access