Falconry Support gives authorised client teams a clear route for usage questions, configuration issues, incidents, integrations, data problems and agreed change requests—so the right need reaches the right owner quickly.
Separate usage, incidents, configuration and change.
Capture impact, evidence and reproduction context.
Retain status, resolution and escalation history.
Clear classification improves triage, ownership and resolution—and keeps support, enhancement and advisory work from becoming blurred together.
How do I complete a task or use an existing configured capability?
Why is an existing field, permission, approval, notification or workflow behaving this way?
A platform function is unavailable, failing or behaving differently from its intended design.
A source-system exchange, mapped record or governed dataset is incomplete, delayed or inconsistent.
The client wants new functionality, workflow logic, configuration, reporting or integration scope.
The need is methodological, regulatory or operating-model advice rather than product support.
Good support starts with the right classification, enough diagnostic context, clear ownership and visible status. The request history should show what happened, what was changed and how closure was confirmed.
Record business impact, affected workflow, user, record, time, evidence and expected versus actual behaviour.
Classify the request and direct it to support, technical, success or advisory ownership.
Diagnose, coordinate dependencies and provide meaningful progress updates.
Confirm resolution, reconcile affected records where relevant and retain the closure history.
Identify who is affected, what cannot be completed and whether a governance deadline is at risk.
Capture the steps, record, screen, user context, time and expected versus actual behaviour.
Identify the relevant entity, module, integration, workflow or permission context.
Explain why the request is urgent or materially affecting operations rather than relying on a label alone.
Provide approved screenshots, references or technical information that helps reproduce and isolate the issue.
Confirm the user outcome and any required data reconciliation before the request is considered closed.
A scheduled ERP exchange stops updating control evidence. The request is classified as an integration issue, the last successful run and affected records are identified, technical investigation is coordinated, the client receives progress updates and data is reconciled before closure.
© 2026 Falconry360. All rights reserved.
Falconry360 is operated by Falconry Ltd and its affiliates, as applicable.