Workspace & support / Troubleshooting
Get help with an Ariy setup or problem
Share enough context to make the next step clear, without exposing private information or repeating the whole story.
Last reviewed October 8, 2026
Editorial perspective: Ariy&Co · Product guidance
Start with your existing conversation
If you are already working with Ariy, reply in the existing setup or project conversation so the context stays together. For Front Desk configuration, you can also check your signed-in settings.
The help center does not create a support ticket just because you read this page. Keep any confirmation from the actual support conversation; do not assume a request was saved if an error appeared.
Include a small, useful problem report
Product and page URL: What I was trying to do: What I expected: What happened instead: Approximate time and time zone: Error text or reference, with private details removed: What I have already tried:
Share the minimum needed
Do not send passwords, API keys, calendar tokens, private recordings or entire customer transcripts in a public message. A redacted screenshot or exact error reference is often enough to start.
If the issue involves a payment, booking or publication with an unclear result, avoid repeating the action blindly. First check the existing confirmation or ask for the outcome to be verified.
Distinguish a problem from new implementation work
If you want a new connection or capability, describe the outcome you need and your current tools. That is a useful implementation brief even if the exact integration has not been built yet.
If an agreed feature is failing, keep the report focused on the expected behavior and evidence. The team can use that to identify whether a correction, setup change or separate implementation is needed.
Keep going
Prepare a useful help request, or continue your existing Ariy setup or project conversation. For Nia configuration, open your Front Desk settings.