▤Reports

Personalised PDF reports for each interim manager — created and sent at the push of a button. They summarise what has happened for the person concerned in the selected period.

The purpose is accountability: the recipient sees that work was done and on what, without anyone having to write it up by hand.

Enlarge

Sender profile and period at the top determine the sender and the content.

Without a sender profile, sending is blocked — this is not an error but the safeguard against a report going out without a recognisable sender.

When you put a new instance into operation, creating the sender profile is one of the first steps; otherwise it is noticed at exactly the moment the report is supposed to go out.

Yes, and you should always do so. “Preview” shows the finished PDF exactly as the recipient will get it.

The rule of thumb from the interface: look first, then send — “Send” really does send.

Via “Monthly batch sending”. It sends to everyone with an email address — with a dry run beforehand.

The number in the confirmation window is the number of real emails. Read it. It is the last check before a sending run that cannot be undone.

From the actual events in the system — contacts, activities, sending — not from estimates.

If a number in the report does not match your expectation, check the period first: it determines what goes into the report and is the most common cause of discrepancies.

Two maps of Germany that show where things are:

• Independent companies per location — companies are counted, not contact persons.
• Contact persons per location.

The assignment to a location works exactly via the postcode. That leads to the most common finding: if contacts are missing a postcode, they are missing from the map. After an import without an assigned postcode column, the map therefore stays empty even though there is data.

The maps are useful above all for territory discussions — they show blank spots faster than any table.

PDF generation is where fonts and layout are most likely to diverge. If you notice something — cut-off tables, wrongly displayed umlauts, overlapping lines — that makes for a good report, because it can be reproduced.

State in the report: which report, which period, and what exactly looks wrong. Ideally with the generated PDF.

When sending individually, the person you select; when batch sending, everyone with an email address.

That is exactly why the dry run before batch sending is not a formality: it shows how many there really are. The number in the confirmation window is the number of real emails.

The one you want to account for — usually the past month.

A longer period does not make the report more meaningful, only longer. And a report that shows the same window every month can be compared; one with a changing period cannot.

The structure is fixed; you control what goes into it via the sender profile and period.

If something is missing or there is too much, that makes for a good report — reports go to customers, and what is in them shapes the impression. Write in the report which detail is missing and what it is needed for.

Without a sender profile, sending is blocked. That is the most common cause and can be fixed in two minutes.

Other possibilities: no connected sender mailbox, protected sending mode (then nothing at all leaves the system) or a paused licence.

All three are shown on the overview in the line with system, licence and mailbox.

As a picture, not as statistics. A map answers in one second the question that a table cannot answer in ten minutes: where are we strong, and where is there nothing?

For a territory discussion, that is exactly the starting point. Bear in mind that the assignment works exactly via the postcode — an empty map almost always means that the postcode is missing from the contacts, not that there are no contacts there.