Every notification colobbo sends can be reworded, and you do it in one place: Settings → Notification, then the pencil on the row you want to change. Each channel — email, in-app, and text — has its own wording, and a live preview shows exactly what the recipient will get before you save.

This article covers editing. For what notifications exist and where they arrive, see How Notifications Work: Email, Reminders and the In-App Bell.

Changes apply to your whole organisation, not to one person. The tick boxes on the row decide who gets the message and on which channel; the pencil decides what it says.

Four separate pieces of wording, because a good email and a good text are not the same thing:

Click a personalisation token. The coloured pills above each field insert a placeholder such as {{woCode}} at your cursor. When the notification is sent, colobbo replaces it with the real value.

The pills differ per area — work order rows offer work order fields, booking rows offer booking fields. Common ones:

You can type a token by hand, but clicking the pill avoids typos — a misspelled token is left blank in the message rather than filled in.

The panel on the right shows your wording rendered as the recipient will see it, on all three channels at once — the branded email, the bell and push line, and the text on a phone. Sample values fill the tokens, so you are reading the shape of the message rather than real data.

Use it to catch the two things that are hard to spot in a form: an email that has become a wall of text, and a text message that has quietly grown into two messages.

Texts arrive from the sender name colobbo rather than a phone number, so they are recognisable in an inbox and cannot be replied to.

Three things to know when writing one:

10 texts per active user each month, capped at 200 free per organisation. A team of five has 50; a team of forty has 200 rather than 400. Your current usage is shown under Settings → Billing.

Email and in-app notifications are unlimited — the allowance applies to texts only.

A copy of the notification sent to an address of your choosing — typically a shared inbox such as [email protected], or somebody who needs visibility but does not use colobbo.

It is always sent, even when Email is switched off for Users and Team on that row. That is deliberate: it is how you keep a record in a shared inbox without emailing the whole field team. You can enter several addresses separated by commas.

Reminder rows have a Reminder Time field — the number of days ahead to send. Set it to 2 and the reminder goes out two days before the due date.

colobbo checks twice a day and sends one email per type of reminder, listing everything inside it with its own View link — so ten work orders due is a single email titled Work order reminders — 10 work orders, not ten emails. Work orders, schedules, bookings, actions due soon and actions overdue are each their own grouped email, so an overdue action is never buried in a list of things merely due.

The Child Work Order row at the bottom of the Work Order section is a single switch. It has no wording of its own — it uses the Work Order messages above and decides whether they are sent for child work orders at all.

It is off by default, and off means off — no email, no Notify To copy, no in-app notification and no text. This keeps a large job with many linked work orders from filling inboxes. Switch it on and child work orders behave like any other work order.

Yes. Each field has Reset to default, which restores colobbo's original wording for that field only — your other edits are left alone. If you leave the panel with unsaved changes you are asked whether to discard them or keep editing.

Either the token name is misspelled, or that record genuinely has no value for it — a work order with no supervisor leaves Supervisor empty. Click the pill rather than typing to rule out the first.

The counter under the text preview shows how many messages your wording produces. Shorten the text, or remove a token that expands to something long such as the address. Links are already shortened and are not usually the cause.

Yes. Notification wording is set for the whole organisation, not per person. The tick boxes on each row control who receives it.

Check that Text is ticked for Users or Team on that row, that the people involved have a valid mobile number on their profile, and that your monthly allowance has not run out under Settings → Billing.

How Notifications Work: Email, Reminders and the In-App Bell

Why do booking notifications say Customer and User?

A booking has two very different audiences, so the columns on those rows are named differently from everywhere else.

Everywhere else in this screen those two columns are Users and Team. On bookings they are renamed because "Users" would be misleading: the person who made the booking is not one of your users at all.

The two audiences do not receive the same email. Only the customer gets the buttons to reschedule, cancel or update the booking — those act on that one booking and belong to the person who made it. Your staff member gets the same booking details without those buttons.

Push notifications still read Users and Team, because a member of the public has no app to receive a push.

>