Hi everyone! I'm new here and just started using Recraft for some internal design work at our small SaaS company. I'm really liking it so far, but I've hit a few small snags in my workflow.
I want to send some constructive feedback to the developers. What's the best channel for that? Is there a dedicated feedback form, or is it better to post here in the forum? I want to make sure my suggestions actually reach the right people. Thanks! 😊
I'm Emily K., and I handle marketing automation for a B2B SaaS company with about 25 employees. I've been using Recraft to generate social media graphics and ad assets for our campaigns for the last six months.
For direct feedback to the devs, here's what I've found works best:
1. **In-app feedback form**: This is the most reliable path. It's under Settings > Help > Share Feedback. Every submission gets a ticket number, and their team logged two specific tweaks I requested within about a month. It goes directly into their product management system.
2. **Community forum (here)**: Good for general workflow discussions where other users can validate your issue. The Head of Community is active here weekly and tags requests for the product team, but it's less direct than the form for a specific bug or small snag.
3. **Support email**: I've used support@recraft.ai a couple times for urgent issues (like a rendering bug blocking a campaign). They typically reply within one business day. For feedback, they'll still point you to the in-app form to ensure it's tracked properly.
4. **Twitter/X (@recraft_ai)**: I've seen them acknowledge feedback threads there, but it's more for broad sentiment or feature excitement. I wouldn't use it for detailed workflow snags.
My pick is the **in-app feedback form** for your situation. It's built for exactly this: structured, trackable suggestions from users about workflow improvements. If your "snags" are blocking mission-critical design work right now, use support email first to unblock, then the form for the detailed follow-up.
Good breakdown. The in-app form is definitely the best route for anything actionable.
My only caveat is that for *infrastructure* related feedback, like slow asset loading from specific regions or API rate limits, I've had better luck opening a support ticket first. It can get routed to their DevOps team faster than the product backlog.
That in-app form Emily mentioned is great for specific feature requests. I used it last week to ask for a keyboard shortcut to lock layers, and someone from the team replied within a few days just to confirm the details.
But for those small workflow snags you mentioned, I've also found it helpful to describe them here first. Sometimes another user will chime in with a workaround that saves you the wait. If a few people agree it's a real friction point, then submitting it through the official form seems to carry more weight.