Tell it
Show Joyflow how your business works.
Add your services, tone, policies, notes, and repeat jobs so Joyflow has context before it starts.
How work gets done
Flow is what happens after you ask Joyflow for something. It gathers the context, gets the work ready, and comes back when it needs your input.
Example flow
How it works
You choose what Joyflow can use, see what it prepares, and step in before important actions happen.
Tell it
Add your services, tone, policies, notes, and repeat jobs so Joyflow has context before it starts.
Limit it
Connect your tools, then choose where Joyflow is allowed to use them. If an app is off, it stays off limits.
Ask it
Say what you want done. Joyflow gathers the background, prepares the next step, and shows its work.
Approve it
Emails, refunds, charges, publishing, and important record changes wait when Joyflow needs your input.
Set it up once
Add your services, voice, policies, and documents so replies sound right.
Pick which apps each channel can use. Everything else stays off limits.
Ask in plain language, or run a saved skill when the same job comes back.
Messages, refunds, and bigger changes wait for your sign-off.
Examples
Ask: Send the team a weekly revenue update.
Result: Joyflow checks the numbers, writes the recap, and gets the file ready.
Ask: Follow up with this account before Friday.
Result: Joyflow checks the account history, writes the email, and waits before sending.
Ask: Handle this refund if it matches our rules.
Result: Joyflow checks your refund rules, prepares the refund, and asks before it runs.
Execution path
Joyflow keeps the work moving without hiding the important parts. You can see what it used, what it prepared, and where your input was needed.
Use a chat or channel. Say what needs to happen in normal language.
It looks at the business details, saved jobs, and apps it is allowed to use.
That could be a draft, task, update, file, report, or next step.
If your input matters, Joyflow shows what it prepared before moving on.
Approve it, edit it, or reject it.
You can come back later and see what happened.
FAQ
Joyflow checks the context it has, uses only the apps you allowed, prepares the work, and asks when it needs your input. Afterward, you can see what happened.
A saved skill is a repeat job you do not want to rebuild every time. Think weekly recaps, invoice follow-ups, support triage, or any process your business runs again and again.
No. You can keep app access limited by workspace or channel. If an app is not allowed for that area, Joyflow does not use it there.