How work gets done

Ask once.
Joyflow handles the steps.

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

Renewal follow-up

Ready
Check the account historyDone
Write the renewal emailDone
Wait before sendingNeeds you
Joyflow only uses apps you turned on.You can see what it is preparing.You can edit, approve, or reject the draft.Every finished job leaves a record.

How it works

Four simple checks
before work moves.

You choose what Joyflow can use, see what it prepares, and step in before important actions happen.

Tell it

Show Joyflow how your business works.

Add your services, tone, policies, notes, and repeat jobs so Joyflow has context before it starts.

Limit it

Pick the apps it can use.

Connect your tools, then choose where Joyflow is allowed to use them. If an app is off, it stays off limits.

Ask it

Ask for the outcome.

Say what you want done. Joyflow gathers the background, prepares the next step, and shows its work.

Approve it

Step in when it matters.

Emails, refunds, charges, publishing, and important record changes wait when Joyflow needs your input.

Set it up once

Teach Joyflow once. Reuse the job later.

Tell Joyflow about your business

Add your services, voice, policies, and documents so replies sound right.

Choose app access

Pick which apps each channel can use. Everything else stays off limits.

Ask for the work

Ask in plain language, or run a saved skill when the same job comes back.

Approve sensitive work

Messages, refunds, and bigger changes wait for your sign-off.

Examples

Real work, ready to review.

Weekly revenue recap

Ask: Send the team a weekly revenue update.

Result: Joyflow checks the numbers, writes the recap, and gets the file ready.

Customer renewal reply

Ask: Follow up with this account before Friday.

Result: Joyflow checks the account history, writes the email, and waits before sending.

Support refund review

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

From request to record.

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.

  1. 1

    You ask for the outcome

    Use a chat or channel. Say what needs to happen in normal language.

  2. 2

    Joyflow checks the right context

    It looks at the business details, saved jobs, and apps it is allowed to use.

  3. 3

    It prepares the work

    That could be a draft, task, update, file, report, or next step.

  4. 4

    It pauses when it needs you

    If your input matters, Joyflow shows what it prepared before moving on.

  5. 5

    You decide

    Approve it, edit it, or reject it.

  6. 6

    The record stays behind

    You can come back later and see what happened.

FAQ

What people usually ask.

What happens after I send a request?

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.

What is a saved skill in Joyflow?

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.

Can Joyflow use every connected app everywhere?

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.