Something appeared on my list that nobody typed. What is it?

Either a flow created it — those carry a Flow badge — or the product raised it because something needed a person: a card payment disputed by the client's bank, or a cancellation fee that couldn't be collected. Read the notes; they say which.

Why does a chargeback become a task rather than a notification?

Because it has a deadline and somebody has to act on it. A notification is read once and gone; a task sits on the list until it's done, which is what a thing with a deadline needs.

Can I stop the product creating tasks?

Not for chargebacks or uncollected fees — those exist precisely because losing them silently costs you money. Flow-created tasks are yours: they come from a step you added, and removing the step stops them.

How do I tell a product-raised task from one a colleague typed?

By reading it. Only flow-created tasks are badged; a chargeback or a fee task looks like any other row until you read its notes, which are written by the product and say so.

Can I make a task about a particular client?

Not by hand. The client's name shows on rows where there is one, but the New task dialog has no client field — a task gets attached to a client only when a flow or the product raises it. Name them in the title instead.

The same problem happened twice. Will I get two tasks?

No. Both product-raised kinds are deduplicated against what caused them, so a retried charge or a repeated notification from Stripe won't pile up copies.

Where tasks come from

Most of your list is things somebody wrote down. Some of it isn't, and those rows are usually the important ones.

Four things create a task in RewireBox.

Somebody types it

New task on the Tasks screen. This is most of the list, and it's covered in Your task list.

A flow creates one

A flow can include a Create task step, so a rule you set up once produces a task every time it fires — "a client hasn't been in for four months" becoming Call Priya about her colour correction, with her actual name in it.

These are the only tasks that carry a badge. You'll see a small Flow label on the row, which is your cue that a rule made it rather than a colleague. They arrive unassigned, and they carry the client they're about.

A client disputes a card payment

When a client's bank disputes a payment, the product raises a task about it.

A single task card reading Chargeback: respond to a $45.00 disputed payment, with a paragraph beneath naming the sale number, the dispute reason, the deadline to respond in Stripe and what evidence to use. — Nobody typed this one. Everything you need to answer it is in the notes.

This is the one worth reading carefully, because the notes are the job. They carry the amount, the reason the bank gave, the sale number, the fact that you respond in Stripe rather than here, and — the part people miss — what counts as evidence when the disputed payment was a cancellation fee: the policy the client accepted at booking, with the time it was accepted, the reminders you sent, and the absence of any cancellation.

That paragraph exists because somebody has a deadline and needs to know what to gather before it passes. A one-line "you have a chargeback" would tell you the bad news and nothing you could act on.

A cancellation fee doesn't collect

Two versions, and both mean money is sitting uncollected:

The card was declined. You charged a late-cancellation or no-show fee to the card on file and it didn't go through. The task carries the amount, the decline reason, and the fact that the fee is waiting as an open sale for you to take another way.
It couldn't be recorded automatically. The appointment already had an open sale on it — a checkout somebody started — so the fee had nowhere to go. The task tells you to add it to that sale by hand.

Neither of these is an error message. They're the product refusing to lose your money quietly: without the task, a declined fee would be a line in a log nobody reads.

Reading a task you didn't write

Two habits make these useful rather than alarming.

Read the notes before deciding what it is. The title is a summary; the notes are the instruction, and on a product-raised task they were written to be acted on. This is the one place on the list where the second line matters more than the first.

Don't delete one to make it go away. Delete is permanent, and the underlying thing — a disputed payment, an uncollected fee — carries on being true. Complete it when it's actually handled.