Detailed answers for common sales, onboarding, migration, and support situations.
Which channel should we use for a live document or payment issue?+
Use WhatsApp first if active work is blocked and your team needs quick triage. If the issue needs screenshots, exports, or owner follow-through, send the same context by email as well.
What should we share before asking for migration help?+
Share source software name, file type, whether you want a new-firm import or existing-firm import, approximate data size, and whether duplicate review is expected for parties or items.
Can your team recover our data if we lose a backup passphrase?+
No. Recovery depends on the backup and its passphrase both being available. Support can guide the restore process, but it cannot reconstruct a lost backup secret.
How do we report a plan or feature-access mismatch?+
Send your plan name, invoice or payment reference if recent billing changed, the feature you expected, and the screen where the feature is blocked. We will verify entitlement state before suggesting next steps.
What helps most when PDF, print, or share behavior looks wrong?+
Share the document type, whether the issue is in preview, print, or share, a screenshot or sample PDF if possible, and the platform where it happened. Mention if the issue started after a recent update or settings change.
Do you promise real-time cloud sync support on the website?+
No. Public support and website wording stay within shipped behavior. We guide users on current release capabilities, rollout status, and safe workarounds only.
Who should contact support for migration or restore decisions?+
Owner or admin users should lead migration, restore, and role-sensitive requests because those workflows affect live firm data, duplicate decisions, and recovery planning.
What is the best way to escalate if our business is blocked?+
Use WhatsApp or email during support hours with the words "operations blocked", then include the affected firm, platform, last successful step, visible error, and whether a temporary workaround exists.