Have you encountered a problem on the platform? Please let us know—every piece of feedback helps us improve Deeplink.ai.
Send an email to support@deeplink.ai. A ticket will be automatically created for you with a tracking number. For any follow-up correspondence, please reply to the same email so that all communications remain in one place.
The SAR Method
Pour qu’on puisse reproduire et corriger le problème rapidement :
- Screen — Where were you in the app? (e.g., Studio, Events, a specific chatbot, the PV feature, Translator…)
- Action — What did you do, step by step? (e.g., “I clicked on X, then entered Y, then submitted”)
- Result — What happened? And what did you expect to happen?
What Really Helps Us
- Relevant content — paste the text causing the problem rather than just a screenshot
- Screenshots or videos — welcome, especially if the error is visual
- Browser console (optional, for those who are comfortable with it) — open the developer tools (F12) → Console or Network tab, and attach a screenshot of the errors displayed
- Your environment (optional)—PC or Mac, and the browser you’re using (Chrome, Firefox, Safari…)
Example of a Good Report
General description: The page reloaded unexpectedly, and nothing happened—no response was generated, as if my request had been ignored.
Screen: Studio
Action: I opened a new conversation, pasted a 3-page text into the input field, and then clicked “Send.” The page reloaded automatically after a few seconds.
Result: No response was generated. I was expecting a summary of the document. The issue occurs every time I try this with this text.
Attachments: screenshot of the page after it reloaded + the pasted text as an attachment
The more detailed your description is, the faster we can take action. Thank you.
Requests for Changes
Is your request regarding an improvement or a new feature? Please contact your account manager or project manager rather than support.
In addition to describing the desired feature, please provide context by explaining how it relates to aspects of your business or organization that would be affected: What specific problem does it solve? Which users would be affected? In what context or process does this change fit?
The more the need is rooted in a real-world use case, the better we can evaluate it and prioritize it in our roadmap.