How communication, replies, and support are generally handled.

Last updated: April 2026

1. General purpose

Norvicka uses this page to set reasonable expectations around inquiries, communication, project updates, and post-delivery support. More specific expectations may apply if a paid engagement moves forward under written project terms.

2. Best first contact path

The guided intake is the preferred first step for project-related inquiries, because it creates a clearer starting point and makes it easier to understand the situation before deeper discussion begins. Direct email may still be used for simpler or more specific questions.

3. Inquiry review and response timing

Norvicka aims to review legitimate inquiries in a reasonable timeframe, but does not guarantee immediate responses, same-day replies, acceptance of every inquiry, or availability for every request. Response timing may vary depending on workload, project fit, complexity, and other active commitments.

4. No guaranteed availability or acceptance

Contacting Norvicka or submitting an intake does not guarantee project acceptance, scheduling, or service availability. Some inquiries may be outside scope, deferred, declined, or redirected if they are not a practical fit.

5. Communication expectations during a project

If a project moves forward, communication is expected to remain practical, reasonably timely, and tied to the agreed scope. Clear and consolidated feedback is strongly preferred over scattered or repeated revisions across multiple channels.

6. Client responsibilities

Clients are generally expected to provide required materials, approvals, corrections, and responses within a reasonable timeframe so work can move forward clearly. Delays in feedback, missing materials, or incomplete project information may affect schedule, scope, or project flow.

7. Support boundaries after delivery

Delivery of a project does not automatically include unlimited ongoing edits, indefinite support, or open-ended maintenance. If a support window is included, it is limited to the stated period or scope. Additional work, changes, or support beyond that may require a new scope or separate support arrangement.

8. Technical issues vs new requests

Norvicka may distinguish between a genuine delivery issue and a new change request. Fixing a confirmed issue related to agreed delivered work is different from adding new functionality, new copy, new pages, new integrations, or expanded scope after delivery.

9. Communication channels

Norvicka may use intake forms, email, structured follow-up messages, and other reasonable business communication channels to handle inquiries and project communication. Not every channel will necessarily be monitored equally or used as the primary support path.

10. Respectful and appropriate communication

Communication should remain respectful, lawful, and appropriate for a business setting. Norvicka may pause, decline, or stop communication where messages are abusive, misleading, threatening, spam-like, or otherwise inappropriate.

11. Changes to support expectations

These expectations may be updated over time as the site, workflows, legal requirements, or service structure evolve. The current version published on this page will be the controlling public version unless stated otherwise.

12. Contact

For general support, contact, or communication-expectation questions, you can email Norvicka directly using the address below.