A member accepts the rules, posts in three channels, does everything the welcome flow asked for, and never gets the Member role. A server admin hit exactly this with a flow Q had built for them, and the bug was ours. A rule could not react to a role that another rule had just handed out, so a flow with several steps got through the first ones and went quiet. It now carries on to the end. Test it with a fresh account: a member who already finished the steps is not promoted after the fact, and if someone is stuck halfway, give them the last role by hand.
The other three changes this fortnight have the same shape. Something ended before the person got what they came for.
An application that ends with a time
On most servers the form is the easy part. Someone reads the answers, wants to talk to the applicant, and then spends three days of direct messages agreeing on a time, usually losing the person at “what is that in my timezone?”
Open a form response and choose Arrange interview. Offer up to eight times, or set one. The applicant gets a message from the bot with a link, sees your options in their own timezone, picks one, and the rest close. Reminders go out 24 hours and 1 hour before, to everyone involved.
Everything scheduled lands on one Calendar page, and nothing about it is specific to hiring. A review call or a staff meeting is the same thing with a different title. Ask Q to offer an applicant three times next week and it creates exactly what the button creates. It cannot move a confirmed meeting behind your back.
If the applicant has direct messages from server members switched off, the bot cannot deliver the link. Qreate says so right after you send, and the link is there to copy. Try it once with a test response before you rely on it.
A form that answers back
Someone spends ten minutes on their answers, presses submit, and gets a thank-you screen. A week later they are asked what they wrote.
Turn on the copy option in a form’s settings and anyone who signs in with Discord before submitting gets their answers as a direct message. If they filled the form in without signing in, or their direct messages are closed, the ending screen tells them there will be no copy. The submission is saved either way. Existing forms stay as they are until you switch it on.
Automations can now notice a specific status move on a response, to or from Accepted, say, and Q can list applicants, read an answer, change a status or add a staff note from chat. Q cannot delete a response, and that stays.
A chat you can leave
Setting up a server rarely happens in one sitting. You ask for a welcome flow, go and look at a channel in Discord, and come back to approve the greeting.
An ordinary chat request can now ask to keep going in the background. The chat tells you that you can leave only once the server has recorded the work, and Stop ends it on purpose. When you come back, you get the saved answer, or a plain note that the work was interrupted. We do not rerun an interrupted request on your behalf. Repeating work against a Discord server needs more care than restarting a spinner, so you decide, and Changes shows what was already applied.
A long conversation can start a new chat from a summary of what was asked, decided and changed. The summary is short rather than complete, you can edit it before sending, and the new chat links back to the old one. The channel picker also keeps a saved channel that has since gone missing visible, so Qreate never swaps in a different one for you.
The test is easy. Open a past chat and see whether you can tell what Q proposed, what was applied and what still needs you. If that is not clear, tell us.
