Client reports

Client reports are scheduled performance reports built from your Morse data, for one of your customers or for your own team. Build one, preview it and set its schedule and recipients here. Each report is generated from real data and waits for a person to approve it before anything is emailed.

Turning sending on

Sending is off until two switches are on:

Report sending for your account. Morse operates this switch. While it is off, every reports page says: “Report sending isn’t switched on yet. You can build, preview and schedule reports now. Nothing is generated or sent until sending is switched on, and each report waits for your approval.”
Send reports to this customer, in each customer’s settings on the Client reports page. It is off by default for every customer. Internal reports, which have no customer, use the same switch in Settings → Workspace.

Only an owner or admin can change the customer switch, each change is recorded in the audit log, and the switch can’t be changed in demo mode. Turning it on asks you to confirm: “Real email will be sent to this customer’s report recipients on each report’s schedule…”.

While a customer’s switch is off, that customer’s reports say why: “Sending is off for Northwind. Turn it on in the customer’s settings.” Internal reports say: “Sending is off for internal reports. Turn it on in the report settings for this workspace.” Turning a switch on later sends no backlog.

What you see

Client reports appear in the sidebar’s Reports group, as Client reports beside Weekly summary, only when reports are enabled for your organization (and in the demo workspace).

Reports list

/reports lists every report with Report, For (a customer, or Workspace for an internal report), Schedule, Next send, Recipients and Status. Filter by status (All, Active, Draft, Paused, Archived) or audience, or search reports and customers. Start from a template opens the builder with a template filled in.

Builder

New report opens a builder with six steps: Template, Audience & scope, Sections, Look, Schedule & recipients and Review. You can preview the report as you build it.

Report status

A report that is set up and active, while delivery is not live, reads Configured, delivery pending — never “Active” as if it would be sent. Its Next send reads Delivery pending, with “Nothing is sent yet”.

Next send and Last sent appear only when delivery is live: both switches are on, the report is active, and at least one recipient can still receive it. Then the tile shows the next send date and time with “last sent {date}” or “not sent yet”. A paused report reads Paused.

Approve then send

Every report run goes through the same steps: generating → awaiting approval → sending → sent, partial (some recipients received it, some did not) or failed.

Generate. An owner or admin generates a run from real data. Generating sends nothing.
Approve. Every generated run waits for an owner or admin to approve it. If delivery is not on, approval is refused: “Delivery is not on for this report, so nothing was sent. The run stays awaiting approval.”
Send. After approval, Morse emails each recipient. A recipient set to the PDF format gets the report attached; others get a link.

Approval is required by default. Only the organization owner can turn on automatic sending, and only after one approved run. Even then, a scheduled run is sent without a person only when its data is complete and nothing about the report has changed since it was approved. Changing the audience, customer, scope, sections, recipients or other content settings turns approval back on.

In the app today, a report’s Runs panel reads “No reports generated yet. Runs, approvals and delivery history will appear here.” The app doesn’t have controls to generate or approve a run yet; those steps exist in Morse’s API ahead of delivery launching.

Delivery status per recipient

Each run records every recipient’s delivery: queued, sent, failed, skipped or bounced, with up to three attempts. A recipient is skipped, with the reason, when they Unsubscribed, their Address bounced or reported spam, they are No longer permitted for this customer, or there is No address on file. A run reports how many were sent, failed (bounces included) and skipped.

Unsubscribe and suppression

Every report email ends with “You receive this report because you were added as a recipient. Unsubscribe.” The link opens a page in the Morse app asking “Stop receiving this report?” — nothing changes until the recipient selects Unsubscribe, so a mail scanner following the link can’t unsubscribe anyone. Afterwards it reads “You are unsubscribed”. Where the account is set up for it, the email also carries the one-click unsubscribe header that mail clients show next to the sender.

A permanent bounce or a spam complaint marks that delivery bounced and stops future sends to that address.

How to use it

Build a report from a template, preview it, and set its schedule and recipients — for example ops@example.com for an internal report.
Read Status: Configured, delivery pending means nothing will be sent yet.
Once delivery is on, approve each generated run before it goes out.

Before you have data

With no reports, the list offers Start from a template. While delivery is off, every page shows the notice above, and no report is generated or sent.

Home — the Weekly Summary, the other entry in the Reports group.
Executive summary — a fixed-period summary you can share as a PDF or link today.