App support and troubleshooting
On this page
Use Support to report an issue and keep its conversation, replies, and evidence together. Describe the task you were completing and the result you expected so Coryntas can identify where help is needed.
Before you begin: Access to the support request through your signed-in account or a valid guest link. Check evidence for secrets before attaching it.
Send a support request#
- Open Support and choose New request when a request list is present.
- When signed in, choose Request for: Personal for a request visible to you and Support, or Organization for one shared with the company's support contacts. Select the correct Organization when needed.
- Enter a subject that identifies the affected task, such as “Invoice PDF still preparing” or “Delivered agent access unavailable.”
- In How can we help?, describe what you expected, what happened, when it happened, the business impact, and any action that may already have completed.
- Include the agent, invoice, or workspace reference. For an organization request, use the optional Link an agent, workspace or order controls when helpful.
- Add relevant screenshots or files within the limits shown beside the attachment control.
- Review the request, then select Send request.
You should see: the new request and its conversation after successful submission. For guest support, follow the email access or recovery instructions shown on the public page; signing into a different account does not grant access to a guest conversation.
Share the evidence needed to investigate. Remove passwords, API keys, invitation tokens, and unrelated private information from attachments.
Follow replies and attachments#
Open the request to review its conversation and status. Attach evidence, wait for a ready upload, and send the reply. See Upload and resume attachments for file limits and interrupted uploads. Guests can use Recover access to a guest support request when their link expires.
Check common app problems#
| Problem | What to check first | Next step |
|---|---|---|
| Invitation expired or wrong account | Latest invitation email and the invited, verified address. | Use the correct account or ask the Owner to resend the invitation. |
| Billing or Members is missing | Selected company and company role. | Ask an Owner to review access. Billing requires Owner or Billing; Members requires Owner. |
| Agent list is empty | Selected company, filters, and whether you are a Member. | Clear filters. Members see delivered agents; ask the Owner about pending delivery. |
| Payment submitted but balance remains | Invoice evidence, verified payments, and the remaining amount. | Allow for verification and contact Support with the invoice and transaction reference before paying again. |
| Preparing PDF | Current invoice document state. | Refresh later; report the invoice reference if preparation remains unresolved. |
| Workspace connection status unknown | The delivered agent's access link and any workspace error. | Try the workspace link; report the result. A missing update alone does not prove the agent has stopped. |
| Credit allocation or return pending | Allocation status, workspace balance, and report update time. | Wait for workspace confirmation; report the affected allocation rather than submitting another one for the same need. |
| Company save conflict | Latest saved values and your draft. | Load the latest details, review overlapping edits, and save explicitly. |
Recover safely after a connection failure#
If a page read fails, use its retry action. If an order, payment-evidence submission, invitation, or credit action may have completed, check its resulting record before starting another request.
Keep the original tab available while the app resolves an uncertain submission. If sign-in is requested, sign in and review the page afterward; a failed write is not automatically resubmitted.
When you contact Support, state whether you have already transferred money, submitted evidence, or confirmed an action. Include the original reference and any partial result.
Provide a useful report#
Use this structure for the request description:
Task: what I was trying to complete.
Expected: the result I expected to see.
Actual: the message or result I saw.
Reference and time: the affected agent, invoice, or workspace; approximate time and timezone.
Impact: who is affected and whether work can continue.
Already tried: steps taken and whether an action may have completed.
For service response targets and help investigating agent output or connected-system behavior, see Troubleshooting and support.
Related guides#
Last updated on