Necora

Customer support

Operational help from people who know PodIQ™.

Contact the Necora team for product questions, access issues, integration troubleshooting, or help interpreting an incident. Jira Service Management keeps each request, response, timestamp, and status together through resolution. Email is available as a fallback channel.

Support portal

Sign in to our Jira Service Management portal to open and track a request. Your submission, our responses, timestamps, and status stay in one ticket through resolution.

Sign in to support portal

Email

Email us if you need portal access or your question needs more context or attachments. Email replies remain in the original thread; use the support portal for a status-tracked ticket.

info@necora.io

Current support standard

What to expect after you contact us.

We aim to acknowledge support requests within one business day. This is our current operating target, not a contractual service level. Customer agreements take precedence where applicable.

  1. 01

    Request received

    Jira Service Management records the request and submission time. Email retains the original message timestamp.

  2. 02

    Triage and response

    A team member reviews the request, asks for any missing context, and shares the next action or resolution.

  3. 03

    Updates tracked

    Jira replies, agent actions, and status changes remain with the original ticket. Email follow-ups stay in the original thread.

  4. 04

    Resolution confirmed

    We summarize the outcome, then close the Jira ticket or confirm resolution in the final email reply.

Troubleshooting

Common questions before you open a request.

I can’t sign in. What should I check?

Confirm that you are using your work email and the correct PodIQ workspace URL. Retry the password-reset flow, then contact us with the time of the attempt and the error shown if access is still blocked.

A dashboard or alert is not updating. What should I send?

Refresh the page once and note whether other views are updating. If the issue continues, send the affected workspace or facility, the approximate start time, the page or alert ID, and a screenshot with sensitive data removed.

An integration appears to have stopped sending data.

Check whether the source system is reachable and note the last known successful update. Send us the integration type, affected data source, relevant timestamps, and any sanitized error message. Never include passwords, API keys, or access tokens.

How do I question a recommendation or incident analysis?

Share the recommendation or incident ID, the facility context, and what you expected to see. Our team will review the underlying signals and reasoning, explain the outcome, and track any required correction through resolution.

Help us resolve your request safely.

Include relevant timestamps, the affected page or integration, the expected behavior, and a sanitized screenshot when useful. Do not send passwords, API keys, access tokens, private keys, or other secrets through the support portal or email.

Support process current as of August 26, 2026