FAQ

Answers to common questions.

If you don’t see what you need, head to the knowledge base or contact support.

FAQ illustration
Quick answers for the most common requests.

General

  • How do I access my account?

    Use the login link in the header; password recovery is available from the login page.

  • Where are release updates?

    See the changelog and release notes in the Updates section.

  • How do I report an incident?

    Check system status first, then submit a request via Contact Support.

Product & billing

  • What products are available?

    Plexbook is available now; future products are listed on the roadmap.

  • How is billing handled?

    Plans are seat-based; billing questions are covered in the Billing & Invoices KB article.

  • Can I talk to sales?

    Yes—email sales or open a support request and we’ll route it.

When to contact support

  • Access blocked

    You’ve tried reset steps and still can’t sign in.

  • Billing mismatch

    An invoice looks incorrect after checking the billing KB.

  • Operational impact

    A workflow is blocked or degraded; include timestamps and impact.

Operational depth

Use FAQ content to remove repetitive uncertainty at high volume

FAQ sections should answer common policy and usage questions in plain operational language so responders can reference answers quickly.

Primary audience

End users, managers, and support queues handling repeat questions

Decision focus

Resolve routine questions without opening workflow-breaking support requests

Operational risk

Unclear FAQ answers push low-complexity questions into escalation channels

Field scenario

A team onboarding week generates repeated policy questions that should be resolved through reference content.

Execution walkthrough

  • 1. Frame the objective

    FAQ sections should answer common policy and usage questions in plain operational language so responders can reference answers quickly.

  • 2. Align participants

    End users, managers, and support queues handling repeat questions

  • 3. Validate the decision

    Resolve routine questions without opening workflow-breaking support requests

  • 4. Mitigate known risk

    Unclear FAQ answers push low-complexity questions into escalation channels

Interpretation matrix

Signal
Interpretation
Operational scenario
A team onboarding week generates repeated policy questions that should be resolved through reference content.
Successful outcome
Successful use of this page leaves teams with clear direction on Resolve routine questions without opening workflow-breaking support requests.
If skipped
Skipping this step often introduces Unclear FAQ answers push low-complexity questions into escalation channels.
Recommended next step
Route unresolved or account-specific cases to knowledge base or direct contact support.