Quick answer
Contact Logentic from the channel that best matches the urgency and context. Use in-app chat when you are already working in Logentic, email when you need to send detailed evidence, and your shared Slack support channel when your team already uses one with Logentic.
Choose the right support path
Situation | Best path | What to include |
A live warehouse, launch, shipping, receiving, or order blocker | Use in-app chat or your agreed urgent support path. | Order, SKU, PO, shipment, warehouse, screenshot, what you expected, and what happened. |
A detailed bug report with screenshots or a recording | Email support@getlogentic.com. | Steps to reproduce, expected result, actual result, affected workflow, and priority. |
A quick question while you are signed in | Open Logentic and use in-app chat. | The screen you are on, the goal, and anything you already tried. |
A feature request or workflow improvement | Send it by email, in-app chat, or your shared Slack support channel. | The customer problem, current workaround, desired outcome, and business impact. |
Before you contact us
Check whether the article for the workflow answers the question or gives the next safe action.
Keep passwords, API keys, card details, customer addresses, and private tokens out of screenshots and recordings.
Mask private customer data unless it is required for Logentic to investigate the issue.
Send us this information
For blocked workflows, use What information should I send support when something is blocked?.
Workspace, brand, warehouse, or account context.
Order ID, SKU, PO number, shipment, tracking number, or other relevant identifier.
Screenshot or short recording of the exact blocker.
Expected result and actual result.
Time, timezone, user role, filters, and page context when relevant.
Feature requests
Tell us what outcome you are trying to improve, what slows the team down today, and how often the problem happens. We use that context to route the request into product review without asking you to repeat the same details later.
What happens next
Support requests are reviewed by the Logentic team and routed to the right owner.
Credible bugs and feature requests may be linked to product work so the customer evidence stays attached.
We will avoid promising timing, carrier outcomes, billing decisions, or roadmap behavior until the owner has reviewed the request.